Stream: implementers
Topic: Multiple Implemetation Guide for single server
Siarhei Bartoshyk (May 15 2020 at 16:12):
Hi there,
I have a question about proper implementation for multiple Implementation Guides in a single server. In the scope of our project, we have to implement CarinBB and USCore guides. Both IG has PractitionerRole resource.
From US Core IG PractitionerRole.practitioner field has to be filled because of cardinality 1..1.
But for CarinBB IG PractitionerRole.practitioner field is optional because of cardinality 0..1.
So there are questions:
How should we resolve this conflict from the capability statement's point of view?
Do we have to implement our own IG to merge all conflicts?
Does the metadata endpoint have to return the next resource?
{
"type": "PractitionerRole",
"profile" : "http://hl7.org/fhir/custom/StructureDefinition/custom-practitionerrole",
"supportedProfile": [
"http://hl7.org/fhir/us/carin/StructureDefinition/carin-bb-practitionerrole"
],
...
}
Regards, Siarhei.
Michele Mottini (May 15 2020 at 16:32):
(deleted)
David Pyke (May 15 2020 at 16:41):
Carin-bb has PractitionRole.practitioner as 1..1 in version 0.1.0 and in the current version. It's not possible to relax that constraint in a depended profile Can you screenshot where you see it being 0..1 in Carin?
Lloyd McKenzie (May 15 2020 at 16:48):
Generally the solution is to spit out instances that meet the requirements of everyone. That gets a bit tougher if you're also needing to consume data from everyone. It's also tricky if the profiles impose constraints on the max that can be sent. In those situations, the best thing to do is to push back on the profile authors. (e.g. it's bad practice to constrain Patient.name to 1..1. Instead, enforce that there's a mandatory slice with enough metadata that would allow you to extract that one name from amongst all the others that might exist
Last updated: Apr 12 2022 at 19:14 UTC
