Stream: IG creation
Topic: US core procedure example error
Eric Haas (Dec 01 2020 at 19:51):
for the code in this procedure example:
...
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "24165007",
"display": "Alcoholism counseling"
},
{
"system": "http://www.cms.gov/Medicare/Coding/ICD10",
"code": "HZ30ZZZ",
"display": "Individual Counseling for Substance Abuse Treatment, Cognitive"
}
],
"text": "Alcohol rehabilitation"
},
...
getting this error and this info:
Error: None of the codes provided are in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-procedure-code (http://hl7.org/fhir/us/core/ValueSet/us-core-procedure-code), and a code from this value set is required) (codes = http://snomed.info/sct#24165007, http://www.cms.gov/Medicare/Coding/ICD10#HZ30ZZZ)
Info: Code System URI 'http://www.cms.gov/Medicare/Coding/ICD10' is unknown so the code cannot be validated
Eric Haas (Dec 01 2020 at 19:53):
the code 24165007 is a child of Procedure - so should be valid
The system http://www.cms.gov/Medicare/Coding/ICD10 should be recognized as it is in the HL7 Terminology IG
Lloyd McKenzie (Dec 01 2020 at 23:05):
Why on earth is the terminology IG posting something that's different than what's defined here: http://build.fhir.org/icd.html???
Lloyd McKenzie (Dec 01 2020 at 23:06):
@Grahame Grieve
Grahame Grieve (Dec 02 2020 at 00:14):
Why on earth is the terminology IG posting something that's different than what's defined here
where is it doing that?
Grahame Grieve (Dec 02 2020 at 00:16):
The system http://www.cms.gov/Medicare/Coding/ICD10 should be recognized as it is in the HL7 Terminology IG
well, it's defined there, but it doesn't provide any content, so it's not a basis for the terminology server to know what to do with it
Eric Haas (Dec 02 2020 at 01:18):
I'm pretty sure this is the result of a previous tracker has been vetted by HTA. but this is informative anyway and Is not an issue blocking going to ballot. The Error is however and it has to do with Snomed not being recognized
Lloyd McKenzie (Dec 02 2020 at 02:21):
@Eric Haas Is the HTA asserting anywhere that the canonical URL for ICD is different than what's defined in the core spec, and if so, where?
Grahame Grieve (Dec 02 2020 at 02:21):
no. it's not
Grahame Grieve (Dec 02 2020 at 02:22):
you're confused, because you think that http://www.cms.gov/Medicare/Coding/ICD10 must have something to do with ICD-10, but you'd be wrong. It's got nothing to do with ICD-10 in either structure, scope, or form.
It's procedure codes, not diagnosis codes.
This is your tax dollars at work. ... well, actually, not yours and mine ;-)
Lloyd McKenzie (Dec 02 2020 at 02:27):
If only I could say with confidence that mine are always better used... :)
Robert McClure (Dec 02 2020 at 02:34):
"Meaningful" canonical urls can cut both ways when the CMS folks choose a particularly misleading "meaningful" url. @Lloyd McKenzie this is your love of "meaningful" come back to bite you in the...
Eric Haas (Dec 02 2020 at 02:35):
see https://chat.fhir.org/#narrow/stream/179175-argonaut/topic/ICD-9.20and.20ICD-10.20system.20URIs
Grahame Grieve (Dec 02 2020 at 02:40):
to be fair, @Robert McClure I don't know how much better a non-meaningful name would be on this one - it would point back to something that had the name, and the confusion would start again.
Grahame Grieve (Dec 02 2020 at 03:24):
@Eric Haas:
"binding": {
"strength": "required",
"valueSet": " http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.114222.4.11.837"
}
Grahame Grieve (Dec 02 2020 at 03:24):
the space is a problem
Grahame Grieve (Dec 02 2020 at 03:26):
I see 100s of cases of this
Grahame Grieve (Dec 02 2020 at 03:32):
anyway, this will be fixed next time I release both IG publisher and terminology server. Hopefully within 24 hours
Eric Haas (Dec 02 2020 at 03:35):
(deleted)
John Moehrke (Dec 02 2020 at 13:09):
OIDS are never misleading.. :-)
Eric Haas (Dec 10 2020 at 00:34):
@Grahame Grieve this Warning is still extant:
Procedure/rehab: Procedure.code (l21/c18) warning The code "HZ30ZZZ" is not valid in the system http://www.cms.gov/Medicare/Coding/ICD10 (from http://tx.fhir.org/r4)
Procedure/rehab: Procedure.code.coding[1] (l27/c11) information Code System URI 'http://www.cms.gov/Medicare/Coding/ICD10' is unknown so the code cannot be validated
Grahame Grieve (Dec 10 2020 at 01:25):
right. as far as I know, that is not loaded in tx.fhir.org yet
Eric Haas (Feb 24 2021 at 02:41):
@Rob Hausam is this something you can help us out with?
Rob Hausam (Feb 24 2021 at 05:52):
@Eric Haas Yes, I think I should be able to help. Will need to look further into the details, and make sure that we have an available and reliable source of the codes.
Eric Haas (Jun 09 2021 at 00:23):
@Rob Hausam this is still an issue: see http://build.fhir.org/ig/HL7/US-Core/qa.html
Eric Haas (Jun 09 2021 at 00:23):
Eric Haas (Jun 09 2021 at 00:25):
Is this something that we can get fixed within next 2 weeks?
Rob Hausam (Jun 09 2021 at 01:05):
Thanks for the ping on it, Eric. Yes, it seems reasonable to have it ready within 2 weeks. It appears that a usable source should be available. Then the primary steps are (1) tranform that content to a FHIR resource and commit it to the packages repo and (2) get the packages updated and loaded on tx.fhir.org (currently done by Grahame).
Eric Haas (Jun 09 2021 at 01:13):
tranform that content to a FHIR resource
if you give me the source file ( hoping in csv or spreadsheet ) I can do the transform asap
and then you can review expecially the metadata..
Rob Hausam (Jun 09 2021 at 02:05):
I appreciate the offer, @Eric Haas. But first we have to make sure that we have identified usable (hopefully optimal) source file(s). I'm stating that as plural, as my prior experience with ICD flavors is that multiple files have usually been required and need to be combined appropriately to do the transformation. Technically ICD-10-PCS isn't really "ICD-10", but the source files may fall into a similar pattern. We'll have to check that out. Then we'll want the transformation (hopefully) to be a reasonably reproducible and not too tedious process that can be used for needed future maintenance. When we're at that point if you want to help to create that process, that's great.
Last updated: Apr 12 2022 at 19:14 UTC
