Stream: V2
Topic: EKG images in v2
Linda (Jan 05 2021 at 17:43):
I am trying to understand where an EKG strip/image is put in a v2 message. From what I have read, the EKG results go in an ORU message, example in IG. A jpg or pdf could go as encoded data in an OBX-5 in an ORU. So curious, do I have the right location? Is anyone actually doing this? ThanQ in advance
Craig Newman (Jan 05 2021 at 18:14):
I'm not sure I've seen an EKG strip done but sending as encoded data in OBX-5 sounds right and is consistent with what I've seen for other types of content like that.
Frank Oemig (Jan 06 2021 at 06:13):
If you treat it as a document you can also use MDM messages.
Craig Newman (Jan 06 2021 at 13:09):
It probably depends some on how you want it treated in the receiving system. Is more like a results or a dictated or scanned document. How a receiving system processes (and ultimately displays) an ORU is potentially quite different than how it displays an MDM
Frank Oemig (Jan 06 2021 at 15:47):
Both is encapsulated data, so that the appropriate viewer is needed. But agreed, the mngmt process is different
Linda (Jan 07 2021 at 21:43):
@Vassil Peytchev Are your familiar with EKG Strips going in V2 messages perhaps as pdfs?
Linda (Jan 07 2021 at 21:46):
@Vassil Peytchev Have you seen EKG images in v2 messages
Frank Oemig (Jan 08 2021 at 07:43):
Transporting documents of all types is done with MDM. OBX is either referencing that file by location and name, or included into the message. The letter requires an appropriate encoding as hex or base64.
Here it does not matter whether it is a small discharge letter, a huge DICOM jpeg2000 file, or an EKG image, the logic is always the same. You can use all file formats. In the end it depends on the viewer.
Last updated: Apr 12 2022 at 19:14 UTC
