HL7 Conformance Statement RadCentre. Release

Transcription

1 HL7 Conformance Statement Release

2 Editing The editing is done by i-slutins Health GmbH. If you have any suggestions for improvement or requests for modification etc, please let us know. You can reach us in the following ways: i-slutins Health Contact Center Phone: + 49 (0) Fax: + 49 (0) Mail: i-slutins Health GmbH Burgstraße Bochum Am Exerzierplatz Mannheim Lorenzweg 42, Haus Magdeburg This publication is protected by copyright. part of this documentation may be copied or transferred for any reason without the written permission of i-slutins Health GmbH, regardless of the method, electrical, mechanical or the media, with which this is performed. All rights of reproduction by presentation are reserved. The information and data contained in this documentation may be changed without further notice. As far as refered to third-party hardware or software, the vendors of this products are listed at the end of this document i-slutins Health GmbH

3 Table of Contents 2 Introduction Revision Record Purpose and Intended Audience Acronyms and Abbreviations Inbound Messages Supported Trigger Events Supported ADT Evens Supported RM Events Supported DFT Events Supported HL7 Attributes (inbound) MSH Segment Mappings PID Segment Mappings PV1 Segment Mappings MRG Segment Mappings RC Segment Mappings BR Segment Mappings ZDS Segment Mappings DFT Segment Mappings Acknowledgements utbound Messages Supported Trigger Events Supported ADT Events Supported RM Events Supported DFT Events Supported BAR Events Supported RU Events Supported MDM Events Supported MFN Events HL7 Conformance Statement Issue:

4 4.2 Supported HL7 Segments (outbound) MSH Segment PID Segment PV1 Segment MRG Segment RC Segment BR Segment ZDS Segment DFT Segment PR1 Segment BX Segment TXA Segment Queries Query Query - MSH Segment Query - QPD Segment Query - RCP Segment HL7 Conformance Statement Issue:

5 2 Introduction 2.1 Revision Record Revision Number Date Author Reason for Change PLEH/MHF Initial 2.2 Purpose and Intended Audience This document is a HL7 Conformance Statement for the HL7 Services associated with. It ist assumed that the reader of this document is involved in system integration and/or software design. It is also assumed that the reader is familiar with the terminology and concepts that are used in HL and HL7 2.5 standard and the IHE Technical Framework. Readers not familiar with HL7 terminology should first read the appropriate parts of the HL7 standard itself, prior to reading this conformance statement. Although the use of this conformance statement in conjunction with the HL7 standard is intended to facilitate communication with, it is not sufficient to guarantee, by itself, the interoperation of the connection between and the 3rd party HL7-based system. The integration of any device into a system of interconnected devices goes beyond the scope of the HL7 standard and this conformance statement when interoperability is desired. It is the user s responsibility to analyze the applications requirements and develop a solution that integrates the i-slutins Health equipment with other vendors systems. 2.3 Acronyms and Abbreviations Definitions, terms and abbreviations used in this document are defined within the HL7 standard. Abbreviations and terms are as follows: Acronym ADT AL1 Definition Admission, Discharge and Transfer message Patient Allergy Information segment HL7 Conformance Statement 1.1 IKRU Issue:

6 Acronym EVN Definition Event Type segment HL7 Health Level 7 IHE MDM MFN MRG MSH NTE BR BX RC RM RU PID PV1 QRD RIS Integrating the Healthcare Enterprise Medical Document Management Master Files Change tification Merge Patient Information segment Message Header segment tes and comments segment bservation Request segment bservation/result segment Common rder segment rder Request message bservation Results - Unsolicited message Patient ID segment Patient Visit segment Query Definition segment Radiology Information System HL7 Conformance Statement 1.1 IKRU Issue:

7 3 Inbound Messages 3.1 Supported Trigger Events Supported ADT Evens Inbound support for ADT triggers is implemented by a lookup table. This table may be edited to meet a site s needs. Table 2-1. Supported ADT Events Func Area Event Code ADT Trigger Event InboundSupported ADT A01 Admit a patient Yes ADT A02 Transfer a patient Yes ADT A03 Discharge a patient Yes ADT A04 Register a patient Yes ADT A05 Preadmit a patient Yes ADT A06 Transfer an outpatient to inpatient ADT A07 Transfer an inpatient to outpatient ADT A08 Update patient information Yes Yes Yes ADT A09 Patient departing ADT A10 Patient arriving ADT A11 Cancel admit Yes ADT A12 Cancel transfer Yes ADT A13 Cancel discharge Yes ADT A14 Pending admit Yes ADT A15 Pending transfer Yes ADT A16 Pending discharge Yes ADT A17 Swap patients ADT A18 Merge patient information HL7 Conformance Statement 1.1 IKRU Issue:

8 Table 2-1. Supported ADT Events Func Area Event Code ADT Trigger Event InboundSupported QRY A19 Patient query ADT A20 Nursing/Census application updates ADT A21 Leave of absence - out (leaving) ADT A22 Leave of absence - in (returning) ADT A23 Delete a patient record ADT A24 Link patient information ADT A25 Cancel pending discharge ADT A26 Cancel pending transfer ADT A27 Cancel pending admit ADT A28 Add person information Yes ADT A29 Delete person information Yes ADT A30 Merge person information ADT A31 Update person information Yes ADT A32 Cancel patient arriving ADT A33 Cancel patient departing ADT A34 Merge patient information - patient ID only ADT A35 Merge patient information - account number only ADT A36 Merge patient information - patient ID and account Yes ADT A37 Unlink patient information ADT A38 Cancel pre-admit ADT A39 Merge person - external ID ADT A40 Merge patient - internal ID Yes ADT A41 Merge account - patient account number ADT A42 Merge visit - visit number HL7 Conformance Statement 1.0 EFR Issue:

9 Table 2-1. Supported ADT Events Func Area Event Code ADT Trigger Event InboundSupported ADT A43 Move patient information - internal ID ADT A44 Move account information - patient account number ADT A45 Move visit information - visit number Yes ADT A46 Change external ID ADT A47 Change internal ID ADT A48 Change alternate patient ID ADT A49 Change patient account number ADT A50 Change visit number ADT A51 Change alternate visit ID ADT Segments Processed The following segments are processed when receives an ADT message: MSH EVN PID [PD1] [{NK1}] PV1 [PV2] [{AL1}] [{DG1}] [{IN1 [IN2] } ] HL7 Conformance Statement 1.0 EFR Issue:

10 3.1.2 Supported RM Events Table 2-2. Supported RM Events Func Area Event Code RM Trigger Event Inbound Supported RM 01 General order message Yes RR 02 rder response Yes RM Messages: Supported Control Codes and rder Status Table 2-3a. Default rder Control Codes supported from RC 1,1 Control Code (RC-1) Value NW SC CA C X SN NA Table 2-3b. Default rder Control Codes supported from RC 5,1 rder Status (RC-5) Value CA CM IP SC RM Segments Processed HL7 Conformance Statement 1.0 EFR Issue:

11 MSH [PID [PV1 [PV2] ] [{IN1 [IN2] } ] [{AL1}] ] {RC [BR [{NTE}] [{BX ] } Supported DFT Events Table 2-4. Supported DFT Events Func Area Event Code RM Trigger Event Inbound Supported DFT P03 Post detail financial transaction Yes DFT Segments Processed MSH EVN PID [PV1] [PV2] {FT1} HL7 Conformance Statement 1.0 EFR Issue:

12 3.2 Supported HL7 Attributes (inbound) MSH Segment Mappings Table 2-5. MSH Attribute Support in Seq HL7 Field Name Value Required Default Mapping to (Yes/) 1 Field Separator R 2 Encoding Characters R 3 Sending Application 4 Sending Facility 5 Receiving Application 6 Receiving Facility 7 Date/time of Message R 8 Security 9 Message Type R Yes Table g_casemove 10 Message Control ID R Yes Table g_casemove 11 Processing ID R 12 Version ID R 13 Sequence Number 14 Continuation Pointer 15 Accept Acknowledgement Type 16 Application Acknowledgement Type 17 Country Code 18 Character Set 19 Principal Language of Message HL7 Conformance Statement 1.0 EFR Issue:

13 3.2.2 PID Segment Mappings Table 2-6. PID Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Set ID - Patient ID 2 Patient ID (External ID) Yes 3 Patient ID (Internal ID) R Yes Table g_pat, Table g_case 4 Alternate Patient ID 5 Patient Name R Yes Table g_pat 6 Mother's Maiden Name Yes Table g_pat 7 Date of Birth Yes Table g_pat 8 Sex Yes Table g_pat 9 Patient Alias 10 Race 11 Patient Address Yes Table g_pat 12 Country Code Yes Table g_pat 13 Phone Number - Home Yes Table g_pat 14 Phone Number - Business Yes Table g_pat 15 Primary Language Yes Table g_pat 16 Marital Status Yes Table g_pat 17 Religion Yes Table g_pat 18 Patient Account Number 19 SSN Number - Patient 20 Driver's Lic Num - Patient 21 Mother's Identifier 22 Ethnic Group 23 Birth Place 24 Multiple Birth Indicator 25 Birth rder 26 Citizenship HL7 Conformance Statement 1.0 EFR Issue:

14 Table 2-6. PID Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 27 Veterans Military Status 28 Nationality Yes Table g_pat 29 Patient Death Date/Time Yes Table g_pat 30 Patient Death Indicator Yes Table g_pat HL7 Conformance Statement 1.0 EFR Issue:

15 3.2.3 PV1 Segment Mappings Table 2-7. Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Set ID - Patient Visit 2 Patient Class Yes Table g_case 3 Assigned Patient Location Yes Table g_casemove 4 Admission Type Yes Table g_case 5 Pre-admit Number 6 Prior Patient Location 7 Attending Doctor Yes Table g_casemove 8 Referring Doctor Yes Table g_casemove 9 Consulting Doctor Yes Table g_casemove 10 Hospital Service 11 Temporary Location 12 Pre-admit Test Indicator 13 Readmission Indicator 14 Admit Source 15 Ambulatory Status 16 VIP Indicator 17 Admitting Doctor 18 Patient Type Yes Table g_casemove 19 Visit Number Yes Table g_case 20 Financial Class Eff. Date 21 Charge Price Indicator Yes Table g_casemove 22 Courtesy Code 23 Credit Rating 24 Contract Code Yes Table g_case 25 Contract Effective Date 26 Contract Amount HL7 Conformance Statement 1.0 EFR Issue:

16 Table 2-7. Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 27 Contract Period 28 Interest Code 29 Transfer to Bad Debt Coder 30 Transfer to Bad Debt Date 31 Bad Debt Agency Code 32 Bad Debt Transfer Amount 33 Bad Debt Recovery Amt 34 Delete Account Indicator 35 Delete Account Date 36 Discharge Disposition 37 Discharged to Location 38 Diet Type 39 Servicing Facility 40 Bed Status 41 Account Status 42 Pending Location 43 Prior Temporary Location 44 Admit Date/Time Yes Table g_casemove 45 Discharge Date/Time Yes Table g_casemove 46 Current Patient Balance 47 Total Charges 48 Total Adjustments 49 Total Payments 50 Alternate Visit ID 51 Visit Indicator Yes 52 ther Healthcare Provider HL7 Conformance Statement 1.0 EFR Issue:

17 3.2.4 MRG Segment Mappings Table 2-8. MRG Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Prior Patient ID - Internal R Yes Table g_pat, g_case 2 Prior Alternate Patient ID 3 Prior Patient Acct Number 4 Prior Patient ID - External 5 Prior Visit Number Yes Table g_case 6 Prior Alternate Visit ID 7 Prior Patient Name RC Segment Mappings Table 2-9. RC Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 rder Control R Yes 2 Placer rder # Yes 3 Filler rder # Yes 4 Placer Group # Yes 5 rder Status Yes 6 Response Flag 7 Quantity/Timing Yes 8 Parent 9 Date/Time of Transaction Yes 10 Entered By 11 Verified By Yes 12 rdering Provider Yes 13 Enterer's Location Yes 14 Call Back Phone Number HL7 Conformance Statement 1.0 EFR Issue:

18 Table 2-9. RC Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 15 rder Effective Date/Time Yes 16 rder Control Reason 17 Entering rganization 18 Entering Device 19 Action By HL7 Conformance Statement 1.0 EFR Issue:

19 3.2.6 BR Segment Mappings Table BR Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Set ID - bservation Request 2 Placer rder # Yes 3 Filler rder # Yes 4 Universal Service ID R Yes 5 Priority Yes 6 Requested Date/Time 7 bservation Date/Time Yes 8 bservation End Date/ Time 9 Collection Volume 10 Collector Identifier 11 Specimen Action Code 12 Danger Code 13 Relevant Clinical Inf. 14 Specimen Rec'd Date/ Time 15 Specimen Source 16 rdering Provider family 17 rder Callback Phone. 18 Placer Field 1 Yes 19 Placer Field 2 Yes 20 Filler Field 1 Yes 21 Filler Field 2 Yes 22 Result Rpt/Status Change - Date/Time Yes 23 Charge To Practice 24 Diagnostic Serv Sect Id HL7 Conformance Statement 1.0 EFR Issue:

20 Table BR Attribute Support in Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 25 Result Status Yes 26 Parent Result 27 Quantity/Timing Yes 28 Result Copies To 29 Parent Number 30 Transportation Mode Yes 31 Reason For Study Yes 32 Principal Result Interpreter 33 Assistant Result Interpreter 34 Technician 35 Transcriptionist 36 Scheduled Date/Time Yes 37 Number of Sample Containers 38 Transport Logistics of Collected Sample 39 Collector's Comment 40 Transport Arrangement Responsibility 41 Transport Arranged 42 Escort Required 43 Planned Patient Transport Comment 44 Procedure Code HL7 Conformance Statement 1.0 EFR Issue:

21 3.2.7 ZDS Segment Mappings Table ZDS Attribute Support Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Study Instance UID Yes DFT Segment Mappings Table DFT Attribute Support Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Set ID - FT1 2 Transaction ID 3 Transaction Batch ID 4 Transaction Date R Yes 5 Transaction Posting Date 6 Transaction Type R Yes 7 Transaction Code R Yes 8 Transaction Description 9 Transaction Description 10 Transaction Quantity Yes 11 Transaction Amount Yes 12 Transaction Amount -Unit 13 Department Code 14 Insurance Plan ID 15 Insurance Amount 16 Assigned Patient Location 17 Fee Schedule 18 Patient Type 19 Diagnosis Code - FT1 20 Performed By Code Yes HL7 Conformance Statement 1.0 EFR Issue:

22 Table DFT Attribute Support Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 21 rdered By Code Yes 22 Unit Cost 23 Filler rder Number 24 Entered By Code 25 Procedure Code 3.3 Acknowledgements The HL7 mapping returns a NAK if the incoming message cannot be processed. Any processing error returns an Acknowledgment Code of.ce. HL7 Conformance Statement 1.0 EFR Issue:

23 4 utbound Messages 4.1 Supported Trigger Events Supported ADT Events Table 3-1. Supported ADT Events Func Area Event Code ADT Trigger Event utbound Supported ADT A04 Register a patient Yes ADT A08 Update patient information Yes ADT A10 Patient arriving Yes ADT A04 Register a patient Yes ADT A28 Add person information Yes ADT A31 Update person information ADT A34 Merge patient information - patient ID only Yes Yes ADT A40 Merge patient - internal ID Yes ADT Segment Processed The following segments are processed when receives an ADT message: MSH EVN PID PV1 [{IN1 [IN2] } ] HL7 Conformance Statement 1.1 IKRU Issue:

24 4.1.2 Supported RM Events Table 3-2. Supported RM Events Func Area Event Code RM Trigger Event utbound Supported RM 01 General order message Yes RR 02 rder response Yes RM Messages: Supported Control Codes and rder Statuses Table 3-3a. Default rder Control Codes supported from RC 1,1 Control Code (RC-1) Value NW SC CA C X SN NA Table 3-3b. Default rder Control Codes supported from RC 5,1 rder Status (RC-5) Value CA CM IP SC RM Segments Processed HL7 Conformance Statement 1.1 IKRU Issue:

25 MSH [PID [PV1] [{IN1 [IN2] } ] [{AL1}] ] {RC [BR [{NTE}] [{BX ] } Supported DFT Events Table 3-4. Supported DFT Events Func Area Event Code DFT Trigger Event utbound Supported DFT P03 Post detail financial transaction Yes DFT Segments Processed MSH EVN PID [PV1] {FT1} HL7 Conformance Statement 1.1 IKRU Issue:

26 4.1.4 Supported BAR Events Table 3-5. Supported BAR Events Func Area Event Code BAR Trigger Event utbound Supported BAR P01 Post detail financial transaction Yes BAR Segment Processed MSH EVN PID [PV1] [PV2] {PR1} Supported RU Events Table 3-6. Supported RU Events Func Area Event Code RU Trigger Event utbound Supported RU R01 Unsolicited transmission of an observation message Yes RU Segments Processed MSH {[PID ] } } [PV1] {[RC] BR {[BX] } HL7 Conformance Statement 1.1 IKRU Issue:

27 4.1.6 Supported MDM Events Table 3-7. Supported MDM Events Func Area Event Code MDM Trigger Event utbound Supported MDM T02 riginal document notification and content Yes MDM T08 Document edit notification and content Yes MDM T11 Document cancel notification Yes MDM Segments Processed MSH EVN PID PV1 TXA Supported MFN Events Table 3-8. Supported MFN Events Func Area Event Code MFN Trigger Event utbound Supported MFN M09 Test/bservation (Categorical) master file Yes MFN Segments Processed MSH MFI { MFE M1 } HL7 Conformance Statement 1.1 IKRU Issue:

28 4.2 Supported HL7 Segments (outbound) MSH Segment Table 3-9. MSH Attribute Support in Seq HL7 Field Name Value Required (Yes/ ) 1 Field Separator R Yes Field Separators " " 2 Encoding Characters R Yes Encoding Characters "^~\&" 3 Sending Application Yes Configurable 4 Sending Facility Yes Configurable 5 Receiving Application Yes Configurable 6 Receiving Facility Yes Configurable 7 Date/time of Message R Yes 8 Security 9 Message Type R Yes Configurable 10 Message Control ID R Yes Configurable 11 Processing ID R Yes Configurable (P or T) 12 Version ID R Yes Configurable 13 Sequence Number 14 Continuation Pointer 15 Accept Acknowledgement Type 16 Application Acknowledge ment Type Yes Configurable Yes Configurable 17 Country Code Yes Configurable 18 Character Set Yes Configurable 19 Principal Language of Message Yes Configurable HL7 Conformance Statement 1.1 IKRU Issue:

29 4.2.2 PID Segment Table PID Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - Patient ID 2 Patient ID (External ID) Yes Configurable 3 Patient ID (Internal ID) R Yes 4 Alternate Patient ID 5 Patient Name R Yes 6 Mother's Maiden Name Yes Configurable 7 Date of Birth Yes 8 Sex Yes 9 Patient Alias 10 Race 11 Patient Address Yes 12 Country Code Yes 13 Phone Number - Home Yes Configurable 14 Phone Number - Business Yes Configurable 15 Primary Language Yes Configurable 16 Marital Status Yes Configurable 17 Religion Yes Configurable 18 Patient Account Number 19 SSN Number - Patient 20 Driver's Lic Num - Patient 21 Mother's Identifier 22 Ethnic Group 23 Birth Place 24 Multiple Birth Indicator 25 Birth rder 26 Citizenship Yes Configurable 27 Veterans Military Status HL7 Conformance Statement 1.1 IKRU Issue:

30 Table PID Attribute Support in Seq HL7 Field Name Value Required (Yes/) 28 Nationality Yes Configurable 29 Patient Death Date/Time 30 Patient Death Indicator HL7 Conformance Statement 1.1 IKRU Issue:

31 4.2.3 PV1 Segment Table PV1 Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - Patient Visit 2 Patient Class Yes Configurable 3 Assigned Patient Location Yes Configurable 4 Admission Type Yes Configurable 5 Pre-admit Number 6 Prior Patient Location 7 Attending Doctor 8 Referring Doctor Yes Configurable 9 Consulting Doctor 10 Hospital Service 11 Temporary Location 12 Pre-admit Test Indicator 13 Readmission Indicator 14 Admit Source 15 Ambulatory Status 16 VIP Indicator 17 Admitting Doctor 18 Patient Type 19 Visit Number Yes 20 Financial Class Eff. Date 21 Charge Price Indicator Yes Configurable 22 Courtesy Code 23 Credit Rating 24 Contract Code 25 Contract Effective Date 26 Contract Amount 27 Contract Period HL7 Conformance Statement 1.1 IKRU Issue:

32 Table PV1 Attribute Support in Seq HL7 Field Name Value Required (Yes/) 28 Interest Code 29 Transfer to Bad Debt Code 30 Transfer to Bad Debt Date 31 Bad Debt Agency Code 32 Bad Debt Transfer Amount 33 Bad Debt Recovery Amt 34 Delete Account Indicator 35 Delete Account Date 36 Discharge Disposition 37 Discharged to Location 38 Diet Type 39 Servicing Facility 40 Bed Status 41 Account Status 42 Pending Location 43 Prior Temporary Location 44 Admit Date/Time Yes Configurable 45 Discharge Date/Time Yes Configurable 46 Current Patient Balance 47 Total Charges 48 Total Adjustments 49 Total Payments 50 Alternate Visit ID 51 Visit Indicator Yes 52 ther Healthcare Provider HL7 Conformance Statement 1.1 IKRU Issue:

33 4.2.4 MRG Segment Table MRG Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Prior Patient ID - Internal R Yes 2 Prior Alternate Patient ID 3 Prior Patient Acct Number 4 Prior Patient ID - External 5 Prior Visit Number 6 Prior Alternate Visit ID 7 Prior Patient Name RC Segment Table RC Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 rder Control R Yes 2 Placer rder # Yes 3 Filler rder # Yes 4 Placer Group # 5 rder Status Yes 6 Response Flag 7 Quantity/Timing Yes 8 Parent 9 Date/Time of Transaction Yes 10 Entered By Yes Configurable 11 Verified By Yes Configurable 12 rdering Provider Yes Configurable 13 Enterer's Location 14 Call Back Phone Number 15 rder Effective Date/Time Yes Configurable HL7 Conformance Statement 1.1 IKRU Issue:

34 Table RC Attribute Support in Seq HL7 Field Name Value Required (Yes/) 16 rder Control Reason 17 Entering rganization Yes Yes Configurable 18 Entering Device 19 Action By HL7 Conformance Statement 1.1 IKRU Issue:

35 4.2.6 BR Segment Table BR Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - bservation Request Yes 2 Placer rder # Yes 3 Filler rder # Yes 4 Universal Service ID R Yes 5 Priority Yes 6 Requested Date/Time 7 bservation Date/Time Yes 8 bservation End Date/ Time 9 Collection Volume 10 Collector Identifier 11 Specimen Action Code 12 Danger Code 13 Relevant Clinical Inf. 14 Specimen Rec'd Date/ Time 15 Specimen Source 16 rdering Provider family 17 rder Callback Phone. 18 Placer Field 1 Yes Configurable 19 Placer Field 2 Yes Configurable 20 Filler Field 1 Yes Configurable 21 Filler Field 2 Yes Configurable 22 Result Rpt/Status Change - Date/Time Yes Configurable 23 Charge To Practice 24 Diagnostic Serv Sect Id HL7 Conformance Statement 1.1 IKRU Issue:

36 Table BR Attribute Support in Seq HL7 Field Name Value Required (Yes/) 25 Result Status Yes Configurable 26 Parent Result 27 Quantity/Timing Yes Configurable 28 Result Copies To 29 Parent Number 30 Transportation Mode Yes Configurable 31 Reason For Study Yes Configurable 32 Principal Result Interpreter 33 Assistant Result Interpreter 34 Technician 35 Transcriptionist 36 Scheduled Date/Time Yes Configurable 37 Number of Sample Containers 38 Transport Logistics of Collected Sample 39 Collector's Comment 40 Transport Arrangement Responsibility 41 Transport Arranged 42 Escort Required 43 Planned Patient Transport Comment 44 Procedure Code HL7 Conformance Statement 1.1 IKRU Issue:

37 4.2.7 ZDS Segment Table ZDS Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Study Instance UID Yes DFT Segment Table DFT Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - FT1 Yes 2 Transaction ID 3 Transaction Batch ID 4 Transaction Date R Yes 5 Transaction Posting Date 6 Transaction Type R Yes 7 Transaction Code R Yes 8 Transaction Description 9 Transaction Description 10 Transaction Quantity Yes 11 Transaction Amount Yes 12 Transaction Amount -Unit 13 Department Code 14 Insurance Plan ID 15 Insurance Amount 16 Assigned Patient Location 17 Fee Schedule 18 Patient Type 19 Diagnosis Code - FT1 20 Performed By Code 21 rdered By Code HL7 Conformance Statement 1.1 IKRU Issue:

38 Table DFT Attribute Support in Seq HL7 Field Name Value Required (Yes/) 22 Unit Cost 23 Filler rder Number Yes Configurable 24 Entered By Code 25 Procedure Code HL7 Conformance Statement 1.1 IKRU Issue:

39 4.2.9 PR1 Segment Table PR1 Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - PR1 Yes 2 Procedure Coding Method R Yes 3 Procedure Code R Yes 4 Procedure Description Yes Configurable 5 Procedure Date/Time Yes 6 Procedure Functional Type 7 Procedure Minutes Yes Configurable 8 Anesthesiologist 9 Anesthesia Code 10 Anesthesia Minutes 11 Surgeon 12 Procedure Practitioner Yes Configurable 13 Consent Code 14 Procedure Priority Yes Configurable 15 Associated Diagnosis Code 16 Procedure Code Modifier 17 Procedure DRG Type 18 Tissue Type Code HL7 Conformance Statement 1.1 IKRU Issue:

40 4.2.10BX Segment Table BX Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - BX R Yes 2 Value Type R Yes 3 bservation Identifier R Yes 4 bservation Sub-Id 5 bservation Value R Yes 6 Units 7 References Range Yes 8 Abnormal Flags 9 Probability 10 Nature of Abnormal Test 11 bservation Result Status R 12 Date Last bservation rmal Value Yes 13 User Defined Access Checks 14 Date/Time of the bservation Yes Configurable 15 Producer's ID Code 16 Responsible bserver Yes Configurable 17 bservation Method 18 Equipment Instance Identifier 19 Date/Time of the Analysis HL7 Conformance Statement 1.1 IKRU Issue:

41 4.2.11TXA Segment Table TXA Attribute Support in Seq HL7 Field Name Value Required (Yes/) 1 Set ID - TXA R Yes 2 Document Type R Yes 3 Document Content Yes 4 Activity Date/Time Yes 5 Primary Activity Provider Yes 6 rigination Date/Time Yes 7 Transcription Date/Time Yes 8 Edit Date/Time Yes 9 riginator Code/Name Yes 10 Assigned Document Yes 11 Transcriptionist 12 Unique Document R Yes 13 Parent Document 14 Placer rder 15 Filler rder Number Yes 16 Unique Document File Yes 17 Document Completion R Yes 18 Document Confidentiality 19 Document Availability 20 Document Storage Status 21 Document Change Yes 22 Authentication Person 23 Distributed Copies HL7 Conformance Statement 1.1 IKRU Issue:

42 5 Queries 5.1 Query can issue the query to search patient demographic data using HL7 QBP^Q22 message Query MSH Segment creates the MSH segments as follows: Table 4-1. MSH segments Seq HL7 Field Name Value Required Default Mapping to Attribute(s) (Yes/) 1 Field Separator 2 Encoding Characters 3 Sending Application 4 Sending Facility 5 Receiving Application Configured MPI Application 6 Receiving Facility Configured MPI Facility 7 Date/time of Message Current timestamp 8 Security 9 Message Type QBP^Q22 10 Message Control ID 11 Processing ID 12 Version ID 13 Sequence Number 14 Continuation Pointer 15 Accept Acknowledgement Type Installationsanleitung 1.1 IKRU Issue:

43 Table 4-1. MSH segments Seq HL7 Field Name Value Required 16 Application Acknowledgement Type Default Mapping to Attribute(s) (Yes/) 17 Country Code 18 Character Set 19 Principal Language of Message Query QPD Segment The following table describes how creates the QPD segment of the query message. Table 4-2. QPD Attribute Support in Seq HL7 Field Name Value Required Default Mapping from Attribute(s) (Yes/) 1 Message Query Name R Yes Template 2 Query Tag R 3 User Parameters R 4 User Parameters Query RCP Segment The following table describes how creates the QPD segment of the query message. Table 4-3. RCP Attribute Support in Seq HL7 Field Name Value Required Default Mapping from Attribute(s) (Yes/) 1 Query Priority Yes Fix "I" (Immediate) 2 Quantity Limited Request 3 Response Modality Installationsanleitung 1.1 IKRU Issue:

44 Table 4-3. RCP Attribute Support in Seq HL7 Field Name Value Required Default Mapping from Attribute(s) (Yes/) 4 Execution and Delivery Time 5 Modify Indicator 6 Sort-by Field 7 Segment group inclusion Installationsanleitung 1.1 IKRU Issue:

45 CNTACT i-slutins Health GmbH Am Exerzierplatz Mannheim Telefon: Telefax: Burgstr Bochum Telefon: Telefax: info@i-solutions.de Copyright 2014 i-slutins Health GmbH. All rights reserved.