Processing multiple HL7 versions

[Bob L]

We receive messages from two parties, one in HL7 v2.3.1 and the second in
v2.5. We will be reporting all messages to a third part in v2.5.1. The
initial thought was to add an appropriate map to the receive pipeline for
each party so that we had only v.2.5.1 internally. The thought is that this
is simpler than receiving the v2.3.1 and v2.5 into the MessageBox and
building the v2.5.1 for reporting. The parties are moving to v2.5.1 and as
they do we would remove the ReceivePipeline map. The only potential downside
I can see is that we wouldn’t have the original message in the MessageBox. We
do archive it to a folder. However, this is our first project and I am
concerned that we may be missing something.
Is this the common approach to this scenario?

Thanks,

Bob

[Eric Stott]

Bob,
There are two different approaches, you can put the map in the recieve port,
or you can put it in the send port.
If you have an archive component in the decode stage of your receive
location (if you need one, I have one you can use
(http://blog.hl7-info.com/contact.aspx)) then you should be okay.

Eric
http://hl7-info.com

Post by Bob L
We receive messages from two parties, one in HL7 v2.3.1 and the second in
v2.5. We will be reporting all messages to a third part in v2.5.1. The
initial thought was to add an appropriate map to the receive pipeline for
each party so that we had only v.2.5.1 internally. The thought is that this
is simpler than receiving the v2.3.1 and v2.5 into the MessageBox and
building the v2.5.1 for reporting. The parties are moving to v2.5.1 and as
they do we would remove the ReceivePipeline map. The only potential downside
I can see is that we wouldn't have the original message in the MessageBox.
We
do archive it to a folder. However, this is our first project and I am
concerned that we may be missing something.
Is this the common approach to this scenario?
Thanks,
Bob

[Bob L]

Thanks Eric.

Post by Eric Stott
Bob,
There are two different approaches, you can put the map in the recieve port,
or you can put it in the send port.
If you have an archive component in the decode stage of your receive
location (if you need one, I have one you can use
(http://blog.hl7-info.com/contact.aspx)) then you should be okay.
Eric
http://hl7-info.com

Post by Bob L
We receive messages from two parties, one in HL7 v2.3.1 and the second in
v2.5. We will be reporting all messages to a third part in v2.5.1. The
initial thought was to add an appropriate map to the receive pipeline for
each party so that we had only v.2.5.1 internally. The thought is that this
is simpler than receiving the v2.3.1 and v2.5 into the MessageBox and
building the v2.5.1 for reporting. The parties are moving to v2.5.1 and as
they do we would remove the ReceivePipeline map. The only potential downside
I can see is that we wouldn't have the original message in the MessageBox.
We
do archive it to a folder. However, this is our first project and I am
concerned that we may be missing something.
Is this the common approach to this scenario?
Thanks,
Bob

[Shaik Dawood]

One of my client has the same scenario of receiving multiple versions. We
have a system setup to receive V25 messages and process them. I am looking to
have one map each to to convert other version (V23, V24 etc) to V25 and then
have this either in the recieve port or in the send port. But the challenge I
am facing is that in the map itself - how could we have multiple source
schemas in the map. I don't want to go with the orchestration route of having
a transform shape to do this. Any help would be really appreciated!!
Thanks,
Shaik Dawood.

Post by Bob L
Thanks Eric.

Post by Eric Stott
Bob,
There are two different approaches, you can put the map in the recieve port,
or you can put it in the send port.
If you have an archive component in the decode stage of your receive
location (if you need one, I have one you can use
(http://blog.hl7-info.com/contact.aspx)) then you should be okay.
Eric
http://hl7-info.com

Post by Bob L
We receive messages from two parties, one in HL7 v2.3.1 and the second in
v2.5. We will be reporting all messages to a third part in v2.5.1. The
initial thought was to add an appropriate map to the receive pipeline for
each party so that we had only v.2.5.1 internally. The thought is that this
is simpler than receiving the v2.3.1 and v2.5 into the MessageBox and
building the v2.5.1 for reporting. The parties are moving to v2.5.1 and as
they do we would remove the ReceivePipeline map. The only potential downside
I can see is that we wouldn't have the original message in the MessageBox.
We
do archive it to a folder. However, this is our first project and I am
concerned that we may be missing something.
Is this the common approach to this scenario?
Thanks,
Bob

[Tom Canter - Neudesic]

Shaik,
Simply put each a map for each source message version that maps to the
target message in the receive port.
At receipt, the receive port will select the appropriate map that
matches the input message type.

Tom