Stream: IG creation
Topic: Constraints on CodeableReference
Nick Freiter (Feb 02 2021 at 18:12):
We are beginning work on supporting the CodeableReference type in FHIR shorthand, and are running into questions about how constraints may be applied to a CodeableReference. As an example, let's say I wanted to constrain CarePlan.activity.detail.reason (a CodeableReference) to only be able to reference Condition. I can see that if I wanted to do this, I could change the targetProfiles array on CarePlan.activity.detail.reason. But would it be legal if instead I applied the constraint by changing targetProfiles on CarePlan.activity.detail.reason.reference? How do we handle cases where the CodeableReference and the Reference it contains both have constraints? It seems like a misuse of the CodeableReference type to do this, but I don't see anything saying I can't do this.
Lloyd McKenzie (Feb 02 2021 at 18:53):
Can you submit a change request for us to clarify that?
Nick Freiter (Feb 02 2021 at 19:27):
Sure thing, added a change request: https://jira.hl7.org/browse/FHIR-30877.
If you already know how that guidance will be clarified, a sneak peek would be appreciated, so that we can support this correctly in FHIR Shorthand. But if some time will be needed to determine what should happen in this situation, no worries, we can wait.
Lloyd McKenzie (Feb 02 2021 at 19:30):
I suspect it'll be something like CodeableConcept and Coding - bindings can technically exist at either level, but should generally be applied at the top one.
Last updated: Apr 12 2022 at 19:14 UTC
