I have some problems in using the openEHR-EHR-OBSERVATION.imaging_exam.v1 archetype from CKM. The information about images is placed under the protocol section. Is it better to view images as observation data obtained from patient and put images into standalone observation archetype?
Imaging is a little tricky. It is ok to have that info in the protocol section because the result of an imaging test is not the image, is the report. The image gives context for the report but IMO the important thing is the report.
In fact, if I would store images, I may store them in the ACTION that executes the INSTRUCTION (study order). Of course this approach can be discussed.
I wouldn’t store the image itself in an openEHR repo, I prefer just to use the DICOM ids and have a reference to the image that can be used to retrieve the image or images from a PACS. This is ok for a hospital or a network sharing an EHR, but when you need to send the report to another facility without access to the PACS, I would include the image data in the openEHR data using XML compositions.
I think there is a misunderstanding, there is a Dv-multimedia
element under results in the archetype when you can store the metadata of the image or the uri. Under protocolol you have info on the device that was used.
I find openEHR-EHR-CLUSTER.imaging.v1 archetype in CKM, should it be better to reuse this archetype as a slot in openEHR-EHR-OBSERVATION.imaging_exam.v1 archetype?
Imaging is one of the archetypes that will be up for review early on in the Industry Sprint, so I would defer any decision for a little while and Imaging examination Result http://www.openehr.org/ckm/#showArchetype_1013.1.1494 is likely to be the start point you might want to ‘adopt’ this archetype so you get notified when the review starts.
We are pretty likely to drop the cluster archetype and a few other ‘legacy’ approaches.