...
Because CDA uses a variety of codes from SNOMED, LOINC and others, there is a need to bulk-import concepts and their mapping to MVP/CIEL upon module install. This is done via the ReferenceTermDictionary.xml file in the resources folder. Upon build, this XML file is transformed to a liquibase.xml file and placed in the omod file. This file contains mapping to CIEL concepts where appropriate and allows the module to use those mappings in an easy to maintain XML File (editable within Microsoft Excel as a table)
Orders
Many entries within the CDA document carry what are known as moodCodes. These mood codes identify the mode of the entry.
- Entries carrying a mood code of EVN (event) represent something did occur (i.e. I did observe X)
- Entries carrying a mood code of INT (intent) represent the intent to do what the entry represents (i.e. I intend to observe X, or I would like someone to observe X)
- Entries carrying a mood code of GOL (goal) mean the entry represents a desired end state such as in a care plan (i.e. The goal is to observe X by Y date)
- Entries carrying a mood code of PRP (proposal) mean the entry represents a proposal to perform something
Within the CDA import module, entries are imported into OpenMRS' data model depending on their mood code. Below is a table representing the source CDA RMIM class by moodCode and the resulting structure in OpenMRS.
| RMIM Class / Mood | EVNEVNEVN | INT | GOL | PRP |
|---|---|---|---|---|
| Observation | Obs | ObservationOrder | Obs Group (having GOAL sub-obs) | Obs Group (having PROPOSAL sub-obs) |
| Organizer | Obs Group | N/A | N/AN/ | N/AN |
| SubstanceAdministration | Obs Group (160741) | DrugOrder | N/AN/ | N/A |
| Procedure | Obs Group (160714) | ProcedureOrder | Obs Group (having GOAL sub-obs) | Obs Group (having PROPOSAL sub-obs) |
| Act | ActiveListItem (Allergy or Problem) | N/A | N/AN/A | N/A |
Note: ProcedureOrder and ObservationOrder are extended orders having additional data placed in the procedure_order and observation_order tables in OpenSHR's data model respectively. These classes were extended to qualify the type of order as well as track additional data required such as targetSiteCode, procedure/observation requested, and goal ranges.
Known Issues / Todo
Most up-to date listed here: https://github.com/jembi/openmrs-module-shr-cdahandler/issues
...