iSantePlus vs 3.x Demo: Gap Analysis

Participants involved creating this Gap Analysis:

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. 

Next Steps

  • Initial Gap Analysis
    • 2022-01-27 session - First session: Sample workflow walkthrough
    • 2022-02-03 session - Second session: Sample 3.x workflow walkthrough
    • 2022-02-10 session - continue 3.x workflow with sample patient flow
    • ____ - I.d. Gaps and add Priority levels for gaps
    • Confirm: Any role-based customization? (e.g. Nurse can only see X, Clinician, etc; certain people can only see certain forms?)
    • Look at sample Test Results
    • OCL and OMRS (Maxy talking to PIH)
  • Dev Onboarding & Capacity Building planning
    • Mozzy & Piotr to set up 3.x frontend on existing DB (cc Xina, Rony, Jan, Kemar & Maxy)
    • Peer support options
  • ID a first project
  • ID a pilot goal / scope


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"

ThemeFeatureCurrent State in iSantePlusFuture State (with 3.x)StatusPriorityNotes/Comments


Flows: 
  • Must create Visit to create Encounters. No defined visit "types". 
  • Each form = an Encounter
  • Multiple forms/encounters can be included in a Visit
  • Enrollment not so much used in iSantePlus. 
  • Gender & Age configures the fields in the form (e.g. don't ask men if pregnant)






READY



HomeHome page

READY




Pt Search


READY




Pt Dashboard

Patient Flags for Pt Alerts:

  • Missed Appointment

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 registrationAdaptation 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

Link to Jira Issues for Gaps

key summary type created updated due assignee reporter priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.