FHIR Chat · IG Publisher Error: Invalid System URI: http://loinc.org · implementers

Stream: implementers

Topic: IG Publisher Error: Invalid System URI: http://loinc.org


view this post on Zulip Max Nakamura (Aug 17 2017 at 20:26):

Hello Grahame,

When I run the latest FHIR Build package, the error "Invalid System URI: http://loinc.org" is being reported for almost all of the compositions.

I am using the latest FHIR Build package from https://github.com/HL7/ccda-on-fhir, and the org.hl7.fhir.igpublisher.jar from http://build.fhir.org/org.hl7.fhir.igpublisher.jar.

However, This directly contradicts the official FHIR documentation, which requires http not https:, as specified in http://hl7.org/fhir/terminologies-systems.html.

Please let me know if you require more details or further clarification on the issue.

Thank you,

Meenaxi Gosai
QA Analyst/Engineer
Lantana Consulting Group
t: 360.450.0545
Maple Ridge—BC PST

www.lantanagroup.com
Blog | Twitter | LinkedIn

view this post on Zulip Rick Geimer (Aug 17 2017 at 20:37):

I think Meenaxi forgot to mention that if you change the URI to "https://loinc.org" in the sample files she is referring to the error goes away, but according to the terminologies-systems page the HTTPS URI is not the correct one.

view this post on Zulip Grahame Grieve (Aug 18 2017 at 02:29):

how do I reproduce this?

view this post on Zulip Rick Geimer (Aug 18 2017 at 16:26):

Run the IG publisher against any IG that has example files with <system value="http://loinc.org"/> in them, then look at the resulting qa.html. Here are two examples:
http://build.fhir.org/ig/HL7/ccda-on-fhir/qa.html
http://build.fhir.org/ig/cqframework/qi-core/qa.html

view this post on Zulip Rick Geimer (Aug 18 2017 at 16:27):

Search for "Invalid System URI" in those qa.html files to see the issue. Meenaxi also discovered that if you try resolving http://loinc.org now, it redirects to https://loinc.org, so that might be part of the issue.

view this post on Zulip Lloyd McKenzie (Aug 18 2017 at 17:08):

The redirect wouldn't be causing the issue. I've had that error before when the issue was the code and not the system - so you might double-check your code and display name. Alternatively, it might be a terminology server problem.

view this post on Zulip Rick Geimer (Aug 18 2017 at 18:24):

@Lloyd McKenzie The codes are valid LOINC codes, and as Meenaxi and I reported above, if you change the system in the example files to https://loinc.org the error goes away. Also, I ran this against an older version of the IG publisher jar file from July 19 and the error does not occur when using that version, so unless it is accessing a different terminology server I'm guessing the bug is in the IG publisher code itself.

view this post on Zulip Lloyd McKenzie (Aug 18 2017 at 18:43):

The error goes away because there isn't special code that looks for "https://loinc.org". There is for "http://loinc.org". (Your problem would go away if you changed to to "http://foo.bar" too :>)

view this post on Zulip Rick Geimer (Aug 18 2017 at 20:14):

@Lloyd McKenzie @Grahame Grieve Might have a clue. I did some debugging locally, and found that on line 629 of org.hl7.fhir.r4.validation.InstanceValidator context.supportsSystem() is returning false for http://loinc.org. It returns true for http://snomed.info/sct, http://hl7.org/fhir/v3/ActClass, etc.

view this post on Zulip Lloyd McKenzie (Aug 19 2017 at 00:18):

Ok. That sounds like there may be an issue with the terminology server


Last updated: Apr 12 2022 at 19:14 UTC