Info

icon	false
title	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.

Info

icon	false
title	Reference Demos (videos or demo environments)

Info

icon	false
title	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

Info

Scope Ideas for first use case

Pt Registration

Note

title	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

Info

title	Legend

Gap Status:

Status

colour	Green
title	Ready

Status


colour	Yellow
title	To Config

Status


colour	Red
title	Gap

Gap Priority:

Status


colour	Green
title	LOW

Status


colour	Yellow
title	Medium

Status


colour	Red
title	High

Note
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:

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)

Status

colour	Green
title	Ready

Home

Home page

Status

colour	Green
title	Ready

Pt Search

Status

colour	Green
title	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.

Status


colour	Red
title	Gap

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.

Status


colour	Red
title	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

Status


colour	Yellow
title	To Config

Fingerprint

Status


colour	Red
title	Gap

Registration Summary

Used after registering to edit pt information

Status

colour	Green
title	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

Status


colour	Red
title	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)

Status


colour	Red
title	Gap

GAP

Reports

Status

colour	Green
title	Ready

(no change)

Shows any problems with outgoing data

Status

colour	Green
title	Ready

(no change)

Status


colour	Yellow
title	To Config

Status


colour	Yellow
title	To Config

Vaccinations

Status


colour	Red
title	Gap

GAP

Growth Chart

Status


colour	Red
title	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.

Status


colour	Yellow
title	To Config

Labs

Lab History:

Separate Viral Load History:

Status


colour	Yellow
title	To Config

Medication Orders

Rx Form

Status


colour	Yellow
title	To Config

Med History

Status


colour	Red
title	Gap

Clinicians review Forms history when seeing pt to see what has happened in pt's past

Status

colour	Green
title	Ready

Pt Summary

Users use dashboard to review case.

Status


colour	Red
title	Gap

Diagnosis History

Gap Status:

Status

colour	Green
title	Ready

Status


colour	Yellow
title	To Config

Status


colour	Red
title	Gap

Gap Priority:

Status


colour	Green
title	LOW

Status


colour	Yellow
title	Medium

Status


colour	Red
title	High

Link to Jira Issues for Gaps

Jira Legacy

server	OpenMRS Issues
columnIds	issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues	20
jqlQuery	labels = isanteplus AND resolution = unresolved
serverId	45c5771b-fa4b-3e43-b34a-c19dc45ccc95

Versions Compared

Old Version 21

New Version Current

Key

Gap Analysis

Link to Jira Issues for Gaps

Page Comparison

Versions Compared

Old Version 21

New Version Current

Key

Gap Analysis

Link to Jira Issues for Gaps