IMPAX 6.0 HL7 Conformance Statement - Agfa HealthCare
IMPAX 6.0 HL7 Conformance Statement - Agfa HealthCare IMPAX 6.0 HL7 Conformance Statement - Agfa HealthCare
HE/8558126 Page 10 of 29Document No. 8558126, Revision 2Agfa HealthCare 10 October 20052.1.2.2 ORM Segments ProcessedThe following segments are processed when IMPAX 6.0 receives an ORM message:MSHPIDPV1[ AL1 ]ORCOBR2.1.3 Supported ORU EventsThe ORU^R01 is the only code supported for observation messages.Table 5 Supported ORU EventsFuncAreaEventCodeORU Trigger EventInboundSupportedORU R01 Unsolicited transmission of an observation message Y2.1.3.1 ORU Segments ProcessedThe following segments are processed when IMPAX 6.0 receives an ORU message:MSHPID[ PV1 ]{[ ORC ]OBR[ ZOS ]*{[ OBX ][ ZIR ]*}}* The ZOS and ZIR segments are used when receiving ORU messages from certain 3 rd party RIS systems.2.2 Supported HL7 AttributesThe following sections indicate the default mapping of HL7 attributes to internal IMPAX 6.0 data attributes.
HE/8558126 Page 11 of 29Document No. 8558126, Revision 2Agfa HealthCare 10 October, 20052.2.1 MSH Segment MappingsSeq HL7 Field Name ValueRequiredby HL7Table 6 MSH Attribute Support in IMPAX 6.0Default Mapping toIMPAX Attribute(s)(Yes/No)1 Field Separator Yes Yes Usually "|"2 Encoding Characters Yes Yes Usually "^~\&"3 Sending Application No No4 Sending Facility No No5 Receiving Application No No6 Receiving Facility No No7 Date/time of Message No Yes8 Security No No9 Message Type Yes YesComments10 Message Control ID Yes Yes Generated by sending application11 Processing ID Yes Yes12 Version ID Yes Yes “2.1”, “2.2”, “2.3”, “2.3.1”13 Sequence Number No No14 Continuation Pointer No No15 AcceptAcknowledgement Type16 ApplicationAcknowledgement Type17 Country Code No NoNoNoNoNo18 Character Set No Yes If missing, will use character_encoding fromIMPAX 6.0 configuration19 Principal Language ofMessageNoNo
- Page 1 and 2: HE/8558126 Page 1 of 29Document No.
- Page 3 and 4: HE/8558126 Page 3 of 29Document No.
- Page 5 and 6: HE/8558126 Page 5 of 29Document No.
- Page 12 and 13: HE/8558126 Page 12 of 29Document No
- Page 14 and 15: HE/8558126 Page 14 of 29Document No
- Page 16 and 17: HE/8558126 Page 16 of 29Document No
- Page 18 and 19: HE/8558126 Page 18 of 29Document No
- Page 20 and 21: HE/8558126 Page 20 of 29Document No
- Page 22 and 23: HE/8558126 Page 22 of 29Document No
- Page 24 and 25: HE/8558126 Page 24 of 29Document No
- Page 26 and 27: HE/8558126 Page 26 of 29Document No
- Page 28 and 29: HE/8558126 Page 28 of 29Document No
HE/8558126 Page 10 of 29Document No. 8558126, Revision 2<strong>Agfa</strong> <strong>HealthCare</strong> 10 October 20052.1.2.2 ORM Segments ProcessedThe following segments are processed when <strong>IMPAX</strong> <strong>6.0</strong> receives an ORM message:MSHPIDPV1[ AL1 ]ORCOBR2.1.3 Supported ORU EventsThe ORU^R01 is the only code supported for observation messages.Table 5 Supported ORU EventsFuncAreaEventCodeORU Trigger EventInboundSupportedORU R01 Unsolicited transmission of an observation message Y2.1.3.1 ORU Segments ProcessedThe following segments are processed when <strong>IMPAX</strong> <strong>6.0</strong> receives an ORU message:MSHPID[ PV1 ]{[ ORC ]OBR[ ZOS ]*{[ OBX ][ ZIR ]*}}* The ZOS and ZIR segments are used when receiving ORU messages from certain 3 rd party RIS systems.2.2 Supported <strong>HL7</strong> AttributesThe following sections indicate the default mapping of <strong>HL7</strong> attributes to internal <strong>IMPAX</strong> <strong>6.0</strong> data attributes.
Change language