search

IHE / pharm-meow

IHE Pharmacy Medication Record Profile Implementation Guide
MIT License
2 stars 0 forks source link

Request from HL7-FHIRi: tighten the context of the "basedOn: and the "based on extension" extensions. #29

Open bvdh opened 9 months ago

bvdh commented 9 months ago

Section Numbers/URLS

  1. IHE-FHIR-PHARM-MEDICATIONRECORD\basedOn - FHIR v5.0.0 (links to a CarePlan)
  2. IHE-FHIR-PHARM-MEDICATIONRECORD\Based On Extension - FHIR v5.0.0 (link to a MedicationStatement)

Issue HL7 FHIR-i is reviewing extensions defined in the FHIR space in order to clean them up, remove redundant extensions and improve the definition of the remaining ones.

During this process, a set of IHE defined extensions where discussed that need work.

The extensions context is 'Element', allowing it to be used on any element on any resource. FHIR-i is concerned that this is far to generic and strongly recommends restricting the use to the specific context where it is intended to be used.

For the first extension (basedOn) this would be MedicationStatement, as that is the only place it is used). The context of use of the second extention (link to MedicationStatement) is unknown and should be specified or the extension should be removed.

The descriptions of both extensions is very sparse making it very difficult to deduct their intend and use, please extend these and make them more specific.

Proposed Change Restrict the use of these extensions to the root level of MedicationStatement. This can be achieved by adding the line Context: DiagnosticReport to the header of these extensions in the sushi fsh file.

Extend the description of these extensions.

Priority:

costateixeira commented 9 months ago

the IG that is mentioned doesn't exist anymore. This has been migrated and the extension doens't exist (yet/anymore)? Leaving the ticket open for now while that content is reconsidered (just to not dismiss the ticket) .And the need is still there, not sure if we will eventually have the extension.