iSantePlus vs 3.x Demo: Gap Analysis
Participants involved creating this Gap Analysis:
Kemar Celestin, @Dupuy Rony Charles, @Jean Daboul MAXY Max @Christina White, @Jan Flowers, @Jennifer Antilla, @Grace Potma
Currently already working to switch sites from iSante to iSantePlus. (Workflow modifications; iSante wasn't OMRS based). (~150 sites; 64 sites using plus; 23 switching in March; 100 sites using iSantePlus by Feb end)
Users' reactions to the changes: Not that hard. If already familiar w iSante, really easy to switch. Rare complaints. 2-3 days of in person training with them, then they call for assistance as needed. Complaints more often about "we used to have this, now we don't". Or it was there, they just couldn't find it.
Reference Demos (videos or demo environments)
Next Steps
New Work Item: Emergency Functionality (ER & Inpatient)
CDC Haiti has added resources into TAP to do this with CHARESS. Scope not yet totally clear.
Current CHARESS priority is the rollout of iSantePlus. Some new dev'mpt assistance from
Scope Ideas for first use case
Pt Registration
Major Questions/Concerns/Gaps for Discussion:
iSantePlus Core version = v1.9.2-3
Accompaniment Support: Small Haitian group ~20 ppl interested in building something on O3. How can they market what they're doing? Peers to join with?
Viewing permissions: e.g. only allow limited version of Patient Summary for someone in Lab? eg **** over certain info? eg Social Worker not able to see Diagnosis History? eg Not want Archivist to see HIV +?
HFE
+++ test rigor in place in existing iSantePlus including for integrations - would want that in place
Performance: how does it compare to 2.x?
Portable Performance: responsiveness across Desktop and Tablet. E.g. 1 computer on ward, plus tablet(s) nurses can work around with.
General need for tablets: Seeing trend of health facilities that would like to expand the scope that OMRS operates in - different service lines. Buying laptops, desktops etc is expenseive, they get stolen. Increasingly thinking "how do we expand scope in a clinic and still have some budget/hardware limits" (esp CDC/MOHs). In some places, seeing clinicians can be more accepting of using EMR if using tablet; easier to move around in hospital where mobile btwn patient stations; cheaper.
Haiti: Going to need iSantePlus available for tablets. 3.x as huge opportunity b/c have wanted to use system using tablet. Expands ability to serve inpatient settings.
Performance on unstable network environment
Some sites don't have good connection. Those that do, can update remotely. But still have local server in case of downtime.
Performance: Time to load → where is this documented? How can I compare to what we have? Is everything frontloaded? What's cached?
Browser uses ++ memory → unideal for phones
What will we be able to do w/ 3.x? Technical benefits may be clear for technical team, but need the benefits to be clear for the stakeholders too → ways to communicate that
Possible to import Angular or Vue applications
e.g. could current devs build a widget in Angular
AngularJS deprecation - iding path of least resistance
Gap Analysis
Legend
Gap Status: Ready To Config Gap
Gap Priority: LOW Medium High
Note: Any tickets identified/created in this process should be labelled "isanteplus"
Theme | Feature | Current State in iSantePlus | Future State (with 3.x) | Status | Priority | Notes/Comments |
|---|---|---|---|---|---|---|
|
| Flows:
|
|
|
|
|
|
|  |   | Ready |
|
|
Home | Home page |  |  | Ready |
|
|
| Pt Search |  |
| Ready |
|
|
| Pt Dashboard |  Patient Flags for Pt Alerts:
Permissioning: Based on permissions granted to the user, only certain actions possible. Archivist or Receptionist example: After creating patient, can go to pt dashboard, but can only see some things.
|
 | Gap | Patient Flags |
|
| Patient Flags |
| Where would "missed appointment" & other flags go? → Expect to see at top of patient chart, not necessarily in Header, but at top of patient summary. | Gap | GAP & NICE 3.x IDEA → see timeline idea |
|
| Vital Signs |
|   
|
| Can't save vitals form Vitals Form buggy:  Grey'd out not clear why  |
|
| Registration |  |
| To Config |
|
|
|
| Fingerprint  |
| Gap |
|
|
| Registration Summary | Used after registering to edit pt information  |    | Ready | BUG Clicking "Cancel" in Edit form brings you back home instead of into pt chart  Chan't save pt edits; get null message |
|
| Address Hierarchy |
|
| Gap | GAP |
|
| Fingerprint registration | Adaptation of a fingerprint in core modules AND integration with M2Sys (app that captures the print and provides an additional unique Identifier) |
| Gap | GAP |
|
|
| Reports  |
| Ready (no change) |
|
|
|
|  Shows any problems with outgoing data  |
| Ready (no change) |
|
|
|
|   |
| To Config |
|
|
|
| 
|
| To Config |
|
|
| Vaccinations |  |
| Gap | GAP |
|
| Growth Chart |  |
| Gap |
|
|
| Lab Orders | Done through Lab Order form:  Large effort to mimic the paper form structure - most important when first adopting system. Along the way, modified a bit to have more electronic-friendly functionality. But recognition that designing just like paper form can even be annoying for Point of Care use.  |
| To Config |
|
|
| Labs |
Lab History:  |
|
|
|
|
|
| Separate Viral Load History:  |
| To Config |
|
|
| Medication Orders | Rx Form   |
| To Config |
|
|
| Med History |  |
| Gap |
|
|
|
| Clinicians review Forms history when seeing pt to see what has happened in pt's past  |
| Ready |
|
|
| Pt Summary | Users use dashboard to review case.  |
| Gap |
|
|
| Diagnosis History |
|
|
|
|
|
Gap Status: Ready To Config Gap
Gap Priority: LOW Medium High