FHIR Chat · RatioRange and CodeableReference in choice types · implementers

Stream: implementers

Topic: RatioRange and CodeableReference in choice types


view this post on Zulip Lee Surprenant (Dec 08 2021 at 13:51):

R4B introduces new data types RatioRange and CodeableReference, but the list at https://build.fhir.org/branches/R4B/datatypes.html#open is not updated to include them.

RatioRange is already used as a choice type in Ingredient, so I assume they can both be used as extension values and that list should be updated to include them.

view this post on Zulip Lee Surprenant (Dec 08 2021 at 13:54):

Additionally, wherever the conformance resources (e.g. the ones you get from https://build.fhir.org/branches/R4B/downloads.html) list the set of allowed types, I think these two new types should be added.

view this post on Zulip Lee Surprenant (Dec 08 2021 at 14:00):

I also noticed something unusual while looking into this one:

Task.input.value[x] (https://build.fhir.org/branches/R4B/task-definitions.html#Task.input.value_x_) and Task.output.value[x] seems to enumerate all the different allowed types. Should those just be an "open" types (*) instead?

For example, like: https://build.fhir.org/branches/R4B/elementdefinition-definitions.html#ElementDefinition.defaultValue_x_

Interestingly, it seems like the "open" choice types end up with the expanded list of types in the actual conformance artifacts, so its just some display sugar I guess.
Both cases are missing the new data types.

view this post on Zulip Lee Surprenant (Dec 08 2021 at 17:49):

Another spot that probably needs changing if the new types are allowed in "open" choice types: https://build.fhir.org/branches/R4B/extensibility.html#list

view this post on Zulip Lee Surprenant (Dec 08 2021 at 17:50):

Also, I've always wondered, is that list different than https://build.fhir.org/branches/R4B/datatypes.html#open ? Maybe better just to maintain that list in one spot?

view this post on Zulip Lee Surprenant (Dec 10 2021 at 22:33):

I've opened FHIR#34453 for this one.

view this post on Zulip Grahame Grieve (Dec 14 2021 at 05:11):

fixed in R4B and R5

view this post on Zulip Grahame Grieve (Dec 14 2021 at 05:11):

the code maintains it in one place internally

view this post on Zulip Lee Surprenant (Jan 24 2022 at 22:15):

looks like this change will need to be backed out for R4B based on the new resolution posted to https://jira.hl7.org/browse/FHIR-34453 ...

view this post on Zulip Lee Surprenant (Jan 24 2022 at 22:23):

but I'm confused about how we could say its not an allowed choice type when its explicitly listed as a choice type in https://build.fhir.org/branches/R4B/ingredient.html

view this post on Zulip Lloyd McKenzie (Jan 25 2022 at 00:37):

Sorry, it SHOULD be a choice type. It can't be an extension type. We don't have to worry about choice types breaking anything because the only place they can be used is in the new/changed resources.

view this post on Zulip Lee Surprenant (Jan 25 2022 at 12:31):

ah, that wasn't clear to me from the resolution text at all. agree it makes sense, although
it sounds like a fun one given that grahame mentioned above that the two lists currently come from a single place


Last updated: Apr 12 2022 at 19:14 UTC