Currently type slicing and value set binding are not differentiated in the FHIR PATH Generation resulting in errors in the Pathengine used in Copy operations
e.g. in the Slicing
cannot be handled.
For that Codesystems, Valuesets, Structuredefinitions have to be initialized in such a way, that correct FHIR PATH String with a system check can be implemented.
For that from the structure definition the correct valueset has to be indentified and then the system urls from the valuesets need to be extracted and checked. Note: We do not check to contents of the valueset, just the allowed system urls
Probably Hapi Validator CLI with its IG loading could help.
Lucas0T
commented
1 month ago
Currently type slicing and value set binding are not differentiated in the FHIR PATH Generation resulting in errors in the Pathengine used in Copy operations e.g. in the Slicing
cannot be handled. For that Codesystems, Valuesets, Structuredefinitions have to be initialized in such a way, that correct FHIR PATH String with a system check can be implemented. For that from the structure definition the correct valueset has to be indentified and then the system urls from the valuesets need to be extracted and checked. Note: We do not check to contents of the valueset, just the allowed system urls
Probably Hapi Validator CLI with its IG loading could help.