Stream: implementers
Topic: Help...extensible binding and repeating elements oh my!!
Eric Haas (Feb 15 2017 at 00:03):
In my IG am struggling how to represent an extensible binding for a codeableConcept type element that repeats:
- Slicing works (kind of ) for required bindings but not for extensible bindings
- I tried a FHIRPath invariant with a warning (see below) which is what I would like but I can't validate that it will work.
Condition.where(category in 'http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category').exists()
Other suggestions?
Grahame Grieve (Feb 15 2017 at 01:44):
an extensible binding on a repating element sounds veyr straight forward, so I am assuming that there's something you haven't told us here
Eric Haas (Feb 15 2017 at 02:27):
As we discussed before the extensible binding would apply to each repeat of the codeableconcept unless you can slice it. but according to this " Note: At present, only a fixed value or a required value set should be used for slicing;" and my invariant does not seem to work. I would like to know if I have misunderstood something here.
Grahame Grieve (Feb 15 2017 at 02:28):
do you want only the first category to be subject to the extensible binding?
Eric Haas (Feb 15 2017 at 02:29):
To clarify I would like valueset "A" to be used at least once. Another value from a nother valueset may be used in another repeat assuming orthogonal categorizations in this case.
Eric Haas (Feb 15 2017 at 02:29):
Yes
Grahame Grieve (Feb 15 2017 at 02:30):
well, you can slice by index, and make the first slice required. That makes re-profiling that element hard though. Or you can use your invariant. Are you making this constraint in the resource, or in a profile?
Eric Haas (Feb 15 2017 at 15:27):
For a profile, but after further consideration, I relaxed the binding to 'prefered' in this instance. For future reference if I were to use an invariant is this correct ( and I may still use it as a best practice warning).
Condition.where(category in '[some valueset url]').exists()
Grahame Grieve (Feb 15 2017 at 18:07):
yes
Last updated: Apr 12 2022 at 19:14 UTC
