Hello all!
(And specifically @akanter @grace @ibacher @ball @dkigen @dkayiwa @mksd @mksrom )
There have been multiple requests from implementers asking how to get the new O3 Inpatient Ward App running within their own implementations, so I have working to get the Ward App configured within the O3 Ref App Distro.
The Ward App relies on the EMR API module, and, specifically, the ADT logic that was built into it during the development of OpenMRS 2.0.
The EMR API module depends on various metadata being configured, including encounter types, location tags, concepts and metadata mappings. I’m in the process of updating the Ref App Distro with the needed configurations. For more of the metadata, I can add them via Initializer and we can discuss and review in the context of PR I issue, but the concepts require a broader discussion.
I was hoping that the concepts we (PIH) have beeen using would have equivalents in CIEL, (and os I could just import those into the Ref App Demo) but it looks like, except for one, they don’t. (Which may suggest we never agreed on a way to standardize this back in the day).
The functionality will require the following concepts to work. Specific names don’t matter, the key is the structure, and that they have appropriate “org.openmrs.module.emrapi” concept source mappings, which is how the EMR API module references them.
Ideally all these concepts would be set up in CIEL (or existing concepts to use would be identified) and then we could create an OCL package with them which could be added to the Ref App distro project.
The concepts we need are below. Thoughts?
Take care, Mark
Disposition Construct
- Type: ConvSet
- A construct to collect various descriptions for movement of patients within the hospital
- has SAME-AS mapping - org.openmrs.module.emrapi:Disposition Concept Set
This set needs the following three members:
Disposition
- Type: Coded Question
- Records a Disposition for patient; see potential answers below
- has SAME-AS mapping - org.openmrs.module.emrapi:Disposition
- See below for possible answers
Admission Location
- Type: Text Question (stores location_id/uuid behind the scenes)
- The location in the hospital the clinician is requesting a patient be admitted to
- has SAME-AS mapping - org.openmrs.module.emrapi:Admission Location
Transfer Location
- Type: Text Question (stores location_id/uuid behind the scenes)
- The location in the hospital the clinician is requesting a patient be transferred to
- has SAME-AS mapping - org.openmrs.module.emrapi:Internal Transfer Location
Then Dispostion has the following 3 answers (it can have more to reflect other dispositions, but these are the ones key for the EMR-API inpatient functionality):
Admit to Hospital
- Type: Misc/NA (not sure how important it is that it is this type, it just needs to be a type that allows it to be a valid answer to the “Disposition” Coded Question)
- Represents a disposition where a clinician requesting a patient be admitted to the hospital
- No special mapping code required
Transfer Within Hospital
- Type: Misc/NA (not sure how important it is that it is this type, it just needs to be type that allows it to be a valid answer to the “Disposition” Coded Question)
- Represents a disposition where a clinician requesting a patient be transferred internally within the hospital
- No special mapping code required
Discharge
- Type: Misc/NA? (not sure how important it is that it is this type, it just needs to be type that allows it to be a valid answer to the “Disposition” Coded Question)
- Represents a disposition where a clinician requesting a patient be discharged from the hospital
- No special mapping code required
We also need the following:
Admission Decision
- Type: Coded Question
- Used specifically to track when a request to admit a patient (via a disposition of admit) is denied (this is how we record when a patient is removed from the “Awaiting Admission” list)
- has SAME-AS mapping - org.openmrs.module.emrapi:Admission Decision
This can have multiple answered, but only one is required for IPD functionality:
Deny
- Type: Misc/NA
- Represents a decision to deny admission to a hospital (ie override an admission request)
- has SAME-AS mapping - org.openmrs.module.emrapi:Deny Admission
Clinician Impression Comments
- Type: Text Question
- Free text for non coded clinical impressions (this is the concept we use to store free-text inpatient notes)
- has SAME-AS mapping - org.openmrs.module.emrapi:Consult Free Text Comments
- In PIH EMR we use CIEL:159395 for this, so probably all we want to do is add the above mapping to CIEL:159395
