web stats
Mapping DICOM tags to FHIR - Mirth Community

Go Back   Mirth Community > Mirth Connect > General Discussion

Reply
 
Thread Tools Display Modes
  #1  
Old 11-13-2018, 12:19 PM
hsedidn hsedidn is offline
What's HL7?
 
Join Date: Nov 2018
Posts: 2
hsedidn is on a distinguished road
Lightbulb Mapping DICOM tags to FHIR

Dicom-File-Format


Dicom-Meta-Information-Header


Used TransferSyntax: LittleEndianExplicit
(0002,0000) UL 182 # 4, 1 MetaElementGroupLength
(0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion
(0002,0002) UI =CTImageStorage # 26, 1 MediaStorageSOPClassUID
(0002,0003) UI 1.3.12.2.1107.5.1.1.20377.20031125114113176.4 # 46, 1 MediaStorageSOPInstanceUID
(0002,0010) UI =LittleEndianImplicit # 18, 1 TransferSyntaxUID
(0002,0012) UI 1.2.826.0.1.3680043.2.93.0.99 # 30, 1 ImplementationClassUID
(0002,0013) SH ERAD_60 # 8, 1 ImplementationVersionName


Dicom-Data-Set


Used TransferSyntax: LittleEndianImplicit
(0008,0005) CS ISO_IR 100 # 10, 1 SpecificCharacterSet
(0008,0008) CS ORIGINAL\PRIMARY\LOCALIZER\CT_SOM4 TOP # 38, 4 ImageType
(0008,0016) UI =CTImageStorage # 26, 1 SOPClassUID
(0008,0018) UI 1.3.12.2.1107.5.1.1.20377.20031125114113176.4 # 46, 1 SOPInstanceUID
(0008,0020) DA 20031125 # 8, 1 StudyDate
(0008,0021) DA 20031125 # 8, 1 SeriesDate
(0008,0022) DA 20031125 # 8, 1 AcquisitionDate
(0008,0023) DA 20031125 # 8, 1 ContentDate
(0008,0030) TM 113945.000000 # 14, 1 StudyTime
(0008,0031) TM 114003.384000 # 14, 1 SeriesTime
(0008,0032) TM 114109.299000 # 14, 1 AcquisitionTime
(0008,0033) TM 114109.299000 # 14, 1 ContentTime
(0008,0040) US 0 # 2, 1 ACR_NEMA_OldDataSetType
(0008,0041) LO IMA TOPO # 8, 1 ACR_NEMA_DataSetSubtype
(0008,0060) CS CT # 2, 1 Modality
(0008,1090) LO SOMATOM PLUS 4 # 14, 1 ManufacturersModelName


Key to Dicom-File-Format

•The first column contains the DICOM tags.
•The second column contains the actual content (prefixed by data type).
•The third column contains the actual number of characters belonging.
•The fourth column tells if the actual field has more than one data contained (these are back slash-separated like in the second row) and the official DICOM name of the field.

The DICOM standard has specific names for the different DICOM tags or data or DICOM field identified by a certain pair of tags. For instance (0008,0060) is the tag identifying the DICOM field called Modality. The content of this field above is CT. Another example is the StudyDate being the official name of the field containing the actual date of the study: the tag is (0008,0020) and the content above is 20031006, that is November 6, 2003.

I created an Azure Function App that decodes the tags and saves them to a no-SQL repository, in this case, Azure Cosmos DB

The source code is written in C#.

See the attached pdf.
Attached Files
File Type: pdf anatomy of a Dicom file.pdf (1.58 MB, 4 views)
Reply With Quote
Reply

Tags
azure vm, database destination, dicom/hl7, fhir channel

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 01:44 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation