Stream: terminology
Topic: Expanding valueset importing a non-existent codesysetm
Michael Calderero (Oct 31 2019 at 08:20):
Hi All - what should be the behavior of the $expand operation if it expands a valueset and the valueset has a compose.include on a codesystem that does not exist in the FHIR server?
Take for example http://build.fhir.org/immunization-definitions.html#Immunization.vaccineCode, which has EXAMPLE binding on http://build.fhir.org/valueset-vaccine-code.html. This valueset imports urn:oid:1.2.36.1.2001.1005.17, which doesn't exist in our FHIR server and I can't find a ready-to-use CodeSystem for it.
The logic for expanding valuesets (i.e. http://build.fhir.org/valueset.html#expansion) only has to say about this:
Otherwise: For each compose.include:
If there is a system, identify the correct version of the code system, and then:
If there are no codes or filters, add every code in the code system to the result set.
If codes are listed, check that they are valid, and check their active status, and if ok, add them to the result set (the parameters to the $expand operation may be used to control whether active codes are included).
I'm assuming the "check that they are valid" part means looking up if the code exists in the codesystem.
1. If the code doesn't exist in the codesystem, does the $expand operation fail with an OperationOutcome? Or the code is just not included?
2. If the codesystem itself is not found, does the $expand operation fail with an OperationOutcome? Or all the codes the valueset listed under that codesystem are just not included?
Grahame Grieve (Oct 31 2019 at 11:02):
I think it should be an error
Last updated: Apr 12 2022 at 19:14 UTC
