Stream: implementers
Topic: Binding strengths best practice
Robin Bosman (Jul 01 2019 at 08:05):
Some base profiles have valuesets with a binding strength of 'extensible'.
Let's say in my profile based on that base profile I want to make it clear that when the code cannot be found in the base valueset it shall come from a specific other valueset/codesystem. What is the best practice?
Do I create a new valueset for my profile including the ones from the original valueset + the codes from that other system?
Lloyd McKenzie (Jul 01 2019 at 14:18):
You can declare a 'max' binding - it identifies where additional codes are permitted to come from. The extension is here: http://build.fhir.org/extension-elementdefinition-maxvalueset.html
Robin Bosman (Jul 02 2019 at 12:23):
Did not know that one, it will come in handy - tx!
Michael Lawley (Jul 03 2019 at 23:37):
I think it's a real shame this is an extension - it's not very well known, but it's use can quite dramatically shift the thinking of people building associated ValueSets and doing the binding.
David Hay (Jul 03 2019 at 23:47):
Perhaps a link from the SD page: http://build.fhir.org/structuredefinition-profiles.html ?
Grahame Grieve (Jul 04 2019 at 00:01):
it's a candidate for a core property. but you'd have to show that it meets the criteria
Last updated: Apr 12 2022 at 19:14 UTC
