MFE - Proof of concept release

Slack channel for PoC release here.

Test environment here: MFE test environment.

Background 

The goal is to create a packaged release to prove the feasibility of MFE from an implementation perspective. 

This is not a production use case, this is a way to get the community excited about this framework and to prove that it works and to get some learnings on how to better secure adoption in the future. The idea is not for the implementation to replace the existing solution (yet) but to get the MFE to work alongside with the current applications. 

The main focus of this POC is not the end-user but the implementer. The main goal is to gain momentum around OpenMRS 3.0 and commit to releasing more often.  We will not create fixes to back-releases (e.g. bug in 2.0→ fix goes out in next release; patches for emergencies) - because patches can dis-incentivize people from moving off of old versions. 

Steps

• v0 - 3.0 Frontend Technical Vision Alignment
  • Draft - Done
  • Present to Bahmni Coalition - July 30
  • Present to Bahmni PAT - ____
  • Share with Community - Early Aug, before Aug 13 Squad Showcase
• v1 - Login, Search, Homepage, Registration
  • Trial period among PIH, AMPATH, Mekom with current set-up - using OMRS Spa Module - Goal: End of August
  • Workshop for community on how to set up for your site - Early Sept?
  • Trial with more champions - Late Sept?
    • Define and select the ideal candidate (early adopter) from an implementation perspective (potentially Ampath and PIH)
    • Find out what's the bare minimum that we need from an architecture & metadata perspective (shall we consider dockerization best practices?)
• v2 - Patient Chart: ______

HIV Clinic Workflow

Step	User	Description	Why	Part of AMRS POC needed	Part of MFE Proof of Concept MVP scope?
Patient check-in	Registration clerk	Patient checks-in and issues clinic card at the registration desk. Patient is searched either by name or identifier indicated on the card.	Ensure that the patient is well identified and add relationships (in case they have any - e.g. a spouse). It is also at this point that the patient contacts are verified/updated.
Start Visit	Registration clerk	After patient search, today's visit is started by the registration clerk in the HIV Program that the patient is enrolled into e.g. HIV standard program. Patient is then sent to the triage nurse's desk.	By starting the visit, the patient is marked as checked-in
Triage	Nurse	Patient is triaged by capturing the vitals which are filled in a triage form within the visit that was started. Vitals captured are: BP, Pulse, RR, Temp, Weight, Height, Sp02, BMI (Auto calculated from weights vs height), MUAC. Patient is then sent to the Clinicians desk.	To find out if the patient is suffering from any other ailments e.g. high blood pressure.
View HIV summary	Clinician	Patient is reviewed by the clinician where they first get a review of the patient HIV summary and today's' vitals which are displayed below the patient header.	View historical medications that the patient is taking from the summary. Check patient adherence to medications.
View clinical notes	Clinician	Clinician reviews the clinical notes of the patient which is accessible on the side drawer menu within the HIV program.	View previous notes that a clinician/nurse had written about the patient that might need action.
View historical lab results	Clinician	Clinician reviews historical lab data results of the patient. This can go up to the date the patient was enrolled into HIV care. The most recent results will display on the first column.	Check if the patient is responding well to the medications administered by lowering their viral load and improving their immunity (CD4 count)
View lab orders	Clinician	Check to see if the patient has had any blood works ordered recently and if there is any pending lab orders whose results have not been received yet.	To determine whether to order a new test as required by the HIV guidelines.
Fill clinical encounter	Clinician	The clinician will then open a return clinical encounter which they would fill by asking the patient a number of specific questions that have been coded in the form. NB: Its also within the clinical encounter that medication orders, test orders and appointments are captured.	Patient is reviewed and clinical judgements made for the patient e.g. changing medications if they are not responding well to the current meds. By filling the clinical encounter, a number of concepts are captured in the form which are used for reporting purposes.
Order medications	Clinician	Medications are ordered on the form in the medication history page. There is a use value button (to use previous values) in case the current medication orders are not changing to a new one. We are currently capturing the orders through the form and the concepts are saved as observations	Capture the regimen of anti-retrovirals, PCP and TB medications  that the patient is currently taking.
Indicate medication plan	Clinician	On the plan section, the clinician will indicate whether the regimen is a continuation, change, restart.....etc A prescription form is then written (hard copy) that is given to the patient to present at the pharmacy.	Capture any changes or continuation of the medications that the patient is taking.
Order for tests	Clinician	The test orders are made on the Plan page under Test Orders section. Upon saving the form, an order number will be generated that is used to track the test results from the AMPATH lab system. The results are synced into POC automatically. The patient is issued with a lab order form with the order number that will be presented to the phlebotomist.	Record any tests that the patient is supposed to undergo on their current visit. This helps in tracking the results from the lab system.
Give appointments	Clinician	The patient is given next visit appointment in the appointments section under the plan page. Since HIV clinics are quite busy at AMPATH a calendar is displayed after choosing the appointment date to display distribution of appointments through the week of the date selected. Patient is then sent to the pharmacy to pick drugs and/or the lab to get pricked if they have any blood work orders.	Capture appointments and help in tracing a patient in case they miss their appointment date. Appointments are displayed on the appointments schedule.
Draw test samples	Phlebotomist	The phlebotomist will receive the order number and key it into POC and indicate the date the sample was received after pricking the patient. They will also record the sample type extracted and post the order which shall be reflected in the AMPATH lab system as received.	Confirm the sample as received since not all patients that are sent to the phlebotomist actually go there. Some decide to go to the pharmacy and leave.
Dispense medications	Pharmacist	The patient will finally go to the pharmacy and present the prescription form which is recorded in the pharmacy system and patient issued with medications for the period indicated. First they will look up the patient in the pharmacy system (ADT) by searching their names	Find the correct patient in ADT
Dispense medications	Pharmacist	After finding the correct patient they would dispense the medications indicated on the prescription.	Ensure that they dispense the correct medications in ADT.

Tiny Clinic Workflow

These workflows relate to the rural clinics operated by PIH Mexico, which are staffed by one doctor, and sometimes a nurse.

Step	User	Description	Why	Part of PIH EMR needed	Part of MFE Proof of Concept MVP scope?
Patient check-in	Nurse or clinician	The clinician or nurse search for the patient by name. If the patient is found in the database, they proceed to enter vitals. If not, they register the patient.	Find out who the patient is and whether they're in the system.
Registration	Nurse or clinician	If the patient isn't found in the database, the user registers them.	Creates a patient record.
Vitals	Nurse or clinician	Record the chief complaint. Take the patient's weight, blood pressure, RR & HR. Take height if it's not unlikely to have changed since the last recorded value. Maybe take temp and SatO2. For known diabetic patients, take blood glucose and ask if the patient is fasting.	If there's a nurse, this saves time for the doctor.
Chart review	Clinician	Quickly look over the summary data of a patient's clinical history.	Helps jog the doctor's memory of this patient and their problems. For patients that haven't been in in a while, or that were seen by a previous doctor, provides important information about clinical history.
Start filling out consult form	Clinician	Start filling out a SOAP note, making reference to whatever other clinical data is available.	Record the details of the current interaction with the patient.
Condition-specific or program-specific chart review	Clinician	Refer back to more detailed information about the patient's clinical history. (This probably rarely happens in the current EMR because of the lack of support for entering and viewing data simultaneously).	Glean information that might be clinically important for the patient.
Program enrollment and program-specific data entry	Clinician	Mark the patient as needing continued care specific to one or more long-term conditions.	Provide high-quality and continuous care for high-risk patients.
Analysis, Plan	Clinician	Make a diagnoses (or several), make a plan for care	Finish SOAP

Widgets: Functionality and UI to tie together

Priorities

Our focus areas for the next cycle.

Now:

1. Onboarding Eric Achilla TPM  (Grace Potma)
2. Style Guide vs Design System comparison (Brandon Istenesand Romain Buisson supporting Ciaran with analysis)
   1. Tuesday presentation
   2. Friday TAC recommendation
   3. Begin design system switch-over
      1. Integration into application
      2. Changing over application pieces to use that design system
      3. Review for bugs
3. Extension-based Architecture
   1. Definition & tickets (Brandon Istenes & Dennis Kigen (Unlicensed) - time together)
4. Patient Registration Page 
   Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    (Nicholas Hill)
   
   1. Wrap up remaining work:
      1. Identifiers
      2. Address templates & hierarchy
      3. Death information
      4. Edit workflow (next sprint)
      5. I18n - Patient Registration page localizable
5. Wrap up some Patient Chart work
   1. Immunizations - wrap up, taking into account Burke's latest feedback
   2. Bug Fixes on Patient Chart
6. Test Results (ThoughtWorks with Ajay Brar (UX) and ____)
   
   1. Implementation: Table view
   2. Design: Results Ready: How do I see that something is new
   3. Investigation of https://lhcforms.nlm.nih.gov/ compared to Bahmni forms - Jonathan Dick f/u with ThoughtWorks team to compare
7. Styling & UI Improvements
   1. Mobile device testing together (Eric)
   2. Document issues
   3. Consistent validation
8. Early QA 
   
   1. f/u with AMPATH TPM/QA team (Grace Potma –> Eric)
   2. Testing i18n with locale change - JJ to follow up with Derrick Rono re. running Cyprus against Web App distro for end-to-end workflow testing
9.  Misc
   
   1. I18n Blocker: Unable to get Home Page translations working; Patient Registration (Brandon Istenes - PR in esm-home) (Blocker for Mekom & PIH)
   2. Bug fixes
   3. Cucumber MVP (Grace Potma)

.......

Next:

1. Form Entry (Historically: PIH using HTML form entry; Ampath custom; Mekom BM forms)
   1. Clarity needed for Test Results Data Entry: If no agreed on UI, need to be clear together about data structures in order to use this widget - OMRS rules guidance for storage as observations, upper/lower bounds.  
   2. Via integration of Bahmni forms? (So people can build the functionality they need w/ form renderer) (this is currently scoped as one of Florian's deliverables)
2. (Florian - back Sept 1) Package everything together in distribution (most sites need things to work offline, unlikely to use CDN) (Romain Buisson )
   
   1. Backend packaging - Next sprint
   2. Frontend packaging - Proof of concept stalled without Florian (generating forward-compatible artifacts - to replace OMOD approach)
3. (Florian - back Sept 1) Domain Decomposition
   1. Design session - Monday 
   2. Complete definition to start splitting up pt chart widgets following cycle
4. Testing
   
   1. Environments: Staging vs Demo Prod?
   2. Automated tests in staging/integration (right now mostly unit tests)
   3. Outline of what's expected on phone, what's not
5. Whitelabelling (via overwriting style guide)
6. Patient Chart Next Focus
   1. Test Results Widget -  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      1. User test Test Results wireframes w/ staff from field
      2. MVP

People 

PM, BA

• Grace Potma - Product Direction
• Dave - BA - 10% (4-5hrs/wk)
• Pilar - PM - 30-50% 
• JJ - PM/prs - 50% (vacation week 2)
• (Tw) Helena - BA - trying to find replacement for Lucus

Devs

• (P) Brandon - vacation for first week; 15% (for prs, discussion)

• (A) Donald - 80%
• (A) Dennis - 60%
• (A) Bett - 50% (back-end)
• (A) Derek - not available
• (Tw) Nick - 5hrs/wk (30-50%); may reduce July
• Ian Bacher - backend as-needed - 10%
• Florian Rappl - vacation 4+ weeks starting week 2 Thurs.
• Romain Buisson - devops - Distribution management - 5-6 hrs/wk
• Ivange Larry - 100%

Testing

• Ampath QA Team - 50% (4 person team)

Nicholas Hill - Patient Registration module 

Mike Seaton+Romain Buisson 

Pilar Rubio - Product & project support

@mfsquad in slack