IMPAX 6.0 HL7 Conformance Statement - Agfa HealthCare

More documents

Recommendations

Info

HE/8558126 Page 18 of 29Document No. 8558126, Revision 2Agfa HealthCare 10 October 2005Seq HL7 Field Name ValueRequired14 Date/Time of theObservationNoDefault Mapping toIMPAX Attribute(s)(Yes/No)Yes15 Producer’s ID No No16 Responsible Observer No Yes17 Observation Method No No2.3 AcknowledgementsCommentsThe HL7 mapping returns a NAK if the incoming message cannot be processed. If the reason is themessage type is not mapped, the Acknowledgment Code is set to “AR”. Any other parsing error returns anAcknowledgment Code of “AE”.
HE/8558126 Page 19 of 29Document No. 8558126, Revision 2Agfa HealthCare 10 October, 20053 OUTBOUND MESSAGES3.1 General Processing RulesThe default outbound mapping is generally the inverse of the HL7 inbound mapping3.2 Outbound Message Types Supported3.2.1 HL7 Message Type, Event MappingsThe following table lists all of the default outbound HL7 messages supported. There is no single set ofmappings that will service all IMPAX 6.0 installations, so this table will likely be edited when the deviceis installed. The default mappings are the inverse of the inbound HL7 to IMPAX 6.0.Table 14 Outbound HL7 Message TypesHL7 message typeHL7 TriggerADTADTADTADTADTADTADTADTADTADTORMA01A02A03A05A08A11A18A23A33A38O013.2.2 Segments ProcessedThe following table lists the segments that are processed for each HL7 message type by the defaultHL7 outbound mappings.Table 15 HL7 Out Segments ProcessedHL7 Message TypeADTADT Merge messages add:ORMSegments ProducedMSHPIDPV1[ AL1 ]MRGMSHPIDPV1[AL1 ]ORCOBRBy default, all HL7 data elements correspond to HL7 v2.3.1.
Page 1 and 2: HE/8558126 Page 1 of 29Document No.
Page 10 and 11: HE/8558126 Page 10 of 29Document No

IMPAX 6.0 HL7 Conformance Statement - Agfa HealthCare

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?