Stream: implementers
Topic: DICOM -> ImagingStudy
Shantha Andrews (Aug 17 2019 at 14:42):
This is the first time post, please guide me if this is not the right forum / etiquette !
Im trying to sync an Upstream DICOM instances to the local DICOM server for a given patient (ID). ie. Bring all the studies, series and instances. Also converting the study into ImagingStudy metadata object, basically converting the DICOM Tags. My question is
(1) how / where do I store the Patient Infromation in ImagingStudy ? "subject"? The mapping as described in the resouce is " subject (0010/*)" . can someone help me with the JSON that will be pushed into the subject ?
These are the fields of interest
"patientName": "{{ study.random_dicom.read_property("0x10", "0x10") }}",
"patientID": "{{ study.random_dicom.read_property("0x10", "0x20") }}",
"patientBirthDate": "{{ study.random_dicom.read_property("0x10", "0x30") }}",
"patientSex": "{{ study.random_dicom.read_property("0x10", "0x40") }}",
"patientAddress": "{{ study.random_dicom.read_property("0x10", "0x1040") }}"
(2) If the patient is not available in the downstream server, what should be workflow that I should adopt to create the patient?
John Moehrke (Aug 18 2019 at 17:04):
Yes you use the Patient resource.... Hmm, there should be a DICOM mapping in the Patient resource. Could you make a Change Request (CR) to add this to Patient. Your guess right now is a good start. Others from the Imaging Workgroup will help with details -- @Elliot Silver @Jonathan Whitby @Brad Genereaux
Shantha Andrews (Aug 19 2019 at 11:48):
Thanks @John Moehrke much appreciated
Elliot Silver (Aug 19 2019 at 17:42):
I think we (II/WG-20) discussed adding mappings between various resources and DICOM, but got push back from DICOM WG-06 because of concerns about how "official" and complete mappings are. In the absence of mappings, though, creating a Patient resource should not be too challenging, although there will need to be some transformations: DICOM PN to FHIR HumanName, etc.
The question of who should create the Patient, where it (and the ImagingStudy) should live, what the workflows are, how updates are detected/managed, etc. are open. I think practical experience is needed before we have answers on these.
Last updated: Apr 12 2022 at 19:14 UTC
