TMY PACS HL7 Conformance Statement

Transcription

1 Rev.: 01 Pg. 1 of 7 Written or Updated by: Name Title Date Signature Erdal Orak technical department 11-v-2013

2 Rev.: 01 Pg. 2 of 7 Contents 1. INTRODUCTION Purpose and Intended Audience of this Document Liability Acronyms and Abbreviations INBOUND MESSAGES HL7 to MVD Mappings MSH Segment Mappings PID Segment Mappings PV1 Segment Mappings ORC Segment Mappings OUTBOUND MESSAGES QUERIES... 7

3 Rev.: 01 Pg. 3 of 7 1. INTRODUCTION 1.1. PURPOSE AND INTENDED AUDIENCE OF THIS DOCUMENT This document is a HL7 for the HL7 Services of TMYPACS.The user of this document is involved with system integration and/or software design. Weassume that the reader is familiar with the terminology and concepts that are used in the HL7 standard and the IHE Technical Framework.Readers not familiar with HL7 terminology should first read the appropriate parts of the HL7standard 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 TMYPACS System, it is not sufficient to guarantee, byitself, the inter -operation of the connection between TMYPACS System and the 3rd party HL7-basedsystem. 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.the responsibility for analyzing the applications requirements and developing a solution thatintegrates the TELEMEDIKAL equipment with other vendors systems is the user s responsibility and should not be underestimated LIABILITY TELEMEDİKALYAZILIM shall notbe liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this publication. TELEMEDİKALYAZILIM reserves the right to revise this publication and to make changes to its content at any time, withoutobligation to notify any person or entity of such revisions and changes. This publication may only be used in connection with the promotion, sales, installation and useof TELEMEDI AL equipment by TELEMEDI AL personnel ACRONYMS AND ABBREVIATIONS HL7 Health Level 7 IHE Integrating the Healthcare Enterprise MSH Message Header segment OBR Observation Request segment ORC Common Order segment PID Patient ID segment PV1 Patient Visit segment

4 Rev.: 01 Pg. 4 of 7 2. INBOUND MESSAGES 2.1. HL7 TO TMYPACS MAPPINGS The following sections describe the default mapping of data from an HL7 message to an TMY message MSH SEGMENT MAPPINGS 1 Field Separator Yes 2 Encoding Characters 3 Sending Application 4 Sending Facility 5 Receiving Application 6 Receiving Facility 7 Date/time of Message 8 Security 9 Message Type 10 Message Control ID 11 Processing ID 12 Version ID 13 Sequence Number 14 Continuation Pointer Accept 15 Acknowledgement Type Application 16 Acknowledgement Type 17 Country Code 18 Character Set Principal Language of 19 Message PID SEGMENT MAPPINGS 1 Set ID Patient ID 2 Patient ID Yes PatientID 3 Patient ID List 4 Alternate Patient ID 5 Patient Name Yes PatientName First^Last

5 Rev.: 01 Pg. 5 of 7 6 Mother s Maiden Name 7 Date of Birth 8 Sex Yes PatientGendre 9 Patient Alias 10 Race 11 Patient Address Yes PatientAddress 13 Phone Number Home Yes PatientPhone Phone Number 14 Business 15 Primary Language 16 Marital Status Yes PatientStatus 17 Religion 18 Patient Account Number 19 SSN Number Patient 22 Ethnic Group 23 Birth Place 24 Multiple Birth Indicator 25 Birth Order 28 Nationality Patient Death 29 Date/Time 30 Patient Death Indicator PV1 SEGMENT MAPPINGS 1 Set ID - Patient Visit 2 Patient Class 3 Assigned Patient Location Yes 4 Admission Type 5 Pre-admit Number 6 Prior Patient Location 7 Attending Doctor 8 Referring Doctor 9 Consulting Doctor 10 Hospital Service 11 Temporary Location 13 Readmission Indicator 14 Admit Source 15 Ambulatory Status 16 VIP Indicator 17 Admitting Doctor 19 Visit Number 29 Transfer to Bad Debt

6 Rev.: 01 Pg. 6 of 7 Code 36 Discharge Disposition 37 Discharged to Location 39 Servicing Facility 42 Pending Location 43 Prior Temporary Location 44 Admit Date/Time 45 Discharge Date/Time Physician Mappings A physician mapping ideally will always have a name and an ID. This will correctly populate the tmypacs_person and tmypacs_person_id tables. New entries in each table are only created for new unique name and ID pairs.if only a name is present, a new person table entry is always created and no entry is made in the tmypacs_person_id table. So for each ^ALI^EK BER which shows up as a physician, you will get one newtableentry. If onlyanid ispresent, the name is assumed to be blank. New entries arecreatedforeach uniqueid.each person_id has a reference to itsown entry in the person table(whichhasa blankname).this logic applies to all physician mappings in the PV1,ORC,and OBRsegments ORC SEGMENT MAPPINGS 1 Order Control Yes 2 Placer Order # Yes 3 Filler Order # Yes 4 Placer Group # 5 Order Status Yes 6 Response Flag 7 Quantity/Timing 8 Parent 9 Date/Time of Transaction Yes 10 Entered By 11 Verified By 12 Ordering Provider 13 Enterer s Location 14 Call Back Phone Number 15 Order Effective Date/Time 16 Order Control Reason 17 Entering Organization Yes TMYPACSDepartment 18 Entering Device Yes TMYPACSStation 19 Action By

7 Rev.: 01 Pg. 7 of 7 3. OUTBOUND MESSAGES TMYPACS does support outbound messages. 4. QUERIES TMYPACS does support queries.