![]() Then - once Design Model done - Fix encounter model of Order Basket - orders should be part of your desired clinical encounterĭebrief w/ Ian: Main concern is reporting.A little design that shows us how we put the encounter context in. Go into order and select something in there. Amazon - I want to cancel something in my orders. Design time - user mental model way to give them the context of what they're in → _ (Grace f/u on how to fund.but, this is really a technical thing e.g.Introduce encounter context → Burke → Talk post ongoing here.Confirm Order History plan - for now we'll proceed w/ simple table.Multiple Active Visits at once: End Modal should be clear about which one you're ending how can UI make clearer which Active Visit you are adding information to? We would like things to be logged against a single encounter - not one for the drug order, one for a form, etc etc. When you order a drug it creates a Drug Encounter. Implementation might decide to have everything in the same encounter. Nurse, Clinician, Social Worker - may be in same department/visit but different encounter. Need to know explicitly "you are adding something to this encounter." Or, patient has left, and I want to keep working on some documentation for that past encounter. See past mistake or issue in last month's encounter - I want to edit that. Pt comes in for return HIV visit: Write note, orders, form for right now. Why do we allow multiple encounters or visits at once?.If you're in different context, border color changes etc. Bahmni's implicit encounters - setting a timer when an encounter is created, any new data coming in w/in certain frame of time, goes in that encounter. Use cases: Why do we make multi-active possible at all?.Want encounter in the system to represent the encounter in real life. ![]() Need ability for multiple components to contribute to 1/the same encounter. Problem/challenge: O3 has pulled apart the "everything in 1" form approach.Form based approach not something we want to continue doing.). PIH - Vitals Encounter for info entered in Vitals Form (very form-based looking for O3 to support better than current form-based approach does. Clinical Meaning vs Technical/Backend Meaning can be used differently.Right now it's possible for them to unknowingly enter info against a completely different encounter/visit. Should be clear which encounter / visit they're working within. Encounters & Visits: How we show users which encounter or visit they're working within at any given time.Allergies: See Duffy latest ideation (follow-up from last week) - moved to next weekįrontend "Encounter Context" & Visit Context - "You are here".content switchers, tide headers - next week or week after Design System & Design Components & Code Components and how to bring into greater alignment (Ciaran, Aline, Dennis, Grace ?Ian, ?Daniel, ?Eudson, ?Pius, ?Samuel M) → ? dev work to look at the code components and see which are easy to refactor, e.g.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |