O3 Labs & Tests

Historic Links:

Community Discussion Thread: https://talk.openmrs.org/t/o3-lets-move-forward-on-lab-orders/37155
Designs in Zeplin (same as link in the first email) https://zpl.io/g8LornO
UI Patterns for the Order Basket (*new*) https://zeroheight.com/23a080e38/p/71ad91-order-basket (The design team is looking for any feedback on this page right now actually)
End-to-End Walkthrough video of the Lab Orders - this will show more detail than either of the assets above, especially the "result entry" flow Paul & Wamz are proposing. Grace is not sure if we should be building those pieces into the EMR or not. Recording from the cmty design call 2023-March-13: https://iu.mediaspace.kaltura.com/media/t/1_nzrv9fzr?st=2894 (I've linked directly to the timestamp where Paul does this walkthrough)

Squad for Labs v2: Kick-Off Call Oct 16 2023

Attendees: Brandon, Burke, Casey, David, Eudson, Gilbert, Grace, Michael B

Link to Wamz's demo on Oct 12th Squad call: https://iu.mediaspace.kaltura.com/media/t/1_2b8r9rf1?st=1810

Area	Now: What we have now (as of Oct 16th)	Where we want to go: Next Priorities	Notes
Order Labs/Tests	Lab Order form in Order Basket Test Search Lab Order number is generated but only in the Angular Form Order component ("Lab order(s) generated 1 : Haemoglobin : ORD-441)	Bug: Drug concepts should not be showing up (_____) Remove "Lab reference number" in the order form. Usually exists on a pre-printed form. Aka Accession # or Specimen #. Order number needs to end up in the FHIR request (___) Order Form should be driven by a form made in / editable in the Form Builder Start an Order in an Encounter via a Form Ang Form Engine link into Order Basket (Brandon/Mekom) React Form Engine link into Order Basket (________) Form Engine Powered Built-in Forms: Render Forms elsewhere in O3 (eg in Lab Order app) - Reference a particular form within an app's o3 config (e.g. change triage / lab form UID for your distro); built in forms would be stored the same way we store form engine forms	Implementation: Options are from all concepts called "Test" Lower priority: Provider's "Favorites" (_____)
Per Patient: Order Status	Nothing	See any pending Lab Order Flag "done and critical"	Order status and lab status are not necessarily the same thing. e.g. "specimen collected" is an order status but not a lab status? Phlebotomy Status: Drawn? Label Printing? Where someone needs to add #'s like Reference #, Sample #, Accession #? Status page: rejections of samples by lab. Critical results, alert worthy? Certainly on the status page, but do you want to bug the ordering doc as well? I just wanted to add this so I don’t forget when we run out of time.
All Patients: Order Status		Flag critical results Rejection Workflow - sample not good enough; alert Phlebotomy to re-do	(In Lieu of a bigger Lab Info System; similar to Dispensing App)
Results Entry	Via manually-built Form with ConceptIDs for Lab tests	Add Results from the Status page
Results Viewing		Fix Tree hardcoding - should be driven by LabSets / ConvSets Tree View Logic: Decision - do we want to allow multiple levels? ______	No Order relationship yet... "Orderable" vs "Viewable": Filter to exclude stuff you don't need to see in the Order view, (want to see "Blood Cultures" in orders, but not the sub-tests for each strain of resistance), PIH has driven through "Orderable Labs ConvSet" that tend to be different per country
Result Alerts Inbox	None; lab-specific results	Future

Peoples' Needs:

UCSF: 4-week Sprint starts tomorrow; want something w/ labs
PIH: Not a top priority for MCOE project but want to be involved
MSF: Critical for first pilot in a few months from now; want to align requirements
DIGI: OpenELIS-OMRS fhir-based connection for O3 for Cote d'Ivoire; currently just for VL but want for all lab tests (interested in statuses)
General Support: (assisted by Mekom/Brown (Brandon/Ian)): Implemented Lab Order form in Order Basket; Test Search functionality. Next:
Major Overlaps: Status; Requirements