Stream: conformance
Topic: Profile of an unconstrained Resource
John Moehrke (Dec 04 2017 at 20:48):
How do I indicate that my ImplementationGuide and/or CapabilityStatement is happy with a specific resource that is not constrained? For example my Server is happy with Patient resource. It seems I can't create a StructureDefinition that has no constraints? Or is that just a tooling issue? Or is there some better way to say that my IG likes the Patient resource as published by FHIR?
Lloyd McKenzie (Dec 04 2017 at 21:02):
Refer to the structure definition that defines the resource itself.
Eric Haas (Dec 05 2017 at 03:03):
Good question:
If you are talking about references to e.g., patient, the reference is the by default in the tooling if type is empty to the base Patient, are you as the author constraining it to the 'only' the base Patient resources vs say My_Patient resource in my implementation which has some swell extensions. Or really saying 'I don't care' since I'm not defining that?
Eric Haas (Dec 05 2017 at 03:05):
My approach has been to say nothing about the stuff I'm not constraining. ( only the delta ) I assume that the rest in really undefined in the IG and left to the implementers to do interpret as they wish.
John Moehrke (Dec 05 2017 at 13:18):
In this case (PDQm) we want to say ANY Patient. It could be core, it could be constrained, it could be extended. Any Patient resource. Given this and the answer from Lloyd vs Eric; I don't know what to specify.
Lloyd McKenzie (Dec 05 2017 at 15:51):
If a system doesn't specify a profile at all, that doesn't mean they accept all data that's legal in the Patient resource - it means they're not documenting what they accept vs. not. If you want to affirmatively say that you can handle everything that's in the base Patient resource, then point to that resource.
John Moehrke (Dec 05 2017 at 15:59):
Lloyd, you mention 'system'... I am specifying an IG thus capabilitystatement.kind=requirements... would you give the same answer? I am happy with it, just wanting clarity as the various use-cases for capabilitystatement seem to be somewhat confusing
Lloyd McKenzie (Dec 05 2017 at 16:12):
Yes, I'd give the same answer
Last updated: Apr 12 2022 at 19:14 UTC
