FHIR Chat · Binding polymorphic elements · implementers

Stream: implementers

Topic: Binding polymorphic elements


view this post on Zulip Richard Townley-O'Neill (Feb 13 2020 at 01:46):

I wish to confirm the following.

  • When I have a polymorphic element whose types include CodeableConcept and string (e.g. Observation.value), and I bind the element to a ValueSet, the binding applies to both CodeableConcept values and string values.
  • If I want to bind CodeableConcept values and leave string values unbound, I must slice by type and bind the CodeableConcept slice.

view this post on Zulip Grahame Grieve (Feb 13 2020 at 01:49):

yes and yes

view this post on Zulip Shovan Roy (Feb 13 2020 at 01:51):

@Grahame Grieve , just curious to know why do we have to slice while the options are already provided as a part of Observation.value[x]

view this post on Zulip Grahame Grieve (Feb 13 2020 at 01:56):

if you want to differentiate the bindings?

view this post on Zulip Shovan Roy (Feb 13 2020 at 02:01):

it's may be me, but bit confusing. I think if I want to introduce any binding, I should be able to do that without slicing by just adding binding to a particular type , the allowed types are already provided as a part of value[x] 0..1 carnality

view this post on Zulip Shovan Roy (Feb 13 2020 at 02:02):

pasted image confuses me. confused where the binding gets applied to

view this post on Zulip Grahame Grieve (Feb 13 2020 at 02:05):

you bind the element, not the type

view this post on Zulip Shovan Roy (Feb 13 2020 at 02:13):

thanks @Grahame Grieve , yes, so If I add a binding, that means that binding is applicable to all the selected types as part of value[x] ? can it be a preferred binding or slicing is the only way to solve it ?

view this post on Zulip Grahame Grieve (Feb 13 2020 at 02:26):

yes. slicing is the way


Last updated: Apr 12 2022 at 19:14 UTC