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-04-11 Computable Name: JohnMoehrkeTestDicom

testDicom

This creates and example AuditEvent 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

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….)

IG builder analysis

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (johnmoehrke.testdicom.example.r4) and R4B (johnmoehrke.testdicom.example.r4b) are available.

Dependency Table

IGPackageFHIRComment
.. JohnMoehrkeTestDicomjohnmoehrke.testdicom.example#0.1.0-currentR4
... HL7 Terminology (THO)hl7.terminology.r4#5.3.0R4Automatically added as a dependency - all IGs depend on HL7 Terminology
... FHIR Extensions Packhl7.fhir.uv.extensions.r4#1.0.0R4Automatically added as a dependency - all IGs depend on the HL7 Extension Pack
... fhir.dicom#2024.2.20240331R4

Package hl7.fhir.uv.extensions.r4#1.0.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.