Closed varshini39 closed 1 year ago
Is then when running the g10 suite or the US Core suite?
Is then when running the g10 suite or the US Core suite?
This error occurs in both view.
Could you provide me with a link to test session where this is occurring in the g10 suite?
Could you provide me with a link to test session where this is occurring in the g10 suite?
Here is the link for US core v3.1.1, where we are facing this issue. https://inferno.healthit.gov/suites/test_sessions/a45ddd43-566a-45ec-b75d-cc61f302fece#us_core_v311-us_core_v311_encounter
Terminology validation in the US Core suite is performed by tx.fhir.org
, which we do not control. You can report issues with tx.fhir.org
in zulip: https://chat.fhir.org/#narrow/stream/179202-terminology
The g10 suite uses a different method for terminology validation. Please let us know if you see a similar error when running the g10 suite.
Running this query on tx.fhir.org (http://tx.fhir.org/r4/CodeSystem/$validate-code?code=453701000124103&system=http://snomed.info/sct) returns the same error.
Running this query on tx.fhir.org (http://tx.fhir.org/r4/CodeSystem/$validate-code?code=453701000124103&system=http://snomed.info/sct) returns the same error.
So is this code not valid anymore? Also I have local setup of this tool, in that the error is not shown. So can you please tell me why both are having different response?
What do you mean "local setup"?
The code is valid. It could be the server does not have the latest SNOME CT update.
What do you mean "local setup"?
The code is valid. It could be the server does not have the latest SNOME CT update.
I have downloaded the test kit from this https://github.com/onc-healthit/onc-certification-g10-test-kit/releases and running it in my machine. I didn't get this issue in that, but I'm getting the error in live. Any reason why there is different response for both?
onc-certification-g10-test-kit has its own terminology validation and it does not use tx.fhir.org.
Recently after the tool was updated to v.0.3.2, there is an issue in encounter type, where one of the snomed codes isn't getting passed.
Here is the "type" value for encounter:
"type": [ { "coding": [ { "system": "http://snomed.info/sct", "code": "453701000124103", "display": "In-person encounter" } ], "text": "In-person encounter" } ],
For this, I'm getting the error as below:
I have also verified with the latest snomed codes, that this code "453701000124103" is valid one and this issue occurred only after the tool got updated to v.0.3.2 and not in previous version.
Please look into this and let us know.