Different Message Format

This topic has 3 replies, 3 voices, and was last updated 15 years, 4 months ago by Rob Abbott.

Creator

Topic
December 2, 2010 at 7:17 pm #52137
Kevin Crist
Participant
Has anyone worked with any message looking like the one below?

I am not yet sure if this is to be the recieving or sending system doing this, i was just sent a document. If so, is there a way to treat this to make an HL7? Thanks for any ideas.

Where:

The following hierarchy demonstrates the message segments.

M Message Header

H Account Identification

P Donor and test information

S Collection Site identification

O Ordered test information

T Results per analyte

C Notes and Comments (added when applicable
Creator

Topic

Viewing 2 reply threads

Author

Replies
- December 2, 2010 at 7:49 pm #73192
  Jim Kosloskey
  Participant
  Kevin,
  
  My guess is you can use an HRL comprised of VRL components (some of which repeat).
  
  The VRL look like the fields are | seperated.
  
  Then this looks like some sort of Result so I am assuming the receiving system wants an HL/7 ORU – or if an Order an ORM.
  
  So you would have the HRL as inbound and HL/7 as outbound.
  
  email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.
- December 2, 2010 at 8:04 pm #73193
  Kevin Crist
  Participant
  Thanks Jim,
  
  Looks like a fun learning experience should we chose to do it now that it should be possible. I am sure i will need some assistance with it down the road if we go this route.
  
  thanks again.
- December 2, 2010 at 8:22 pm #73194
  Rob Abbott
  Keymaster
  It sort of looks like ASTM … which uses 1-character segment IDs.
  
  The best way to handle this IMO is to convert it to or from HL7.
  
  Rob Abbott
  Cloverleaf Emeritus
Author

Replies

Viewing 2 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.