0.1.0-current - ci-build International flag

JohnMoehrkeTestDicom, published by John Moehrke (himself). This guide is not an authorized publication; it is the continuous build for version 0.1.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/JohnMoehrke/testDicom/ and changes regularly. See the Directory of published versions

Home

Official URL: http://johnmoehrke.github.io/testDicom/ImplementationGuide/johnmoehrke.testdicom.example Version: 0.1.0-current
Draft as of 2024-08-28 Computable Name: JohnMoehrkeTestDicom

testDicom

This creates and example ImagingStudy with two valueSets. One assembles some DICOM codes. The other calls for pulling in a DICOM valueset.

Note this IG is depending on the fhir.dicom IG so as to have access to DICOM defined vocabulary published within. See http://fhir.org/packages/fhir.dicom/

success

  • valueSet made up of some DICOM Modalities
    • build success. as expected
  • expansion valueSet made up of all modalities in a DICOM defined valueSet
    • build expands the valueset success.
  • example using valid DICOM code, but not a modality
    • build rightly complains that this is not a valid code in the valueSet. success
    • The Coding provided (http://dicom.nema.org/resources/ontology/DCM#PRINT) is not in the value set http://johnmoehrke.github.io/testDicom/ValueSet/JustModalitiesVS, and a code is required from this value set. (error message = Not in value set http://johnmoehrke.github.io/testDicom/ValueSet/JustModalitiesVS ([]))

warnings

  • profile trivial is used to show that there are two warnings the IG publisher throws regardless of the profiling. These warnings are not related to the scope of this test IG, but do show some issue with ImagingStudy in FHIR core. –> Thus these are put in the ignore warnings.
    • The valueSet reference http://www.rsna.org/RadLex_Playbook.aspx on element ImagingStudy.procedureCode could not be resolved
    • The valueSet reference http://dicom.nema.org/medical/dicom/current/output/chtml/part04/sect_B.5.html#table_B.5-1 on element ImagingStudy.series.instance.sopClass could not be resolved
  • profile using internal valueSets
  • profile using dicom valueSets

DICOM recognized URI for SOP Class

Note that http://dicom.nema.org/resources/ontology/DCMUID should be used in FHIR R4 on sopClass as the .system value when using a DICOM recognized SOP Class UID.

Grahame says these are okay

  • profile binding the .modality to the DICOM defined valueSet
    • why can't this show a valueSet, where as it is just a link to DICOM
  • example using valid code, but with profile using valueSets
    • build complains that the valid code is not in the given valueset…
      • note that the valueSet does expand now
    • The Coding provided (http://dicom.nema.org/resources/ontology/DCM#AR) is in the expansion value set http://johnmoehrke.github.io/testDicom/ValueSet/JustModalitiesVS, and a code is required from this value set. (error message = The Coding provided (http://dicom.nema.org/resources/ontology/DCM#AR) is not in the value set http://johnmoehrke.github.io/testDicom/ValueSet/JustModalitiesVS, and a code is required from this value set….)

FHIR core use of DICOM codes

added AuditEvent, Provenance, and Consent – as they all use the ValueSet that has DICOM codes in them. These work without issues if you include a dependency on fhir.dicom; but in R5 give warnings if you do not. Given this IG needs fhir.dicom, they are here to show everything without warnings.

IG builder analysis

Cross Version Analysis

Dependency Table

IGPackageFHIRComment
.. JohnMoehrkeTestDicomjohnmoehrke.testdicom.example#0.1.0-currentR5
... HL7 Terminology (THO)hl7.terminology.r5#6.0.2R5Automatically added as a dependency - all IGs depend on HL7 Terminology
... FHIR Extensions Packhl7.fhir.uv.extensions.r5#5.1.0R5Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
... fhir.dicom#2024.2.20240331R4

Package hl7.fhir.uv.extensions.r5#5.1.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.