hl7dk / dk-core

7 stars 6 forks source link

Error in the QA-report #89

Closed tmsMedcom closed 4 months ago

tmsMedcom commented 1 year ago

Currently we have the following error in the QA-report. We are waiting on HL7 to do some fixes, before we can solve it. Milestone is set to the next release.

"This code DOES exist and is published by IEEE. But somehow the code system tooling missed it along the way

ERROR: Bundle/ContinuaBundleWithDevice: Bundle.entry[7].resource/Observation/BloodPressureStatus.Poul.133527/.code.coding[0]: Local Error: Resolved system urn:iso:std:iso:11073:10101 (v2.0.1), but the definition is not complete. Server Error: The code "8410608" is not valid in the system urn:iso:std:iso:11073:10101; The code provided (urn:iso:std:iso:11073:10101#8410608) is not valid in the value set 'All codes known to the system' (from http://tx.fhir.org/r4) for 'urn:iso:std:iso:11073:10101#8410608' (0 uses)"

jacand commented 1 year ago

Progress can be monitored on Zulip in this thread: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Missing.20MDC.20code Status as of today: A new RTMMS terminology server for the IEEE codes was launched last week here http://rtmms.nist.gov/ and I can confirm that the missing code has been added to this server. According to the Zulip thread, Grahame is working with Michael Faughn to synchronize the FHIR terminology service with this new server. So at this point, we are waiting for them to do some background magic.

jacand commented 1 year ago

I have poked Grahame and Michael on Zulip, asking for progress. Apparently the thread died in May and no progress happened since then...

jacand commented 12 months ago

The solution should be in the pipes: https://github.com/FHIR/packages/pull/14 https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Missing.20MDC.20code

jacand commented 10 months ago

@tmsMedcom @jkiddo Poked Grahame again on Zulip. He answered that he will try to get it done this week. https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Missing.20MDC.20code

tmsMedcom commented 9 months ago

@jacand Do you know if the issue has been fixed?

jacand commented 9 months ago

Doesn't look like it. After I asked Grahame a month ago, he answered that he needed to upgrade the server. Later in the same stream he says that the entire CI pipeline is broken and needs fixing. And then later he comes back and says that a code signing certificate was lost when changing to a different computer. So I guess he is on it but has his hands full... @tmsMedcom

tmsMedcom commented 9 months ago

Of course - should we postponed the issue, @jacand?

jacand commented 9 months ago

As long as it is not critical and things blow up, I would just wait it out. Perhaps remind him again early next year. But this situation confirms the need to ensure that terminology hosting is properly funded and governed - as we discussed on the meeting last week regarding Snomed translations...

tmsMedcom commented 5 months ago

@jacand is there any news around this issue?

jacand commented 5 months ago

@tmsMedcom As far as I can tell, it has been resolved. Can you confirm that the error has disappeared (and close the issue if that is the case)? The following lookup yields a result, and the problem was that it didn't: https://tx.fhir.org/r4/CodeSystem/$lookup?system=urn:iso:std:iso:11073:10101&code=8410608

tmsMedcom commented 5 months ago

@jacand Great, it seems to be solved in the latest build of the IG.