Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System. HL7 Results Specification

HL7 Results Specification Imaging Quickly and easily connect your Imaging System with Practice Fusion s Electronic Health Record (EHR) System 1 P a g e HL7 Results Specification

About This Document This document describes how to integrate with Practice Fusion s Electronic Health Record (EHR) system by submitting Observation Result Unsolicited messages that contain imaging results data to the Practice Fusion API. Audience This document is intended for developers who are familiar with the nature of Health Level Seven (HL7) messages and have previously integrated imaging results information with other systems. It is not intended to provide a comprehensive education about HL7 messages and integrations. For comprehensive information about the HL7 specification, go to http://www.hl7.org. Practice Fusion also provides a tool named Practice Fusion Client that monitors a directory for ORU_R01 messages and sends them to Practice Fusion for RIS that do not wish to integrate directly with the API. For information on how to use this tool instead of the API, see the Practice Fusion Client Quick Start Guide or the Practice Fusion Client User Guide. How to Use This Document You should read Understanding the Practice Fusion ORU_R01 Implementation first. That section attempts to summarize the most important details about the Practice Fusion specification to pay attention to without reading the entire document. The Sample Messages section gives examples of messages that validate successfully against the Practice Fusion API. The ORU_R01 Detailed Segment Definitions section then documents each field in detail, which can be helpful if your messages are being rejected because of a specific field. The Practice Fusion User Interface section identifies the user interface elements in Practice Fusion that display fields in a message. The Practice Fusion SOAP-Based Services and Practice Fusion RESTful Services sections describe how to invoke those services to send HL7 data to the Practice Fusion API. The Appendix section details the cardinality, requiredness, and data type information about each field. Recommended Utilities There are several utilities you can use to view and edit HL7 files while testing your integration, which can be more helpful than trying to count delimiter positions in a text editor. Some are: QuickViewHL7 (http://sourceforge.net/projects/quickviewhl7) HL7 Analyst (http://hl7analyst.codeplex.com/downloads/get/287761) HL7 Inspector (http://sourceforge.net/projects/hl7inspector/) 2 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Versions and Code Sets HL7 version 2.3 The Practice Fusion lab result API operates on HL7 version 2.3. More information about HL7 and version 2.3 of the standard can be found at www.hl7.org LOINC version 2.27 or higher The Practice Fusion lab result API works with observation requests and observations based upon the LOINC 2.27 standard or higher. All incoming results are expected to be primary coded using LOINC, and optionally coded with internal identifiers. More information about LOINC can be found at www.loinc.org. 3 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Understanding the Practice Fusion ORU_R01 Implementation The next section ORU_R01 Detailed Segment Definitions documents the properties of each segment and field in an ORU_R01 message that can be processed by Practice Fusion. This section presents a higher-level overview of the Practice Fusion implementation to provide you with an idea of where to focus most of your effort, and how this integration project might differ from other integration projects. Practice Fusion ignores all data in the Order Common (ORC) segment. The order number, accession number, and date and time of the report are all taken from the last Observation Request (OBR) segment contained in the message. Make sure that the value generated for the OBR-2 Placer Filler Number contains a unique value for each imaging order; if it does not, the result will be imported as a corrected or final result. Note (NTE) segments can be associated with the following segments: The Patient Identification (PID) segment, where the note applies to the entire imaging result The OBR segment, where the note applies to all observations related to that procedure The OBX segment, where the note applies to only that one observation or test Although the PID-5 Patient Name field is the only field required in the PID segment (aside from the segment type id field), Practice Fusion recommends that you populate as many fields as possible to equip providers with as much information as possible to deliver quality healthcare. Phone numbers in every field in the message must be formatted in a specific way for the message to validate successfully. The rules for valid phone numbers are: Opening parentheses Three-digit area code Closing parentheses Three-digit exchange number Hyphen Four-digit subscriber number No spaces in data Example: (555)555-5555 All fields containing Social Security Numbers must match the following regular expression: \\b(?!000)(?!666)(?!9)[0-9]{3}[-]?(?!00)[0-9]{2}[- ]?(?!0000)[0-9]{4}\\b The rules for invalid SSN's are: Numbers with all zeros in any digit group (000-##-####, ###-00-####, ###-##-0000) Numbers with 666 in the first digit group (666-##-####) Numbers with 900 through 999 in the first digit group Example: 155-70-5049 4 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Sample Messages This section contains sample messages that conform to the Practice Fusion ORU_R01 message specification. Bare Minimum File MSH ^~\& madhatterpracti 20090826163020 ORU^R01 MessageControlID P 2.3 PID Smith^John^Pete PV1 AttendingPhysicianID^AttendingPhysicianLastName^AttendingPhysicianFirst Name OBR 1 Placer1234 Filler56789 TestID^TestName^IDSystem ObservationDate/Time SpecimenReceivedDate/Time ResultChangeDate/Time ResultStatus(From HL7 table 0123) OBX 1 OBX5- DataType ObservationID^ObservationName^IDSystem ResultValue 20090831145055 With Two Attachments MSH ^~\& SendingApplication SendingFacility PracticeAccount# ORU^R01 MessageCo ntrolid P 2.3 PID PatientLastName^PatientFirstName^PatientMiddleName PV1 AttendingPhysicianID^AttendingPhysicianLastName^AttendingPhysicianFirst Name OBR 1 Placer1234 Filler56789 TestID^TestName^IDSystem ObservationDate/Time SpecimenReceivedDate/Time ResultChangeDate/Time ResultStatus(From HL7 table 0123) OBX 1 OBX5- DataType ObservationID^ObservationName^IDSystem ResultValue LastObservatio ndate/time NTE 1 TX A note on the order NTE 2 TX Another line in the note OBX 2 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 3 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 4 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 5 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 6 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 7 ED PDF^PDF BASE64 1 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 2 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 5 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

OBX 3 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 4 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 5 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 6 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 OBX 7 ED PDF^PDF BASE64 2 ^PDFReport^PDF^Base64^RTlENTUxOTFDMTIwQzQ3OUE0MDU2NzZDNkM4ODI1Mz5dL0luZG V4WzE4IDI4 6 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

ORU_R01 Detailed Segment Definitions This section of the document provides detailed information about every field in every segment. Each item in the following bulleted list links to the section that describes the identified segment: Message Header (MSH) 9 Patient Identification (PID) 13 Patient Visit (PV1) 18 Order Common (ORC) 29 Observation Request (OBR) 34 Observation Result (OBX) 43 Note (NTE) 49 File Trailer Segment (FTS) 50 Each subsection provides a brief description of the segment and an example of the data it might contain in a valid message. The fields of each segment are detailed in a table with eight columns. When a field should contain values from a table identified by HL7 and the number of values is manageable, those values are included for convenience; if the number of values is too large (for example, in the case of Country Codes), the table is identified but only a few examples are given to avoid making the guide too large. Table 1: Field Information identifies each column and describes what information it provides about the field. Table 1: Field Information Column Name Seq Name Value Type Req d Length Contents Contains the sequence number of the field within the message. Contains the name of the field. Contains the value that must appear in the field (such as ORU^R01 for the Message Type field) or that might appear in the field (such as an example value for a date field that will not always contain the same value), as well as rules that must be applied to the data (such as the required structure for a Social Security Number). Hard-coded or example values are formatted in Courier font to make them easy to identify from surrounding text. Identifies the data type of the field. For detailed information about each data type, see Data Types in the appendix. The value in this column is linked to its definition in the appendix. Identifies whether the field is required, optional, or required in certain conditions. For detailed information about each possible value, see Requiredness in the appendix. The value in this column is linked to its definition in the appendix. Identifies the maximum length of this field. Fields that contain more characters in this field than are specified by the maximum length are truncated when processed by the API. 7 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Column Name Card Used? Disp? Contents Identifies the cardinality of the field. For detailed information about each possible cardinality state, see Cardinality in the appendix. The value in this column is linked to its definition in the appendix. Indicates whether or not the field is used at all in the business logic of Practice Fusion. Indicates whether or not the field is displayed or not in the Practice Fusion application; some fields might be used in the logic layer, but never displayed in the presentation layer. 8 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Message Header (MSH) The MSH segment is the first segment in every HL7 message, and defines the message s source, purpose, destination, and certain syntax specifics such as the delimiters and character sets used in the message. The MSH segment is required and may only appear once. MSH ^~\& accountidentifer 20120816122332-0800 ORU^R01 MessageID1234 P 2.3 Seq Name Value Type Req d Length Card Used? Disp? MSH-0 MSH-1 MSH-2 Segment identifier Field delimiter Encoding characters MSH ST R 3 1..1 Y N (the pipe character) ST R 1 1..1 Y N ^~\& ST R 4 1..1 Y N MSH-3 Sending application Identifies your application Example: Radiology InformationSystemNa me HD O 180 0..1 N N MSH-4 Sending facility Identifies the sending radiology or reporting site HD O 180 0..1 N N Example: Wildfire_Atlanta^45 D0470381^CLIA MSH-5 Receiving application Identifies Practice Fusion as the destination HD O 180 0..1 N N Example: Practice Fusion MSH-6 Receiving facility Identifies the healthcare organization for which the message is intended HD R 200 1..1 Y MSH-6 Example: DrSussmanPractice 9 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? MSH-7 Message date and time Identifies the date and time the message was created TS R 26 1..1 Y N Example: 20130205022300-0500 MSH-8 Security Used in some implementations for security features ST O 40 0..1 N N MSH-9 Message type ORU^R01 CM R 7 1..1 N N MSH-10 Message control ID Contains the value the system uses to associate the message with the response to the message ST R 200 1..1 Y N Example: UNX3ZMH5YAPHBL63SB3 V MSH-11 Processing ID P for in production D for in debugging T for in training PT R 3 1..1 N N MSH-12 HL7 version 2.3 VID R 60 1..1 N N MSH-13 Sequence number A non-null value in this field indicates that the sequence number protocol is in use NM O 15 0..1 N N MSH-14 Continuation pointer Contains the value used by a system to associate a continuation message with the message that preceded it when the data of an unsolicited observation request must be split into multiple messages ST O 180 0..1 N N 10 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? MSH-15 Accept acknowledge ment type AL to always require accept acknowledgement messages to be returned ID O 2 0..1 N N NE to never require accept acknowledgements SU to only require accept acknowledgements for successfully transmitted messages ER to only require accept acknowledgements in the event of an error MSH-16 Application acknowledge ment type AL to always require application acknowledgements to be returned ID O 2 0..1 N N NE to never require application acknowledgements to be returned SU to require application acknowledgements to be returned only in response to successfully transmitted messages ER to only require application acknowledgements in the event of an error MSH-17 MSH-18 Country code HL7 recommends values from ISO table 3166 Example: US for United States Character set Valid character set codes are defined in HL7 table 0211 Example: ASCII for the ASCII character set ID O 2 0..1 N N ID O 6 0..1 N N 11 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? MSH-19 Principle language of message HL7 recommends values from ISO table 639 Example: en for English CE O 60 0..1 N N 12 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Patient Identification (PID) The PID segment is used by all applications as the primary means of communicating patient identification information. This segment contains identifying and demographic information about the patient that is not likely to change frequently. The PID segment is required and may only appear once. PID PF00001 TEST^PRESTON 19710425 M 555 South Main St.^APT #123^Some City^CA^94066 (555)555-1234 123-456-7890 Seq Name Value Type Req d Length Card Used? Disp? PID-0 Segment type ID PID SI R 3 1..1 N N PID-1 Sequence number Identifies the number of the PID segment in circumstances where the message contains multiple patient reports SI O 4 0..1 N N Example: 1 PID-2 External patient ID Unique identifier for the patient; retained for backward compatibility CX O 20 0..1 Y PID-2 Example: 9817566735 PID-3 Patient identifier list Uniquely identifies the patient using values such as a medical record number, billing number, birth registry, and so forth ST O 200 0..1 Y N Example: 9847466735^^^^PATGU ID PID-4 Alternate patient ID Contains alternate, pending, or temporary optional patient identifiers to be used, such as a social security number, a visit date, or a visit number; it has been retained for backward compatibility ID O 200 0..1 N N 13 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PID-5 PID-6 Patient name Example: Beth Emhoff Mother s maiden name <family name>^<given name>^<middle initial or name>^<suffix>^<prefix >^<degree>^<name type code> HD R 200 1..1 Y PID-5 Example: Jenner XPN O 48 0..1 N N PID-7 Patient date of birth Example: 19740509 DT O 8 0..1 Y PID-7 PID-8 Patient gender Valid gender codes are defined in HL7 table 0001 IS O 1 0..1 Y PID-8 Example: M for male PID-9 Patient alias 2106-3^White^HL70006 PID-10 Patient race Valid race codes are defined in HL7 table 0005 XPN O 48 0..1 N N CE O 80 0..1 N N Example: WH PID-11 Patient address Example: 123 MAIN ST^APT 4J, MIDDLE ROOM^NEW YORK^NY^10021^ XAD O 660 0..1 Y PID-11 <street address> ^ <other designation> ^ <city> ^ <state> ^ <zip> ^ <country> ^ <address type> ^ <other> ^ <county> ^ <census tract> PID-12 Patient county code Valid county codes are defined in HL7 table 0289 IS O 4 0..1 N N Example: 42001 14 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PID-13 Patient home phone number The rules for valid phone numbers are: Opening parentheses Three-digit area code Closing parentheses Three-digit exchange number Hyphen Four-digit subscriber number No spaces in data XTN O 13 0..1 Y PID-13 Example: (555)555-5555 PID-14 Patient work phone number Example: (555)555-5556 XTN O 13 0..1 N N PID-15 Patient language HL7 recommends values from ISO table 639 CE O 60 0..1 N N Example: en for English PID-16 Patient marital status Valid marital status codes are defined in HL7 table 0002 CE O 80 0..1 N N Example: M for married PID-17 Patient religion Valid religion codes are defined in HL7 table 0006 CE O 80 0..1 N N Example: OTH for Other PID-18 Patient account number Contains the number assigned by accounting for the patient against which all charges and payments are recorded CX O 250 0..1 N N Example: 9817566735 15 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PID-19 Patient Social Security Number Social Security Numbers must match the following regular expression: ST O 16 0..1 N N \\b(?!000)(?! 666)(?!9)[0-9]{3}[- ]?(?!00)[0-9]{2}[- ]?(?!0000)[0-9]{4}\\b The rules for invalid SSN's are: Numbers with all zeros in any digit group (000-##-####, ###-00-####, ###- ##-0000) Numbers with 666 in the first digit group (666-##-####) Numbers with 900 through 999 in the first digit group Example: 155-70-5049 PID-20 Driver s license number Example: B9559796 DLN O 25 0..1 N N PID-21 Mother s identifier Used to link a newborn to its mother by her unique identifier CX O 20 0..1 N N Example: 9817566735 PID-22 Patient ethnic group Valid ethnic groups are defined in HL7 table 0189 CE O 80 0..1 N N Example: H for Hispanic PID-23 Patient birth place Example: 123 MAIN ST^APT 4J, MIDDLE ROOM^NEW YORK^NY^10021^ ST O 60 0..1 N N 16 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PID-24 Multiple birth indicator Valid multiple birth indicators are defined in the HL7 yes/no table 0136 ID O 1 0..1 N N Example: Y to indicate the patient was part of a multiple birth PID-25 Birth order Indicates the order in which the patient was born if part of a multiple birth NM O 2 0..1 N N Example: 1 PID-26 Citizenship HL7 recommends values from ISO table 3166 CE O 80 0..1 N N Example: US for United States PID-27 Veteran s military status Specifies the code in userdefined table 0172 to identify the military status of a veteran CE O 60 0..1 N N PID-28 Nationality Contains a code that identifies the nation or national grouping to which the person belongs. This information may be different from a person s citizenship in countries in which multiple nationalities are recognized, such as Basque and Catalan in Spain Valid nationality codes are defined in HL7 table 0212 CE O 80 0..1 N N PID-29 Patient death date and time Example: 20130205022300-0500 TS O 26 0..1 N N PID-30 Patient death indicator Valid death indicators are defined in the HL7 yes/no table 0136 ID O 1 0..1 N N Example: N to indicate the patient has not died 17 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Patient Visit (PV1) The PV1 segment contains information about a specific patient visit. This segment can be used to send multiplevisit statistic records to the same patient account or single-visit records to more than one account. The PV1 segment is required and should appear only once. PV1 1 12345^Who^Doctor Seq Name Value Type Req d Length Card Used? Disp? PV1-0 PV1-1 Segment identifier Sequence number PV1 SI R 3 1..1 N N 1 SI O 1 0..1 N N PV1-2 Patient class Valid patient classes are defined in HL7 table 0004 C for commercial account N for not applicable U for unknown E for emergency I for inpatient O for outpatient P for preadmit R for recurring patient B for obstetrics IS O 4 0..1 N N PV1-3 Assigned patient location Identifies the patient s initial assigned location or the location to which the patient is being moved. The first component may be the nursing station for inpatient locations, or clinic or department for locations other than inpatient. For situations where a transaction is being cancelled or a patient is being discharged, this field identifies the current PL O 80 0..1 N N 18 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? location of the patient. If a value exists in the fifth component (location status), it supersedes the value in PV1-40 - Bed Status PV1-4 Admission type Valid admission type codes are defined in HL7 table 0007 IS O 2 0..1 N N A for accident C for elective E for emergency L for labor and delivery N for newborn R for routine U for urgent PV1-5 Pre-admit number Identifies the patient s account prior to admission CX O 250 0..1 N N PV1-6 Prior patient location Identifies the prior location of the patient when being transferred; the old location is null if the patient is new. If a value exists in the fifth component (location status), it supersedes the value in PV1-40 - Bed Status PL O 80 0..1 N N PV1-7 Attending provider Unique identifier for the attending provider XCN R 400 1..1 Y PV1-7 PV1-8 Referring provider Unique identifier for the referring provider XCN O 250 0..1 N N PV1-9 Consulting provider Unique identifier for a consulting provider XCN O 250 0..1 N N PV1-10 Hospital service Valid hospital service codes are defined in HL7 table 0069 IS O 3 0..1 N N CAR for cardiac service MED for medical service 19 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PUL for pulmonary service SUR for surgical service URO for urology service PV1-11 Temporary location A location other than the assigned location required for a temporary period of time, such as an operating room; if a value exists in the fifth component (location status), it supersedes the value in PV1-40 - Bed Status PL O 80 0..1 N N PV1-12 Preadmit test indicator Specifies the code in userdefined table 0087 that Indicates whether the patient must have preadmission testing done in order to be admitted IS O 2 0..1 N N PV1-13 Readmission indicator Indicates whether or not the patient is being readmitted to the facility IS O 2 0..1 N N HL7 recommends a null value, or R for readmission PV1-14 Admit source Valid admission source codes are defined in HL7 table 0023 1 for physician referral 2 for clinic referral 3 for HMO referral 4 for transfer from a hospital 5 for transfer from a skilled nursing facility 6 for transfer from another healthcare facility 7 for emergency room 8 for court/law enforcement 9 for information not IS O 6 0..1 N N 20 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? available PV1-15 Ambulatory status Valid ambulatory status codes are defined in HL7 table 002309 IS O 2 0..1 N N A0 for No functional limitations A1 for Ambulates with assistive device A2 for Wheelchair/stretcherbound A3 for Comatose; nonresponsive A4 for Disoriented A5 for Vision impaired A6 for Hearing impaired A7 for Speech impaired A8 for Non-English speaking A9 for Functional level unknown B1 for Oxygen therapy B2 for Special equipment (tubes, IVs, catheters, etc.) B3 for Amputee B4 for Mastectomy B5 for Paraplegic B6 for Pregnant PV1-16 VIP indicator Valid very-importantperson (VIP) status indicators are defined in the HL7 yes/no table 0136 Y to indicate VIP status N to indicate standard status IS O 2 0..1 N N PV1-17 Admitting provider Unique identifier for the admitting provider XCN O 250 0..1 N N 21 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PV1-18 Patient type Specifies the code in userdefined table 0018 to identify the type of patient IS O 2 0..1 N N PV1-19 Visit number Contains the unique number assigned to the patient visitation CX O 250 0..1 N N PV1-20 Financial class Valid financial classes are defined in HL7 table 0064 FC O 50 0..1 N N V01 for Not VFC eligible V02 for VFC eligible Medicaid/Medicaid Managed Care V03 for VFC eligible Uninsured V04 for V eligible American Indian/Alaskan Native V05 for VFC eligible Federally Qualified Health Center Patient (underinsured) V06 for VFC eligible State-specific eligibility (for example S-CHIP plan) V07 for VFC eligible local-specific eligibility V08 for Not VFC eligible Under-insured PV1-21 Charge price indicator Specifies the code in userdefined table 0032 to determine which price schedule is to be used for room and bed charges IS O 2 0..1 N N PV1-22 Courtesy code Specifies the code in userdefined table 0045 to identify the type of insurance coverage or types of services that are covered for the billing system; for example, a physician s billing system might only IS O 2 0..1 N N 22 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? want to receive insurance information for plans that cover physician or professional charges PV1-23 Credit rating Specifies the code in userdefined table 0046 to determine past credit experience IS O 2 0..1 N N PV1-24 Contract code Specifies the code in userdefined table 0044 to identify the type of contract entered into by the healthcare facility and the guarantor for the purpose of settling outstanding account balances IS O 2 0..1 N N PV1-25 Contract effective date Specifies the date the contract started or is to start DT O 8 0..1 N N Example: 20001031 PV1-26 Contract amount Specifies the amount to be paid by the guarantor each period according to the contract NM O 12 0..1 N N PV1-27 Contract period Specifies the duration of the contract NM O 3 0..1 N N PV1-28 Interest code Specifies the code in userdefined table 0073 to identify the amount of interest that will be charged the guarantor on any outstanding amounts IS O 2 0..1 N N PV1-29 Transfer to bad debt code Specifies the code in userdefined table 0110 to indicate that the account was transferred to bad debts and specifies the reason IS O 1 0..1 N N PV1-30 Transfer to bad debt date Example: 20130122 DT O 8 0..1 N N 23 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? PV1-31 Bad debt agency code Specifies the code in userdefined table 0021 to identify the bad-debt agency to which the account was transferred IS O 10 0..1 N N PV1-32 Bad debt transfer amount Contains the amount of money transferred to baddebt status NM O 12 0..1 N N PV1-33 Bad debt recovery amount Contains the amount of money recovered from the guarantor on the account NM O 12 0..1 N N PV1-34 Delete account indicator Specifies the code in userdefined table 0111 that indicates that the account was deleted from the file IS O 1 0..1 N N PV1-35 Delete account date Example: 20130122 DT O 8 0..1 N N PV1-36 Discharge disposition Specifies the code in userdefined table 0111 that identifies the patient s anticipated location or status following the encounter IS O 3 0..1 N N 01 for Discharged to home or self care (routine discharge) 02 for "Discharged/transferred to a short-term general hospital for inpatient care" 03 for "Discharged/transferred to skilled nursing facility (SNF) with Medicare certification" 04 for Discharged/transferred to an intermediate care facility (ICF) 05 for "Discharged/transferred to another type of institution not defined elsewhere in 24 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? this code list" 06 for "Discharged/transferred to home under care of organized home health service organization" 07 for Left against medical advice or discontinued care 08 for Discharged/transferred to home under care of a Home IV provider 09 for Admitted as an inpatient to this hospital 20 for Expired 30 for Still Patient 40 for Expired at home 41 for Expired in a medical facility (e.g. hospital, SNF, ICF, or free-standing hospice) 42 for Expired - place unknown 43 for "Discharged/transferred to a federal health care facility" 50 for "Hospice - home" 51 for "Hospice - medical facility" 61 for "Discharged or transferred to hospitalbased Medicare approved swing bed" 62 for "Discharged or transferred to an inpatient rehabilitation facility (IRF) including rehabilitationdistinct part units of a hospital" 63 for "Discharged or transferred to a Medicare- 25 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? certified long-term-care hospital" 64 for "Discharged or transferred to a nursing facility certified under Medicaid but not certified under Medicare" 65 for "Discharged or transferred to a psychiatric hospital or psychiatricdistinct unit of a hospital" 66 for "Discharged or transferred to a Critical Access Hospital" PV1-37 Discharged to location Specifies the code in userdefined table 0113 that identifies the location to which the patient was discharged CM O 25 0..1 N N PV1-38 Diet type Specifies the code in userdefined table 0114 that identifies a diet the patient must adhere to, such as liquid or fasting IS O 2 0..1 N N PV1-39 Servicing facility Specifies the code in userdefined table 0115 that identifies the particular facility in a multiple-facility environment that is associated with the visit IS O 2 0..1 N N PV1-40 Bed status Specifies the code in userdefined table 0116 that identifies the status of the patient s bed; for example, that the bed is occupied, available, or requires cleaning IS O 2 0..1 N N PV1-41 Account status Specifies the code in userdefined table 0117 that identifies the status of the patient s account IS O 2 0..1 N N PV1-42 Pending The location to which the PL O 80 0..1 N N 26 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? location patient may be moved. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient. If a value exists in the fifth component (location status), it supersedes the value in PV1-40 - bed status PV1-43 Prior temporary location Identifies the patient s temporary location (such as the operating room or x-ray facility) prior to a transfer from a temporary location to an actual location, or from a temporary location to another temporary location. The first component may be the nursing station for inpatient locations, or the clinic, department, or home for locations other than inpatient PL O 80 0..1 N N PV1-44 PV1-45 Admit date and time Discharge date and time 20130205022300-0500 TS O 26 0..1 N N 20130205022300-0500 TS O 26 0..1 N N PV1-46 Current patient balance Specifies the balance due for the visit NM O 12 0..1 N N PV1-47 Total charges Specifies the total charges for the visit NM O 12 0..1 N N PV1-48 Total adjustments Specifies the total adjustments for the visit NM O 12 0..1 N N PV1-49 Total payments Specifies the total payments for the visit NM O 12 0..1 N N PV1-50 Alternate Specifies the code in HL7 table 0061 that contains the CX O 250 0..1 N N 27 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? visit ID alternative, temporary, or pending optional visit ID number to be used if needed PV1-51 Visit indicator Specifies the code in HL7 table 0326 that indicates the level at which the data is being sent A for account-level V for visit-level IS O 1 0..1 N N PV1-52 Other healthcare provider Identifies other healthcare providers (for example, nurse care practitioner, midwife, or physician assistant) XCN O 60 0..1 N N 28 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Order Common (ORC) The optional ORC segment identifies basic information about the order for interpretation of the image. This segment includes identifiers of the order, who placed the order, when it was placed, what action to take regarding the order, and so forth. The ORC segment is not required, but if it is present, the minimum information needed for the segment to be valid are the ORC-0, ORC-1, and ORC-5 fields. ORC RE 20130103131405196 F Seq Name Value Type Req d Length Card Used? Disp? ORC-0 Segment type ORC SI R 3 1..1 N N ORC-1 Order control Specifies the code in HL7 table 0119 that identifies the action to be taken for the order Examples: NW for new order or service request CA for cancel order or service request ID R 2 1..1 N N ORC-2 Placer order number Identifies the application requesting the order ED O 22 0..1 N N Example: 04fc7500-9e28-4340-800eb97fdd3c49d5 ORC-3 Filler order number The order number of the application filling the order ED O 22 0..1 N N Example: 27798445140^RIS ORC-4 Placer group number Used by the application placing the order to group sets of orders together and identify them ED O 22 0..1 N N ORC-5 Order status Specifies the code in HL7 table 0038 that identifies the status of the order. The purpose of this field is to report the status of an ID O 2 1..1 N N 29 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? order either upon the receipt of a solicited request, or when the status changes unsolicited. It does not initiate action. It is assumed that the order status always reflects the status as it is known to the sending application at the time that the message is sent. Only the filler can originate the value of this field. Although HL7 Table 0038 - Order status contains many of the same values contained in HL7 Table 0119 - Order Control Codes and their meaning, the purpose is different. Order status may typically be used in a message with an ORC-1 - Order Control value of SR or SC to report the status of the order on request or to any interested party at any time ER for Error, order not found SC for In progress, scheduled IP for In process, unspecified RP for Order has been replaced CM for Order is completed HD for Order is on hold CA for Order was cancelled DC for Order was discontinued A for Some, but not all results are available ORC-6 Response flag Specifies the code in HL7 table 0121 that allows the ID R 1 0..1 N N 30 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? placer application to determine the amount of information to be returned from the filler. Sometimes the requested level of response may not be possible immediately, but when it is possible, the filler application must send the information. When the field is null, D is the default interpretation of the field N for Only the Message Acknowledgement (MSA) segment is returned E for Report exceptions only R for Report exceptions, Replacement, and Parent- Child D for Report exceptions, Replacement, Parent-Child, and associated segments F for Report exceptions, Replacement, Parent-Child, associated segments, and explicit confirmations ORC-7 Quantity and timing Specifies the priority, quantity, frequency, and timing of an order request TQ O 200 0..1 N N Example for administration of a unit of blood: 1^QAM^X3 for three units given on successive mornings ORC-8 Parent Associates a child order request with its parent order request. For example, an application might receive a request to administer an electrocardiogram test on each of three successive mornings. The application creates three child orders CM O 200 0..1 N N 31 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? one for each morning and uses this field to associate them. After the first test is performed, a request might be received to cancel the test; the parent cannot be cancelled because one child has already been performed, but the remaining two children can be cancelled ORC-9 Date and time of transaction Identifies the date and time the request enters the application TS O 26 0..1 N N 20130205022300-0500 ORC-10 Entered by Identifies the individual responsible for entering the request into the application ORC-11 Verified by Identifies the individual responsible for verifying the accuracy of the request, such as when a technician enters the request and a nurse needs to verify it XCN O 250 0..* N N XCN O 250 0..* N N ORC-12 Ordering provider Identifies the individual responsible for creating the request, such as the ordering physician XCN O 250 0..* N N ORC-13 Enterer s location Identifies the location of the individual who entered the request, such as a nursing station or clinic PL O 80 0..* N N ORC-14 Callback phone number Identifies the telephone number to call for clarification of a request or other information regarding the order; identical to the value populated in OBR-17 Order Callback Phone Number XTN O 250 0..N (2) N N Example: (555)555-5555 32 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? ORC-15 Order effective date and time Specifies the date and time that changes to the request took effect or should take effect TS O 26 0..1 N N Example: 20130205022300-0500 ORC-16 Order control code reason Describes the reason that the ORC-1 Order Control field contains the value that it does; in the event of a cancellation, for example, it might explain that a physician s drug order was cancelled because of a possible allergic reaction to the drug CE O 250 0..1 N N ORC-17 Entering organization Identifies the organization (such as a medical group or department) that the individual identified in the ORC-10 Entered By field belonged to at the time they entered the order CE O 250 0..1 N N ORC-18 Entering device Identifies the physical device, such as a computer or ipad that the individual identified in the ORC-10 Entered By field used to enter the order CE O 250 0..1 N N ORC-19 Action by Identifies the individual who initiated the event represented by the corresponding order control code; for example, if the order is being cancelled, this field identifies the individual who initiated the cancellation XCN O 250 0..* N N 33 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Observation Request (OBR) The OBR segment is used to transmit information specific to an order for a diagnostic study or observation, physical exam, or assessment. It defines the attributes of a particular request for diagnostic services (for example radiology or EKG) or clinical observations, (for example, vital signs or physical exam). The OBR segment is required and may repeat. OBR 1 Placer1234 Filler56789 SOL23010^Potassium 20120816122332-0800 20120816122332- Seq Name Value Type Req d Length Card Used? Disp? OBR-0 Segment type OBR ST R 3 1..1 N N OBR-1 Sequence number SI R 4 1..1 N OBR-1 OBR-2 Placer order number Identifies the application requesting the order; identical to the value in ORC-2 Placer Order Number ED R 30 1..1 Y OBR-2 Example: 04fc7500-9e28-4340-800eb97fdd3c49d5 OBR-3 Filler order number Contains a permanent identifier for an order and its associated observations ED O 75 0..1 Y OBR-3 OBR-4 Universal service ID Specifies the code for the requested observation or test battery CE O 400 0..1 N OBR-4 Example: 266706003^SNOMED- CT^Continuous ECG monitoring OBR-5 Priority Specifies the priority of the request, but exists for backward compatibility only; in current implementations, the priority value is specified by the sixth component of the OBR-27 Quantity/Timing ID O 2 0..1 N N 34 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? field OBR-6 Requested date and time Specifies the date and time of the request, but exists for backward compatibility only; in current implementations, the value is specified by the fourth component of the OBR-27 Quantity/Timing field TS O 26 0..1 N N OBR-7 Observation date and time Identifies the clinicallyrelevant date and time of the observation TS R 26 1..1 Y OBR-7 In the case of observations taken directly from a subject, it is the actual date and time the observation was obtained In the case of a specimenassociated study, this field identifies the date and time the specimen was collected or obtained Example: 20130205022300-0500 OBR-8 Observation end date and time Identifies the end date and time of a study or timed specimen collection. If an observation takes place over a substantial period of time, it will indicate when the observation period ended. For observations made at a point in time, it will be null. This is a results field except when the placer or a party other than the filler has already drawn the specimen TS O 26 0..1 N N Example: 20130205022300-0500 OBR-9 Collection volume Specifies the collection volume of a specimen. Valid values are identified in Figure 7-13. Common CQ O 20 0..1 N N 35 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? ISO derived units and *ISO extensions in Chapter 7 of the HL7 specification Example: ML OBR-10 Collector identifier Identifies the individual, department, or facility that collected the specimen XCN O 60 0..* N N OBR-11 Action code Specifies the code in HL7 table 0065 that identifies the action to be taken with respect to the specimens that accompany or precede the order ID O 1 0..1 N OBR-11 A for Add ordered tests to the existing specimen G for Generated order; reflex order L for Imaging to obtain specimen from patient O for Specimen obtained by service other than a lab P for Pending specimen; order sent prior to delivery R for Revised order S for Schedule the tests specified below OBR-12 Danger code Contains the code, or text, or both that indicate any known or suspected patient or specimen hazards, such as a patient with active tuberculosis or blood from a patient with hepatitis. The code must always appear in the first component position and text must always appear in the second component; if the code is absent, the text must be preceded by a component delimiter CE O 60 0..1 N N 36 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? OBR-13 Relevant clinical information Contains additional clinical information about the patient or specimen, such as the suspected diagnosis and clinical findings on requests for interpreted diagnostic studies. For example, this field might identify the amount of inspired carbon dioxide for blood gasses, the point in the menstrual cycle for cervical pap tests, and other conditions that influence test interpretations. For some orders this information may be sent on a more structured form as a series of OBX segments that immediately follow the order segment ST O 300 0..1 N N OBR-14 Specimen received date and time Identifies the date and time a diagnostic service receives the specimen TS R 26 1..1 Y N Example: 20130205022300-0500 OBR-15 Specimen source Identifies the site where the specimen should be obtained or where the service should be performed. CM O 300 0..1 N N Valid codes for the specimen source code subcomponent are defined in HL7 table 0070. Valid codes for the body site code subcomponent are defined in HL7 table 0163 OBR-16 Ordering provider Identifies the individual that requested the order or prescription XCN O 80 0..* N N OBR-17 Order callback Identifies the telephone XTN O 40 0..N N N 37 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? phone number number to call for clarification of a request or other information regarding the order; identical to the value populated in ORC-14 Callback Phone Number (2) OBR-18 OBR-19 Example: (555)555-5555 Placer field #1 Contains free-form text entered by the placer Placer field #2 Contains free-form text entered by the placer ST O 60 0..1 N N ST O 60 0..1 N N OBR-20 Filler 1 Contains free-form text entered by the filler OBR-21 Filler 2 Contains free-form text entered by the filler ST O 60 0..1 N N ST O 60 0..1 N N OBR-22 Result reported date and time Identifies the date and time when the results are entered in a report or when the status value in the ORC- 5 - Order Status field was changed. When other applications (such as office or clinical database applications) query the radiology application for results that have not yet been transmitted, the information in this field may be used to control processing in the exchange. Usually, the ordering service would want only those results for which the reporting date and time is greater than the date and time the inquiring application last received results TS R 26 0..1 Y N Example: 20130205022300-0500 OBR-23 Charge to Contains the charge to the CM O 40 0..1 N N 38 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? practice ordering entity for the studies performed, when applicable. The first subcomponent is a dollar amount identified by the filler; the second subcomponent is a charge code identified by the filler OBR-24 Diagnostic serv sect ID Specifies the code in HL7 table 0074 that identifies where the observation was performed ID O 10 0..1 N N Examples: AU for Audiology RAD for Radiology OBR-25 Test status Specifies the code in HL7 table 0123 that identifies the status of results for the order ID R 1 1..1 Y OBR-25 O for Order received; specimen not yet received I for No results available; specimen received; procedure incomplete S for No results available; procedure scheduled but not performed yet A for Some, but not all results are available P for Preliminary: a verified early result is available, but final results are not yet obtained C for Correction to results R for Results stored, but not yet verified F for Final results are stored and verified; can only be changed with a corrected result X for No results available; 39 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? order cancelled Y for No order on record for this test Z for No record of the patient OBR-26 Parent result Identifies the OBX segment of a parent s result in situations such as toxicology tests CM O 400 0..1 N N OBR-27 Quantity and timing Specifies the priority, quantity, frequency, and timing of an order request; similar to the ORC-7 field TQ O 200 0..* N N OBR-28 Result copies to Identifies other individuals who are to receive copies of the result XCN O 150 0..N (5) N N OBR-29 Parent Associates a child order request with its parent order request; similar to the ORC-8 field CM O 150 0..1 N N OBR-30 Transportation mode Specifies the code in HL7 table 0124 that identifies how the patient should be transported ID O 20 0..1 N N CART for Cart or gurney PORT for The examining device is transported to the patient s location WALK for Patient walks to diagnostic service WHLC for Wheelchair OBR-31 Reason for study Specifies the code or text using the conventions for coded fields as documented in Chapter 2 of the HL7 specification CE O 300 0..* N N OBR-32 Principle result interpreter Identifies the individual who interpreted the observation and is responsible for the CM O 200 0..1 N N 40 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? contents of the report OBR-33 Assistant result interpreter Identifies the clinical observer who assisted with interpreting the observation CM O 200 0..* N N OBR-34 Technician Identifies the performing technician CM O 200 0..* N N OBR-35 Transcriptionist Identifies the transcriber of the report CM O 200 0..* N N OBR-36 Scheduled date and time Identifies the date and time the filler scheduled an observation TS O 26 0..1 N N Example: 20130205022300-0500 OBR-37 Number of sample containers Identifies the number of containers for a given sample NM O 4 0..1 N N OBR-38 Transport logistics of collected sample Identifies the means by which a sample reaches the diagnostic service provider, such as a transport van or public postal service CE O 60 0..* N N OBR-39 Collector s comment Contains additional comments related to the sample CE O 200 0..* N N OBR-40 Transport arrangement responsibility Identifies the individual responsible for arranging transport to the planned diagnostic service, such as Requester, Provider, or Patient CE O 60 0..1 N N OBR-41 Transport arranged Specifies the code in HL7 table 0224 that identifies whether or not transportation has been arranged ID O 30 0..1 N N A for Arranged N for Not arranged 41 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? U for Unknown OBR-42 Escort required Specifies the code in HL7 table 0225 that identifies whether or not an escort is required for the patient R for Required N for Not required U for Unknown ID O 1 0..1 N N OBR-43 Planned patient transport comment Contains a code or freeform comments on special requirements for the transportation of the patient CE O 200 0..* N N 42 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Observation Result (OBX) The OBX segment is used to transmit a single observation or observation fragment. It represents the smallest indivisible unit of a report and is designed to carry information about observations in report messages. The OBX segment is required and may repeat. OBX example with an imaging site: OBX 1 TX Identifier^ObservationName^NameOfCodingSystem 5.5 meq/l 2.5-5.3 H Status 20120816122332-0800 LP^Imaging Partners^123 SomeDrive^AnyTown^CA^95835^MedicalDirector^(555)555-1212 OBX example without an imaging site: OBX 1 TX Identifier^ObservationName^NameOfCodingSystem 5.5 meq/l 2.5-5.3 H Status 20120816122332-0800 OBX example with an Attachment: OBX 1 ED 1 ^PDFReport^PDF^Base64^JVBERi0xLjUNJeLjz9MNCjE4IDAgb2JqDTw8L0xpb mvhcml6zwqgms9midiy Seq Name Value Type Req d Length Card Used? Disp? OBX-0 OBX-1 Segment type Sequence number OBX ST R 3 1..1 N N SI R 6 1..1 N N OBX-2 Value type Contains the format of the observation value If the value is CE then the result must be a coded entry If the value is TX or ST then the results are bulk text If the value is ED, then the results will appear as an attached image CE, ST, NM, TX, ED, SN R 2 1..1 N N OBX-3 Observation identifier Contains a unique identifier for the observation, such as Local Observation Identifiers Names and Codes (LOINC) CE R 325 1..1 Y OBX-3 43 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? values OBX-4 Observation sub-id Contains a unique identifier for each OBX segment with the same value in the OBX-3 Observation Identifier field in a single Observation Request ST R 20 0..1 N N OBX-5 Observation value Contains the value observed by the producer 1 O 200 1..1 Y OBX-5 If the value in the OBX-2 Value Type field is ED, then this field should contain the embedded file value in OBX5.5; otherwise, this field should contain the value in OBX-5.1 This field can include a URL for more information if needed. OBX-6 Result units Specifies the ISO value of the units for the measurement CE O 50 0..1 Y OBX-6 OBX-7 Result unit reference range Specifies lower limits, upper limits, or both for result values ST O 50 0..1 Y OBX-7 Examples: > 10 1 This field contains the format of the observation value in OBX. It must be valued if OBX-11-Observation result status is not valued with an X". If the value is CE then the result must be a coded entry. When the value type is TX or FT then the results are bulk text. The valid values for the value type of an observation are listed in HL7 table 0125 - Value type. The observation value must be represented according to the format for the data type defined in Chapter 2, Section 2.8, "Data Types" in the HL7 documentation. For example, a PN consists of 6 components, separated by component delimiters. Although NM is a valid type, observations which are usually reported as numbers will sometimes have the string (ST) data type because non-numeric characters are often reported as part of the result, e.g., >300 to indicate the result was off-scale for the instrument. In the example, ">300", ">" is a symbol and the digits are considered a numeric value. However, this usage of the ST type should be discouraged since the SN (structured numeric) data type now accommodates such reporting and, in addition, permits the receiving system to interpret the magnitude. All HL7 data types are valid, and are included in Table 0125 except CM, CQ, SI, and ID. 44 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? < 15 3.5 4.5 OBX-8 Abnormal flags Specifies the code in HL7 table 0078 that identifies the normalcy status of the result IS O 2 0..N (5) Y OBX-8 L for below normal low LL for alert low < for panic low H for above normal high HH for alert high > for panic high A for abnormal N for normal AA for very abnormal U for significant change up D for significant change down B for better W for worse S for susceptible R for resistant I for intermediate MS for moderately susceptible VS for very susceptible NULL for no range defined, or normal ranges don t apply OBX-9 Probability Contains a decimal value between 0 and 1 that identifies the probability of the result being true NM O 5 0..1 N N OBX-10 Nature of abnormal Specifies the codes in HL7 table 0080 that identify the ID O 2 0..* N N 45 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? test nature of an abnormal test A for An age-based population N for Non-generic normal range R for A race-based population S for A sex-based population OBX-11 Observation result status Specifies the codes in HL7 table 0085 that identifies the current completion status of the observation result ID R 20 1..1 Y OBX-11 C for Record coming over is a correction and replaces a final result D for Delete the OBX record F for Final results; can only be changed with a corrected result I for Specimen in lab; results pending P for Preliminary results R for Results entered but not yet verified S for Partial results X for Results cannot be obtained for this observation U for Results status change to Final without retransmitting results already sent as preliminary W for Post original as wrong, such as when the results were sent for the wrong patient OBX-12 Effective date of last Contains changes in the observation methods that DT O 26 0..1 N N 46 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? normal observation would make values obtained from an old method not comparable with those obtained from the new method OBX-13 User-defined access checks Permits the producer to record results-dependent codes for classifying the observation at the receiving system ST O 20 0..1 N N OBX-14 Observation date and time Identifies the physiologically-relevant date and time of the report DT O 26 0..1 Y OBX-14 20130205022300-0500 OBX-15 Producer s id (imaging site information) Contains the unique identifier of the responsible producing service CE O 903 0..1 Y OBX-15 <Radiology Site ID>^<Radiology Site Name>^<Radiology Site Street Address>^<Radiology Site City>^<Radiology Site State>^<Radiology Site Zip>^<Radiology Site Director Name>^<Radiology Site Phone Number> OBX-17 Responsible observer Contains the unique identifier of the individual responsible for performing or verifying the observation XCN O 3220 0..1 N N OBX-17 Observation method Identifies the method or procedure by which an observation was obtained when the sending system wishes to distinguish between measurements obtained by different CE O 705 0..* N N 47 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? methods 48 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Note (NTE) The NTE segment contains notes and comments, and can be attached to the PID, OBR and OBX segments; it cannot be attached to the ORC segment. The NTE segment is optional and may repeat. NTE 1 TX EPITHELIAL CELL ABNORMALITY: SQUAMOUS CELLS Seq Name Value Type Req d Length Card Used? Disp? NTE-0 Segment type NTE ST R 3 1..1 N N NTE-1 Sequence number 1 SI R 6 1..1 N N NTE-2 Comment source Identifies the source of the comment ID O 2 0..1 N NTE-2 Examples: P for practice O for other system NTE-3 Comment Contains the comments entered by the source EPITHELIAL CELL ABNORMALITY: SQUAMOUS CELLS FT O 2 32000 0..* N NTE-3 2 As of August 21, 2012 if an NTE comment is blank it will show up as a blank line in Practice Fusion. 49 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

File Trailer Segment (FTS) Currently only one message per file is supported, so the FTS segment is optional and does not affect the processing of the message whether present or not. The FTS segment is optional and may appear only once. FTS 1 End of File Seq Name Value Type Req d Length Card Used? Disp? FTS-0 Segment type FTS ST O 3 0..1 N N FTS-1 ID 1 NM O 6 0..1 N N FTS-2 File trailer comment End of File ST O 32000 0..1 N N 50 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Practice Fusion User Interface PID-5 OBR-2 PID-7 PID-2 PID-8 PID-13 PID-11 PID-7 OBR-4 OBR-25 PV1-7 MSH-6 NTE-3 OBX-3 OBR-7 OBR-3 OBR-1 OBX-14 OBR-22 OBX-3 OBX-6 OBX-7 OBX-11 OBX-8 OBX-5 NTE-2 Note: The Additional information is not currently populated and will probably be removed. OBX-15 OBR-11 51 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Practice Fusion SOAP-Based Services There are two services you can make SOAP-based calls to in order to submit ORU_R01 messages to Practice Fusion for processing: Practice Fusion Security Service Practice Fusion LabConnect Service Practice Fusion Security Service The Practice Fusion Security Service is the first service you should invoke, providing the username and password assigned to your organization by the Practice Fusion Business Development team during the onboarding process. The service returns a token you will then use when invoking the LabConnect service, as well as a status value about the invocation. The token is cached and can be used for two hours before having to re-authenticate. Making a Request of the Security Service To make an authentication request of the Security Service, issue an HTTP POST with the variables described in Request Object Structures to the following endpoint: https://pfws.practicefusion.com/pfapi/security.asmx Practice Fusion replies with data as documented in Response Object Structures. Request Object Structures The following sections detail the Login request objects for SOAP versions 1.1 and 1.2. SOAP 1.1 SOAP 1.2 Table 2: Login Object Variables documents the attributes in the objects; populate the necessary attributes with the appropriate values. Table 2: Login Object Variables Attribute username password Value to Populate The API username provided to you by Practice Fusion. The password for your API username SOAP 1.1 POST /PFAPI/Security.asmx HTTP/1.1 Host: pfws.practicefusion.com Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "http://pfapi.practicefusion.com/2010/01/28/security/login" <?xml version="1.0" encoding="utf-8"?> 52 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<soap:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:body> <Login xmlns="http://pfapi.practicefusion.com/2010/01/28/security"> <username>string</username> <password>string</password> </Login> </soap:body> </soap:envelope> SOAP 1.2 POST /PFAPI/Security.asmx HTTP/1.1 Host: pfws.practicefusion.com Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:body> <Login xmlns="http://pfapi.practicefusion.com/2010/01/28/security"> <username>string</username> <password>string</password> </Login> </soap12:body> </soap12:envelope> Sample Security Request Object <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sec="http://pfapi.practicefusion.com/2010/01/28/security"> <soapenv:header/> <soapenv:body> <sec:login> <!--Optional:--> <!--Optional:--> <sec:username>${#project#solstas Username}</sec:username><sec:password>${#Project#Solstas Password}</sec:password></sec:Login> </soapenv:body> 53 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

</soapenv:envelope> Receiving a Response from the Security Service PracticeFusion returns a LoginResponse object in response to your POST call, returning information such as your security token or information about any errors. Response Object Structures The following sections detail the LoginResponse objects for SOAP versions 1.1 and 1.2. SOAP 1.1 SOAP 1.2 Table 3: LoginResponse Object Attributes documents the attributes in the response object and the values they contain. Table 3: LoginResponse Object Attributes Attribute Data Type Value Populated token String Contains the security token returned by Practice Fusion operationstatus ComplexType Contains the success, errorcode, and errordetails attributes success boolean Contains the value true if the request was successful, or false if there was an error errorcode String Contains a code specifying the error in the event of an unsuccessful request Example: ACCOUNT_LOCKED errordetails String Contains text describing the error in the event of an unsuccessful request Example: Account was locked but 10 minute timeout has passed SOAP 1.1 HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:body> <LoginResponse xmlns="http://pfapi.practicefusion.com/2010/01/28/security"> <LoginResult> <token>string</token> </LoginResult> 54 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<operationstatus> <success>boolean</success> <errorcode>string</errorcode> <errordetails>string</errordetails> </operationstatus> </LoginResponse> </soap:body> </soap:envelope> SOAP 1.2 HTTP/1.1 200 OK Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:body> <LoginResponse xmlns="http://pfapi.practicefusion.com/2010/01/28/security"> <LoginResult> <token>string</token> </LoginResult> <operationstatus> <success>boolean</success> <errorcode>string</errorcode> <errordetails>string</errordetails> </operationstatus> </LoginResponse> </soap12:body> </soap12:envelope> Sample Security Request Object <soap:envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema"> <soap:body> <LoginResponse xmlns="http://pfapi.practicefusion.com/2010/01/28/security"> <LoginResult> <token>412bed18fe304155ab10261d4c43f636c86f7d771e9c474bbd321e4b3d40e7eb</token> 55 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

</LoginResult> <operationstatus> <success>true</success> </operationstatus> </LoginResponse> </soap:body> </soap:envelope> Security WSDL You can view the WSDL for the API by entering the URI of the endpoint in the browser and appending?wsdl to the end of the address; it contains the following XML: <?xml version="1.0" encoding="utf-8"?> <wsdl:definitions xmlns:s="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://pfapi.practicefusion.com/2010/01/28/security" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textmatching/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetnamespace="http://pfapi.practicefusion.com/2010/01/28/security" <wsdl:types> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <s:schema elementformdefault="qualified" targetnamespace="http://pfapi.practicefusion.com/2010/01/28/security"> type="s:string" /> type="s:string" /> <s:element name="login"> <s:complextype> <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="username" <s:element minoccurs="0" maxoccurs="1" name="password" </s:sequence> </s:complextype> </s:element> <s:element name="loginresponse"> <s:complextype> <s:sequence> 56 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<s:element minoccurs="0" maxoccurs="1" name="loginresult" type="tns:loginresult" /> <s:element minoccurs="0" maxoccurs="1" name="operationstatus" type="tns:operationstatus" /> </s:sequence> </s:complextype> </s:element> type="s:string" /> type="s:boolean" /> type="s:string" /> type="s:string" /> <s:complextype name="loginresult"> <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="token" </s:sequence> </s:complextype> <s:complextype name="operationstatus"> <s:sequence> <s:element minoccurs="1" maxoccurs="1" name="success" <s:element minoccurs="0" maxoccurs="1" name="errorcode" <s:element minoccurs="0" maxoccurs="1" name="errordetails" </s:sequence> </s:complextype> </s:schema> </wsdl:types> <wsdl:message name="loginsoapin"> <wsdl:part name="parameters" element="tns:login" /> </wsdl:message> <wsdl:message name="loginsoapout"> <wsdl:part name="parameters" element="tns:loginresponse" /> </wsdl:message> <wsdl:porttype name="securitysoap"> <wsdl:operation name="login"> <wsdl:input message="tns:loginsoapin" /> <wsdl:output message="tns:loginsoapout" /> </wsdl:operation> </wsdl:porttype> <wsdl:binding name="securitysoap" type="tns:securitysoap"> 57 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<soap:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="login"> <soap:operation soapaction="http://pfapi.practicefusion.com/2010/01/28/security/login" style="document" /> <wsdl:input> <soap:body use="literal" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:binding name="securitysoap12" type="tns:securitysoap"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="login"> <soap12:operation soapaction="http://pfapi.practicefusion.com/2010/01/28/security/login" style="document" /> <wsdl:input> <soap12:body use="literal" /> </wsdl:input> <wsdl:output> <soap12:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="security"> <wsdl:port name="securitysoap" binding="tns:securitysoap"> <soap:address location="http://pf-int-app1/pfapi/security.asmx" /> </wsdl:port> <wsdl:port name="securitysoap12" binding="tns:securitysoap12"> <soap12:address location="http://pf-int-app1/pfapi/security.asmx" /> </wsdl:port> </wsdl:service> </wsdl:definitions> 58 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Practice Fusion LabConnect Service After you have successfully invoked the Practice Fusion Security Service and received a token you can invoke the Practice Fusion LabConnect Service to send your ORU_R01 message. Making a Request of the LabConnect Service Issue an HTTP POST with the variables described in Request Object Structures to the following endpoint: https://pfws.practicefusion.com/pfapi/labconnect.asmx Practice Fusion replies with data as documented in Response Object Structures. Request Object Structures The following sections detail the ProcessLabResult request objects for SOAP versions 1.1 and 1.2. SOAP 1.1 SOAP 1.2 Table 4: ProcessLabResult Object Variables documents the attributes in the object; populate the necessary attributes with the appropriate values. Table 4: ProcessLabResult Object Variables Attribute token Base64HL7Result Value to Populate The token returned by the Practice Fusion Security Service Your HL7 message encoded as Base64 data SOAP 1.1 POST /PFAPI/LabConnect.asmx HTTP/1.1 Host: pfws.practicefusion.com Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "http://pfapi.practicefusion.com/2012/02/01/labconnect/processlabresult" <?xml version="1.0" encoding="utf-8"?> <soap:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:body> <ProcessLabResult xmlns="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <token>string</token> <Base64HL7Result>base64Binary</Base64HL7Result> </ProcessLabResult> </soap:body> 59 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

</soap:envelope> SOAP 1.2 POST /PFAPI/LabConnect.asmx HTTP/1.1 Host: pfws.practicefusion.com Content-Type: application/soap+xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:body> <ProcessLabResult xmlns="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <token>string</token> <Base64HL7Result>base64Binary</Base64HL7Result> </ProcessLabResult> </soap12:body> </soap12:envelope> Sample LabConnect Request Object <soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:lab="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <soapenv:header/> <soapenv:body> <lab:processlabresult> <!--Optional:--> <!--Optional:--> <lab:token>${#project#solstas token}</lab:token><lab:base64hl7result>cid:solstassimple6.obx</lab:base64hl7result> </lab:processlabresult> </soapenv:body> </soapenv:envelope> Receiving a Response from the LabConnect Service PracticeFusion returns a ProcessLabResultResponse object in response to your POST call, returning information about the success or failure of the processing. Response Object Structures The following sections detail the ProcessLabResultResponse objects for SOAP versions 1.1 and 1.2. SOAP 1.1 60 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

SOAP 1.2 Table 5: ProcessLabResultResponse Object Attributes documents the attributes in the response object and the values they contain. Table 5: ProcessLabResultResponse Object Attributes Attribute Data Type Value Populated resultstatus ComplexType Contains the success, errorcode, and errordetails attributes success boolean Contains the value true if the message was successfully processed, or false if there was an error errorcode String Contains a code specifying the error in the event of a processing failure Example: SYSTEM_DOWN errordetails String Contains text describing the error in the event of a processing failure Example: The system is currently down for maintenance. Please try again later. SOAP 1.1 HTTP/1.1 200 OK Content-Type: text/xml; charset=utf-8 Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:body> <ProcessLabResultResponse xmlns="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <resultstatus> <success>boolean</success> <errorcode>string</errorcode> <errordetails>string</errordetails> </resultstatus> </ProcessLabResultResponse> </soap:body> </soap:envelope> SOAP 1.2 HTTP/1.1 200 OK Content-Type: application/soap+xml; charset=utf-8 61 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Content-Length: length <?xml version="1.0" encoding="utf-8"?> <soap12:envelope xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:body> <ProcessLabResultResponse xmlns="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <resultstatus> <success>boolean</success> <errorcode>string</errorcode> <errordetails>string</errordetails> </resultstatus> </ProcessLabResultResponse> </soap12:body> </soap12:envelope> Sample LabConnect Response Object <soap:envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http://www.w3.org/2001/xmlschema"> <soap:body> <ProcessLabResultResponse xmlns="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <resultstatus> <success>true</success> <errorcode>0000</errorcode> </resultstatus> </ProcessLabResultResponse> </soap:body> </soap:envelope> LabConnect WSDL You can view the WSDL for the API by entering the URI of the endpoint in the browser and appending?wsdl to the end of the address; it contains the following XML: <?xml version="1.0" encoding="utf-8"?> <wsdl:definitions xmlns:s="http://www.w3.org/2001/xmlschema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://pfapi.practicefusion.com/2012/02/01/labconnect" 62 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textmatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetnamespace="http://pfapi.practicefusion.com/2012/02/01/labconnect" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"> <wsdl:types> <s:schema elementformdefault="qualified" targetnamespace="http://pfapi.practicefusion.com/2012/02/01/labconnect"> <s:element name="processlabresult"> <s:complextype> <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="token" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="base64hl7result" type="s:base64binary" /> </s:sequence> </s:complextype> </s:element> <s:element name="processlabresultresponse"> <s:complextype> <s:sequence> <s:element minoccurs="0" maxoccurs="1" name="resultstatus" type="tns:operationstatus" /> /> </s:sequence> </s:complextype> </s:element> <s:complextype name="operationstatus"> <s:sequence> <s:element minoccurs="1" maxoccurs="1" name="success" type="s:boolean" /> <s:element minoccurs="0" maxoccurs="1" name="errorcode" type="s:string" /> <s:element minoccurs="0" maxoccurs="1" name="errordetails" type="s:string" </s:sequence> </s:complextype> </s:schema> </wsdl:types> <wsdl:message name="processlabresultsoapin"> <wsdl:part name="parameters" element="tns:processlabresult" /> </wsdl:message> <wsdl:message name="processlabresultsoapout"> 63 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<wsdl:part name="parameters" element="tns:processlabresultresponse" /> </wsdl:message> <wsdl:porttype name="labconnectsoap"> <wsdl:operation name="processlabresult"> <wsdl:input message="tns:processlabresultsoapin" /> <wsdl:output message="tns:processlabresultsoapout" /> </wsdl:operation> </wsdl:porttype> <wsdl:binding name="labconnectsoap" type="tns:labconnectsoap"> <soap:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="processlabresult"> <soap:operation soapaction="http://pfapi.practicefusion.com/2012/02/01/labconnect/processlabresult" style="document" /> <wsdl:input> <soap:body use="literal" /> </wsdl:input> <wsdl:output> <soap:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:binding name="labconnectsoap12" type="tns:labconnectsoap"> <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" /> <wsdl:operation name="processlabresult"> <soap12:operation soapaction="http://pfapi.practicefusion.com/2012/02/01/labconnect/processlabresult" style="document" /> <wsdl:input> <soap12:body use="literal" /> </wsdl:input> <wsdl:output> <soap12:body use="literal" /> </wsdl:output> </wsdl:operation> </wsdl:binding> <wsdl:service name="labconnect"> <wsdl:port name="labconnectsoap" binding="tns:labconnectsoap"> 64 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<soap:address location="http://pfws.practicefusion.com/pfapi/labconnect.asmx" /> </wsdl:port> <wsdl:port name="labconnectsoap12" binding="tns:labconnectsoap12"> <soap12:address location="http://pfws.practicefusion.com/pfapi/labconnect.asmx" /> </wsdl:port> </wsdl:service> </wsdl:definitions> 65 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Practice Fusion RESTful Services Practice Fusion also exposes a Representational State Transfer (REST) service that can process HL7 data. Practice Fusion LabConnectHTTPService The Practice Fusion LabConnectHTTPService is a RESTful endpoint you can invoke to process HL7 messages. Make an HTTP POST to the following URI for each HL7 message: https://pfws.practicefusion.com/pfapi/labconnecthttpservice.svc/processlabresult The call must include headers containing the username and password provided by Practice Fusion according to the Basic Authentication protocol as defined in RFC 2617. The imaging result data should be sent as raw HL7, not in Base64 encoding as with the Practice Fusion SOAP services. See Sample REST Request for an example call. Sample REST Request POST http://pf-qa-app1.hq.practicefusion.com/pf.api- B2/LabConnectHttpService.svc/processlabresult HTTP/1.1 Accept-Encoding: gzip,deflate Content-Type: plain/text Authorization: Basic cxvlc3r0zxn0onrlc3qxmtex Content-Length: 1192 Host: pf-qa-app1.hq.practicefusion.com Connection: Keep-Alive User-Agent: Apache-HttpClient/4.1.1 (java 1.5) MSH ^~\& STL Mhat 201201041955 ORU^R01 06969551 T 2.3 NE PID MT8584 477a422-da76-4040-883f- 4f429627b057^^^^PATGUID Quest^RestSvc 19710405 M 777 ANY STREET^^BEVERLY HILLS^CA^90210 PV1 1 96985^LowLow^HighHigh J ORC RE 11 F OBR 1 laborder112712 FilerOrderNumber SOL23040^Glucose 201103210851 201103210 851 96985^LowLow^HighHigh J 201103210814 F NTE 1 TX UNSOLICITED RESULTS OBX 1 ST SOL230025^Glucose^NameOfCodeSystem 250 mg/dl 70-99 HH F SLN^Solstas Imaging Partners^4380 Federal Drive, Suite 100^Greensboro, NC 27410^^ OBX 2 ST ALKPHOS^Alkaline Phos^NameOfCodeSystem 140 IU/L 140-450 F SLN^Solstas Imaging Partners^4380 Federal Drive, Suite 100^Greensboro, NC 27410^^ OBX 3 ST HLBBUN^Urea Nitrogen^NameOfCodeSystem 8 mg/dl 8-21 F SLN^Solstas Imaging Partners^4380 Federal Drive, Suite 100^Greensboro, NC 27410^^ OBX 4 ST BUN^Urea Nitrogen^NameOfCodeSystem 1 mg/dl 8-21 LL F ML^HealthLab^25 N. Winfield Road^Winfield, IL 60190^630-933-2633^ OBX 5 ST CREAT^Creatinine^NameOfCodeSystem 0.6 mg/dl 0.6-1.3 F ML^HealthLab^25 N. Winfield Road^Winfield, IL 60190^630-933-2633^ 66 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

FTS 1 End of File Receiving a Response from the LabConnectHTTPService PracticeFusion returns a HL7 Acknowledgement (ACK) message in response to your request, returning information such as error details. The segments of the ACK message are documented in the following sections: Message Header (MSH) Message Acknowledgement (MSA) Message Header (MSH) Fields in the MSH segment of the ACK message are set to the values from the original ORU_R01 message, except for MSH-7, which is set to the date and time the ACK message is created. Seq Name Value Type Req d Length Card Used? Disp? MSH-0 MSH-1 MSH-2 Segment identifier Field delimiter Encoding characters MSH ST R 3 1..1 Y N (the pipe character) ST R 1 1..1 Y N ^~\& ST R 4 1..1 Y N MSH-3 Sending application Identifies your application Example: Radiology InformationSystemNa me HD O 180 0..1 N N MSH-4 Sending facility Identifies the sending radiology or reporting site HD O 180 0..1 N N Example: Wildfire_Atlanta^45 D0470381^CLIA MSH-5 Receiving application Identifies Practice Fusion as the destination HD O 180 0..1 N N Example: Practice Fusion MSH-6 Receiving facility Identifies the healthcare organization for which the message is intended HD R 200 1..1 N MSH-6 Example: DrSussmanPractice MSH-7 Message date and time Identifies the date and time the message was created TS R 26 1..1 NA NA 67 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Seq Name Value Type Req d Length Card Used? Disp? Example: 20130205022300-0500 MSH-10 Message control ID Contains the value the system uses to associate the message with the response to the message ST R 200 1..1 NA NA Example: UNX3ZMH5YAPHBL63SB3 V MSH-11 Processing ID P for in production PT R 3 1..1 NA NA D for in debugging T for in training Message Acknowledgement (MSA) Seq Name Value Type Req d Length Card Used? Disp? MSA-1 Acknowledge ment Code Indicates whether or not the ORU_R01 message was accepted ID R 2 1..1 NA NA AA for Accepted AE for Error MSA -2 Message Control ID Contains the value from the MSH-10 field in the original ORU_R01 message to correlate with this acknowledgement ST R 200 1..1 NA NA Example: UNX3ZMH5YAPHBL63SB3 V MSA -3 Text Message In the event of an error, contains information about it Example: HL7Message is not ORU_R01 ST O 80 0..1 NA NA 68 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Appendix This section details the values that appear in the Req d, Card, and Type columns in the detailed segment definition tables. Requiredness This section defines the values that appear in the Req d of the detailed segment definitions, which specify whether the segment is required, optional, or required based on certain conditions. R The segment is required. O The segment is optional, and may be omitted. C The segment might be required depending on conditions related to the trigger event or the value of other fields. Cardinality This section defines the cardinality values displayed in the Card column of the detailed segment definitions, which specify the logic behind how a segment may repeat or not. 0..1 The segment may be omitted and can occur only once. 1..1 The segment must occur only once. 0..* The segment may be omitted or may repeat an unlimited number of times. 1..* The segment must appear at least once, and may repeat an unlimited number of times. 0..N The segment may be omitted or may repeat a specific number of times. Data Types This section defines the data types displayed in the Type column of the detailed segment definitions. 69 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

CE Coded Element This data type transmits codes and the text associated with the code. <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)> CM Composite A field that is a combination of other meaningful data fields. The specific components of CM fields are defined within the field description, not by the data type itself. CQ Composite Quantity with Units Used to express a quantity, and the units in which the quantity is expressed. <quantity (NM)> ^ <units (CE)> CX Extended Composite ID with Check Digit Used to express an alphanumeric identifier, a check digit and scheme, and the source of the identifier, check digit, and scheme. <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ < assigning authority (HD)> ^ <identifier type code (IS)> ^ < assigning facility (HD) DLN Driver s license number <license number (ST)> ^ <issuing state, province, country (IS)> ^ <expiration date (DT) DT Date A date in the format YYYYMMDD ED Encapsulated data Data that is primarily intended for human interpretation or for further machine processing outside the scope of HL7, such as a Portable Document Format (PDF) file. This includes unformatted or formatted written language, multimedia data, or structured information as defined by a different standard, such as XML signatures. EI Entity identifier The entity identifier permits the identification of a given entity within an application or system. 70 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> FT Formatted text This data type is derived from the string data type by allowing the addition of embedded formatting instructions. HD Hierarchic designator A unique name that identifies the system that was the source of the data. The HD type is designed to be used either as a local version of a site-defined application identifier or as a publicly-assigned UID. <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)> ID Coded value for HL7- defined tables The value of such a field follows the formatting rules for an ST field except that it is drawn from an HL7-defined table. A specific HL7 table number is inherently associated with the field, rather than explicitly stated, when this data type is used. IS Coded values for userdefined tables The value of such a field follows the formatting rules for an ST field except that it is drawn from a user-defined table. A specific HL7 table number is inherently associated with the field, rather than explicitly stated, when this data type is used. NM Numeric A series of ASCII numeric characters consisting of an optional leading sign (+ or -), the digits, and an optional decimal point. In the absence of a sign, the number is assumed to be positive. If there is no decimal point, the number is assumed to be an integer. Leading zeros or trailing zeros after a decimal point are not significant. PL Person location <point of care (IS )> ^ <room (IS )> ^ <bed (IS)> ^ <facility (HD)> ^ < location status (IS)> ^ <person location type (IS)> ^ <building (IS )> ^ <floor (IS )> ^ <location description (ST)> PT Processing type <processing ID (ID)> ^ <processing mode (ID)> SI Sequence ID A non-negative integer in the form of an NM field. 71 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

SN Structured numeric The structured numeric data type is used to unambiguously express numeric clinical results along with qualifications. <comparator (ST)> ^ <num1 (NM)> ^ <separator/suffix> ^ <num2 (NM)> Examples: <^.255 >^100 ^1^:^100 ^5^-^10 ST String data Any printable ASCII characters except the defined delimiter characters. To include any HL7 delimiter character (except the segment terminator) within a string data field, the appropriate HL7 escape sequence must be used. String data is left justified with trailing blanks optional. TM Time A time value in the format HH[MM[SS[.S[S[S[S]]]]]][+/-ZZZZ] TS Timestamp Any timestamp value formatted according to the HL7 specifications for the TS data type, with items in brackets ([ ]) being optional: YYYY[MM[DD[HHMM[SS[.S[S[S[S]]]]]]]][+/-ZZZZ] The preferred format of Practice Fusion is YYYYMMDDHHMMSS±ZZZZ (where ZZZZ is the time zone offset from Greenwich Mean Time),such as 20130205022300-0500 TX Text data String data meant for print or for display on a terminal. Not necessarily left justified. Leading spaces may contribute to clarity of the presentation to the user. VID Version identifier Used to identify the HL7 version. <version ID (ID)> ^ <internationalization code (CE)> ^ <international version ID (CE) XAD Extended address Used to express address data associated with a person or institution. 72 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

<street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)> ^ <address representation code (ID)> XCN Extended composite ID number and name for persons Used to express person name information in conjunction with a composite ID and check digit. <ID number (ST)> ^ <family name (ST)> & <last_name_prefix (ST) ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code (ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ <name representation code (ID)> XON Extended composite name and identification number for organizations Used to express organization name information in conjunction with a composite ID and check digit. <organization name (ST)> ^ <organization name type code (IS)> ^ <ID number (NM)> ^ <check digit (NM)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility ID (HD)> ^ <name representation code (ID)> XPN Extended person name Used to express person name information. <family name (ST)> & <last_name_prefix (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (IST)> ^ <name type code (ID) > ^ <name representation code (ID)> XTN Extended telecommunications number Used to express telecommunications information. [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)> 73 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

Version History Version Date Comment Current Version (v. 28) v. 25 May 08, 2013 Nov 28, 2012 Reformatted, and added greater detail Added information about more than one attachment, and on the support for a secure URL and secure URL account information in OBR 20 and 21. Added correct info on OBX-5 use, and clarified OBX-3 use. v. 24 Nov 13, 2012 Increased NTE 3 from 200 to 32000 v. 23 Nov 08, 2012 Added requirement for MSH-11 v. 22 Nov 07, 2012 Increased OBX 3.2 length from 75 to 200 v. 21 v. 20 v. 19 v. 18 v. 17 v. 16 v. 15 v. 14 v. 13 v. 12 v. 11 v. 10 v. 9 v. 8 v. 7 Nov 02, 2012 Oct 03, 2012 Oct 03, 2012 Aug 17, 2012 Aug 16, 2012 Aug 03, 2012 Jul 24, 2012 Jul 24, 2012 Jul 23, 2012 May 30, 2012 May 03, 2012 Apr 23, 2012 Apr 18, 2012 Apr 17, 2012 Apr 17, 2012 Supporting additional abnormal flags. Updated PV1.7 to reflect our use of NPI for provider lookup. Formatting changes Removed footnote stating OBR-22 cannot be present in some cases. Formatting changes and updated examples to match the spec. Also added comment about NTE.3 handling Changed patient first name to be required. Added that OBX.3.1, 3.2, and 3.3 not required when value type is ED (embedded PDF) Added footnote to OBX.11 stating that it's not required when Value Type is set to ED for embedded PDF Refactored by marking any unused fields as such. Refactored OBR and OBX tables. Added supported abnormal flags. Many other changes. Updated OBX-15 to reflect all the imaging site information that can be sent. Removed OBX-18+ as they are not valid in HL7 v2.3.information Updated PV1 table to show all fields and formatted for easier readability. Reverted back to requiring PID-3 (not PID-2) for ID after team discussions. PID-2 is deprecated in later HL7v2 versions. Marked PID-3 as not required/display and PID-2 as required/displayed based on current system behavior. Updated MSH section to show all fields and include details about sub-components when necessary. Massive update to the PID section. Added all pid fields. Greyed out unused fields. Updated valid phone numbers 74 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n

v. 6 v. 5 v. 4 v. 3 v. 2 v. 1 Apr 17, 2012 Apr 12, 2012 Apr 09, 2012 Mar 27, 2012 Mar 27, 2012 Mar 27, 2012 and SSN's. Updated PID-11 (Address) to show all fields that have size limitations. Also marked appropriate fields as displayed in EHR. Added additional PV1-7 fields. Also clearly marked what is required or not required in PV1-7 Added sub-components for PID-3 Added MSH-6 sub components and indicated that we use the first one for Vendor Client Account Number Indicated that OBX.3's subcomponents are required (identifier and text) New Document 75 P a g e H L 7 R e s u l t s S p e c i f i c a t i o n