Stream: implementers
Topic: Derived profiles - extensible binding
Kevin Mayfield (Oct 10 2020 at 10:13):
In this UK Core profile https://simplifier.net/guide/UKCoreDevelopment/ProfileUKCore-MedicationDispense
MedicationDispense.type has extensible binding to UKCoreMedicationSupplyType
In the derived profile https://simplifier.net/guide/DigitalMedicines/DM-MedicationDispense
This is bound (required) to MedicationDispense Type.
Is this allowed?
It's ok in forge but HAPI/HL7 validation is going to the former as required and ignores the extensible.
Grahame Grieve (Oct 12 2020 at 05:36):
I'm confused. Isn't it the latter than is required?
Grahame Grieve (Oct 12 2020 at 05:37):
the profiles are technically legitimate, but only really valid if MedicationDispense Type is a proper subset of UKCoreMedicationSupplyType - I didn't checkc
Kevin Mayfield (Oct 12 2020 at 07:54):
my understanding of extensible is other codes can be used
For example in this STU3 profile https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Immunization-1
COVID-19 vaccine codes would be legitimate - the binding is extensible
Last updated: Apr 12 2022 at 19:14 UTC
