Open annabel-uzl opened 4 months ago
EDIT: bodyStructure is not an element in R4, but bodySite is, so we could argue using a bodyStructure extension to put morphology in it
EDIT2: in context of the datacapabilities project (KWS data to FHIR) this is an urgent question
I'll bring this topic back to life cuz we need an answer and there is a WG tomorrow ;)
I'll suggest making a OncologyProfile to handle cancer diagnoses and tumors. Doing that we can following mCode of the US and make a morphology extension on a higher level (not as part of the bodystructure). I want to propose a LM but I need a place to do this.
We need to decide on where to put morphology of wounds, open fractures, ... I would think a wound is not always a condition (e.g. cracked nail). Some options:
this will be discussed in the business work group and referred back to WG through @bdc-ehealth
Morphology is defined as an element of bodyStructure (see https://build.fhir.org/bodystructure.html) but, I assume, we don't want to put diagnosis in the bodyStructure element. Therefore we came across some questions:
Case burn injury: seems valid to describe the wound in the bodyStructure and thus add morphology Case tumor: ??? depends on the case - procedure / observation / ... also related to Question about logical model for oncologie: https://github.com/hl7-be/core-clinical/issues/38 Case open or closed fracture: maybe using an extension? Or putting it in the bodyStructure?
The US made an extension: https://build.fhir.org/ig/HL7/fhir-mCODE-ig/StructureDefinition-mcode-histology-morphology-behavior.html that, I think, is only used in their oncology model.
My suggestion would be the following:
Something like that? Are there other/better suggestions?
FYI related topics: