Allergy Message a60

Gerand,

Assuming use of Xlate,

COPY each of the components following the first (inbound PID3.1 to one less in the outbound.

For example (notation may not match but you should get the idea):

COPY

   …PID#3.[1]  —> …PID#3.[0]

COPY

   …PID#3.[2]  —> …PID#3.[1]

and so on… for as many components as you want.

Gerand,

What release of Cloverleaf(R) ar you on?

The ADT^A60 message is in Version 2.4 of HL/7. That is supplied in Cloverleaf(R) 5.6 aqnd later.

It looks like this:

MSH

EVN

PID

[PV1]

[PV2]

[{IAM}]

IAM is a new segment to 2.4 and has fields not defined prior to 2.4.

So if you do not have 2.4 (HL/7), you could still build the variant You would need to build the fields for the IAM segment however.

I do not have an example Tcl proc because I would build the variant and use the Xlate.

Maybe someone else can provide you with some Tcl.

I got sent on a wild goose chase myself when I had to do an allergy integration using an HL7 2.3 ADT^A60 which doesn’t exist.

I pointed out to the vendor that there was no ADT^A60 message type for HL7 2.3 and first thought the vendor made up that message type.

They kept saying what do you mean there is no HL7 2.3 ADT^A60.

I also questioned why they were using already allocated item numbers inconsistantly then finally I discovered HL7 2.4 does have an ADT^A60 and so does cloverleaf even on version 5.2.

Then the vendor said “Oh we really don’t care about the HL7 version that much” and had been saying HL7 2.3 out of habit when they really should of said HL7 2.4.

Needless to say that cloverleaf is a little more picky about HL7 version numbers and when I switched to HL7 2.4 life got much easier.