Hi all, Let me please introduce myself. My name is Christian, I am working at the German Cancer Research Center in the HiGHmed project. We are working on Radiomcis image analyses and use the archetype OBSERVATION.imaging_exam_result. We had the requirement to represent certain DICOM tags with the …

Hi to all, I am a colleague of Christian. BTW, is this just for DICOM SR or do you want to store the imaging/video/waveform study metadata also in openEHR? No, it is not just for DICOM SR. It is also supposed to cover other IODs, most prominently different DICOM * Image IODs (* like CT, MR, US …

Dear all, thank you for your great input! I quickly drafted a mindmap that represents the idea of Ian having a slot for extra DICOM metadata on each level. I also renamed the DICOM IODs as they were in my previous mindmap to DIOCOM modules to be compliant with the DICOM standard. For the individual…

Hi, OBSERVATIONS are containers of time series data, so basically: OBSERVATION ->* EVENT Each EVENT has an archetypable (generic) data structure inside, and the EVENT contains the “timestamp” for that data. What I was thinking is: since DICOM objects are obtained in series, maybe the EVENT data cou…

Hi, Not directly relevant for the Modelling but: I would even try to cover more attributes than the above ones, DICOM itself provides only very basic search capabilties and covering more Attributes, if wanted, does not harm. Especially since AQL allows quite complex queries. The Sequences shown…

Hi all, @pablo : Thanks for your explanation. I have developed a structure for a template. As basis I would use openEHR-EHR-COMPOSITION.report and integrate a cluster with the required DICOM study tags via the slot “Extension”. For the observation, I would use openEHR-EHR-OBSERVATION.imaging_exam_…

Hi @christian.haux - that looks pretty identical to how I would have done it, based on my more limited understanding of DICOM - so go for it!! The other value of modelling it this way is that it allows folks who do not need or want that level of DICOM detail to be included, to work on the same bas…

and please submit the resulting archetypes to the international CKM so we can publish and share widely.

@christian.haux looks good me for too. I think putting the series at the entry level in the protocol is a smart move to have one series associated with many objects, one per event. Wonderful! I would also leave room for extra extensions at those 3 levels, just in case you need extra tags, you can a…

[image] pablo: I would also leave room for extra extensions at those 3 levels, just in case you need extra tags, you can associated extra cluster or element archetypes. That is good advice Pablo but we actually have those slots already, pretty well as standard - one at composition level, one …

DICOM compliance of OBSERVATION.imaging_exam_result

Clinical

heather.leslie (Heather Leslie) 10 May 2022 00:57 27

ICYMI - OBSERVATION.Imaging examination result and CLUSTER.imaging.exam ready to be published

Topic		Replies	Views
OBSERVATION.Imaging examination result and CLUSTER.imaging.exam ready to be published CKM publication	4	733	15 May 2022
Modelling radiology response for prostate cancer biopsy Clinical archetype	26	604	9 October 2024
Eyes on openEHR Clinical	43	1111	2 July 2026
Echocardiography - Change of "Imaging result" CLUSTER archetype? Reuse lab analyte design pattern for nested/repeated clusters? Clinical aql , archetype , template	14	1043	28 May 2025
Imaging Exam Archetype Clinical (archive)	8	13	19 January 2011
Question to vendors Implementation	12	655	25 October 2021
openEHR-clinical Digest, Vol 35, Issue 21 Clinical (archive)	6	14	26 March 2015
Imaging Examination - which Archetype to use Clinical archetype	12	710	12 September 2023
Review status of CLUSTER.case_identification.v0 Ask IEB archetype	8	120	25 June 2026
Refreshing archetypes related to pathology reporting Clinical archetype , pathology	87	2863	17 April 2024

DICOM compliance of OBSERVATION.imaging_exam_result

Related topics