New Institutional Module: Is it time?

Started the Assisted Living Care Domain to companion with Behavioral Health Domain.
Screenshot gives a decent overview for now. Let me know if I can answer any questions.

Mostly now Dashboard ran to help with context management.

Reading the ‘usage_submodule_summary_v0.10.0’ linked above.
I didn’t read every group/ submodule but it’s clear to me that fundamentally they’re well concieved and cover what’s important. Obviously the specifics will get adjusted when they meet reality.

Just a few things that occurred to me:

  • there’s so many moving parts here, and so much overlap with the current OEMR’s features that it’ll be v important to establish a formal vocabulary for consistency and clarity. E.g., what is the ‘episode’ used here /vs/ the current OpenEMR term ‘encounter’. Not clear that/ if they’re the same thing. This is one of the failures of the existing OpenEMR documentation, that having different names for the same elements gets in the way of learning and using the application.
  • As far as the features are concerned, they’re really on the mark but it appears that plenty of overlap will exist between the new features and the current OpenEMR features, so will have to distinguish their scopes clearly. Are these new features or reorg/ re-branding of existing functionalities? E.g., ‘02 Triage - drives labs’ etc, is this going to be an expansion of the existing ‘status’ feature as shown in the flowboard etc, or something new, leaving the ‘status’ dropdown as it is?
  • group c - med management - this will conflict in many ways with commercial 3d party eRx solutions. Either by duplicating the features or requiring interaction with them. Going to have to map out the interactions v carefully!

Will run through the demo later in the week.

Best- Harley

Thanks @htuck
I need to check which demo I assigned to you because I have one that is fully seeded with all data required for every Care Domain.
I’m current restructuring file management to get on board with the domain care concept. Will be done later today.
I’ll PM you.

Hello folks,
I’ve been striving to get a BETA release together. I supplied workflow documents so you can run through how this module works. If you want to demo, send me an email or PM and I’ll give you access.

assisted-living_workflow_guide.docx (26.9 KB)
Maple Grove Assisted Living — Resident Workflow Guide (14 sections, green theme)
Follows all five demo reidents pulled directly from your seed data:

  • Eleanor Hartwell — TIER 3 memory care, SNF transfer pending to Springfield Memory Care
  • George Calloway — post-hip arthroplasty TIER 2, home discharge planned at day 60
  • Ruth Okonkwo — COPD GOLD 2, TIER 1, inhaler adherence management
  • Harold Steinberg — Parkinson’s H&Y 3, fall this morning, hospital eval pending
  • Dorothy Vasquez — CHF + T2DM, weight gain alert, CHF decompensation eval

Covers every submodule: Resident Board flags logic, Intake (with the form_encounter guard), ADL MDS 3.0 scoring table, Morse Fall Scale history tables, MAR with the furosemide medication error incident, Care Plans (FHIR/CCDA note), Shift Handoff snapshot with red-highlighted severity rows, all five discharge pathways, and the full feature flag reference table.

obs_acute_workflow.docx (27.7 KB)
Springfield General Hospital — Acute Care & Observation Stay (14 sections, blue/teal theme)
Purpose-built for the ED_ACUTE and OBS_STAY domain contexts:

  • ED vs OBS context comparison table (audience, features, HL7 events)
  • ESI level 1-5 definitions with color-coded rows and module actions
  • Automated alert sources: qSOFA sepsis screen, LWBS risk, overdue tasks, OBS billing flags
  • Two-midnight rule threshold table (NORMAL → APPROACHING_1 → APPROACHING_2 → CONVERSION_DUE → OVERRUN) with a live sample billing view
  • OBS protocol engine (GENERAL_OBS, CHEST_PAIN, custom) and task runway generation
  • Acute MAR with heparin high-alert dual-verification note
  • Full HL7 ADT event map (A04, A01, A08, A02, A03, A11)
  • BH boarding extension (legal status, EMTALA, placement tracking)
  • CMS quality measures (OP-18b, OP-20, troponin TAT, LWBS rate)

Update to v0.16.0
Finished some core integrations as part of this version:

  • Facilities Multi-Facility support
  • Users
  • Patient data
  • Care plans
  • Care Teams
  • Clinical Notes
  • Interventions
    I spent considerable time on workflow navigation of current care context. So if Assisted Living context then all page scopes pertaining to the context is available on the page. Point is that the user should never have to go to top level menus. Eventually I hope to extend to the task manager so when working a task related buttons to achieve the task are highlighted and task checklist gets updated as summary towards task completion.

Next immediate core interaction to be done is Prescription ↔ MARS which leads to if I’m going to develop an eRx submodule. TBD…

Since I now have the Domain Care concept structurally in place I can start mapping workflow variations for locales such as US, EU, Asia, Africa etc. This will require considerable research and expertise and if done right a domain needs can be easily expanded over time.

If anyone can point out any differences on how institutional is handled across international locations I’d greatly appreciate the input. A couple screen shots for Assisted Living relationship with core




Thanks to all of you giving me private encouragement.

2 Likes

Hi @sjpadgett

Looking good!

Myself, for now I’d leave for later an eRx submodule since what we have at the moment does work. I mean I don’t know anything about weno’s integration but Ensora has some data exchange habits w/ OpenEMR that seem tricky to me… though o’course I’m not a dev and don’t know the code of the interface.

  • HT

Sorry @htuck I meant eMARS.
MAR is pretty much done.

Hot dang this is fun!

On the whole it looks encyclopedic. V complex but as soon as you get the screen logic works pretty good.

  • At this point I’m seeing little UI things like, when you select a time in the date/time picker there’s no positive action to make it so- just clicking outside the ctrl sets it. Which seems prone to serious error.

  • I take it the definition of ‘episode’ would be close to ‘stay’ or ‘admission’?

  • Have not been able to check the PRN admin function to see if it prevented doses timed too closely. When I tried to give a PRN med it did this:

  • At some point while operating the Inst. Mod the OpenEMR header disappears showing only the Inst. tab contents (no screenshots right now). I haven’t been able to find precisely how to get into, or out of, that display

  • which begs the question, how integrated is the Inst. module going to be with the ‘Clinic’ (as it were) OpenEMR ? Will providers be able to look in the pt’s OpenEMR record and see notes, procedures etc that they had as inpatient?

I’m having fun playing with this demo; at the moment practicing navigating between contexts and workflows. Would it be possible to get another test user so I can compare entries made by one as viewed or edited by the other?
Thanks again- HT

2 Likes

I was wondring if we can implement The MAR (Medication Administration Record along with barcode wristban scanning simialr to Cerner Bridge Medical.

2 Likes

Sorry, I’ve been out of it past couple days. Thanks for report and I have addressed MAR issues but I haven’t put up on demo yet. I have openemr care plan available in module and can create new care plan on either side but I’m thinking to restrict that care plans and clinical notes can only be managed in openemr.

If you generate a report or print it will open a new window or tab. You should be able to see and go back to openemr main tab. Still I don’t like and have been fixing as I come across i.e. new tab in openemr.

PRN is fixed plus some other MAR issue but I’m moving a little slow so give me til Monday and I’ll have demo updated.

1 Like