Skip to content
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

Validation error: CareTeam.participant.role not valid but role is valid and removing the role to retest, tool continues to report the deleted role code #94

Open
rberge opened this issue Aug 31, 2022 · 2 comments

Comments

@rberge
Copy link

rberge commented Aug 31, 2022

ValidatorErrors-codeNotInFile

"system": "http://snomed.info/sct", "version": "http://snomed.info/sct/731000124108/version/20220301", "filter": [ { "property": "concept", "op": "=", "value": "768734005" } ]
However it is reported by the validator as invalid

CareTeam.participant[2].role[0]: Error from server: The filter "concept = 768734005" from the value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1099.27 was not understood in the context of http://snomed.info/sct
That is the first error.
After experiencing that error, I switch to a different SCT code in the same file, but got the same error for code 768734005. After that, i started a new Safari tab to retest and got the same result. Then i started Google Chrome and tested there, using only the default us core care team example without changing the role sct code. That validation gives the same error four times for code 7687... even though i am not using that code in the file being validated.

ValidatorErrors-code

@yunwwang
Copy link

yunwwang commented Sep 1, 2022

Inferno validator uses tx.fhir.org to do terminology validation. This is a known issue on tx.fhir.org. Please see the discussion here: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/SNOMED.20.22.3D.22.20operation

@rberge
Copy link
Author

rberge commented Sep 1, 2022

I wasn't sure if that was the same issue with the terminology. But there are two issues here. The other issue is that the resource I was validating did not have that code in it. I switched to a different app to test this.

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

No branches or pull requests

2 participants