| Author |
Message
|
| gakana |
 Posted: Mon Nov 21, 2005 9:41 am Post subject: HL7 Messageset in TDS Format |
 |
|
Apprentice
Joined: 27 Jul 2005
Posts: 28
Location: Michigan
|
Hi All,
I would like to process this sample message in TDS format using HL7 standard.
MSH|^~\&|XXX||YYY|ZZZ|20050131191539||ADT^A01|01254647P
here
'^' Component separator in HL7
'|' Data element separator in HL7
'~' Repeating element delimiter in HL7
'&' Sub-component separator in HL7
'\' is Escape delimiter
The messageset tree should be populate like this
Field separator = |
EncodingCharacters = ^~\&
SendingApplication
NamespaceID = XXX
UniversalID
UniversalIDType
SendingFacility
NamespaceID
UniversalID
UniversalIDType
ReceivingApplication
NamespaceID = YYY
UniversalID
UniversalIDType
--
--
MessageType
MessageType = ADT
TriggerEvent = A01
--
ProcessingID
ProcessingID = 01254647P
ProcessingMode
--
--
etc
but I am getting the values like this in the message tree in the debug mode
MRM
HL7_SGMSH
Field separator = ^~\&
EncodingCharacters = XXX
SendingApplication
NamespaceID = YYY
UniversalID = ZZZ
UniversalIDType = 20050131191539
--
etc
I am working on MB 5.0.5 version and I have set all default values
in the messages set for HL7 standard
I also set Filed Identification Tag to "MSH'
Please hlep me how to get the expected values
Thanks
Gakana |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Nov 21, 2005 3:55 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You need to set 'Interpret Element Value' on the service string, and then make sure that you use HL7 mnemonics ( such as <HL7_FS> ) for all your Delimiters, Repeating Element Delimiters, Group Indicators and Group Terminators.
It's not straightforward to get the model right, so feel free to ask if you're still stuck. |
|
| Back to top |
|
|
| wooda |
| Posted: Tue Nov 22, 2005 12:50 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
As kimbert has said Se your Messaging Standard to "HL7" and set "Interpret Element Value" on the field separator and service string to "HL7 Field Separator" and "HL7 Service String" respectively. Then make sure you use the correct mnemonics in for your delimters, repeat delimiters etc.
As modelling the whole HL7 standard would be a very large task It is also worth mentioning that IBM has an off the shelf HL7 message set solution available. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 22, 2005 6:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| You should definitely consider using the IBM-supplied solution. It's a good implementation of the standard, and I've seen it work out-of-the-box on more than one project. Let me know if you need contact details - IBM Dublin usually do this sort of thing, but I think HL7 may be different. |
|
| Back to top |
|
|
| gakana |
| Posted: Tue Nov 22, 2005 11:48 am Post subject: HL7 Messageset in TDS Format<Solved> |
|
|
Apprentice
Joined: 27 Jul 2005
Posts: 28
Location: Michigan
|
Hi Kimbert, thanks for your reply with tips and suggestions.
As your suggestions and hints I am able to parse my messages through my HL7 messageset in TDS format.
For that I used Data Element separation is 'Variable Length Elements Delimited' and Delimiter is <HL7_FS>. For childs used <HL7_CS>
I did not used the HL7 Service String option for the local Elements
I took default value for Interpret Element Value is 'None' and Length is 'Zero'.
A pre-defined message set solution for HL7 may be purchased from IBM.
Thanks all for your support
Gakana |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Nov 28, 2005 5:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I did not used the HL7 Service String option for the local Elements |
In that case you'd better be sure that all of the messages use the default separators. If you ever encounter a message which overrides the Field Separator in the service string (they are quite common) , your message will not parse correctly.
If you want help with interpreting the service string correctly, just ask. |
|
| Back to top |
|
|
|
|
