The current form behaviour of recording causes of death restricts users to only pick from HIV related causes of death or the list of causes of death as added under the conceptUUID for causes of death. It’s restrictive for implementations that are now in all service delivery areas in a health facility setting and limits generating data for reporting for other causes that are already provided in a diagnosis terminology service like ICD-11 and local MOH NHDDs.
We would like to suggest enhancing the form under the mark-decease-patient-workspace to pick the cause of death from a local and international standard to help in reporting and capturing the correct cause of death for data sharing and standardization.
The point of having the concept set here is so that it can be customized by each implementation as different countries and different contexts have different values that make sense. If you need codes that correspond to ICD-11 or NHDD, you should be mapping the concepts in your implementation to the appropriate codes.
In other words, yes, that’s the type of thing we expect implementations to take care of.
If you need multiple causes, etc. you probably need a custom form to handle it. The default cause of death form is based around the OpenMRS data model which allows a single cause of death to be added to a patient.
@ckote There is an OpenMRS global property (name=concept.causeOfDeath) which is customized for your the implementation. The value is set to the unique concept mapping or concept uuid.
Depending on our country/health facility, Partners In Health uses different causes of death. Your standard might not be the same as mine. That’s the beauty of OpenMRS.
In OCL, here are 2 examples of concept sets (class=ConvSet) used for cause of death:
Probable cause of death (1599) is a coded concept which can be populated from any concept, so the question is where does that list come from? A value set like Ellen provided, or via a query of a diagnosis concept that has an ICD-11 code map (for example).
@ibacher I get what you are saying but as rightly put by @akanter, internationally you’re expected to capture * Immediate Cause (Final) * Underlying Cause(Primary) * Mechanism of Death(e.g, where poison was the primary) these are important, especially for public health response and how a deceased body shoul be handle.
So @ibacher this is standard even FHIR resources require this data for SHR.
So what we are suggesting is adding other two fields to ensure we can capture the details in full, then we can work on how we can consume data sources through UUIDs without affecting OpenMRS data model
We haven’t any complaints from other implementations because may be its been only HIV or disease specific cause of death reporting which can just be on.
