Stream: terminology
Topic: Code System $validate-code Operation
Peter Jordan (Dec 21 2017 at 05:21):
Why are the relevant sections in the spec, for this new operation on the CodeSystem resource, called "Value Set based Validation? e.g. http://build.fhir.org/operationslist.html and http://build.fhir.org/codesystem-operations.html#validate-code
Grahame Grieve (Dec 21 2017 at 05:25):
copy paste error- one of the last things I did in the tx space. thought I got all the value set bits. sorry
Peter Jordan (Dec 21 2017 at 05:43):
Guessed as much - but it's good news that this operation has been added and (hopefully @Richard Ettema) we can test it at the New Orleans Connectathon.
Richard Ettema (Dec 21 2017 at 15:54):
@Peter Jordan We'll be adding support for the FHIR R4 Ballot version (v3.2.0) over the next few days to Touchstone. After that, we can update the existing $validate-code TestScripts for Connectathon 17.
Peter Jordan (Dec 21 2017 at 20:17):
@Richard Ettema - as the $validate-code operation on the ValueSet remains, we need to clone those Test Scripts and adapt them to run against the CodeSystem resource. Obviously, some of the In Parameters vary, but the Out Parameters are the same.
Michael Lawley (Dec 22 2017 at 02:38):
I would love to see tests for CodeSystem.supplements and ConceptMap.unmapped - there seem to be big gaps in their specification
Peter Jordan (Dec 22 2017 at 08:45):
Do you have any good examples that AEGIS might be able to use to create Test Scripts?
Michael Lawley (Dec 22 2017 at 22:40):
Not for CodeSystem.supplements. This is a late inclusion I have only just discovered. I believe it is too immature and insufficiently documented for normative status and have created GF#14356 to request it be demoted to Trial Use.
For ConceptMap.unmapped we've not yet implemented or concretely explored the space, but there's some simple edge cases that could be explored -- cyclic references, etc
Last updated: Apr 12 2022 at 19:14 UTC
