DIGI O3 Gap Analysis
Questions/Concerns/Gaps for Discussion:
- ___
Gap Analysis
Legend
Gap Status: READY TO CONFIG GAP
Gap Priority: LOW MEDIUM HIGH
Note: Any OMRS tickets identified/created in this process should be labelled with the org or product name (e.g. "pih" or "kenyaemr")
| Theme | Feature | Current or DESIRED State | Future State (with 3.x) | Status | Priority | Customer | Notes/Comments |
|---|---|---|---|---|---|---|---|
| Forms | 12 Forms | TO CONFIG | Adequately covered by current O3 Form Engine (Angular) - docs here: https://ampath-forms.vercel.app/docs/quickstart | ||||
| Chart | Patient History Info | TO CONFIG | If you need custom widgets e.g. show surgical history - could use esm-template-widget and just change the concepts  | ||||
| General | Security Audit | GAP | |||||
| Home | Appointments | Bahmni Appointments - Appointments is the landing page in the system | TO CONFIG | SGS | Appointments v2 Feature Squad What setup/config do they currently use? | ||
| Patient-Facing | Patient Qnr | SMS Link to pt - "sent to phone # xyz at time abc". Pt clicks unique URL. Pt-facing self-reporting form, with photo. Then that form populates pt-facing encounter. | GAP | ||||
| CDS | CDS | Logic: If any of X or Y is triggered, trigger notification process. Way to parse for actionable items. | GAP | ||||
| Analytics | FHIR Analytics | FHIR analytics pipeline coming packaged; pre-packaged way to send FHIR resources locally or centralized; point at whatever - something that listens and builds encounters into FHIR objects and manages their queuing somehow out into the wider world, or be consumed by an ETL layer | GAP | CI | |||
| Integration | FHIR IPS for Pt History | Pull down FHIR objects from a central server to pull down an IPS (eg embed a lot of the HTML in there) (Would have to be tagged in some way for user to see when it was last updated) | GAP | CI |
Legend
Gap Status: READY TO CONFIG GAP
Gap Priority: LOW MEDIUM HIGH
Link to Jira Issues for Gaps