Stream: committers
Topic: Build failing on claim/valueset-icd-10.xml?
Jean Duteau (Jun 25 2019 at 17:08):
I'm getting a build failure on the file claim/valueset-icd-10.xml. There appear to be a number of codes in that file that aren't valid icd-10 codes:
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '123456' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '123457' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '987654' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '123987' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '112233' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '997755' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
[java] ERROR @ fm:ValueSet[icd-10].compose.include[1]: The code '321789' is not valid in the system http://hl7.org/fhir/sid/icd-10 (2)
Rob Hausam (Jun 25 2019 at 17:19):
I think this is partly the result of some terminology server work that I'm doing. Previously the terminology server only had support for the Vietnamese variant of ICD-10 (don't ask why!). We had an error in IPS due to that which I had to work around. I've been working with Grahame on the general terminology server update process, and we can now add and support additional ICD-10 variants. The problem is that it's not generally straightforward to get an entire list of the codes for a particular ICD-10 variant (including the "base" ICD-10 variant from WHO). At the moment (within the past hour or so) I've added a small set of "base" ICD-10 codes (for system url http://hl7.org/fhir/sid/icd-10). The downside of doing that is that the validator now starts trying to validate codes with that system url and it will only recognize the codes in that limited set (until others are added). So there are several potential solutions that I can see. Maybe the easiest would be for you to give me the set of codes that you want to be able to validate and I will add them for now (that will likely work unless it's a huge set). The better long-term solution, of course, is to get the full set of ICD-10 codes prepared in a usable format for importing and have the terminology service and therefore also the validator support all of them.
Rob Hausam (Jun 25 2019 at 17:21):
@Jean Duteau And as you've noted, none of the codes that you listed above are valid ICD-10 codes - so whatever we do you will eventually need to decide what valid codes you want to replace them with (and we'll make sure the server supports them).
Jean Duteau (Jun 25 2019 at 17:23):
@Rob Hausam The file I listed isn't mine - it's part of the build so we'll need FM to make some changes (or we'll need to do it for them in the interim).
Rob Hausam (Jun 25 2019 at 17:28):
OK. I can help FM with cleaning that up to make sure at least the build works.
Rob Hausam (Jun 25 2019 at 17:45):
I should have a fix for it ready soon.
Rob Hausam (Jun 26 2019 at 07:20):
finally fixed!
Last updated: Apr 12 2022 at 19:14 UTC
