Hi Kathees,
This is actually correct behaviour. It's a somewhat confusing aspect of HL7
v2 at first, but HL7 reuses some message structures for multiple message
trigger events. For example, the ADT^A01 and ADT^A04 messages both need all
of the same data fields, so HL7 decided to reuse the ADT^A01 structure for
the ADT^A04 message. They call this structure ADT_A01 (note the
underscore).
MDM^T02 and MDM^T10 similarly share messages. The thing to note is the
message type and structure in MSH-9:
<MSH.9>
<MSG.1>MDM</MSG.1>
<MSG.2>T10</MSG.2>
<MSG.3>MDM_T02</MSG.3>
</MSH.9>
Cheers,
James
On Tue, Nov 4, 2014 at 4:39 AM, Rajendram Kathees <[email protected]>
wrote:
> Hi,
>
> We used the Hapi library to convert the HL7 message [1] to XML format [2].
> I notice MDM_T02 comes as a root element in the XML. Shouldn't this be
> MDM_T10 like in the other cases? Is this a bug? Can someone explain why
> this is the case?
>
> [1] ER7 Message
> MSH|^~\\&|||||20141104095415.605+0530||MDM^T10^MDM_T02|2101||2.6|
>
> [2] XML Message
> <?xml version="1.0"?>
> <MDM_T02 xmlns="urn:hl7-org:v2xml">
> <MSH>
> <MSH.1>|</MSH.1>
> <MSH.2>^~\&</MSH.2>
> <MSH.7>20141104095415.605+0530</MSH.7>
> <MSH.9>
> <MSG.1>MDM</MSG.1>
> <MSG.2>T10</MSG.2>
> <MSG.3>MDM_T02</MSG.3>
> </MSH.9>
> <MSH.10>2101</MSH.10>
> <MSH.12>
> <VID.1>2.6</VID.1>
> </MSH.12>
> </MSH>
> </MDM_T02>
>
>
>
> Thanks,
> Kathees
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Hl7api-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
>
------------------------------------------------------------------------------
_______________________________________________
Hl7api-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
