We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reported by Dorothy Lee:
For example, a code D0120 from value set “Clinical Oral Evaluation”, if retrieved from VSAC API (https://cts.nlm.nih.gov/fhir/res/ValueSet/2.16.840.1.113883.3.464.1003.125.12.1003/$expand), would have a code system “http://www.ada.org/cdt”. But what you have in the repo (https://github.com/cqframework/ecqm-content-qicore-2024/blob/main/input/vocabulary/valueset/external/valueset-2.16.840.1.113883.3.464.1003.125.12.1003.json) has a code system “http://terminology.hl7.org/CodeSystem/CD2”.
The text was updated successfully, but these errors were encountered:
Yeah I fixed that valueset and entered a bug on the tooling because it set that URL as a part of the VSAC XLS extraction of valuesets
Sorry, something went wrong.
Oh, it's a tooling bug? That's good, the extraction is remapping it. Is the same thing happening with the SOP codesystem?
probably the tooling currently has this for SOP
case "SOP": return "urn:oid:2.16.840.1.113883.3.221.5";
might be worth reviewing all URLs in that code for extraction of valuesets
No branches or pull requests
Reported by Dorothy Lee:
For example, a code D0120 from value set “Clinical Oral Evaluation”, if retrieved from VSAC API (https://cts.nlm.nih.gov/fhir/res/ValueSet/2.16.840.1.113883.3.464.1003.125.12.1003/$expand), would have a code system “http://www.ada.org/cdt”. But what you have in the repo (https://github.com/cqframework/ecqm-content-qicore-2024/blob/main/input/vocabulary/valueset/external/valueset-2.16.840.1.113883.3.464.1003.125.12.1003.json) has a code system “http://terminology.hl7.org/CodeSystem/CD2”.
The text was updated successfully, but these errors were encountered: