Stream: conformance
Topic: Profiling type choices
Chris Grenz (Oct 10 2016 at 21:10):
I just opened GF#12259 based on discussion from the WGM and what I'm finding is inconsistency in the reference servers' handling of constraints on type choice elements. Deeper explanation on my GitHub page here.
Looking for comments either here on in the gForge item as to your current understanding of how this works, especially:
What do you expect to happen if you add an element with path "Patient.deceasedBoolean" to a profile?
1. Does this element's constraints apply only to boolean instances?
2. Are DateTime instances not allowed because of this element?
3. Could an element with path "Patient.deceasedDateTime" also appear in this profile?
4. Should the element with path "Patient.deceased[x]" continue to appear in the snapshot?
Keith Boone (Oct 11 2016 at 19:14):
I virtually slice on deceased[x] in my profile, sometimes having deceasedBoolean if deceased is known, but no date specified, other times adding the more specific deceasedDateTime. That's handled for me in the mapping column, so I don't actually have to use slicing. But my profile supports both, and has both in it. I'm still using spreadsheets though!
Last updated: Apr 12 2022 at 19:14 UTC
