Resolved
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Luud SlagterLuud SlagterReporter
Arianne van de WeteringArianne van de WeteringConcerns version
MP9Classification
Patch (Z)Transactions
Medicatiegegevens (9)Parties involved
Nictiz Informatie analistNictiz HL7-specialistDataset
9.1Bouwsteen
MedicatieToediening uitgevoerdComponents
Fix versions
Priority
Medium
Details
Details
Assignee
Luud Slagter
Luud SlagterReporter
Arianne van de Wetering
Arianne van de WeteringConcerns version
MP9
Classification
Patch (Z)
Transactions
Medicatiegegevens (9)
Parties involved
Nictiz Informatie analist
Nictiz HL7-specialist
Dataset
9.1
Bouwsteen
MedicatieToediening uitgevoerd
Components
Fix versions
Priority
Better Excel Exporter
Better Excel Exporter
Better Excel Exporter
Created February 27, 2019 at 1:40 PM
Updated December 6, 2023 at 4:38 PM
Resolved June 29, 2022 at 7:51 AM
This issue is raised from ---MM-159---
On Simplifier, dosage > rate[x] has no attribute rateRange. However, in a zib such as InstructionsForUse this attribute does appear. Should this attribute not be present in MedicationAdministration as well?
On zibs.nl, the attribute AdministeringSpeed::Range (NL-CM:9.13.23159) and, on Simplifier, the attribute dosage > rate[x] seems like it should either have type Ratio, or the attribute should include another attribute named rateRange.
The zib nor the FHIR profile refer to InstructionsForUse from MedicationAdministration/Medicatietoediening, so that is not applicable here.
However, in the zib a variable rate is permitted. This is currently not obviously possible in the FHIR profile (it can still be done, but only using it in a single UCUM code, however since we need to use the G-standaard unit in The Netherlands, UCUM does not satisfie our requirements).