Skip to content

Internal Terminology Server: Add an warning if an intensional ValueSet cannot be expanded #303

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
oliveregger opened this issue Oct 28, 2024 · 3 comments · Fixed by #314
Closed
Assignees

Comments

@oliveregger
Copy link
Member

When validating with the internal terminology server it would be nice if we could get an information message that the ValueSet could not be validated.

with tx.fhir.org we get the error message: None of the codings provided are in the value set 'Caveat Condition' (http://fhir.ch/ig/ch-rad-order/ValueSet/ch-rad-order-caveat-condition|2.0.0-ballot), and a coding from this value set is required) (codes = http://snomed.info/sct#444444444)"

@oliveregger
Copy link
Member Author

there is a second error message for tx.fhir.org: Unknown code '444444444' in the CodeSystem 'http://snomed.info/sct' version 'http://snomed.info/sct/900000000000207008/version/20240801' | Condition.code.coding[0].code for tx.fhir.org, but the internal terminology server will not verify snomed ct / loinc etc.

@oliveregger
Copy link
Member Author

if you click on one of the matchbox links above it would be nice to see a 'in-progress' in the gui.

@qligier
Copy link
Member

qligier commented Nov 14, 2024

if you click on one of the matchbox links above it would be nice to see a 'in-progress' in the gui.

Done.

When validating with the internal terminology server it would be nice if we could get an information message that the ValueSet could not be validated.
with tx.fhir.org we get the error message: None of the codings provided are in the value set 'Caveat Condition' (http://fhir.ch/ig/ch-rad-order/ValueSet/ch-rad-order-caveat-condition|2.0.0-ballot), and a coding from this value set is required) (codes = http://snomed.info/sct#444444444)"

I have to spend more time on this. When our terminology server returns an additional OperationOutcome, the issues are discarded, not added to the response.
The validation issue seems to be crafted from the type of error returned by the terminology server, most probably in BaseWorkerContext.processValidationResult().

@qligier qligier linked a pull request Nov 21, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants