Stream: implementers
Topic: empty codesystems in a valueset
Robin Bosman (Apr 06 2020 at 15:24):
Hi, I have a couple of CodeSytems that are for now empty of values (content: not-present). These CodeSystem are all in 1 Valueset so the ValueSet contains multiple codesystems but all these codesystems are basically empty.
I noticed when I use this Valueset in a profile (with whatever binding) and do a test with a validator (I use Hapi): it will always give some 'Warning' to say the codes are not known or something.
I would actually expect that when a codesystem declares its content as 'not-present' it would always be OK whatever value I would declare in my example to be part of it.
Is there a better way to say in a profile I want a codeableConcept to use a CodeSystem from a certain list of CodeSystems while ignoring the actual value of the code?
Lloyd McKenzie (Apr 06 2020 at 15:26):
'not-present' means that there are codes in existence, but not exposed in the resource. That means that from a validation perspective, the validator can't tell whether a given code is a legal code or not. It doesn't treat them as errors, but it does raise a warning that effectively says "these codes may or may not be valid - the validator can't tell. A human should double-check them"
Lloyd McKenzie (Apr 06 2020 at 15:27):
There is no way to have the validator not raise a warning other than to actually define the codes and have the codes in your instance match one of those codes.
Robin Bosman (Apr 06 2020 at 15:32):
Thanks, that indeed makes a lot of sense!
Last updated: Apr 12 2022 at 19:14 UTC
