FHIR Chat · terminology oddity · IG creation

Stream: IG creation

Topic: terminology oddity


view this post on Zulip John Moehrke (Jun 18 2021 at 16:18):

The new IG publisher is complaining about DICOM display values in a confusing way. It says it is wrong and gives me the right ones that are the ones I am using...

The display "Export" is not a valid display for the code {http://dicom.nema.org/resources/ontology/DCM}110106 - should be one of [Export] (from http://tx.fhir.org/r4) for 'http://dicom.nema.org/resources/ontology/DCM#110106'

view this post on Zulip David Simons (Jun 21 2021 at 19:33):

Hi @John Moehrke - as a side question - do you access http://dicom.nema.org/resources/ontology/DCM from tx.fhir.org?

Asking because I am getting this HL7 Validation warning, using that system, plus "MR" as code.
Warning @ ImagingStudy.modalityList[0] (line 20, col17) : Could not confirm that the codes provided are in the value set http://hl7.org/fhir/ValueSet/dicom-cid29, and a code should come from this value set unless it has no suitable code (the validator cannot judge what is suitable)

view this post on Zulip John Moehrke (Jun 21 2021 at 19:34):

I suspect I do. I am just running the IG publisher.

view this post on Zulip John Moehrke (Jun 21 2021 at 19:35):

I do have some DICOM codes that are not throwing that warning. (like AuditEvent.type valueset)

view this post on Zulip David Simons (Jun 21 2021 at 19:36):

Thank you :) Each of such warnings is a quest ;)

view this post on Zulip David Simons (Jun 21 2021 at 19:37):

PS: your original "terminology odditity on the display string" was resolved by tx.fhir.org update, right?
(per https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/code.20display.20term.20warnings )

view this post on Zulip John Moehrke (Jun 21 2021 at 19:42):

yes

view this post on Zulip Lloyd McKenzie (Jun 25 2021 at 03:04):

@John Moehrke Is there an IG that @Grahame Grieve or @Mark Iantorno can look at to see the issue?

view this post on Zulip David Simons (Jun 25 2021 at 12:00):

From our end this resolved itself - may have been a timeout on tx.fhir.org
GET: http://tx.fhir.org/r3/CodeSystem/dicom-dcim
GET: http://tx.fhir.org/r3/ValueSet/dicom-cid29

view this post on Zulip John Moehrke (Jun 25 2021 at 12:03):

I agree. It has magically resolved (I noted that on other threads that I had started)

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:03):

If you ever want to know if the terminology server is up or down, go to validator.fhir.org and look at the top right of the screen

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:03):

there are two little indicators, one for tx.fhir.org

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:04):

and one for packages2.fhir.org

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:04):

if they are green, then the site is up

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:04):

if the are spinning grey, but not green, the site is slow

view this post on Zulip Mark Iantorno (Jun 28 2021 at 13:04):

if they are pink/red, the site is down

view this post on Zulip Lloyd McKenzie (Jun 28 2021 at 15:51):

I think you mean "if they are green, the site is up"? :smile:

view this post on Zulip Mark Iantorno (Jun 28 2021 at 19:47):

Fixed sorry


Last updated: Apr 12 2022 at 19:14 UTC