gematik / spec-ISiK-Medikation

The ISiK module "Medication" enables data integration through structured communication options based on a RESTful API for the exchange of medication information ("Medication Plan") as well as prescription and administration data.
Other
6 stars 1 forks source link

💡 [REQUEST] - Clarification on dosage dose UCUM as UOM - ANFISK-334 #133

Open julsas opened 1 month ago

julsas commented 1 month ago

Target Date

No response

Implementation PR

No response

Reference Issues

No response

Summary

Need to clarify if other code systems besides UCUM should be allowed for MedicationAdministration.dosage.dose and Dosage.doseAndRate.doseQuantity for MedicationRequest and MedicationStatement.

ISiK-3 has Quantity.system = http://unitsofmeasure.org. Should other code systems be allowed for concepts like Tablet from EDQM? ISiK-4 introduces the Quantity data type profile Medication Quantity which mentions SNOMED as an alternative to UCUM. But Quantity.system is still set to UCUM. This could this be a use case for http://hl7.org/fhir/R4/extension-iso21090-pq-translation.html

Common Examples

Use case of a Medication with a form:

    "form": {
        "coding":  [
            {
                "code": "10219000",
                "system": "http://standardterms.edqm.eu",
                "display": "Tablet"
            }
        ]
    },

should it be possible to have a MedicationAdministration of that Medication with:

  "dosage": {
    "dose": {
      "system": "http://standardterms.edqm.eu",
      "value": 1,
      "code": "10219000",
      "unit": "Tablet"
    }
  }

?

Drawbacks

Adds extra complexity when different code systems are allowed. US Core is UCUM only: https://build.fhir.org/ig/HL7/US-Core/StructureDefinition-us-core-medicationrequest.html

Unadressed questions

No response

f-peverali commented 1 month ago

hallo @julsas. Danke für die Anfrage. Diskutieren wir intern und dann sicher auch in einer AG.