FHIR Chat · profiling DomainResource · conformance

Stream: conformance

Topic: profiling DomainResource


view this post on Zulip John Moehrke (Dec 11 2019 at 23:01):

I am working on a security IG that is going to set some requirements for ALL resources derived from DomainResource. Specifically a defined set of codes for .meta.security... How do I do this at the DomainResource level?

view this post on Zulip Lloyd McKenzie (Dec 11 2019 at 23:20):

You should be able to profile DomainResource. How the validator would handle that against an instance is an open question. Presume the IG has a narrow scope in terms of the context in which the resources would be used that would allow assertion of security codes? Because it couldn't be done at an international or even U.S.-wide level.

view this post on Zulip Grahame Grieve (Dec 11 2019 at 23:29):

I don't think this is possible at this time

view this post on Zulip Grahame Grieve (Dec 11 2019 at 23:29):

it's not clear to me that it's even allowed

view this post on Zulip John Moehrke (Dec 12 2019 at 00:40):

I am willing to try...

view this post on Zulip John Moehrke (Dec 12 2019 at 00:40):

The bigger part of this is profiling Bundle.meta.security... so that is what I am focusing on first.

view this post on Zulip John Moehrke (Dec 12 2019 at 00:42):

but, the overall is that yes there is a need to say that all the resources within a bundle that is compliant with XYZ profile and thus ABC regulation SHALL be marked with tag LMNOP...

view this post on Zulip John Moehrke (Dec 12 2019 at 14:16):

Or said another way...Given a subset of the vocabulary bound to DomainResource.meta.security in a given IG, when a system declaring conformance to that IG is declaring that they use a subset of codes according to that IG, such that no data (or bundes) will be sent with vocabulary outside that subset and all data consumed with that vocabulary will be processed according to the rules of the IG. It seems this is only possible to say in narrative?


Last updated: Apr 12 2022 at 19:14 UTC