Stream: implementers
Topic: Specifying more than one target profile
Ross Shnaper (Nov 28 2017 at 16:49):
Hi, I was wondering whether it's allowed to have more than one target profile specified for a reference. Like so:
<element id="Encounter.location.location">
<path value="Encounter.location.location"/>
<type>
<code value="Reference"/>
<targetProfile value="http://cihi.ca/fhir/irrs/StructureDefinition/irrs-location-mis-code"/>
<aggregation value="contained"/>
</type>
<type>
<code value="Reference"/>
<targetProfile value="http://cihi.ca/fhir/irrs/StructureDefinition/irrs-location-bed-type"/>
<aggregation value="contained"/>
</type>
<mustSupport value="true"/>
</element>
Lloyd McKenzie (Nov 28 2017 at 16:51):
Yes, that's allowed. Doing this would mean that there's a choice of instances that match the first profile and instances that match the second profile.
Ross Shnaper (Nov 28 2017 at 16:52):
That's weird because the validator always uses the first profile which has a different binding for Location.type and complains about the codes not being from that value set.
Lloyd McKenzie (Nov 28 2017 at 16:56):
Not sure why. It should try validating against both and if it's valid against one, not complain about the other. If that's not what you're seeing, then submit a change request with the problematic instance and profile attached.
Ross Shnaper (Nov 28 2017 at 17:31):
Thanks Lloyd, I just dug into the code and confirmed that is indeed a bug. I'll submit a change request.
Lloyd McKenzie (Nov 28 2017 at 17:58):
If you feel comfortable identifying the specific fix, that'd be even more welcome :)
Ross Shnaper (Dec 01 2017 at 05:24):
I might do just that ;) Still waiting to get access to GForge so that I can submit a ticket :/
Lloyd McKenzie (Dec 01 2017 at 07:00):
There are no pending users listed - check your spam folder for the registration response.
Last updated: Apr 12 2022 at 19:14 UTC
