Two errors are risen from the current MPD R4 IG when imposing IPS ballot version:
1) medication.code is mandatory in IPS.
Medication code cannot be mandatory for prescription systems, because medication.identifier or reference or attributes may be used for identifying the prescribed product. If IPS expects a code (for example, ATC in case an identifier is used) it can be done but only at the time of composing the IPS document. When a package identifier has been used for prescribing, adding ATC to .code would make it difficult to process for the dispenser, because it would not be clear which granularity is expected to be followed at dispense.
2) Quantity data type impose use of UCUM for units, but for medicinal product strength and pack size we may use units of presentation - strength 100mg/1 vial; pack size 26 pens. In these cases other code systems are more appropriate - EDQM, SNOMED CT, etc. While this can, of course, be mapped to UCUM or used as {newunit}, it cannot be expected from prescription systems. There can be no expectation that a MedicationRequest has to use UCUM for all units.
Also, I think curly brackets solution for units of presentation will end up badly translatable and mappable across countries, and that is an important issue for at least European PS.
@gcangioli to bring it to IPS ballot if necessary. Right now, errors regarding non-conformity to IPS remain unresolved in the MPD project, because these restrictions are not reasonable from prescription point of view.
Two errors are risen from the current MPD R4 IG when imposing IPS ballot version:
1) medication.code is mandatory in IPS. Medication code cannot be mandatory for prescription systems, because medication.identifier or reference or attributes may be used for identifying the prescribed product. If IPS expects a code (for example, ATC in case an identifier is used) it can be done but only at the time of composing the IPS document. When a package identifier has been used for prescribing, adding ATC to .code would make it difficult to process for the dispenser, because it would not be clear which granularity is expected to be followed at dispense.
2) Quantity data type impose use of UCUM for units, but for medicinal product strength and pack size we may use units of presentation - strength 100mg/1 vial; pack size 26 pens. In these cases other code systems are more appropriate - EDQM, SNOMED CT, etc. While this can, of course, be mapped to UCUM or used as {newunit}, it cannot be expected from prescription systems. There can be no expectation that a MedicationRequest has to use UCUM for all units. Also, I think curly brackets solution for units of presentation will end up badly translatable and mappable across countries, and that is an important issue for at least European PS.
@gcangioli to bring it to IPS ballot if necessary. Right now, errors regarding non-conformity to IPS remain unresolved in the MPD project, because these restrictions are not reasonable from prescription point of view.