Home

Message Segment Specifications

1. IPA Independent Physician Association J2EE Java 2 Platform Enterprise Edition J2SE Java 2 Platform Standard Edition JAXP Java API for XML Parsing JCAPS Java Composite Application Platform Suite JMS Java Message Services JNDI Java Naming and Directory Interface LIS Lab Information System LOINC Logical Observation Identifiers Names and Codes MEDS Medication and Eligibility Delivery Solution MIS Management Information System MLLP Minimal Lower Level Protocol NPI National Provider Identifier ORM HL7 Order Message ORU HL7 Observational Report Unsolicited PDF Portable Document Format PMS Practice Management System POC Point of Care PPMS Physician Practice Management System PRNE Physicians Reducing Negative Events PSC Quest Diagnostics Patient Service Center QLS Quest Lab Systems SAML Security Assertion Markup Language SCP Secure Copy SFTP SSH File Transfer Protocol SIG Script Information Gateway SOAP Simple Object Access Protocol Note As of SOAP v1 2 referred to only as an acronym SQL Structured Query Language SSH Secure Shell Abbreviation Acronym Description SSL Secure Sockets Layer SSO Single Sign On UDDI Universal Description Discovery and Integration UPIN Universal Physician Identifier Number URI Uniform Resource Identifier URL Uniform Resource Locator VPN Virtual Private Network W3C World Wide Web Consortiu
2. Segment ID Element Name Type Length Comments Req d PV1 11 Temporary PL 80 NS Location PVI 12 Preadmit Test IS 2 NS Indicator PV1 13 Readmission IS 2 NS Indicator PV1 14 Admit Source IS 3 NS PV1 15 Ambulatory IS 2 NS Status PV1 16 VIP Indicator IS 2 NS PV1 17 Admitting XCN 60 NS Doctor PV1 18 Patient Type IS 2 NS PV1 19 Visit Number CX 20 NS PV1 20 Financial Class FC 50 NS PV1 21 Charge Price IS 2 NS Indicator PV1 22 Courtesy Code IS 2 NS PV1 23 Credit Rating IS 2 NS PV1 24 Contract Code IS 2 NS PV1 25 Contract DT 8 NS Effective Date PV1 26 Contract Amount NM 12 NS PVI 27 Contract Period NM 3 NS PV1 28 Interest Code IS 2 NS PV1 29 Transfer to Bad IS 1 NS Debt Code PV1 30 Transfer to Bad DT 8 NS Debt Date PV1 31 Bad Debt Agency IS 10 NS Code PV1 32 Bad Debt NM 12 NS Transfer Amount PV1 33 Bad Debt NM 12 NS Recovery Amount Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 34 Delete Account IS 1 NS Indicator PV1 35 Delete Account DT 8 NS Date PV1 36 Discharge IS 3 NS Disposition PV1 37 Discharged to CM 25 NS Location PV1 38 Diet Type IS 2 NS PV1 39 Servicing Facility IS 2 NS PV1 40 Bed Status IS 1 NS PV1 41 Account Status IS 2 NS PV1 42 Pending PL 80 NS Loca
3. R Required O Optional C Conditional Dataset 6 Bill To Eligibility File Name N A Description Usage Identifies the insurance carriers that have eligibility contracts with the service provider laboratory There is one entry per carrier Required This dataset is not supported for third party laboratory implementations Conditions There must be a valid carrier type entry in the Bill to dataset BILL_TO_ELIGIBILITY Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 3 Performing site PERFORMING_TOPLAB PKI R char 3 4 Billto ID MC MNEMONIC PKI R char 25 5 Active date MC ACTIVE DTE R datetime 6 Name MC NM O char 30 7 Line 1 addr LINE 1 ADDR char 30 Dataset File Details 21 28 BILL TO ELIGIBILITY Column Name CDC Column Name Key Req d Type Length Valid Values Notes 8 Line 2 addr LINE 2 ADDR O char 30 9 City Name CITY NM O char 25 10 State STATE CD O char 2 11 Zip code ZIP_CD O char 12 a R Required O Optional C Conditional Dataset 7 0rder Code File Name ORDCODE TXT Description Usage Provides data about orderable tests and codes such as draw fees There is one entry per orderable code per laboratory site Required This datas
4. Leu 179 Message Segment Hierarchy sso exesicescaonrg esu RpG E Eq Oda res 179 Message Segment Specifications llis nnn 180 ADT A29 Patient Delete Message Segment Specifications LL 195 Message Segment Hierarchy sss seeker redai ki Ree RR bees oe Cee 195 Messape Sesment SDeCcIHCatlORS erroreen ewe i genes PRU Eden de acp 195 ADT A31 Patient Update Message Segment Specifications 204 Messape Seement Hierarchy s cbs de ze ea xa REVO whee EVE HER teas 204 Message Segment SpeclfiCatlODS sorser gs cide m tace exon Ie oe Red oer E 205 ADT A39 Patient Merge Message Segment Specifications eese 221 Message Seament Hierarchy eos sene boe aware eto qae pui ah UR bti ts 221 Message Segment Specilicati Dn8 ss hese veers Rr eg bande Red e RR 221 Sample Care360 Patient Demographic Messages eee 231 Chapter 10 Care360 SSO and Web Services Site 233 About the Care360 SSO and Web Services Site 6 0 cece cece cee eens 234 Accessing the Care360 SSO and Web Services Site 0 cece eee ee eens 235 About the Sample Application 1 0 0 0 0 cc ccc cece tence eee ee nnn 236 About the WSDL Interface Documents 0 cece eee cece ee een 237 Accessing the User Summary Services WSDL Document 237 About the Sample Code ouo set ma sash e ME ea tess cewek sieges 238 GIOSSONY uoxeu uavuduwiosadassetdu exu eeteueuapuu
5. or KANAA STANOTTE TIS or 3148727127 The Hub verifies that the value complies with rules above PID 14 Phone Number Business XTN 40 NS PID 15 Language Patient CE 60 NS PID 16 Marital Status IS For suggested values refer to user defined table 0002 Marital status NS PID 17 Religion IS NS PID 18 Patient Account Number CX 20 NS PID 19 SSN Number Patient ST Must contain 9 digits Numeric only no space or punctuation If present the Hub verifies that the value complies with rules above Care360 Order Message Segment Specifications n Segment ID Element Name Type Length Comments Req d PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22 Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 For valid values refer to HL7 table NS Indicator 0136 Yes no indicator PID 25 Birth Order NM 2 NS PID 26 Citizenship IS 4 NS PID 27 Veterans CE 60 NS Military Status PID 28 Nationality CE 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 For valid values refer to HL7 table NS Indicator 0136 Yes no indicator a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional
6. submitBatchADTMessage Summary Submits a patient demographic update in HL7 format to Care360 Hub Information Services in batch mode Usage The InboundPatientDemographicRequest object contains the inbound patient demographic update Notes e Even if an inbound patient demographic update is accepted by the Hub it still may ultimately be rejected by Physician Portal For detailed specifications on formatting patient demographic update messages that are sent to Care360 Hub Information Services for processing see Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 Preconditions The Demographics service is configured properly in Hub Information Services Administration Method Signature DemographicResponse submitBatchADTMessage DemographicRequest request throws SOAPException Patient Demographic Objects The Patient Demographic Services API provides the objects described in the following table Object Description Attributes Data Type Req d DemographicRequest Contains the inbound patient demographics update Note For detailed specifications on formatting patient demographic updates that are sent to Care360 Hub Information Services for processing see Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 Attributes that can be set for this object include ADTMessage The ADT Patient byte R Demographic update message content Demog
7. 140 About Patient Demographic Services Patient demographic integration enables patient demographic data changes that occur within a partner application to be forwarded to Physician Portal in order to maintain the integrity of patient demographic data between the two applications The types of patient demographic changes that can be submitted include the following e Add Patient e Update Patient e Delete Patient e Merge Patients Patient demographic updates are communicated to Physician Portal through Care360 Hub Information Services which maintains a record of all patient demographic transactions Any errors that occur when the updates are communicated to Physician Portal are returned to the Hub Patient demographic update messages submitted by the partner application must be formatted according to the specifications detailed in Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 Outbound patient demographic updates are communicated to the partner application through Care360 Hub Information Services which maintains a record of all patient demographic transactions Any errors that occur when the updates are communicated to the partner application are returned to the Hub Patient Demographic Services Connectivity The transfer of all Patient Demographic updates between a partner application and Care360 Hub Information Services will occur via the Hub Patient Demographic Services HTTP Over SSL or HTTPS
8. Date Time DT Date YYYY MM DD TM Time HH MM SS S S S S 2222 TS Time stamp YYYY MM DD HHMM SS S S S S 1 1 1 7 ZZZzZz degree of precision Chapter 9 Care360 Patient Demographic HL7 Specification Data Type Category Data Type Name Notes Format Code Values CE Coded element identifier ST text ST name of coding system ST alternate identifier ST alternate text ST name of alternate coding system ST CK Composite ID with check digit lt ID number NM gt check digit NM gt code identifying the check digit scheme employed ID gt assigning authority HD gt CX Extended composite ID with check digit lt ID ST gt check digit ST gt code identifying the check digit scheme employed ID gt assigning authority HD lt identifier type code IS gt assigning facility HD XCN Extended composite ID number and name In Version 2 3 replaces the CN data type lt ID number ST gt family name ST given name ST middle initial or name ST suffix e g JR or III ST prefix e g DR ST gt degree e g MD ST gt lt source table IS gt assigning authority HD name type code ID identifier check digit ST gt lt code identifying the check digit Scheme employed ID identifier typ IS
9. Following are several sample Master File dataset files Note that only the top portion of each file is shown since the typical file is too large to include here in total Sample One Bill To Edit List E 00 R E 01 TPA A QI A QI A QTI E 03 TPA E 04 7 E 05 007 E 06 001 E 07 T E 08 0 E 09 0000 E 0A 060000 E OB NYG A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A OTI A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT n n n n n n n n n n n n n n n n n n n n a n n n a n E 02 TPA E O0C CE E O0D N E O0E E O0F E 0G E 0H C E 0I E 0J YLA E OK 5 E 0L 2 E 0M Y E 0N P E 00 N E 0P A E 0Q UL A QTI E 0S R E 0T GO E 0U F E 0V A E 0W 999999 E 0X 0000 E 0Y 8 E 02 0000 E 10 0000 E 11 0000 E 12 0000 D DPD E OR MID Sample Master File Dataset Files 51 52 Sample Two Order Code Alias A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI A QTI E 59T l Actinomyces Genital Cytolog
10. NS GT1 22 Guarantor Billing Hold Flag ID NS GT1 23 Guarantor Credit Rating Code CE 80 NS GT1 24 Guarantor Death Date And Time TS 26 NS GT1 25 Guarantor Death Flag ID NS GT1 26 Guarantor Charge Adjustment Code CE 80 NS ADT A31 Patient Update Message Segment Specifications 215 216 Segment ID Element Name Type Length Comments Req d GT1 27 Guarantor CP 10 NS Household Annual Income GT1 28 Guarantor NM 3 NS Household Size GT1 29 Guarantor CX 20 NS Employer ID Number GT1 30 Guarantor IS 1 NS Marital Status Code GT1 31 Guarantor Hire DT 8 NS Effective Date GT1 32 Employment DT 8 NS Stop Date GT1 33 Living IS 2 NS Dependency GT1 34 Ambulatory IS 2 NS Status GT1 35 Citizenship IS 4 NS GT1 36 Primary CE 60 NS Language GT1 37 Living IS 2 NS Arrangement GT1 38 Publicity CE 80 NS Indicator GT1 39 Protection ID 1 NS Indicator GT1 40 Student IS 2 NS Indicator GT1 41 Religion IS 3 NS GT1 42 Mother s XPN 48 NS Maiden Name GT1 43 Nationality CE 80 NS GT1 44 Ethnic Group IS 3 NS GT1 45 Contact Person s XPN 48 NS Name Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d GT1 46 Contac
11. 35 36 Dataset 15 DOS Minimum Volume File Name SPECIMENVOL TXT Description Usage Provides DOS information for the minimum volume of specimen required to perform the test once There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None MINIMUM SPECIMEN VOLUME Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 R Required O Optional C Conditional Dataset 16 DOS Preferred Requirement File Name SPECIMENREQ TXT Description Usage Provides DOS information for preferred specimen requirements There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None PREFERRED_SPECIMEN_REQUIREMENT Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PK1 R char 10 LIS code 4 Sequence number SEQUENCE NO PKI R smallint
12. Care360 A MedPlus Solution Universal Lab Orders and Results Programmer Reference TRIAL Care360 was developed by MedPlus the Healthcare Information Technology subsidiary of Quest Diagnostics Quest Diagnostics e Foreword COPYRIGHT NOTICE MedPlus Inc 4690 Parkway Drive Mason Ohio 45040 U S A 2009 MedPlus Inc All Rights Reserved This document is protected by copyright and distributed under licenses restricting its use copying and distribution Parties to a user agreement with MedPlus for the software described in this document are granted permission to use and reproduce portions of this document solely for their internal training requirements provided that this copyright notice and other proprietary notices appears in all copies Except as provided in this paragraph no part of this document may be reproduced or transmitted in any form or by any means without the express written permission of MedPlus Inc TRADEMARKS MedPlus the associated logo and all associated MedPlus marks are the registered trademarks of MedPlus Inc a wholly owned subsidiary of Quest Diagnostics Quest Quest Diagnostics the associated logo and all associated Quest Diagnostics marks are the registered trademarks of Quest Diagnostics All third party marks and are the property of their respective owners DISCLAIMER OF WARRANTIES THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND EITHER EXPRESS O
13. Re report partials RE_REPORT_PARTIALS R char 1 Valid values Y N F At final only R List as reported A List as reported with comprehensive final 36 Number of copies OF COPIES R char 1 37 Reporting routine REPORT ROUTINE R char 8 38 PAP summary report PAP SUMMARY REPORT R char 1 Valid values Y N 39 Default charge to DEFAULT CHARGE TO R char 8 40 Requisition edit REQUISITION EDIT O char 255 41 Toxicology report TOX REPORT R char 1 Valid values Y N Chapter 2 Care360 Master File Specification TOPLAB CLIENT Column Name CDC Column Name Key Req d Type Length Valid Values Notes 42 Confidential client CONFIDENTIAL_CLIENT R char 1 Valid values Y N results U Unknown 43 Registered patients REGISTERED PATIENTS R char 1 Valid values Y N 44 Client type CLIENT_TYPE R char 1 Valid values P Physician H Hospital T 2 Industrial V Veterinary 45 Client activity report CLIENT ACTIVITY REPORT R char 1 Valid values N 1 2 3 4 5 6 46 Billing sales location NBS SALES LOCATION R char 3 47 NIDA flag NIDA_FLAG R char 1 Valid values Y N U Unknown 48 HMO flag HMO FLAG R char 1 Valid values Y N U Unknown
14. incorrect patient Physician Portal returns an error to the partner application a You cannot delete a patient after clinical entries for example lab results have been associated with that patient or if the patient is associated with an alias patient If a delete cannot be performed due to either of these conditions an error message is returned About Patient Demographic Services 143 Process Walkthrough Submitting a Patient Demographic Update The diagram below illustrates at a high level the flow of information between a partner application Care360 Hub Information Services and Physician Portal Following the diagram is a step by step walkthrough of the patient demographic processes illustrated in the diagram Submitting Patient Demographic Updates to Care360 Physician Portal Physician Office Hub Infrastructure Partner Partner Application Application Submits Patient pp Demographic Updates Care360 Hub Information Services b Hub Database a ae oe NK Copy of Patient j seri d Ser Demographic Updates Hub Forwards Patient Demographic Updates to Portal The following steps outline the procedure and associated systems involved in a partner application submitting patient demographic update requests to Physician Portal L The partner application submits patient demographic update messages to the Hub via the Inbound Patient Demograph
15. 1 FOUND 444669999 PV1 1 O GT1 1 88 Smith John M JR DR MD 3710 Emery Lake Ln Cincinnati OH 45010 1 513 8888888 1234 1 238 4444444 5678 1199 60708000000 M 1T 8 444556666 ABC Inc EFG M 4567 Kelly Drive Oxford OH 45068 55566677777 4556 FT organization INL 1 INSID123 Insurance Plan ABC INSCOID123 insuranceco 1800 Insurance Rd Detroit MI 45777 1 555 6667777 1234 3433 name 11 19960707 LLEEEEEEEEEEEEEEEELEE ELLE LL TL IT Sample Care360 Patient Demographic Messages 231 Sample 4 Merge Patient SH amp SecondSub DemographicDemo DemographicDemoOrg 20061211153336 AD T A39 A39M P 2 3 EVN A39 199608190820 PID 1 ABC NEWMRN 2 Wally SHERRY Dr dkdk 20000101 F 4690 Parway Dr Mason OH 45040 a2 1 226 1111111 2222 1 222 5555555 6666 287 87 8787 RG pid 66 Johnson William L PIDI21 I111119681121 M 3710 Emery Lake Lane Mason OH 45040 1 11999 99 9999 232 Chapter 9 Care360 Patient Demographic HL7 Specification Chapter 10 are360 SSO and Web Services Site F Care360 Single Sign On and Web Services Microsoft Internet Explorer Ele Edt View Favorites Tools Heb O HAD Psh kras AS w DERB8A3 ustcenter corp medplus comftech support portalcenter def ul html Care360 SINGLE SIGN ON AND WEB SERVICES Med lus Welcome to the reference site for connecting to Care360 This site is designe to provi
16. C Conditional NS Not Supported PV1 Patient Visit Data Segment The Patient Visit Data PV1 segment is used by registration patient administration applications to communicate information on a visit specific basis This segment can be used to send multiple visit statistic records to the same patient account or single visit records to more than one account Segment ID Element Name Type Length Comments Req d PV1 00 Segment Type ID ST 4 Must be PV1 R PV1 01 Set ID SI 4 Will always be 1 R PV1 02 Patient Class IS 1 NS PV1 03 Assigned Patient PL 80 NS Location PV1 04 Admission Type IS 2 NS PV1 05 Preadmit CX 20 NS Number PV1 06 Prior Patient PL 80 NS Location Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 07 Attending XCN 60 NS Doctor PV1 08 Referring Doctor XCN 60 NS PV1 09 Consulting XCN 60 NS Doctor PV1 10 Hospital Service IS 3 NS PV1 11 Temporary PL 80 NS Location PV1 12 Preadmit Test IS 2 NS Indicator PV1 13 Readmission IS 2 NS Indicator PV1 14 Admit Source IS 3 NS PV1 15 Ambulatory IS 2 NS Status PV1 16 VIP Indicator IS 2 NS PV1 17 Admitting XCN 60 NS Doctor PV1 18 Patient Type IS 2 NS PV1 19 Visit Number CX 20 NS PV1 20 Financial Class FC 50 NS PV1 21 Charge Price IS 2 NS Indicator PV1 22 Co
17. Chapter 8 Patient Demographic Services API Reference on page 167 Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 Chapter 10 Care360 SSO and Web Services Site on page 233 Chapter 5 Linking to Physician Portal i Quick View Microsoft Internet Explorer Ele gdt View Favorites Tools Help Ork O D A lA seah rreotes Address https www care360 compiphysicianportal app 82 Sep Welcome Any User Care360 A MedPlus Solution Quick View Demo Health Assoc User Preferences Fda patont E177 Quick View Quick View New Results Bit Messages FaxesjTasksy Summary data was last updated on 02 16 2008 at 11 09 AM EST __Refresh Page Action Items I New Results Lost amp Found Results Duplicate Patients I You have 10 new results e You have 10 final results Of these 8 are abnormal e You have no partial results Messages Faxes Tasks Support Whats New IEEE You have no new messages You have no faled fax messages There are no faled fax messages for this org You have no total tasks You have no new tasks You have no pending tasks Last Login Date 02 13 08 03 07 PM EST Preferences Install Contact Us Feedback Quest Diagnostics Resource What s New Help Logout Quick View Clinical Admin Action Items Prescriptions You have 4 prescriptions pending approval You have no prescriptions pending renewal You have no falled faxes
18. Physician Portal UI 146 Datasets Master Files see Master Files Delete patient sample patient demographic message 231 DemographicRequest object description 170 DemographicResponse object description 170 Demographics see Patient demographic integration DGI field requirements order 91 92 segment requirements order 60 Diagnosis segment see DG1 Diagnosis definition 239 Documentation conventions xii related xvi DOS Billing Procedure Code dataset Master Files 34 DOS Container dataset Master Files 35 245 246 Index DOS Methodology dataset Master Files 35 DOS Minimum Volume dataset Master Files 36 DOS Performing Site dataset Master Files 47 DOS Preferred Requirement dataset Master Files 36 DOS Reject Hemolysis dataset Master Files 37 DOS Reject Lipemia dataset Master Files 37 DOS Reject Thaw Other dataset Master Files 38 DOS Specimen Stability dataset Master Files 38 DOS Transport Temperature dataset Master Files 39 Download Sample EMR application 235 E Electronic Medical Record EMR definition 240 Eligibility definition 240 Emergency definition 240 EMR sample application downloading 235 sample application overview 236 EVN field requirements patient demographic 182 182 198 198 207 207 224 224 F Features new in this release xi Formatting requirements linking 131 Fuzzy matching details 142 patient demographic integration 141 G getCounts method description 163 getCou
19. Quest Quest Diagnostics the sociated d lap Nicho Insti and al asieciited Quest Diagnostics marks ara the registerad trademarks of Quast are the property of their respective owners 2000 2008 Quest Diagnostics Incorporated All Diagnostics all third party marks rights reserved In This Chapter e About Linking and Single Sign On SSO e About User Summary Services e About Order Echo ssse s e About Patient Demographic Services e Customizing the Physician Portal User Interface B rosea stes 130 136 138 140 146 129 130 About Linking and Single Sign On SSO This chapter provides information about linking from a partner application for example an electronic medical record EMR application electronic health record EHR application or practice management system PMS to Physician Portal Application linking enables the partner application to directly access specific functions of Physician Portal from within the context of the partner application Linking to Physician Portal enables a partner application to effectively offer lab order and result services through an existing EMR solution Users can launch directly into a specific Physician Portal function using SSO and maintaining their current patient context SSO access allows the user to transparently log in to Physician Portal from within the partner application For more information about SSO see About Single Sign On SS
20. XTN 40 Accepted length of this field is 40 O Business numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt lt area city code NM phone number NM gt extension NM PID 15 Language CE 60 NS Patient PID 16 Marital Status IS 1 NS PID 17 Religion IS 3 NS PID 18 Patient Account CX 20 NS Number PID 19 SSN Number ST 16 Must contain 9 numeric digits or 11 O Patient with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22 Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 NS Indicator PID 25 Birth Order NM 2 NS PID 26 Citizenship IS 4 NS Chapter 9 Care360 Patient Demographic HL7 Specification Indicator Segment ID Element Name Type Length Comments Req d PID 27 Veterans CE 60 NS Military Status PID 28 Nationality CD 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 NS a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported MRG Merge Patient Information Se
21. XTN 40 N Home PID 14 Phone Number XTN 40 N Business PID 15 Language CE 60 N Patient PID 16 Marital Status IS 1 N PID 17 Religion IS 2 N PID 18 Patient Account CX 20 The requisition number C Number generated by the LIS Conditional based on where the order was generated PID 19 SSN Number ST 9 Numeric only no space or C Patient punctuation If the inbound order contains this value this field is populated with the same value PID 20 Driver s Lic DLN 25 N Num Patient PID 21 Mother s CX 20 N Identifier PID 22 Ethnic Group IS 3 N PID 23 Birth Place ST 60 N PID 24 Multiple Birth ID 2 N Indicator Chapter 4 Care360 Results HL7 Specification Segment ID Element Name Type Length Comments Supported PID 25 Birth Order NM 2 N PID 26 Citizenship IS 4 N PID 27 Veterans CE 60 N Military Status PID 28 Nationality CE 80 N PID 29 Patient Death TS 26 N Date amp Time PID 30 Patient Death ID 1 N Indicator a For a description of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never ORC Common Order Segment The Common Order ORC segment is used to transmit fields that are common to all orders all types of services that are requested The ORC segmentis required in the ORM message Segment ID Element Name Type Length Comments
22. segment is used to transmit fields that are common to all orders all types of services that are requested The ORC segmentis required in the ORM message 84 Segment ID Element Name Type Length Comments Req d ORC 00 Segment Type ID ST 4 Must be ORC R ORC 01 Order Control ID 2 Valid value for this field is NW New R Order Used for new orders with a new specimen ORM messages with an NW control code should originate at the ordering facility ORC 02 Placer Order EI 20 The placer application s order number R Number same as OBR 02 All OBRs in the ORM must contain the same value The Hub verifies that this field is present The Hub also verifies that the values for this field in all ORC segments are identical Note The Hub does not require unique order numbers The service provider is responsible for handling any duplicate order numbers that are received ORC 03 Filler Order EI 22 NS Number ORC 04 Placer Group EI 22 NS Number ORC 05 Order Status ID 2 For valid values refer to HL7 table NS 0038 Order status ORC 06 Response Flag ID 1 For valid values refer to HL7 table NS 0121 Response flag ORC 07 Quantity Timing TQ 200 NS ORC 08 Parent CM 200 NS ORC 09 Date Time of TS 26 NS Transaction ORC 10 Entered By XCN 120 NS ORC 11 Verified By XCN 250 Identifies the person who verified the O accuracy of the entered request 11 1 NPP ID Format 11 2 NPP Name NPP ID
23. telecommunications tux 999 1999 9999 X99999 B99999 C any number text telecommunication use code ID lt telecommunication equipment type ID lt email address ST country code NM gt lt area city code NM gt phone number NM extension NM any text ST Time Series TO Timing quantity For timing quantity specifications for orders see Chapter 4 of the HL7 Standard Section 4 4 quantity CQ gt interval duration start date time TS end date time TS gt priority ID gt condition ST text TX gt conjunction ID order sequencing gt ADT A28 Patient Add Message Segment Specifications This section provides detailed specifications for each segment of an ADT A28 Patient Add HL7 message The purpose of this message type is to enable a partner application to add a new patient via the Hub to Physician Portal Message Segment Hierarchy An ADT A28 message must follow the message segment hierarchy as specified below MSH Message Header Required one per file EVN Event Type Required PID Patient Identification Required PD1 Additional Demographics Optional not supported by the Hub NK1 Next of Kin Associated Parties Optional not supported by the Hub PV1 Patient Visit Data Required PV2 Patient Visit Additional Info Optional not supported by the Hub DB1 Disability Information Optional no
24. 1 nillable true maxOccurs 1 gt lt xsd sequence gt lt xsd complexType gt lt xsd complexType name DemographicResponse gt lt xsd sequence gt lt xsd element xmins tp java language_builtins lang type tp ArrayOfString name errors minOccurs 1 nillable true maxOccurs lt xsd element typ lt xsd element typ lt xsd element type xsd string name status minOccurs lt xsd sequence gt lt xsd complexType gt lt xsd schema gt lt xsd schema xmins xsd http www w3 org 2001 XMLSchema xmins stns java javax xml rpc elementFormDefault qualified attributeFormDefault qualified targetNamespace java javax xml rpc gt lt xsd element type stns ServiceException name ServiceException gt lt xsd complexType name ServiceException gt lt xsd schema gt lt xsd schema xmins xsd http www w3 org 2001 XMLSchema xmins stns java javax xml soap lified attribuiteFormDefault ied tarnetNamesnace iavaziavax xml Done In This Chapter About the Patient Demographic Services API Reference 168 e Patient Demographic Services APT esser Ree exeo LOD About the WSDL Interface Document 172 167 168 About the Patient Demographic Services API Reference This section provides details about the Patient Demographic Services API calls provided by Care360 Hub Information Services The Patient Demographic Services component of Care360 Hub Info
25. 10124 CARDIO CRP 20040708164727 1 1111111A52352 Machado Randal l lllllll I R Chapter 3 Care360 Order HL7 Specification s jns y A10j8 amp 10qe Aueg paru L 96 About This Section This section provides detailed information necessary for formatting laboratory test results to be retrieved from a third party laboratory by Care360 Integration Services This section includes the following chapter s e Chapter 4 Care360 Results HL7 Specification on page 97 Third Party Laboratory Results Chapter 4 Care360 Results HL7 Specification In This Chapter e About the Care360 Results HL7 Specification 98 Care360 Result Message Format Requirements 99 e Care360 Result Message Segment Specifications 103 e Sample Care360 Result Messages 0000000000 eee 120 e Receiving Third Party Laboratory Results Files 125 97 98 About the Care360 Results HL7 Specification This chapter provides detailed format specifications for laboratory results that are received by Care360 Hub Information Services from a Quest Diagnostics BU or from a third party laboratory Results may be formatted according to the HL7 2 3 Specification or the HL7 2 3 1 Specification with any exceptions noted in this chapter Note The tables shown in the Care360 Result Message Segment Specifications contain both the HL7 2 3 and HL7 2 3 1 Specifications In cases where these
26. 17 Guarantor XAD 106 No more than 106 characters wide O Employer Address Add1 50 add2 50 city 50 state 2 zip 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above GT1 18 Guarantor XTN 40 NS Employer Phone Number GT1 19 Guarantor CX 20 NS Employee ID Number GT1 20 Guarantor IS D NS Employment Status GT1 21 Guarantor XON 130 NS Organization Name GT1 22 Guarantor Billing ID 1 NS Hold Flag GT1 23 Guarantor Credit CE 80 NS Rating Code GT1 24 Guarantor Death TS 26 NS Date And Time GT1 25 Guarantor Death ID 1 NS Flag GT1 26 Guarantor Charge CE 80 NS Adjustment Code GT1 27 Guarantor CP 10 NS Household Annual Income GT1 28 Guarantor NM 3 NS Household Size GT1 29 Guarantor CX 20 NS Employer ID Number GT1 30 Guarantor Marital IS 1 NS Status Code Segment ID Element Name Type Length Comments Req d GT1 31 Guarantor Hire DT 8 NS Effective Date GT1 32 Employment Stop DT 8 NS Date GT1 33 Living Dependency IS D NS GT1 34 Ambulatory Status IS 2 NS GT1 35 Citizenship IS 4 NS GT1 36 Primary Language CE 60 NS GT1 37 Living Arrangement IS 2 NS GT1 38 Publicity Indicator CE 80 NS GT1 39 Protection Indicator ID 1 NS GT1 40 Student Indicator IS 2 NS GT1 41 Religion IS 3 NS GT1 42 Mother s Maiden XPN 48 NS Name GT1 43 Nationality CE 80 NS GT1 44 Ethnic Group IS 3 NS GT1 45
27. 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Dataset 17 DOS Reject Hemolysis File Name HEMOLYSIS TXT Description Usage Provides DOS information for rejection criteria for hemolized specimens There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SPECIMEN_REJECT_HEMOLYSIS Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 R Required O Optional C Conditional Dataset 18 DOS Reject Lipemia File Name LIPEMIA TXT Description Usage Provides DOS information for rejection criteria for lipemic specimens There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SPECIMEN_REJECT_LIPEMIA Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your perfo
28. ADT A39 Patient Merge Message Segment Specifications 229 230 Segment ID Element Name Type Length Comments Req d PID 18 Patient Account CX 20 NS Number PID 19 SSN Number ST 16 Must contain 9 numeric digits or 11 O Patient with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22 Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 NS Indicator PID 25 Birth Order NM D NS PID 26 Citizenship IS 4 NS PID 27 Veterans CE 60 NS Military Status PID 28 Nationality CD 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 NS Indicator a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported Chapter 9 Care360 Patient Demographic HL7 Specification Sample Care360 Patient Demographic Messages Following are several sample patient demographic messages formatted according to the Care360 Patient Demographic Message Format Requirements on page 175 and the corresponding message segment specifications Patient Add Patient Delete Patient Update or Patient Merge Sample 1 Add Patient MSH amp sending applicat
29. About the Landing Page When accessing Physician Portal from a partner application via SSO linking in a Web service context the BlankPage option is the only landing page option that is applicable The BlankPage option displays a blank page to the user This is used as the landing page from a successful SSO authentication and is irrelevant to the subsequent Web service call Chapter 6 Physician Portal SSO Specification Chapter 7 User Summary Services API Reference i Microsoft Internet Explorer File Edit View Favorites Tools Help 3 D BB JD sem krate O amp M DOHKSZS Address https portal care360 com care350 services UserSummaryWebService WSDL xml versionz 1 0 encoding UTF 8 lefinitions mlns tnsz http www care360 com services xmins wsrz http www openuri org 2002 10 soap reliability mins mimez http schemas xmlsoap org wsdl mime xmins soap12 http schemas xmlsoap org wsdl soap12 xmins http http schemas xmlsoap org wsdl http xmins soapenc http schemas xmlsoap org soap encoding xmins soap12enc http www w3 org 2003 05 soap encoding onvz http www openuri org 2002 04 wsdl conversation http schemas xmlsoap org wsdl soap zhttp www w3 org 2001 XMLSchema xmins http schemas xmlsoap org wsdl targetNamespace http www care360 com services gt schema xmins xsd http www w3 0rg 2001 XMLSchema java com medplus care360 ws org model elementFormDefa
30. CPT_CD PK1 R char 7 Chapter 2 Care360 Master File Specification NBS SERVICE CPT XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes 6 Type MLCP_FDA R char 1 Valid values e L Limited coverage policy e N Non FDA approved e F Frequencyimited 7 Policy effective date EFFECTIVE DTE R datetime 8 Policy expiration EXPIRATION DTE R datetime date a R Required O Optional C Conditional Dataset 11 LCP MN CPT To ICD9 File Name CPTICD9 TXT Description Usage Identifies the diagnosis codes that are acceptable for CPT codes covered under Limited Coverage Policy Medical Necessity policies There is one entry per diagnosis code per CPT code per carrier as identified by the BIS Required This dataset is optional for third party laboratory implementations required if billing Medicare ABN limited coverage frequency Conditions None MLCP CPT ICD9 XREF date Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 Your performing site code 3 Billing carrier ID CARRIER CD PKI R char 6 Must match dataset 4 field 3 and dataset 10 field 3 4 CPT code CPT_CD PKI R char 5 5 ICD9 code ICD9 NO PERIOD PKI R char 6 The code should not include a decimal
31. Care360 Results HL7 Specification on page 97 The results returned by the third party laboratory must be submitted in XML format encapsulating the HL7 file and zero or more report of record PDF files if the laboratory is configured to do so The XML file must be formatted according to the schema detailed in Receiving Third Party Laboratory Results Files on page 123 L The Hub retrieves the results on a predefined schedule and verifies the format and content of the results L TheHub records the results transaction and stores a copy of the discrete content ofthe results for a minimum of 90 days or longer as specified by the laboratory L The Hub submits the results to either the Lab Orders function of Physician Portal or to the third party EMR file system Note If the third party laboratory cannot provide a report of record PDF version of the lab results Lab Orders can generate a customized PDF from the HL7 file C The user logs in to Physician Portal or the third party EMR to view results In Physician Portal the user can view results in one of the following ways L Toview new results received into Physician Portal for all patients the user accesses the New Results page About the Universal Ordering and Resulting Data Flow L To view results for a specific patient the user searches for the desired patient and then accesses the Recent Tests area of the Patient Summary Note All results are se
32. Chapter 2 Care360 Master File Specification Dataset 32 DOS Performing Site File Name PERFLAB TXT Description Usage Provides DOS information for the test performing sites There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None DOS PERFORMING SITE Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT CD PKI R char 10 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset 33 Reference Ranges File Name REFRANGES TXT Description Usage Provides DOS reference range data for the tests There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None REFERENCE RANGES Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT_CD PK1 R char 10 4 Sequence number SEQUENCE NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditiona
33. Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 4 Your performing site code 3 Analyte Code ANALYTE_CD PK1 R char 11 Must match dataset 26 field 4 4 Analyte ANALYTE MNEMONIC R char 25 Can be the same as field 3 5 Analyte Line 1 Desc ANALYTE LINE 1 DESC R char 50 6 Analyte Line 2 Desc ANALYTE LINE 2 DESC O char 25 a R Required O Optional C Conditional Dataset 25 Client UPIN File Name UPIN TXT Description Usage Provides UPIN and or NPI numbers for clients Required This dataset is conditional for third party laboratory implementations required if billing Medicare Conditions None CLIENT_UPIN Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Client number CLIENT_NO PKI R char 6 Client number for billable clients Chapter 2 Care360 Master File Specification CLIENT UPIN Column Name CDC Column Name Key Req d Type Length Valid Values Notes 4 UPIN number UPIN PKI R char 6 5 Name NAME R char 50 a R Required O Optional C Conditional Dataset 26 Worklist Components File Name N A Description Us
34. Container File Name CONTAINER TXT Description Usage Provides DOS information for specimen container requirements There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None CONTAINER Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 R Required O Optional C Conditional Dataset 14 DOS Methodology File Name METHODOLOGY TXT Description Usage Provides DOS information for testing methodology There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None METHODOLOGY Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset File Details
35. E 7039 1 Monday Saturday E 7187 1 Monday Saturday E 7773 1 Monday Saturday E 7781 1 Monday Saturday gt 10090 1 15040 1 15040 2 15180 1 15214 1 15214 2 TO ROS To 17426 1 LIS LTA TA615 25 17617 1 17988 1 185720615 18846 1 19208 1 TO9S2X I 19687 1 T9752 1 19885 1 19950 1L gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt gt E 20008 1 E 20008 2 E 20099 1 E 20T123 1 E 20289 1 E 20321 1 E 20396 1 E 20644 1 E 20750 1 E 20867 1 E 20867 2 E 20867 3 E 20908 1 kdays kdays kdays kdays sday Saturday kdays kdays kdays kdays kdays kdays kdays kdays kdays kdays ekdays nday and Thursday ekdays ekdays ekdays onday to Sunday Days Sunday Nights Monday Friday onday Saturday Days Sunday Nights Monday Friday onday Saturday onday Saturday onday Saturday on Fri on Fri onday Saturday Tuesday Saturday Sunday Friday onday Saturday Days Monday Saturday onday Saturday Sunday Friday Tuesday Saturday Days Sunday Nights onday Friday onday Saturday onday Saturday onday Saturday onday Saturday Tuesday Saturday onday Saturday Days Sunday Nights onday Friday Also stat onday Saturday Nights Monday Saturday or performed on a STAT basis Nights Monday Friday OR can be performed on a STAT basis Sample Ma
36. Length Valid Values Notes 3 Order code TEST_CD PKI R char 16 4 Sequence number SEQUENCE_NO PKI R smallint 5 Alias Name ALIAS NAME O char 175 a R Required O Optional C Conditional Dataset 28 Temperatures File Name TEMPERATURES TXT Description Usage Provides preferred and acceptable temperatures by test code as well as comments associated with each temperature Required This dataset is not supported for third party laboratory implementations information from this dataset is included in Dataset 7 Order Code Conditions None Note This dataset is no longer required the information is in Dataset 7 Order Code TEMPERATURES Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 4 Your performing site code 3 Order code TEST_CD PKI R char 16 4 Preferred PTEMP O char 5 Only one single character preferred Temperatures temperature is allowed Current codes in use include e R Refrigerated e F Frozen e A Ambient room temp e S Special e W Wet ice 5 Preferred PTEMP_COMMENTS O char 30 Temperatures Comments Chapter 2 Care360 Master File Specification TEMPERATURES Column Name CDC Column Name Key Req d Type Length Valid Values Notes 6 Acc
37. MedPlus will work with you to review application security network security password aging practices password complexity rules and user account management practices to determine whether or not your system operates at a minimum level of discipline across these areas L Obtaining a digital certificate This isan RSA encrypted certificate that your application will use for signing SAML assertions before passing them to Physician Portal You must generate a private key and certificate request to be authorized by a third party certificate authority for example VeriSign and then forward the public key to MedPlus L Providing SAML credentials Your SAML implementation must employ a few key pieces of information that must be shared with MedPlus your SAML partner including O Source ID A base64 encoded identifier that uniquely identifies your site This is the primary key component of the organizational trust record MedPlus creates for you in our system O Issuer A unique string typically in URL format that identifies your Internet host point This string is stored in the organizational trust record that MedPlus maintains for you and is also included in all SAML assertions transmitted by your site to Physician Portal o SAML Artifact Redemption Servlet Applies only to partners using the SAML Browser Artifact profile If your site uses the SAML Browser Artifact profile method of authentication this is a URL on your system to which
38. NM lt area city code NM phone number NM extension NM If present the Hub verifies that the value complies with rules above GT1 08 Guarantor Date Time Of Birth TS 26 The date and time of the guarantor s birth Format YYY YMMDDHHMMSS The Hub verifies that the date time is in this format GT1 09 Guarantor Sex IS Valid values for this field include e M Male e F Female e Blank The Hub verifies that one of these values is present in this field GT1 10 Guarantor Type IS NS GT1 11 Guarantor Relationship IS Describes relations to patient Valid values 1 Self 2 Spouse 8 Dependent Blank GT1 12 Guarantor SSN ST 11 Must contain 9 numeric digits or 11 with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above GT1 13 Guarantor Date Begin DT NS ADT A28 Patient Add Message Segment Specifications 189 190 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d GT1 14 Guarantor Date DT 8 NS End GT1 15 Guarantor Priority NM 2 NS GT1 16 Guarantor XPN 130 Employer name No more than 130 O Employer Name characters wide Alphanumeric data only GT1
39. NPP Name Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d ORC 12 Ordering XCN 120 Identifies the provider who ordered the C Provider test same as OBR 16 Format for UPIN Only UPIN Number LastName FirstName Middle UPIN e Format for NPI Only NPI Number LastName FirstName Middle NPI e Format for UPIN and NPI UPIN Number LastName FirstName Middle UPIN NPI Number LastName FirstName Middle NPI If present the Hub passes the value through with no validation Required only if IN1 47 T Third Party Bill ORC 13 Enterer s PL 80 NS Location ORC 14 Call Back Phone XTN 40 NS Number ORC 15 Order Effective TS 26 NS Date Time ORC 16 Order Control CE 200 NS Code Reason ORC 17 Entering CE 60 NS Organization ORC 18 Entering Device CE 60 NS ORC 19 Action By XCN 120 NS a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Care360 Order Message Segment Specifications 85 OBR Observation Request Segment One OBR segment must be transmitted for each Order Code associated with any PID segment This segment is mandatory in ORM messages Segment ID Element Name Type Length Comments Req d OBR 00 Segment Type ID ST 4 Must be OBR R OBR 01 Set ID SI 4 OBR segments are pair
40. Name Type Length Comments Req d IN1 05 Insurance XAD 106 No more than 106 characters wide O Company Add1 50 add2 50 city 50 state 2 Address zip 10 country code 3 Alphanumeric data only If populated the Hub ignores this field IN1 06 Insurance Co XPN 48 NS Contact Person IN1 07 Insurance Co XTN 40 NS Phone Number IN1 08 Group Number ST 50 Characters permitted include O A Z and 1 0 If present the Hub verifies that the value complies with rules above IN1 09 Group Name XON 130 O IN1 10 Insured s Group CX 12 NS Emp ID INI 11 Insured s Group XON 130 NS Emp Name IN1 12 Plan Effective DT 8 NS Date INI 13 Plan Expiration DT 8 NS Date IN1 14 Authorization CM 55 NS Information INI 15 Plan Type IS 3 NS INI 16 Name Of XPN 48 NS Insured IN1 17 Insured s IS 2 NS Relationship To Patient INI 18 Insured s Date TS 26 NS Of Birth INI 19 Insured s XAD 106 NS Address IN1 20 Assignment Of IS 2 NS Benefits IN1 21 Coordination Of IS 2 NS Benefits IN1 22 Coord Of Ben ST 2 NS Priority Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d IN1 23 Notice Of ID 2 NS Admission Flag IN1 24 Notice Of DT 8 NS Admission Date IN1 25 Report Of ID 2 NS Eligibility Flag IN1 26 Report Of DT 8 NS Eligibility Date IN1 27 Release IS 2 NS Information Code IN1 28 Pre
41. Numerical CQ Composite quantity quantity NM gt units CE gt with units NM Numeric Any of the ASCII numeric characters with an optional leading sign or and or an optional decimal point SI Sequence ID A non negative integer in the form of a NM data type Identifier ID Coded values for String data drawn from an HL7 defined table of legal values see HL tables Appendix A of HL7 2 3 IS Coded values for String data drawn from a site defined table of legal values user defined tables HD Hierarchic namespace ID IS gt universal ID ST gt designator universal ID type ID gt Used only as part of EI and other data types EI Entity identifier entity identifier ST namespace ID IS universal ID ST universal ID type ID PL Person location lt point of care IS room IS bed IS facility HD location status IS gt person location type IS building IS floor IS location description ST gt PT Processing type Xprocessing ID ID processing mode ID Date Time DT Date YYYY MM DD TM Time HH MM SS S S S S 2222 TS Time stamp YYYY MM DD HHMM SS S S S S 1 1 7 ZZZZz degree of precision Chapter 3 Care360 Order HL7 Specification Data Type Category Data Type Data Type Name Notes Format Code Values CE Coded element identifier ST text ST name of coding system ST al
42. Order Demography MEL Flowsheet Graph Patient Information Contact Information Last Name Brinkman Address Line 1 222 N Franklin St Add New Patient Peene First Name Rose Address Line 2 Apt 12 Mave Clinical Activities Middle Initial City Winamac Quest Retrieve External History Yes State Province Region Indiana Qe iagnostics Date Of Birth 02 10 1925 Jl 2 Zip Postal Code 47 Gender Femde v Country United States Marital Status z Email Minthnete Maidan nioma mr eres Bj trusted sites In This Chapter e About the Physician Portal SSO Specification e Establishing Organizational Truste zoe ete r9 Ree RS 151 Implementing SAML esee seriem Rem on toe Se enne 152 Usage Scenario 1 Physician Portal SSO for Interactive Users 155 e Usage Scenario 2 Physician Portal SSO for Web Services 149 About the Physician Portal SSO Specification Physician Portal SSO utilizes the Oasis SAML 1 1 specification for exchanging credentials securely between itself and a partner application The implementation of this trust model is based upon a combination of the following items A digital certificate that identifies the external partner e An organizational trust record that is recorded with Physician Portal The organizational trust record follows an assessment process verifying that the partner site can securely and accurately assert the identities of its users on behalf of
43. Order Echo 22e pe n 04620000 463 bk 085 138 About Patient Demographic Services lees 140 Patient Demographic Services Connectivity 0 0 00 eee 140 Real Time vs Batch Processing seek ERU RR ead E CER e kass 140 PID Only ys EUzzy Matchin seses eek e TERRE ERCRHEP eie p 141 Process Walkthrough Submitting a Patient Demographic Update 144 Process Walkthrough Outbound Patient Demographic Updates 145 Customizing the Physician Portal User Interface lees 146 Custom UI Specifications i iscberRbRE 0854 RE RES ER P RE DEERE ETE SS 147 Chapter 6 Physician Portal SSO Specification 149 About the Physician Portal SSO Specification 6 0 cece cece eee eeees 150 Establishing Organizational Trust 0 c ccc e cece cence eee eeeeees 151 Implementing SAML osora nacon a ya RAS RR a ease ema UR AUR RA a d 152 Usage Scenario 1 Physician Portal SSO for Interactive Users 155 About Session Timeouts and Terminations 0 00 00 cece eee eee 155 Abouts5O User Initialization csc dob este key SEE GEHE RERE RETE ER CRT 156 Usage Scenario 2 Physician Portal SSO for Web Services sess 157 About Session Timeouts and Terminations 0 00 00 cece ee eee 159 About SSO User Tnitialuzatt n oirir enrere ot airn er P REA RIOT M URS 160 About the Landing Page 42er 000544 saa tii E EUR He bRe repe 160 Chapter 7 User Summary
44. PV1 43 Prior Temporary PL 80 NS Location PV1 44 Admit TS 26 NS Date Time PV1 45 Discharge TS 26 NS Date Time PV1 46 Current Patient NM 12 NS Balance PV1 47 Total Charges NM 12 NS ADT A28 Patient Add Message Segment Specifications 187 188 Segment ID Element Name Type Length Comments Req d PV1 48 Total NM 12 NS Adjustments PV1 49 Total Payments NM 12 NS PV1 50 Alternate Visit ID CX 20 NS PVI 51 Visit Indicator IS 1 NS PV1 52 Other XCN 60 NS Healthcare Provider a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported GT1 Guarantor Segment The Guarantor GT1 segment contains guarantor for example the person or the organization with financial responsibility for payment of a patient account data for patient and insurance billing applications This segment is applicable only for patient and insurance billing Segment ID Element Name Type Length Comments Req d GT1 00 Segment Type ID ST 4 Must be GTI R GT1 01 Set ID SI 4 GT1 message segments should be numbered sequentially from 1 R GT1 02 Guarantor Number CX 59 NS GT1 03 Guarantor Name XPN 48 No more than 48 characters wide including the delimiter between the last and first names At least on
45. Physician Portal Since password management is not required to access Physician Portal the password management at the partner application endpoint must be comparable Once the organizational trust has been established the partner application can submit authentication requests to Physician Portal in the form of a SAML assertion SAML is an XML based messaging standard that provides for the specification of a partner site identifier user name identifier digital signature of the asserted information and so on This SAML message is typically posted directly to the Physician Portal secure web server using the SAML Browser POST profile Some of the various third party SAML toolsets available include the following e ComponentSpace SAML NET for the Windows NET platform e OpenSAML for Java MedPlus can provide sample implementations using the above toolsets which can be used as a Starting point and for performing system checks for your configuration 150 Chapter 6 Physician Portal SSO Specification Establishing Organizational Trust This section provides a list of business processes that you can follow to facilitate the collection of identifiers and credentials for your site as well as to assess the fitness and requirements of your application infrastructure for the use of SAML in place of Physician Portal passwords The high level processes for establishing organization trust include the following L Performing a security assessment
46. R a R Required O Optional C Conditional Chapter 7 User Summary Services API Reference Chapter 8 Patient Demographic Services API Reference Microsoft Internet Explorer Fle Edt View Favorites Tools Help Q O D M raw 2 H A Address http hubservices medplus com demographic service wsdl lt xml version 1 0 encoding UTF 8 gt definitions xmIns tns http medplus com demographic xmins wsr http www openuri org 2002 10 soap reliability xmins mime http schemas xmlsoap org wsdl mime xmins soap12 http schemas xmlsoap org wsdl soap12 xmins http schemas xmlsoap org wsdl http xmins soapenc http schemas xmlsoap org soap encoding p http www w3 0rg 2003 05 soap encoding xmins conv http www openuri org 2002 04 wsdl conversation xmins soap http schemas xmlsoap org wsdl soap xmins s http www w3 org 2001 XMLSchema xmins http schemas xmlsoap org wsdl targetNamespace http medplus com demographic types xsd schema xmins xsd http www w3 0rg 2001 XMLSchema xmins stns java com medplus serviceHub mpi webservice elementFormDefault qualified attributeFormDefault qualified targetNamespace java com medplus serviceHub mpi webservice gt lt xsd import namespace java language_builtins lang gt xsd complexType name DemographicRequest gt axsd sequence gt lt xsd element type xsd base64Binary name ADTMessage minOccurs
47. XPN 130 NS GT1 17 GT1 18 Guarantor Employer Address Guarantor Employer Phone Number XTN 106 40 NS NS GT1 19 Guarantor Employee ID Number CX 20 NS GT1 20 Guarantor Employment Status IS NS GT1 21 Guarantor Organization Name XON 130 NS GT1 22 GT1 23 Guarantor Billing Hold Flag Guarantor Credit Rating Code ID CE 80 For valid values refer to HL7 table 0136 Yes no indicator NS NS GT1 24 Guarantor Death Date And Time TS 26 NS GT1 25 Guarantor Death Flag ID For valid values refer to HL7 table 0136 Yes no indicator NS GT1 26 Guarantor Charge Adjustment Code CE 80 NS GT1 27 Guarantor Household Annual Income CP 10 NS Care360 Order Message Segment Specifications 81 82 Segment ID Element Name Type Length Comments Req d GT1 28 Guarantor NM 3 NS Household Size GT1 29 Guarantor CX 20 NS Employer ID Number GT1 30 Guarantor IS 1 For suggested values refer to user NS ppm defined table 0002 Marital status Code GT1 31 Guarantor Hire DT 8 NS Effective Date GT1 32 Employment DT 8 NS Stop Date GT1 33 Living IS 9 For suggested values refer to user NS Dependency defined table 0223 Living dependency GT1 34 Ambulatory IS 9 For sugges
48. and Images The Physician Portal logo in the upper left corner as well as the Quest Diagnostics logo in the lower left corner can each be replaced with a similarly sized logo or image to reflect the branding of the partner organization or application For details see Logo and Image Specifications on page 147 Color Palette The overall color scheme of the Physician Portal user interface including the navigational buttons can be modified to reflect the partner organization or application For details see Color Palette Specifications on page 147 Copyright and Trademark Text The Quest Diagnostics copyright and trademark text along the bottom of each page can be changed to reflect the applicable copyright or trademark text of the partner organization For details see Copyright and Trademark Text Specifications on page 147 Link Names and Destinations Several of the hypertext links along the bottom of each page can be changed to display custom text as well as to link to Web based resources associated with the partner organization For example the Contact Us link could be changed to Contact University Hospital with the link providing direct access to the hospital s customer support Web site For details see Link Name and Destination Specifications on page 147 Custom Uniform Resource Locator URL The Web address or URL that is used to access Physician Portal and appears in the user s Web browser while using th
49. gt assigning facility HD gt cod Generic CM Composite No new CMs are allowed after HL7 Version 2 2 Hence there are no new CMs in Version 2 3 Demographics XAD Extended address In Version 2 3 replaces the AD data type lt street address ST gt lt other designation ST gt lt city ST gt lt state or province ST gt zip or postal code ST gt country ID gt address type ID other geographic designation ST county parish code IS census tract IS XPN Extended person name In Version 2 3 replaces the PN data type family name ST given name ST middle initial or name ST gt suffix e g JR or III ST prefix e g DR ST gt degree e g MD ST gt name type code ID gt XON Extended composite name and ID number for organizations organization name ST organization name type code IS gt ID number NM gt check digit NM code identifying the check digit Scheme employed ID gt assigning authority HD gt identifier typ IS assigning facility ID cod HD Care360 Patient Demographic Message Format Requirements 177 178 Data Type Chapter 9 Care360 Patient Demographic HL7 Specification Category Data Type Name Notes Format XTN Extended In Version 2 3 replaces the TN data type
50. httpsifjwww care360 comp physicianportallapp je Edt View Favorites Tools Help Pah trots O gt 3 DJ dA 3 Jg Demo Health Assoc User Preferences Support WhatsNew Help Logout Welcome Any User Care360 Quick View d Quick View MessagesFaxes Tasksy Summary data was last updated on 02 18 2008 at 11 09 AM EST __Refresh Page Diagnostics New Results You have 10 new results You have 10 final results Of these 8 are abnormal e You have no partial results Messages Faxes Tasks You have no new messages e You have no faled fax messages There are no faled fax messages for this org Action Items Prescriptions You have 4 prescstons penting appro You bays na prescretions pending renew You have no total tasks e You have no new tasks You have no faled faxes e You have no pending tasks Last Login Date 02 13 08 03 07 PM EST Quick View Clinical Admin Preferences Install Contact Us Feedback Quest Diagnostics Resource What s New Help Logout Quest Quest Diagnostics the associated Ino Nichols Institute ad al associated Quest Diagnostics marks are the registered trademarks of Quest Diagnostics all third party marks are the property of their respective owners 2000 2008 Quest Diagnostics Incorporated All TS reserved Bj trusted stes The elements of the Physician Portal that can be customized include the following Logos
51. in the ORM message must be present and if present how many of these segments can occur The requirements listed in the table are over and above the field requirements detailed in Care360 Order Message Segment Specifications on page 67 For example if an ORM passes the segment level rules detailed in the following table the message can still fail the field level rules for any of the existing segments Care360 Order Message Format Requirements 59 60 Segment Required Comments Conditions MSH R The Hub verifies that this segment is present in the ORM message Message Header PID R The Hub verifies the following Patient Identifier e This segment is present in the ORM message e There is only one PID in the ORM message PVI O If present the Hub passes the PV1 segments through validating Patient Visit Data the field lengths only not the field values INI R The Hub verifies the following Insurance e This segment is present in the ORM message e No more than two INI segments exist in the ORM message GTI C The Hub verifies that this segment is present if required by the bill Guarantor type as outlined below e Patient Bill Required e Client Bill Optional e Third Party Bill Required If present the Hub also verifies that there is only one GT segment in the ORM message Note Bill type is established using IN1 47 ORC R The Hub verifies the following Common Order e This segment is present in
52. information on possible connectivity methods see Universal Ordering and Resulting Connectivity on page 9 Results Formatting Requirements Results files that are retrieved by Care360 Hub Information Services from a third party laboratory must meet the following requirements e The provider and or provider accounts referenced in the HL7 result message must be valid and active in the Hub e The result HL7 file and any associated report of record PDF files must be submitted as a single XML file e The incoming result XML file must conform to the Hub XML schema see Hub XML Schema below e The result HL7 content must conform to the Physician Portal Results HL7 Specification as outlined in Care360 Result Message Format Requirements on page 99 and Care360 Result Message Segment Specifications on page 103 e If the provider is configured to send a report of record PDF file together with the HL7 message then a primary report PDF file must be present Additionally one or more secondary reports can be provided as needed If the provider is configured to not send a PDF file then the report of record will be generated automatically for the provider and the provider cannot include a PDF file with the HL7 message Hub XML Schema The third party laboratory must provide individual results as XML files on a file server with each XML file containing one HL7 and one or more reports PDF documents The labor
53. new Physician Portal login session Chapter 6 Physician Portal SSO Specification Usage Scenario 1 Physician Portal SSO for Interactive Users In this scenario SSO is used to establish a Physician Portal session for an end user within a Web browser window specifically Internet Explorer on the user s computer The SAML 1 1 Browser POST implementation as outlined in Implementing SAML on page 152 is manifested when the partner application launches the Web browser Doing so loads an HTML document containing a form that targets the Physician Portal SSO security check servlet with the appropriate parameters as hidden input nodes Example Browser POST Note The SAMLResponse value in the following example is truncated for the sake of brevity lt HTML gt lt BODY Onload document forms 0 submit gt lt FORM METHOD POST ACTION https portal care360 com care360 Care360SSOSecurityCheck gt lt input type hidden name targetUri value NewResults gt lt input gt lt input type hidden name branduid value 209252d710e58d150110e58d67190001 gt lt input gt lt INPUT TYPE HIDDEN NAME SAMLResponse VALUE PHNhbWxw0OlJ gt lt INPUT gt lt FORM gt lt BODY gt lt HTML gt In the example above the form is posted to Care360SSOSecurityCheck from the Web browser such that the specified landing page is displayed to the user and the session cookie is established within the br
54. point 6 Policy effective date EFFECTIVE DTE R datetime 7 Policy expiration EXPIRATION DTE R datetime a R Required O Optional C Conditional Dataset File Details 33 34 Dataset 12 DOS Billing Procedure Code File Name CPTCODES TXT Description Usage Provides Directory of Service DOS information for what CPT codes are assigned to service codes The rows of data obtained from NBS are not unique Required This dataset is optional for third party laboratory implementations Conditions None BILLING_PROCEDURE_CODE Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 Your performing site code 3 Performing site LABORATORY_CD PKI R char 4 4 CPT schedule CPT_SCHEDULE PK1 R char 8 5 Request date REQUEST_DTE PKI R datetime 6 Billing service code SERVICE_CD PKI R char 7 Must match dataset 7 field 11 7 CPT code CPT_CD PKI R char 5 8 CPT code modifier CPT_CD_MODIFIER PK1 R char 2 9 CPT service units CPT SERVICE UNITS CNT R smallint count 10 CPT name CPT_NM R char 80 11 Reimbursement REIMBURSEMENT_AMT O money amount 12 Allocation percent ALLOCATION_PCT O decimal 7 4 a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Dataset 13 DOS
55. range 32768 to 32767 varchar length Same as data type char length Chapter 2 Care360 Master File Specification Dataset File Details This section provides the field level details for each of the datasets listed in the Dataset File List on page 15 Datasets are listed numerically and table name for each dataset is shown in the table heading Primary key columns are noted in the dataset structures and usually only one or two keys are identified PK1 is noted for those dataset columns that are part of the first key PK2 is used for the second key etc Dataset 1 Client File Name CLIENT TXT Description Usage Client file for Lab Orders order entry Provides data about an ordering client There is one entry per client per laboratory site Required This dataset is required for third party laboratory implementations Conditions None TOPLAB CLIENT Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 3 Performing site PERFORMING_TOPLAB PKI R char 3 4 Client number TOPLAB_CLIENT_NUMBER PKI R char 15 5 Billing client number NBS_CLIENT_NUMBER R char 15 6 Client mnemonic CLIENT_MNEMONIC R char 26 7 Client name CLIENT_NAME R char 30 8 Alpha name ALPHA_NAME R char 25 Client name without space
56. requirements for loading reference data into the Lab Orders component of Physician Portal Third party laboratory test orders are then created and submitted to the third party laboratory for processing via Physician Portal Chapter 2 Care360 Master File Specification About the Master File Datasets A separate set of Master File dataset files must be provided for each third party laboratory The dataset files that comprise a laboratory s Master Files should be updated on a regular basis and can be automatically retrieved and stored by Care360 Hub Information Services As the Hub retrieves and processes the latest data the data is then integrated into the Lab Orders workflow within Physician Portal Dataset File List The dataset files that the Master Files provide are listed in the following table Each of these datasets is described in more detail in the sections that follow Dataset Dataset Name Code Table Name Req d 1 Client cf TOPLAB CLIENT R 2 Client Bill To cb CLIENT BILL TO XREF R 3 Bill To bt BILL TO C 4 Bill To Edit be BILLING_EDITS O 5 Bill To Edit List bl BILLING EDIT LISTS O 6 Bill To Eligibility by BILL_TO_ELIGIBILITY NS 7 Order Code oc TEST CODE UNIT CODE XREF R 8 Order Code AOE oa AOE O 9 Order Code Component op PROFILE COMPONENT XREF O 10 LCP MN Service to CPT lc NBS SERVICE CPT XREF O ll LCP MN CPT to ICD9 li MLCP CPT ICD9 XREF O 12 DOS
57. sample application and source code Download the Sample Application and Source Code 1 Access the Care360 SSO and Web Services site at the following URL http custcenter medplus com tech support portalcenter 2 When prompted type your username and password and then press Enter For future reference record your username and password in the spaces below Username Password 3 From the Resources area do the following e To download the sample application click the Example SSO Care360 Stage link When prompted click Save As and then locate the desired download directory on your hard disk e To download the sample source code click the SSO Test EMR Source Code link When prompted click Save As and then locate the desired download directory on your hard disk 4 Unzip the contents of the sample application and source code files For an overview of the file contents see About the Sample Application on page 236 Accessing the Care360 SSO and Web Services Site 235 236 About the Sample Application The Physician Portal SSO and Web Services site provides the resources described in this section for partner application developers In addition to the information provided here additional details of each of these resources are provided in a Readme file included with each sample application Example SSO Application The Physician Portal SSO and Web Services site provides the Example SSO Care360 Stage exec
58. street address ST other designation ST gt city ST gt state or province ST gt zip or postal code ST country ID address type ID other geographic designation ST county parish code IS census tract IS XPN Extended person name In Version 2 3 replaces the PN data type family name ST given name ST middle initial or name ST gt suffix e g JR or III ST prefix e g DR ST degree e g MD ST gt name type code ID gt XON Extended composite name and ID number for organizations organization name ST organization name type code IS gt ID number NM gt check digit NM code identifying the check digit Scheme employed ID gt assigning authority HD gt identifier type code IS assigning facility ID HD gt XTN Extended telecommunications number In Version 2 3 replaces the TN data type NNN 999 999 9999 X99999 B99999 C any text telecommunication use code ID lt telecommunication equipment type ID lt email address ST gt country code NM area city code NM phone number NM lt extension NM any text ST Time Series TO Timing quantity For timing quantity specifications for orders see Chapter 4 of the HL7 Standard Section 4 4 quantity CQ gt interva
59. the ORM message e There are no more than 35 ORC segments in an ORM message e For each ORC segment there is one and only one OBR segment in the ORM message OBR R The Hub verifies the following Observation e This segment is present in the ORM message Request e There are no more than 35 OBR segments in the ORM e Each OBR segment is paired with an ORC segment e Only one OBR is associated with an ORC segment Note The Hub does not check the content of the OBR to verify if the Order Codes are duplicated in the ORM message DGI O Downstream clinical and administrative systems may not be able to Diagnosis successfully process the order if the content of this segment exceeds a total of 10 unique ICD 9 codes Therefore it is recommended that the sending system not exceed this limit If present the Hub verifies that all of the required data in this segment is present and in compliance with the format rules Note The Hub does not check the content of the fields and does not perform business logic checks across multiple DG1 segments OBX C AOEs associated with the Order are captured as one to many OBX Observation segments If present the Hub passes the segment through if the Result Detail data in the segment complies with the field level rules detailed in Chapter 3 Care360 Order HL7 Specification Care360 Order Message Segment Specifications on page 67 Segment X Required Comments Conditions NTE O If present the
60. this format and passes the value through OBR 08 Observation End TS 26 NS Date Time OBR 09 Collection CQ 20 NS Volume OBR 10 Collector XCN 60 NS Identifier OBR 11 Specimen Action ID 1 The action to be taken with respect to O Code the specimens that accompany or precede this order OBR 12 Danger Code CE 60 NS OBR 13 Relevant Clinical ST 300 NS Info OBR 14 Specimen TS 26 NS Received Date Time OBR 15 Specimen Source CM 300 For valid values refer to HL7 table NS 0070 Source of specimen OBR 16 Ordering XCN 120 Identifies the provider who ordered the C Provider test same as ORC 12 e Format for UPIN Only UPIN Number LastName FirstName Middle UPIN e Format for NPI Only NPI Number LastName FirstName Middle NPI e Format for UPIN and NPI UPIN Number LastName FirstName Middle UPIN NPI Number LastName FirstName Middle NPI If present the Hub passes the value through with no validation Required only if IN1 47 T Third Party Bill OBR 17 Order Callback XTN 40 NS Phone Number Care360 Order Message Segment Specifications 87 Segment ID Element Name Type Length Comments Req d OBR 18 Placer field 1 ST 60 If present the Hub stores this O information and returns it as received with the associated results Notes e For each unique occurrence of OBRA the OBR 4 value is to be preserved as is the corresponding s
61. update requests are received and processed by the Hub and are then forwarded to Physician Portal Any errors that are generated by Physician Portal are also returned to the originating partner application via the Hub Patient demographic messages must be formatted according to the HL7 2 3 Specification with any exceptions noted in this chapter Supported messages for inbound patient demographic updates include the following e ADT A28 ADT A28 Patient Add e ADT A29 ADT A29 Patient Delete e ADT A31 ADT A31 Patient Update e ADT A39 ADT A39 Patient Merge This chapter includes the following sections e Patient demographic message format requirements For information on the message format requirements see Care360 Patient Demographic Message Format Requirements on page 175 Patient demographic message segment specifications Each result message received by the Hub contains a number of standard sections For requirements on the standard segments of a result message see the following o ADT A28 Patient Add Message Segment Specifications on page 179 o ADT A29 Patient Delete Message Segment Specifications on page 195 o ADT A3 Patient Update Message Segment Specifications on page 204 o ADT A39 Patient Merge Message Segment Specifications on page 221 e Sample patient demographic messages For samples of the various patient demographic update messages see Sample Care360 Patient Demographic Messages on
62. 0 Verification By XCN 60 NS IN1 31 Type Of IS 2 NS Agreement Code IN1 32 Billing Status IS 2 NS ADT A28 Patient Add Message Segment Specifications 193 194 Number Segment ID Element Name Type Length Comments Req d IN1 33 Lifetime Reserve NM 4 NS Days IN1 34 Delay Before NM 4 NS L R Day IN1 35 Company Plan IS 8 NS Code IN1 36 Policy Number ST 50 O IN1 37 Policy CP 12 NS Deductible IN1 38 Policy Limit CP 12 NS Amount IN1 39 Policy Limit NM 4 NS Days IN1 40 Room Rate CP 12 NS Semi Private IN1 41 Room Rate CP 12 NS Private IN1 42 Insured s CE 60 NS Employment Status IN1 43 Insured s Sex IS 1 NS IN1 44 Insured s XAD 106 NS Employer Address IN1 45 Verification ST D NS Status IN1 46 Prior Insurance IS 8 NS Plan ID IN1 47 Coverage Type IS 3 Valid values include O e T Third party bill e P Patient bill e C Client bill If present the Hub verifies that the value complies with rules above IN1 48 Handicap IS 2 NS IN1 49 Insured s ID CX 12 NS a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported Chapter 9 Care360 Patient Demographic HL7 Specification ADT A29 Patient Delete Message Segment Specifications This section provides detailed specifications for each segment of
63. 03 Sending Application HD 180 The name of the sending application MSH 04 Sending Facility HD 180 The sending facility Identifies the owner of the patient data and who initiated the patient demographic request Inbound The Hub verifies that the field is populated Outbound No verification by the Hub Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d MSH 05 Receiving HD 180 The receiving application identifier O Application MSH 06 Receiving Facility HD 180 The receiving facility The account R number defined for the requester Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 07 Date Time of TS 26 The date and time that the sending R Message system created the message Format YYYYMMDDHHMMSS The Hub verifies that this field is populated and that the value complies with the format above MSH 08 Security ST 40 NS MSH 09 Message Type CM 7 The type of message being R transmitted and the event leading to the creation of the message Valid value ADT A28 Add Person Information MSH 10 Message Control ST 20 A number or other data that uniquely R ID identifies the message in its transmission to the lab system The Hub verifies that this field is populated MSH 11 Processing ID PT 3 The placer system s intent for the R m
64. 1 Valid values Y N U Unknown 66 SelecTest date SELECTEST_DATE R datetime 67 SelecTest by whom SELECTEST_BY_WHOM R char 7 68 Display suffix table DISPLAY_SUFFIX_TABLE R char 1 Valid values Y N U Unknown 69 National billing NATIONAL_BILL_MNEMONIC R char 1 Valid values Y N mnemonic U Unknown 70 Valid charge to VALID CHARGE TO R char 255 lor more separated with commas C P T Bill mnemonic a R Required O Optional C Conditional Dataset 2 Client Bill To File Name CLBTX TXT Description Usage Identifies what types of billing and what specific bill to s are valid for an ordering client There is one entry per valid bill to per client per site Required This dataset is required for third party laboratory implementations Conditions There must be a parent entry in the Client dataset CLIENT_BILL_TO_XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 3 Performing site PERFORMING_TOPLAB PKI R char 3 4 Client number TOPLAB_CLIENT_NO PKI R char 15 5 Billto ID BILLING ID PKI R char 9 Valid values C Client P Patient T Third party Bill to ID Client number Chapter 2 Care360 Maste
65. 10165SB BASIC METABOLIC PANEL I IIIIII20030523105800 TP QUEST DIAGNOSTICS TAMPA 4225 E FOWLER AVE TAMPA FL 33617 20030523110900 IFI OBX 1 NM 25000000 GLUCOSE 25000000 GLUCOSE 109 N F 20030523110900 TP L NTE 1 FASTING REFERENCE INTERVAL OBX 2 NM 25000100 UREA NITROGEN BUN 25000100 UREA NITROGEN BUN 15 MG DL 7 25 N F 20030523110900 TP L OBX 3 NM 25000200 CREATININE 25000200 CREATININE 1 6 MG DL 0 5 H 4 PITT IL A I G HE e Oo Cn jw E 65 F 1120030523110900 TP L NM 25000300 BUN CREATININE RATIO 25000300 BUN CREATININE RATIO 9 CALC 6 25 N I F11120030523110900 TP T 5 NM 25000400 SODIUM 25000400 SODIUM 150 MMOL L 135 H F 20030523110900 TP L 6 NM 25000500 POTASSIUM 25000500 POTASSIUM 5 1 MMOL L 3 5 5 3 N F 20030523110900 TP L 7 N 8 NM 25000600 CHLORIDE 25000600 CHLORIDE 102 MMOL L 98 F 20030523110900 TP L NM 25000700 CARBON DIOXIDE 25000700 CARBON DIOXIDE 24 MMOL L 21 33 N F 20030523110900 TP L OBX 9 NM 25001000 CALCIUM 25001000 CALCIUM 9 8 MG DL 8 5 10 4 NI IF 1 20030523110900 TP L OBR 2 3812197 TP362228T 8847SB PROTHROMBIN TIME WITH INR 8847SB PROTHROMBIN TIME WITH INR EI 20030523105800 TP QUEST DIAGNOSTICS TAMPA
66. 12 County Code IS 4 NS PID 13 PhoneNumber XTN 40 Accepted length of this field is 40 O Home numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt lt area city code NM gt phone number NM gt extension NM The Hub verifies that the value complies with rules above PID 14 PhoneNumber XTN 40 Accepted length of this field is 40 O Business numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM lt area city code NM phone number NM gt extension NM The Hub verifies that the value complies with rules above PID 15 Language CE 60 NS Patient PID 16 Marital Status IS 1 NS PID 17 Religion IS 3 NS PID 18 Patient Account CX 20 NS Number Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PID 19 SSN Number ST 16 Must contain 9 numeric digits or 11 O Patient with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22
67. 28T 867SB T 4 THYROXINE TOTAL 867SB T 4 THYROXINE TOTAL IIIIIIII200305231058001 LTP QUEST DIAGNOSTICS TAMPA 4225 E FOWLER AVE TAMPA FL 33617 20030523110900 EI LL ELLE ELE TLF TL JG I EN OBX 1 NMJ55075200 T 4 THYROXINE TOTAL 55075200 T 4 THYROXINE 15 2 MCG DL 4 5 12 5 H F 1120030523110900 TP 1I OBX 2 NMJ55075300 FREE T4 INDEX T7 55075300 FREE T4 INDEX 8 111 4 3 8 HI IF 120030523110900 TP L OBR 5 3812197 TP362228T 899SB TSH 899SB TSH 20030523105800 22d TP QUEST DIAGNOSTICS TAMPA 4225 E FOWLER AVE TAMPA FL 33617 20030523110900 EI LL ELLE ELE TLF T JG I El OBX 1 NM 55080400 T8H 55080400 TSH 5 MIU L 0 40 5 50 N F 1120030523110900 TP L j O H gt E gt HA NJ gt Ov 122 Chapter 4 Care360 Results HL7 Specification Receiving Third Party Laboratory Results Files In order to receive third party laboratory results Care360 Hub Information Services initiates a secure connection to the laboratory s file server on a predefined schedule for example every 3 5 minutes to retrieve and process the available results files The secure transfer of results data between the Hub and a third party laboratory can be accomplished by a number of different methods for example via SSH File Transfer Protocol SFIP For more
68. 3 The reason for the event O Code EVN 05 Operator ID XCN 60 The individual responsible for O triggering the event EVN 06 Event Occurred TS 26 The date and time that the event O actually occurred a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PID Patient Identification Segment The Patient Identification PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID O segments within a message Usually a sequential number beginning with 1 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PID 02 Patient ID CX 20 When the patient is from another R External ID institution outside office etc the identifier used by that institution can be shown in this field This may bea number that multiple disparate corporations or facilities share PID 03 Patient ID CX 20 The primary identifier or other O Internal ID identifiers used by t
69. 4225 E FOWLER AVE TAMPA FL 33617 20030523110900 I EI LL ELE EE ELE EL LL TF TL JG I OBX 1 NM 30040200 INTERNATIONAL NORMALIZED RATIO INR 30040200 INTERNATIONAL NORMALIZED RATIO INR 11 5 N FI 20030523110900 TP L NTE 1 INR REFERENCE INTERVAL APPLIES TO PATIENTS NTE 2 NOT ON ANTICOAGULANT THERAPY 0 9 1 1 NTE 3 NTE 4 SUGGESTED INR THERAPEUTIC RANGE FOR ORAL NTE 5 ANTICOAGULANT THERAPY STABLY ANTICOAGULATED NTE 6 PATIENTS NTE 7 NTE 8 ROUTINE THERAPY 2 0 3 0 NTE 9 NTE 10 RECURRENT MYOCARDIAL INFARCTION NTE 11 OR MECHANICAL PROSTHETIC VALVES 2 5 3 5 NTE 12 NTE 13 l OBX 2 NM 30039900 PROTHROMBIN TIME 30039900 PROTHROMBIN TIME 14 6 SECONDS 9 0 11 5 H F 120030523110900 TP L OBR 3 3812197 TP362228T 861SB T 3 UPTAKE 861SB T 3 UPTAKE 11111120030523105800 1 1 TP QUEST DIAGNOSTICS TAMPA 4225 E FOWLER AVE TAMPA FL 33617 20030523110900 lIEI LLLELLELEEETELLL T I OBX 1 NM J55075100 T 3 UPTAKE 55075100 T 3 UPTAKE 45 22 35 H J F 1120030523110900 TP T Sample Care360 Result Messages 121 OBR J4 3812197 TP3622
70. 49 National account NATIONAL_ACCOUNT_CODE O char 4 code 50 Epidemiology EPIDEMIOLOGY_REPORTS R char 1 Valid values Y N reports U Unknown 51 Reportonly flag REPORT ONLY FLAG R char 1 Valid values Y N U Unknown 52 Fax group FAX_GROUP O char 10 53 Govt agency city GA_CITY O char 40 54 Govtagency county GA_COUNTY O char 40 55 Govt agency zip GA_ZIP_CODE R char 9 56 Client alert flag CLIENT_ALERT_FLAG R char 1 Valid values R Regular J Jeopardy N New 57 Require billing entry REQUIRE_BILLING_ENTRY R char 1 Valid values Y N U Unknown 58 HMO member HMO_MEMBER_NUMBER_REQ R char 1 Valid values Y N number required U Unknown 59 HMO physician HMO_PHYSICIAN_REQ R char 1 Valid values Y N required U Unknown 60 Copy to required COPY_TO_REQUIRED R char 1 Valid values Y N U Unknown 61 Carbon send out site CARBON_SENDOUT_SITE O char 3 Dataset File Details 21 22 TOPLAB CLIENT Column Name CDC Column Name Key Req d Type Length Valid Values Notes 62 Report department REPORT_DID R char 1 Valid values Y N ID U Unknown 63 PAF signature PAF_SIGNATURE R char 2 Valid values Y N U Unknown 64 PAF date PAF_DATE O datetime 65 SelecTest enabled SELECTEST_ENABLED R char
71. 51 Submitting Third Party Master Files 1 0 0 ccc cee cece cence ence eneees 54 About the Carrier Edit Patterns ccce hh n 55 Chapter 3 Care360 Order HL7 Specification Lsuuusuueuuue 57 About the Care360 Order HL7 Specification 0 c cece e cece eens 58 Care360 Order Message Format Requirements leere 59 Messapecesiment Hierarchy oss osos ERST TEC PAR Poe a 2002 RIP PRES 59 Message Segment Requirements 22 see etym tace tx eS we dem PUR bd d eed 59 Newline Characters ioo eo vebepepesehbPeesietpEPCesi eX epeRp SIRE LAG 62 Field Delnnitets ve Tues em E er Ree EORR ORA REA E E EROR 62 Field Specifications 2 ci4cccscice se cence iti stridit trenit itir kiet 63 Data Type Specifications cues acies excl do os Ewdr es Ig p maa E egarerdon deed 64 Care360 Order Message Segment Specifications 00 e cece cece eens 67 Sample Care360 Order Messages 00s cece cence eect eee e een enes 94 Third Party Laboratory Results About This Section 64 0 94 40 3 40 ws e he here pao wae VE See ewe 96 Chapter 4 Care360 Results HL7 Specification L 97 About the Care360 Results HL7 Specification cele 98 Care360 Result Message Format Requirements lees 99 Message Segment Hierarchy esce 0 kerinan rye re eq PAN x HS 99 Newline Characters 2255s Jo v4 XR RRPRRAEREPEPCSAQN Kp Rd eR E ees 99 Field DeElMiters 252o sec dee P
72. 7 Physician Portal accessing directly 135 accessing via SSO 134 linking and SSO 130 overview 4 Production environment 237 Physician Portal Continued Staging environment 237 UI customization x 130 146 Physician Practice Management System PPMS Technology Provider definition 241 PID field requirements order 69 72 field requirements patient demographic 183 185 198 201 208 210 224 227 228 230 field requirements result 105 107 segment requirements order 60 PID only matching details 141 patient demographic integration 141 Preferred Requirement dataset Master Files 36 Process walkthrough Linking and SSO 133 Order Echo 138 outbound patient demographic integration 145 patient demographic integration 144 Universal Lab Orders and Results 5 User Summary Services 137 Production environment Hub 172 Physician Portal 237 Provider definition 241 Provider account definition 241 PSC Hold orders 68 PVI field requirements order 72 75 field requirements patient demographic 185 188 201 203 210 213 segment requirements order 60 Q Quality definition 241 R Real time mode patient demographic integration 140 Reference Ranges dataset Master Files 47 Reject Hemolysis dataset Master Files 37 Reject Lipemia dataset Master Files 37 Reject Thaw Other dataset Master Files 38 Related documentation xvi Request ID definition 242 Required definition 59 63 175 Requirements link formatting 131 Result message segmen
73. 7 110 segment requirements order 60 Order Code Alias dataset Master Files 43 Order Code AOE dataset Master Files 30 Order Code Component dataset Master Files 31 Order Code dataset Master Files 28 30 Order Echo x 130 overview 138 process walkthrough 138 Order message segment requirements DGI fields 91 92 DGl segment 60 GTI fields 79 83 GTI segment 60 IN1 fields 75 78 INI segment 60 MSH fields 67 69 MSH segment 60 NTE fields 93 93 NTE segment 61 OBR fields 86 89 OBR segment 60 OBX fields 90 91 OBX segment 60 ORC fields 84 85 ORC segment 60 PID fields 69 72 PID segment 60 PV1 fields 72 75 PVI segment 60 Orders Care360 HL7 specification 58 Master Files 14 message segment requirements 59 66 PSC Hold 68 Organizational trust establishing for SSO 151 ORM sample messages 94 94 ORU sample messages 120 122 Outbound patient demographic integration overview 140 process walkthrough 145 Overviews Care360 Order HL specification 58 Care360 Patient Demographic HL7 specification 174 Care360 Result HL7 specification 98 Care360 SSO and Web Services site 234 Linking and SSO 130 135 Master Files 14 Order Echo 138 outbound patient demographic integration 140 patient demographic integration 140 Physician Portal UI customization 146 SSO implementation 150 Index 247 248 Index Overviews Continued Universal Lab Orders and Results 4 User Summary Services 136 P Pass Through defi
74. AG R char 1 Valid values 1 Active 0 Inactive 6 Inhouse Flag INHOUSE_FLAG R char 1 Valid values 1 Lab facility 0 Vendor facility 7 Facility Name FACILITY_NAME R char 50 8 Address 1 ADDR_LINE_1 R char 50 9 Address 2 ADDR_LINE_2 R char 50 10 City CITY R char 30 11 State STATE R char 2 12 Zip Code ZIP_CD R char 10 18 Phone number PHONE_NO R char 16 14 PC MES Flag PC_MES_FLAG O char 1 15 Specimen Grouping SPECIMEN_GROUP O char 16 16 Requisition Label format REQ LABEL O char 20 17 Specimen Label format SPECIMEN LABEL O char 20 18 Send In Label format SEND IN LABEL O char 20 19 Send Out Label format SEND_OUT_LABEL O char 20 20 Combo Label format COMBO_LABEL O char 20 21 Sortation Device SORT_DEVICE O char 5 22 Aliquoter Label format ALIQUOTER_LABEL O char 20 Dataset File Details 41 42 PERFORMING_SITE Column Name CDC Column Name Key Req d Type Length Valid Values Notes 23 Medical Director MEDICAL DIRECTOR R char 25 a R Required O Optional C Conditional Dataset 24 Analyte Details File Name N A Description Usage Provides analyte details Required This dataset is not supported for third party laboratory implementations Conditions None ANALYTE_CODE_XREF Column Name CDC
75. About the Carrier Edit Patterns on page 55 54 69 Group number GROUP NO PATTERN 1 16 O char 28 See About the Carrier pattern Edit Patterns on page 55 70 85 Group number list GROUP_NO_PATTERN_LIST_1 16 O char 10 See About the Carrier Edit Patterns on page 55 86 101 Referring physician REFER_DOC_PATTERN_1 16 O char 28 See About the Carrier pattern Edit Patterns on page 55 102 Referring physician REFER_DOC_PATTERN_LIST_1 16 O char 10 See About the Carrier 117 list Edit Patterns on page 55 a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Dataset 5 Bill To Edit List File Name EDITLIST TXT Description Usage Specifies bill to edit lists which are unsequenced collections of string values There is one entry per list value per list Required This dataset is optional not recommended for third party laboratory implementations Conditions None Note See About the Carrier Edit Patterns on page 55 for further explanation and examples of datasets 4 and 5 BILLING_EDIT_LISTS Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Laboratory Code LABORATORY_CD PK1 R char 4 Your performing site code 3 List ID LIST_ID PKI R char 2 Must be two digit alphanumeric 4 List value LIST_VALUE PKI R char 10
76. Admit Cert ST 15 NS PAC IN1 29 Verification TS 26 NS Date Time IN1 30 Verification By XCN 60 NS IN1 31 Type Of IS 2 NS Agreement Code IN1 32 Billing Status IS 2 NS IN1 33 Lifetime Reserve NM 4 NS Days IN1 34 Delay Before NM 4 NS L R Day IN1 35 Company Plan IS 8 NS Code IN1 36 Policy Number ST 50 O IN1 37 Policy CP 12 NS Deductible IN1 38 Policy Limit CP 12 NS Amount IN1 39 Policy Limit NM 4 NS Days IN1 40 Room Rate CP 12 NS Semi Private IN1 41 Room Rate CP 12 NS Private ADT A31 Patient Update Message Segment Specifications 219 220 Segment ID Element Name Type Length Comments Req d IN1 42 Insured s CE 60 NS Employment Status IN1 43 Insured s Sex IS 1 NS IN1 44 Insured s XAD 106 NS Employer Address IN1 45 Verification ST D NS Status IN1 46 Prior Insurance IS 8 NS Plan ID IN1 47 Coverage Type IS 3 Valid values include O e T Third party bill e P Patient bill e C Client bill If present the Hub verifies that the value complies with rules above IN1 48 Handicap IS 2 NS IN1 49 Insured s ID CX 12 NS Number a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported Chapter 9 Care360 Patient Demographic HL7 Specification ADT A39 Patient Merge Message Segment Specifications This section provides detai
77. Billing Procedure db BILLING PROCEDURE CODE O Code 13 DOS Container dc CONTAINER O 14 DOS Methodology dm METHODOLOGY O 15 DOS Minimum Volume dv MINIMUM SPECIMEN VOLUME O 16 DOS Preferred dp PREFERRED_SPECIMEN_REQUIREMENT O Requirement 17 DOS Reject Hemolysis dh SPECIMEN_REJECT_HEMOLYSIS O 18 DOS Reject Lipemia dl SPECIMEN REJECT LIPEMIA O 19 DOS Reject Thaw Other dt SPECIMEN_REJECT_THAW_OTHER O 20 DOS Specimen Stability ds SPECIMEN STABILITY O About the Master File Datasets 15 16 Dataset Dataset Name Code Table Name Req d 21 DOS Transport dx TRANSPORT TEMPERATURE O Temperature 22 Client Specific Order cp CUSTOM PANELS O Code 23 Performing Site Code ps PERFORMING SITE O 24 Analyte Details ac ANALYTE CODE XREF NS 25 Client UPIN up CLIENT UPIN C 26 Worklist Components wc WORKLIST COMPONENT XREF NS 27 Order Code Alias da UNIT CODE ALIAS O 28 Temperatures te TEMPERATURES NS 29 Client Specific Code cc N A O XREF 30 Alternate Specimen dn ALTERNATE SPECIMEN DATA O Data 31 Clinical Significance dg CLINICAL SIGNIFICANCE DATA O Data 32 DOS Performing Site df DOS PERFORMING SITE O 33 Reference Ranges dr REFERENCE RANGES O 34 Setup Days dd SETUP DAYS O 35 Setup Times de SETUP_TIMES O 36 Turnaround Times do TURNAROUND TIMES O 37 Hand Written Order ht HOTT O 38 Client NPP np NPP O 39 Medical Manager mm MED_MGR
78. Care360 Hub Information Services for processing see Chapter 3 Care360 Order HL7 Specification on page 57 Message Segment Hierarchy ORU messages must follow the message segment hierarchy as specified below MSH Message Header PID Patient Identification NTE Notes and Comments ORC Common Order OBR Observation Request I OBX Observation Result NTE Notes and Comments 1 In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional Newline Characters Result HL7 messages must use the carriage return CR character ASCII 0x0D to indicate a newline Result messages that contain a line feed LF character ASCII 0x04 to indicate a newline will be rejected Field Delimiters A delimiter must separate each field Even if a field contains no data it must still be delimited The delimiter for any given HL7 message is always defined in the MSH segment of the message as the first character following the segment identifier MSH 00 See the message segment descriptions for more detail Standard HL7 delimiters are used Field Specifications The following table describes the parameters used to define the data fields within each message segment Parameter Description Type For a description of the data types see Data Type Specifications on page 100 Length The maximum allowed length for the field Care360 Result M
79. Click for an expanded view o Renewal Items Displays a collapsed view of the pending items for the logged in user Click for an expanded view o Failed Faxes Displays a collapsed view of failed faxes sent by the logged in user Click for an expanded view Once the user has linked to a particular Physician Portal function the user can then access the entire Physician Portal application limited only by their assigned access permissions For information about using specific Physician Portal functions refer to the Care360 Physician Portal User Manual or online help Formatting Requirements for Linking to Care360 Physician Portal When a partner enables users to link directly to Physician Portal functions the link that appears within the partner application must be formatted according to the following guidelines e The full Physician Portal product name must be displayed whenever possible and should appear as shown below Care360 Physician Portal e The trademark symbol must always follow Care360 e Ifthe partner application will display a Care360 logo the following logo must be used Care360 A MedPlus Solution Note You can obtain the Care360 logo from the Physician Portal SSO and Web Services site For more information see Chapter 10 Care360 SSO and Web Services Site on page 233 Prior to appearing in a production environment any links to Physician Portal must be submitted through the project manager for c
80. Contact Person s XPN 48 NS Name GT1 46 Contact Person s XTN 40 NS Telephone Number GT1 47 Contact Reason CE 80 NS GT1 48 Contact IS 2 NS Relationship GT1 49 Job Title ST 20 NS GT1 50 Job Code Class JCC 20 NS GT1 51 Guarantor XON 130 NS Employer s Organ Name GT1 52 Handicap IS 2 NS GT1 53 Job Status IS 2 NS GT1 54 Guarantor Financial FC 50 NS Class GT1 55 Guarantor Race IS 1 NS ADT A28 Patient Add Message Segment Specifications 191 192 a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported IN1 lInsurance Segment The Insurance IN1 segment contains insurance policy coverage information necessary to produce properly pro rated and patient and insurance bills This segment is applicable only for insurance billing Segment ID Element Name Type Length Comments Req d IN1 00 Segment ST 4 Must be IN1 R Type ID IN1 01 Set ID SI 4 INI message segments should be R numbered sequentially from 1 IN1 02 Insurance Plan CE 50 The Hub verifies that the field is R ID populated IN1 03 Insurance CX 59 This is the QDI Bill mnemonic O Company ID Note Required only if IN1 47 T Third Party Bill IN1 04 Insurance XON 130 Note Required only if IN1 47 O Company Name T Third Party Bill IN1 05 Insurance XAD 106 No more th
81. D Debug Development The Hub verifies that the value in this field is P T or D MSH 12 Version ID ID 8 The value for this field is 2 3 R MSH 13 Sequence NM 15 NS Number MSH 14 Continuation ST 180 NS Pointer MSH 15 Accept ID D NS Acknowledgment Type MSH 16 Application ID 2 NS Acknowledgment Type MSH 17 Country Code ID 2 NS MSH 18 Character Set ID 6 NS MSH 19 Principal CE 60 NS Language of Message a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported ADT A29 Patient Delete Message Segment Specifications 197 198 EVN Event Type Segment The Event Type EVN segment is used to communicate necessary trigger event information to receiving applications Segment ID Element Name Type Length Comments Req d EVN 00 Segment ST 4 Must be EVN R Type ID EVN 01 Event Type Code ID 3 The second component trigger event R of MSH 09 Message Type should be used to transmit event type code information This field contains the events corresponding to the trigger events described in this section Note This field has been retained for backward compatibility only EVN 02 Recorded TS 26 The date and time that the transaction O Date Time was entered EVN 03 Date Time TS 26 The date and time that the event is O Planned Event planned EVN 04 Event Reason IS
82. D xsi type xsd string gt 2c928dc01195313601119a1d0bb700 5 lt orgUID gt WSOrg gt WSOrg xsi type nl WSOrg gt lt orgName xsi type xsd string gt AUTO LNR US05 orgName lt orgUID xsi type xsd string gt lt lt lt lt 2c928dc01195313601119a206c3700 6 orgUID WSOrg WSOrg xsi type nl WSOrg gt lt orgName xsi type xsd string gt AUTO LNR US06 orgName XorgUID xsi type xsd string gt 2c928dc01195313601119a22079700 7 orgUID WSOrg WSOrg xsi type nl WSOrg gt lt orgName xsi type xsd string gt AUTO LNR US07 orgName XorgUID xsi type xsd string gt 2c928dc01195313601119a24307c00 8 orgUID lt WSOrg gt lt WSOrg xsi type n1 WSOrg gt lt orgName xsi type xsd string gt AUTO LNR US08 orgName XorgUID xsi type xsd string gt 2c928dc01195313601119a25a3 200 9 orgUID lt WSOrg gt lt lt ti orgList gt meStamp xsi type xsd dateTime gt 2007 04 17T12 59 59 420Z lt timeStamp gt lt result gt lt m getOrgsResponse gt lt env Body gt env Envelope For more information about the User Summary services see About User Summary Services on page 136 and Chapter 7 User Summary Services API Reference on page 161 About Session Timeouts and Terminations Session timeout conditions do not need to be actively considered by the partner application integrator when establishing SSO for Web services as long as an SSO a
83. Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 NS Indicator PID 25 Birth Order NM 2 NS PID 26 Citizenship IS 4 NS PID 27 Veterans CE 60 NS Military Status PID 28 Nationality CD 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 NS Indicator a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PV1 Patient Visit Data Segment The Patient Visit Data PV1 segment is used by registration patient administration applications to communicate information on a visit specific basis This segment can be used to send multiple visit statistic records to the same patient account or single visit records to more than one account Segment ID Element Name Type Length Comments Req d PV1 00 Segment Type ID ST 4 Must be PV1 R PV1 01 Set ID SI 4 Will always be 1 O PV1 02 Patient Class IS 1 Examples of valid values R E Emergency I Inpatient O Outpatient ADT A28 Patient Add Message Segment Specifications 185 186 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 03 Assigned Patient PL 80 NS Location PV1 04 Admission Type IS 2 NS PV1 05 Preadmit CX 20 NS Nu
84. IA10QSU 3f HxBYmNkZWZeR2hpamtsbW5vcF5BfHw XprimaryReport JVBERiOxLjMNJeLjz USUR8MTcCONnwyMDA3MDIWwWOTEwMTQOOXx R8MXwxMjMONTY3ODkxMjMONXwyNTI yMDAOMDEzMXxNfHx8fHx8fHx h17 9MNMSAwIG9iago8PAovUGFnZUxheW91d I AvU21uZ2xlUGFnZQovUGFnZUl1vZGUgL1VzZU5vbmUKL1BhZ2VzIDIgMCBSCi9 l1IC9DYXRhbG9nCj4 CmVuZG9iag01IDAgb2JqCjw8Ci9CY primaryReport lt additionalReports gt lt report gt JVBERi0OxLj lt report gt JVBERi0xLj KJf 8KCjEgMCBvYmoKPDwKL1BhZ2V bmdsZVBhZ2UKL1BhZ2VNb2RlIC9Vc2VOb251Ci9Q0YWdlcyAyIDAgUgovVHlwZ Q2FOYWxvZwo tPgplbmRvYmoKCj IgMCBvYmoKPDwKLONvdWwW50 IDEK KJf 8KCjEgMCBvYmoKPDwKL1BhZ2V YXlvdXOgL1Np report YXlvdXOgL1Np bmdsZVBhZ2UKLl1BhZ2VNb2RlIC9Vc2VOb251Ci9QYWdlcyAyIDAgUgovVHlwZ Q2FO0YWxvZwo tPgplbmRvYmoKCj IgMCBvYmoKPDwKLONvdaW50IDEK lt additionalReports gt lt tns result gt K report Receiving Third Party Laboratory Results Files 125 ug uBis ejburs pue unur 128 About This Section Linking and Single Sign On This section provides detailed information necessary for linking a partner application for example a third party EMR EHR or PMS application to Physician Portal This section includes the following chapter s Chapter 5 Linking to Physician Portal on page 129 Chapter 6 Physician Portal SSO Specification on page 149 Chapter 7 User Summary Services API Reference on page 161
85. IN1 38 Policy Limit CP 12 NS Amount IN1 39 Policy Limit NM 4 NS Days Care360 Order Message Segment Specifications 71 78 Segment ID Element Name Type Length Comments Req d IN1 40 Room Rate CP 12 NS Semi Private IN1 41 Room Rate CP 12 NS Private IN1 42 Insured s CE 60 NS Employment Status IN1 43 Insured s Sex IS 1 For suggested values refer to user defined NS table 0001 Sex IN1 44 Insured s XAD 106 NS Employer Address IN1 45 Verification ST 2 NS Status IN1 46 Prior Insurance IS 8 NS Plan ID IN1 47 Coverage Type IS 3 Rules for requirement of the INI GTI R segment are addressed in Care360 Order Message Format Requirements on page 59 Valid values include e T Third party bill e P Patient bill e C Client bill If this segment is present the Hub verifies that this field is populated with one of these values IN1 48 Handicap IS 2 NS IN1 49 Insured s ID CX 12 NS Number a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Chapter 3 Care360 Order HL7 Specification GT1 Guarantor Segment The Guarantor GT1 segment contains guarantor for example the person or the organization with financial responsibility for payment of a patient account data for patient and insurance billing applications This segment
86. If the Send LOINC Data option is selected for a Hub account or if itis not selected and 03 1 03 4 the Hub passes all sub fields through If itis not selected and 03 1 z 03 4 the Hub performs the following transformations Sets 03 1 to value of 03 4 Sets 03 2 to value of 03 5 e Sets 03 3 to value of NULL The Hub passes 03 4 03 5 and 03 6 through unchanged A OO uem cQ Or OBX 04 Observation Sub ID ST 20 OBX 05 Observation Value ID 72 This field either contains the result or the field is blank and accompanying NT segments contain the result OBX 06 Units CE 15 Units of measure in which the result is reported OBX 07 References Range ST 24 The range in which a reported result would be considered as normal for the age and sex of the patient May be expressed as a numeric value such as e Range 3 5 4 5 e Lower Limit 10 e Upper Limit 15 May also be expressed as an alpha value such as e Negative Non reactive Care360 Result Message Segment Specifications 117 118 Segment ID Element Name Type a Length Comments Supported OBX 08 Abnormal Flags ID Contains the normalcy status of the result being reported Valid values include e L Below low normal e H Above high normal A Alpha abnormal e N Normal e Blank No comment C OBX 09 Pro
87. In This Chapter About Universal Ordering and Resulting sese About the Universal Ordering and Resulting Data Flow Universal Ordering and Resulting Connectivity About Universal Ordering and Resulting Care360 Integration Services provides a framework for a third party service provider laboratory or EMR application to integrate with the Physician Portal product suite Integrating a third party laboratory or EMR application into the Physician Portal product suite enables end users of Physician Portal or the third party EMR application to place lab orders with a third party laboratory and to receive results from that laboratory This section provides an overview of Universal Ordering and Resulting including a description of each of the primary components of the Physician Portal product suite Universal Ordering and Resulting Components The Universal Ordering and Resulting product suite consists of the following primary applications e Physician Portal Physician Portal is an Internet based application that provides electronic lab test ordering and online delivery and viewing of the associated lab results in addition to a number of other important patient care features It includes a Lab Orders function used for placing lab orders with either a Quest Diagnostics Business Unit BU or a third party service provider laboratory e Care360 Hub Information Services Care360 Hub Informatio
88. N 03 Date Time TS 26 The date and time that the event is O Planned Event planned EVN 04 Event Reason IS 3 The reason for the event O Code EVN 05 Operator ID XCN 60 The individual responsible for O triggering the event EVN 06 Event Occurred TS 26 The date and time that the event O actually occurred a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported ADT A31 Patient Update Message Segment Specifications 207 208 PID Patient Identification Segment The Patient Identification PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID O segments within a message Usually a sequential number beginning with 1 PID 02 Patient ID CX 20 When the patient is from another R External ID institution outside office etc the identifier used by that institution can be shown in this field This may bea number that multiple disparate corporations or facilities share PID 03 Patient ID CX 20 The primary identifier or other O Inter
89. Name Type Length Comments Supported PID 00 Segment ST 4 Must be PID A Type ID PID 01 Set ID SI 4 Allows identification of multiple C PID segments within a message Usually a sequential number beginning with 1 PID 02 Patient ID CX 20 The same value that was included C External ID in the inbound order If data is available in the inbound order message the same data is passed through to the result message PID 03 Patient ID CX 16 The unique identifier for A Internal ID example accession number assigned by the Sending Facility for this request PID 04 Alternate CX 20 The Lab reference number Same PT Patient ID as ORC 02 and OBR 02 PID 05 Patient Name XPN 24 Must be no more than 24 A characters wide including the delimiter between the last and first names Anything above 24 characters is truncated at the LIS Care360 Result Message Segment Specifications 105 106 Segment ID Element Name Type Length Comments Supported PID 06 Mother s XPN 48 N Maiden Name PID 07 Date of Birth TS 26 Date of birth DOB in C YYYYMMDD format Conditional based on availability of information may return age rather than DOB PID 08 Sex IS 1 Valid values for this field include A e M Male e F Female PID 09 Patient Alias XPN 48 N PID 10 Race IS 1 N PID 11 Patient Address XAD 106 N PID 12 County Code IS 4 N PID 13 Phone Number
90. Note For details of the Patient Demographic Services see Chapter 8 Patient Demographic Services API Reference on page 167 Real Time vs Batch Processing Patient demographic update messages can either be submitted individually as real time updates or batched together as a group of related updates Real time updates can be used for submitting individual patient demographic updates as they occur Batch updates can be used for normal patient updates and they can also be used to process the initial patient demographic data load between a partner application and Physician Portal All updates whether real time or batch are processed in the order in which they are received by Physician Portal In order to distinguish real time and batch updates each type is submitted separately to Care360 Hub Information Services via the Patient Demographic Services Chapter 5 Linking to Physician Portal PID Only vs Fuzzy Matching There are two methods available for processing patient demographic merge requests The partner must specify their preferred method during the initial integration process with Physician Portal The two methods include the following e PID Only Matching This method relies solely on the ability of the partner application to identify a patient using a unique patient identifier PID When using this method the information provided by the partner application is always considered the most accurate that is it overrides an
91. O on page 131 A partner application that is linked to Physician Portal can also take advantage of a number of related services including the following e User Summary services e Order echo e Patient demographic services Inbound and Outbound e Physician Portal UI customization Each of these services is described in more detail later in this chapter Note A partner application must allow users to view Physician Portal in its native resolution 1024x768 displaying all existing menus headers and other navigation elements In most cases Physician Portal will appear in a new browser window otherwise the partner application must display in a higher resolution so that Physician Portal can appear in a separate frame within the application Physician Portal Functions Available for Linking A partner application can link directly to the following Physician Portal functions also referred to as the landing page e New Results The EMR user can directly access Physician Portal s New Results page to view the latest test results that have been received for all of their patients Results can be viewed or printed and can be forwarded to other Physician Portal users via user messaging or fax e Lab Orders The EMR user can directly access Physician Portal s Lab Orders page to create an electronic lab order for submission to either a Quest Diagnostics BU or a third party laboratory for processing The link to Lab Orders can occur in on
92. O UserSummary Services The ability to view Physician Portal lab result and user message counts from within the linked application O Order Echo The ability to receive copies of orders placed using Physician Portal within the linked application o Patient Demographic Updates The ability for the linked application to submit patient add update delete and merge messages to the Physician Portal patient database via Care360 Hub Information Services O Physician Portal User Interface UI Customization The ability to customize certain elements of the Physician Portal user interface to more closely resemble partner applications or product branding For an overview of Care360 Integration Services see Chapter 1 Universal Ordering and Resulting on page 3 Disclaimers This Programmer Reference provides specifications necessary for exchanging laboratory data between a third party Service Provider laboratory or EMR application and the various components of Care360 Integration Services It does not however provide documentation on creating or updating an application to produce data files that conform to these specifications All sample code referenced in this Programmer Reference is provided for example purposes only and it may need to be modified to work in your environment Itis provided as is without warranty of any kind or support from MedPlus Inc What s New in This Release Care360 Integration Services 2 0 provides the f
93. OLOGY 18700 OXNARD STREET TARZANA CA 91356 20030731192600 EL LL LT TL IT 11 ELLE I OBX 1 TX 60000000 CYTOPATHOLOGY NUMBER 60000000 CYTOPATHOLOGY NUMBER 1 11 1 F 20030731192600 UIP L NTE 1 ZP03030749 OBX 2 ST 60000100 SOURCE 60000100 SOURCE VAGINAL F 12003073119 2600 UIP L OBX 3 TX 60000200 SPECIMEN ADEQUACY 60000200 SPECIMEN ADEQUACY 1 111 1FI 120030731192600 UIP L NTE 1 SATISFACTORY FOR EVALUATION NTE ENDOCERVICAL TRANSFORMATION ZONE NTE COMPONENT ABSENT NTE OBX TX 60000300 GENERAL CATEGORY 60000300 GENERAL CATEGORY 11 111I1IEIII 20030731192600 UIP L l NTE 1 NEGATIVE FOR INTRAEPITHELIAL LESION NTE 2 OR MALIGNANCY OBX 5 TX 60000400 NARRATIVE DESCRIPTION 60000400 NARRATIVE DESCRIPTION II 11IFI1120030731192600 UIP L NTE 1 NEGATIVE FOR INTRAEPITHELIAL LESION NTE 2 OR MALIGNANCY OBX 6 ST 60000500 ADDITIONAL FINDINGS 60000500 ADDITIONAL FINDINGS DNR 1 1X 20030731192600 UIP L OBX 7 ST 60001100 COMMENTS 60001100 COMMENTS DNRI 11 X 12003073119 2600 UIP L OBX 8 ST 60001200 RECOMMENDATIONS 60001200 RECOMMENDATIONS DNR 1 X 20030731192600 UIP L OBX 9 ST 60001300 CYTOTECHNOLOGIST 60001300 CYTOTECHNOLOGIST CTUAYY EI F 20030731192600 UIP L OBX 10 ST 60001400 REV CYTOTECHNOLOGIST 60001400 REV CY
94. Optional O Conditional C or Not Supported NS as defined below Required If the corresponding segment is present the field must also be present within the segment and the Hub validates it against any stated requirements If the field is not present the message is rejected by the Hub e Optional The field is not required the segment is accepted by the Hub whether or not this field is present If the field is present the Hub validates it against any stated requirements Conditional The field may or may not be required depending on certain conditions stipulated in the Comments column of each segment table If the stated conditions are not met the message is rejected by the Hub If the field is present the Hub validates it against any stated requirements e Not Supported If a field is described as Not Supported by the Hub the corresponding row appears grayed in the table the content of the field is not used by the Hub but it is validated for field type and length as well as conformance to the specified HL7 table or user defined table as applicable If all fields are successfully validated the content is passed through otherwise the message is rejected by the Hub Care360 Patient Demographic Message Format Requirements 175 176 Data Type Specifications The following table describes the data types that may appear in the message segments Note Brackets indicate that the enclosed data is optio
95. P2752 1 Celiac Panel 935F l 935F P6581 1 7017X 7039W 1 4580 E 7039W 2 BASO STIPPLING Genital Female Qu Il Xu EX CS LED LEO gt gt gt gt gt gt Ei m E m B m B m B m E m E Fr E m E m Be Lak m E m E m E m E m B R B F n B E Fr E m B m Ei Dp E m E m n Fr E Fr E m E Fr E Fr E Chapter 2 Care360 Master File Specification Sample Three Setup Days A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT A QT i i e e x a e a ri A E A E m a A S as Aa x m ee e m Aa i T eS es i ci n i P 7 z A A QT Ej pd Ed Ed Ed EH Dd EH D bd EB DH pd o tH DH op td Do p p E gt E l10 1 Wee E 12 1 Wee E l4 1 Wee E l16 1 Wee E 17 1 Tue E 50 1 Wee E 51 1 Wee E 52 1 Wee E 53 1 Wee E 61 1 Wee E 62 1 Wee E 64 1 Wee E 72 1 Wee E 73 1 Wee E 99 1 Wee E 145 1 We E 187 1 Mo E 199 1 We E 239 1 We E 282 1 We
96. PAction Cookie JSESSIONID F2sq7JLqOsl19hkGfOflv7qghlw2LrLgJT5NBz4HLYlYZybgPJr2 y4 987964007 securityCheckUri Care360SSOSecurityCheck IsSSOClient true sso lastKnownSessionId F2sq7JLqOsl19hkGfOfl1v7qhlw2 LrLgJT5NBz4HLYlYZybgPJr2y4 987964007 1174318122760 SOAP ENV Envelope lt SOAP ENV Body lt nsl getOrgs SOAP ENV encodingStyle http schemas xmlsoap org soap encoding ns1 getOrgs SOAP ENV Body lt SOAP ENV Envelope gt RESPONSE HTTP 1 1 200 OK Date Mon 19 Mar 2007 16 24 18 GMT Content Length 938 Content Type text xml charset UTF 8 Connection Keep Alive lt xml version 1 0 encoding UTF 8 gt lt env Envelope xmlns env http schemas xmlsoap org soap envelope xmlns soapenc http schemas xmlsoap org soap encoding xmlns xsd http www w3 org 2001 XMLSchema mins xsi http www w3 org 2001 XMLSchema instance gt lt env Body env encodingStyle http schemas xmlsoap org soap encoding lt m getOrgsResponse xmlns m http www care360 com services gt result xmlns nl jJava com medplus care360 ws org model xsi type n1l WSOrgData gt maxOrgs xsi type xsd long gt 6 lt maxOrgs gt lt orgList soapenc arrayType nl WSOrg 5 gt Chapter 6 Physician Portal SSO Specification lt lt lt WSOrg xsi type nl WSOrg gt lt orgName xsi type xsd string gt AUTO LNR US04 lt orgName gt XorgUI
97. Physician Portal SSO can call back to redeem an SAML artifact This must be a secure SSL accessible endpoint on your system and may require special firewall configuration which would be examined as part of the security assessment Note If you are using the recommended SAML Browser POST profile this component is not necessary Establishing Organizational Trust 151 152 Implementing SAML Your SAML implementation must employ the digital certificate and SAML identifiers shared and configured as outlined in the previous sections of this chapter This section outlines the general steps required to authenticate successfully to Physician Portal via SAML Sample implementations are provided later in this guide to illustrate how these steps are facilitated on various platforms and in various usage scenarios for example a Web service vs a user s browser These instructions are based upon the SAML Browser POST profile model The following general actions must occur in order to authenticate a partner application user to Physician Portal using SAML 1 1 L The user is authenticated in the partner application Before accessing a link to a Physician Portal feature using SSO the user must authenticate to the partner application environment The means used to authenticate must be that which was previously approved during the security assessment C The user selects a linked Physician Portal feature The user takes some action for example clic
98. R IMPLIED INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT MEDPLUS INC DOES NOT WARRANT THE ACCURACY OR COMPLETENESS OF THE INFORMATION TEXT GRAPHICS OR OTHER ITEMS CONTAINED WITHIN THESE MATERIALS IN NO EVENT SHALL MEDPLUS INC AND ORITS SUPPLIERS BE LIABLE FOR ANY SPECIAL INDIRECT INCIDENTAL OR CONSEQUENTIAL DAMAGES INCLUDING WITHOUT LIMITATION LOSS OF USE DATA OR PROFITS WHICH MAY ARISE OUT OF OR IN CONNECTION WITH THE USE OF THESE MATERIALS THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS THE INFORMATION CONTAINED IN THIS DOCUMENT IS PERIODICALLY CHANGED WITHOUT NOTICE MEDPLUS INC MAY MAKE IMPROVEMENTS AND OR CHANGES IN THE PRODUCT S AND OR THE SOFTWARE DESCRIBED IN THIS DOCUMENT AT ANY TIME RESTRICTED RIGHTS LEGEND All MedPlus products and publications are commercial in nature Use duplication or disclosure by the U S Government is subject to restrictions of FAR 52 227 14 and FAR 52 227 19 or DFAR 252 227 7015 and DFAR 227 7202 3 Any rights not expressly granted herein are reserved Table of Contents About This Manual sse HH HH ix Introduction 6646 45 85 er Ra o XU ea rre ac GR SUR C9 cR e dS SAGAR ESE Y x Disclaimers c sco dem yes era ovp dui tadruc a Sod unido ee ee Ee LLORES x Whats New in This Release 5 22 d e EEG e erEY E Edu Rea Medes ea eae xi Documentation Conventions i a rimar
99. Select Test Indicator SELECTEST IND R char 1 Valid values Y Meets Select Test requirements N U Unknown 13 Billing performing NBS PERFORMING SITE O char 4 Where the test is site performed Must match dataset 23 field 3 14 Special test flag TEST_FLAG O char 1 Valid values P if test is a PAP Q if test has AOE null 15 No bill indicator NO_BILL_INDICATOR O char 1 Valid values Y This code is not billed N Null 16 Bill only indicator BILL ONLY INDICATOR O char 1 Valid values Y This code billed but is nota test N Null 17 Send out reflex SEND_OUT_REFLEX_COUNT R int count 18 Conforming CONFORMING_IND R char 1 Valid values Y N indicator U Unknown Dataset File Details 29 30 TEST CODE UNIT CODE XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes 19 Selectable conditions SELECTABLE CONDITIONS O char 20 Comma delimited list of acceptable conditions If present the ordering user will be allowed to select from these multiple conditions prior to batching or requisition splitting instead of the single entry in field 10 Only one single character temperature is allowed Current codes in use are e R Refrigerated e F Frozen e A Ambient room temp e S Special e W Wet ice a R Requi
100. Services API Reference 161 About the User Summary Services API Reference eee 162 User Summniaty Services APL 5e khe xm 9 tates doro VIRO wd a dares 163 User Summary Methods q i sese mos 20840 Rete Ah em a mba ae S 163 User Summary ODIeCtS 5i epscteecrert9pbqacG ep Oe die 4 on AR I DISSE das 164 Chapter 8 Patient Demographic Services API Reference 167 About the Patient Demographic Services API Reference eese 168 Patient Demographic Services API leeeeeeeeeeeeeee en 169 Patient Demographic Methods 2 2 slcreplcceR aca Mes Xy AEE SES As 169 Parent Demographic ODIects vanor vete RITU ts RGows TED RPITQeeRRPRESS 170 About the WSDL Interface Document 1 1 6 cee cece eee 172 Accessing the Patient Demographic Services WSDL Document 172 Chapter 9 Care360 Patient Demographic HL7 Specification 173 About the Care360 Patient Demographic HL7 Specification 174 Care360 Patient Demographic Message Format Requirements 175 Newline Characters i ebore rex Ge ihe RawESUP EIER E AXE wees 175 Field Delimitets 244222 Rhe rdc Ron a neqne hed ade 175 Field Specifications ied speESORERERERG Gd Ais Whee FARE EE d iddar 175 Data Type Specification ear coco epe rh eer RU RET eo nrnieroowaeecous 176 Table of Contents vii viii Table of Contents ADT A28 Patient Add Message Segment Specifications
101. Status PID 28 Nationality CD 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 NS Indicator a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PV1 Patient Visit Data Segment The Patient Visit Data PV1 segment is used by registration patient administration applications to communicate information on a visit specific basis This segment can be used to send multiple visit statistic records to the same patient account or single visit records to more than one account Segment ID Element Name Type Length Comments Req d PV1 00 Segment Type ID ST 4 Must be PV1 R PV1 01 Set ID SI 4 Will always be 1 O PV1 02 Patient Class IS 1 Examples of valid values R E Emergency I Inpatient O Outpatient 210 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 03 Assigned Patient PL 80 NS Location PV1 04 Admission Type IS 2 NS PV1 05 Preadmit CX 20 NS Number PV1 06 Prior Patient PL 80 NS Location PV1 07 Attending XCN 60 NS Doctor PV1 08 Referring Doctor XCN 60 NS PV1 09 Consulting XCN 60 NS Doctor PV1 10 Hospital Service IS 3 NS PV1 11 Temporary PL 80 NS Location PV1 12 Pread
102. Supported ORC 00 Segment Type ID ST 4 Must be ORC A ORC 01 Order Control ID 2 Valid value for this field is RE A Results ORC 02 Placer Order EI 20 Always contains the placer PT Number application s order number Should be the same as OBR 02 This value is passed through from the inbound order to the LIS to the result ORC 03 Filler Order EI 22 The order number associated A Number with the filler s application The same as OBR 03 The lab accession number populated by the LIS after receipt of the order ORC 04 Placer Group EI 22 N Number ORC 05 Order Status ID 2 Indicates whether the result is A partial or final Valid values for this field include CM Order complete IP Order incomplete or contains pending items ORC 06 Response Flag ID 1 N Care360 Result Message Segment Specifications 107 108 Segment ID Element Name Type Length Comments Supported ORC 07 Quantity Timin TQ 200 N 8 ORC 08 Parent CM 200 N ORC 09 Date Time of TS 26 N Transaction ORC 10 Entered By XCN 120 N ORC 11 Verify By XCN 120 N Chapter 4 Care360 Results HL7 Specification Segment ID Element Name Type Length Comments Supported ORC 12 Ordering Provider XCN 120 Identifies the provider that ordered the test If presentin the inbound order the result echoes this value Version 2 3 e Format for UPIN Only UPIN Number LastName Firs
103. TE segment contains notes and comments for ORU messages and is optional Segment ID Element Name Type Length Comments Supported NTE 00 Segment ST 4 Must be NTE A Type ID NTE 01 Set ID SI 4 May be used to group multiple C NTE segments in a message NTE 02 Source of ID 2 This field is conditional C Comment NTE 03 Comment ST 72 Each new line is sent in a new A NTE segment Blank lines and leading spaces are retained for correct data representation a For a description of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never Care360 Result Message Segment Specifications 119 Sample Care360 Result Messages Following are several sample Observational Report Unsolicited ORU messages formatted according to the Care360 Result Message Format Requirements on page 99 and Care360 Result Message Segment Specifications on page 103 Sample 1 Result Message MSH N amp LAB DAL HUBARTEST 20030802230021 ORU R01 20040908144133784500 PI2 311 11 114 PID 1 808 WD376535M 9646179 DOE JANIS 19510924 F I 111 555667777 EN Ll NTE 1 TX THINPREP ORC RE 9646179 WD376535M CM C91458 Novak James OBR 1 9646179 WD376535M 35455YUIP CYTOLOGY THINPREP PAP 35455YUIP CYTOLOGY THINPREP PAP 20030730101400 11 111120030730105500 JAP UIP UNILAB INSTITUTE OF PATH
104. TOTECHNOLOGIST DNR 1X11120030731192600 UIP L OBX 11 ST 60001500 PATHOLOGIST 60001500 PATHOLOGIST DNR IXI 11200 30731192600 UIP L OBX 12 ST 60001600 PERFORMING SITE 60001600 PERFORMING A AUN SITE DNR IX 120030731192600 UIP L OBX 13 TX 10000043 10000043 I II11IFI1I20030731192600 UIP L lI NTE 1 GYNECOLOGICAL CYTOLOGY IS A SCREENING PROCEDURE NTE 2 SUBJECT TO BOTH FALSE NEGATIVE AND FALSE POSITIVE NTE 3 RESULTS IT IS MOST RELIABLE WHEN A SATISFACTORY NTE 4 SAMPLE IS OBTAINED ON A REGULAR REPETITIVE BASIS 120 Chapter 4 Care360 Results HL7 Specification NTE 5 RESULTS MUST BE INTERPRETED IN THE CONTEXT OF NTE 6 HISTORIC AND CURRENT CLINICAL INFORMATION Sample 2 Result Message MSH amp LAB TMP 98015 20030603151327 ORU R01 20030603692073360000 P 2 3I I PID 1 TP362228T TEST JACK M LLL ELE FL 1 T d LILL ORC RE 3812197 TP362228T CM C91458 Doe James I OBR 1 3812197 TP362228T 10165SB BASIC METABOLIC PANEL
105. Test is a PAP Q Test has AOE Null a R Required O Optional C Conditional File Name PROFILE TXT Dataset 9 Order Code Component Description Usage Identifies components of order codes that are profiles There is one entry per profile component Required This dataset is optional recommended for third party laboratory implementations Conditions Each order code must have a parent entry in the Order code dataset Note Components do not need to be orderable therefore they do not need to be in the Order code dataset PROFILE_COMPONENT_XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 3 Performing site TOPLAB_PERFORMING_SITE PK1 R char 3 4 Order code TEST_CD PKI R char 16 5 Unit code UNIT_CD R char 10 LIS code 6 Order code suffix SUFFIX O char 8 7 Component COMPONENT_TEST_CD PK1 R char 16 8 Component unit COMPONENT_UNIT_CD PKI R char 10 code Dataset File Details 31 32 PROFILE COMPONENT XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes 9 Component suffix COMPONENT SUFFIX O char 8 10 Component title COMPONENT_DESCRIPTION C char 175 Required except for TOPLab which sends this info separately in a repo
106. User Summary Services API refer to User Summary Services API on page 163 An authorized user name and password are required for accessing this Web service For More Information For information about accessing the Web Services Definition Language WSDL documents for Physician Portal see About the WSDL Interface Documents on page 237 Chapter 7 User Summary Services API Reference User Summary Services API This section provides details on the methods and objects provided by each service within the User Summary Services API User Summary Services enables a partner application to receive notification of the availability of user messages and new results within Physician Portal User Summary Methods Following is a brief overview of each method provided by the User Summary Services Web service Usage details for each method are provided in the following section User Summary Method Details e getCounts Retrieves user summary data from Physician Portal for all organizations with which the current partner application user is associated up to the maximum number of organizations allowed getCountsByOrg Retrieves user summary data from Physician Portal for one or more specific organization s with which the current partner application user is associated e getOrgs Retrieves a list of organizations with which the partner application user is associated User Summary Method Details The following table provides d
107. V1 45 Discharge TS 26 NS Date Time PV1 46 Current Patient NM 12 NS Balance PV1 47 Total Charges NM 12 NS Segment ID Element Name Type Length Comments Req d PV1 48 Total NM 12 NS Adjustments PV1 49 Total Payments NM 12 NS PV1 50 Alternate Visit ID CX 20 NS PVI 51 Visit Indicator IS 1 NS PV1 52 Other XCN 60 NS Healthcare Provider a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported GT1 Guarantor Segment The Guarantor GT1 segment contains guarantor for example the person or the organization with financial responsibility for payment of a patient account data for patient and insurance billing applications This segment is applicable only for patient and insurance billing Segment ID Element Name Type Length Comments Req d GT1 00 Segment ST 4 Must be GTI R Type ID GT1 01 Set ID SI 4 GTI message segments should be R numbered sequentially from 1 GT1 02 Guarantor CX 59 NS Number GT1 03 Guarantor XPN 48 No more than 48 characters wide R Name including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alph
108. WSDL interface document describes all of the information that is needed by a Web service client to interact with the associated Web service The WSDL document includes the URL to locate the associated Web services Once you have located the Web service or after you have obtained the WSDL you can build a Web service client application that uses the Web service to perform the desired functions The following section describes the process for obtaining the WSDL documents for Patient Demographic Web services Note You must have a valid user name and password issued by MedPlus in order to access the WSDL interface documents For the Production Hub environment a user name and password will be issued once your application has been developed tested and certified Accessing the Patient Demographic Services WSDL Document To access the WSDL service description for the Patient Demographic Services use your browser to access the corresponding URL shown below Using the WSDL that you obtain you can build a client application to access the Web service Staging Environment To access the Patient Demographic Services in the Staging Hub environment used to develop test and certify your Web service application access the following link https cert hub care360 com demographic service wsdl Production Environment Once you have developed tested and certified your Web service client application in the MedPlus Staging Hub environment you can the
109. _UPDATES NS Updates a R Required O Optional C Conditional NS Not Supported Chapter 2 Care360 Master File Specification Master File Dataset File Specifications Master Files are a current collection of all reference data needed to create a complete and valid electronic order for a third party laboratory system via the Lab Orders component of Physician Portal This section summarizes the format and contents of the reference data that can be retrieved from the Hub for use in the vendor application Dataset files retrieved from the Master Files are caret delimited text files Each file must be formatted according to the specifications described below Dataset Format Specifications Incoming Master File dataset files must conform to the following conventions e Datasets must be provided as ASCII text files e Individual dataset files cannot exceed the maximum file size of 100 MB e Files must be named according to the following convention all lowercase dataset code date time lab identifier where O dataset code is the two digit code specified in the Dataset File List on page 15 o date is the file creation date in yyyymmdd format o time is the file creation time in hhmmss format O lab identifier isthe lab identifier provided by MedPlus File name example oc 20001022 181520 abc In this example the file is for the Order Code dataset oc the unique dataset f
110. a types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported PID Patient Identifier Segment The Patient Identifier PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID O segments within a message Usually a sequential number beginning with 1 PID 02 Patient ID CX 20 The placer s patient ID assigned to this R External ID order If present the Hub verifies that this field is at a maximum 20 characters wide The Hub also verifies that no reserved characters amp are present PID 03 Patient ID CX 20 NS Internal ID PID 04 Alternate CX 20 NS Patient ID Care360 Order Message Segment Specifications 69 70 Segment ID Element Name Type Length Comments Req d PID 05 Patient Name XPN 24 Must be no more than 24 characters R wide excluding any delimiters for example between last and first name Must include at least one character for first and last name A numeric value cannot be used as the first character of th
111. ab per order Billing Third Party Lab Order System Order Copy to Billing System as needed Care360 Hub Information Hospital Lab Services Hub Database Copy of Order Copy of Results Copy of Master Files Physician Lab Hub Returns Third gt Lab Submits Third Independent Party Lab Results Party Results Lab EMR Retrieves and i Lab Submits Applies CDC Files Master Files About the Universal Ordering and Resulting Data Flow Updating Master Files The following steps outline the procedure and associated systems involved in updating the Master File data used by Lab Orders when placing an order to a third party laboratory C The third party laboratory copies updated Master Files to its file system Note Master Files submitted to the Hub must be formatted according to the specifications detailed in Chapter 2 Care360 Master File Specification on page 13 L The Hub retrieves the Master Files from the laboratory file system and verifies the file names of the Master Files L The Hub records the Master Files transaction and stores a copy of the Master Files for a minimum of 90 days or longer as specified by the laboratory L The Hub copies the Master Files to the Lab Orders component of Physician Portal and Lab Orders stores a copy of the Master Files to its file system Ll Lab Orders converts the Master Files to the Quest Diagnostics interna
112. age Provides a cross reference between the Dataset 7 Order Code and the Dataset 24 Analyte Details Required This dataset is not supported for third party laboratory implementations Conditions None WORKLIST_COMPONENT_XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PK1 R char 4 Your performing site code 3 Test Code TEST CD PKI R char 16 4 Analyte Code ANALYTE_CD PKI R char 11 Must match dataset 24 field 3 5 Unit Code UNIT_CD R char 10 LIS code a R Required O Optional C Conditional Dataset 27 Order Code Alias File Name ALIAS TXT Description Usage Provides various alias name by which an order code is recognized by clients If not provided order codes will only be searchable by the Title field provided in Dataset 7 Order Code Required This dataset is optional for third party laboratory implementations Conditions None UNIT_CODE_ALIAS Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PK1 R char 3 Your performing site code Dataset File Details 43 UNIT CODE ALIAS Column Name CDC Column Name Key Req d Type
113. al Committee Service Scope The account based scope defined by a request for lab results Specifically this scope definition provides the EMR vendor the capability of receiving results for every registered care site account associated with a specific Hub ID or alternatively receiving results for specific accounts as defined by their account IDs Single Sign On SSO The practice of facilitating user login to a single site or application and then allowing that same user access to another site or application without requiring the user to enter a second set of user credentials User ID and Password SOAP An XML based protocol for exchanging information in a decentralized distributed environment It provides an envelope that defines a framework for describing what is in a message and how to process it encoding rules for expressing application defined datatypes and a convention for representing remote procedure calls and responses Subscriber An individual who is a member of a benefits plan For example in the case of family coverage one adult is ordinarily the subscriber A spouse and children would ordinarily be dependents Time Scope The time based scope defined by a request for lab results Specifically this scope definition allows the EMR vendor to receive the latest previously unretrieved results or alternatively to receive results ordered within a specific time frame Technology Provider A healthcare technolog
114. am is a step by step walkthrough of the order echo process illustrated in the diagram Receiving Echoed Lab Order Client Lab Hub Infrastructure EMRs Third Party Labs _ Hub Receives Hub Submits Order to Third Party Lab Order Third Party Lab Physician Office See Tm System Hub Echoes Third Party Lab Order Order Copy to Billing System alee as needed Physician Portal Care360 Hospital Lab Hub Information Services Lab Orders Hub Database Physician Lab Copy of Order Partner Application Independent Lab 138 Chapter 5 Linking to Physician Portal The following steps outline the procedure and associated systems involved in placing an order and having the order echoed back to the partner application d d C A user logs in to the partner application The partner application user initiates a link to the Lab Orders function of Physician Portal L When linking to Lab Orders the current patient context may be maintained if an appropriate match can be determined based on the supplied PID The user creates and submits a lab order At a predefined time interval the Hub retrieves the order from Physician Portal The Hub records the order transaction and stores a copy of the discrete content of the order The Hub echoes returns a copy of the order back to the partner application About Order Echo 139
115. ame 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above PID 06 Mother s Maiden Name XPN 48 NS PID 07 Date Time of Birth TS 26 Date of birth DOB in YYYYMMDDHHMMSS format The Hub verifies that the DOB is in this format PID 08 Sex IS Valid values for this field include e M Male e F Female The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 Patient alias name PID 10 Race IS NS PID 11 Patient Address 106 No more than 106 characters wide Addl 50 add2 50 city 50 state 2 zp 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above ADT A39 Patient Merge Message Segment Specifications 225 226 Segment ID Element Name Type Length Comments Req d PID 12 County Code IS 4 NS PID 13 Phone Number XTN 40 Accepted length of this field is 40 O Home numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt area city code NM phone number NM gt extension NM gt PID 14 PhoneNumber
116. an 106 characters wide O Company Add1 50 add2 50 city 50 state 2 zip Address 10 country code 3 Alphanumeric data only If populated the Hub ignores this field IN1 06 Insurance Co XPN 48 NS Contact Person IN1 07 Insurance Co XTN 40 NS Phone Number IN1 08 Group Number ST 50 Characters permitted include O A Z and 1 0 If present the Hub verifies that the value complies with rules above IN1 09 Group Name XON 130 O IN1 10 Insured s Group CX 12 NS Emp ID IN1 11 Insured s Group XON 130 NS Emp Name IN1 12 Plan Effective DT 8 NS Date INI 13 Plan Expiration DT 8 NS Date Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d IN1 14 Authorization CM 55 NS Information IN1 15 Plan Type IS 3 NS IN1 16 Name Of XPN 48 NS Insured IN1 17 Insured s IS 2 NS Relationship To Patient IN1 18 Insured s Date TS 26 NS Of Birth IN1 19 Insured s XAD 106 NS Address IN1 20 Assignment Of IS 2 NS Benefits IN1 21 Coordination Of IS 2 NS Benefits IN1 22 Coord Of Ben ST 2 NS Priority IN1 23 Notice Of ID 2 NS Admission Flag IN1 24 Notice Of DT 8 NS Admission Date IN1 25 Report Of ID 2 NS Eligibility Flag IN1 26 Report Of DT 8 NS Eligibility Date IN1 27 Release IS 2 NS Information Code IN1 28 Pre Admit Cert ST 15 NS PAC IN1 29 Verification TS 26 NS Date Time IN1 3
117. an ADT A29 Patient Delete HL7 message The purpose of this message type is to enable a partner application to delete an existing patient via the Hub from Physician Portal This can be used for example to correct an error in adding the information to delete a duplicate patient record or to purge the patient from Physician Portal Note You cannot delete a patient from Physician Portal after clinical entries for example lab results have been associated with that patient or if the patientis associated with an alias patient If a delete cannot be performed due to either of these conditions an error message is returned Message Segment Hierarchy An ADT A29 message must follow the message segment hierarchy as specified below MSH EVN PID PD1 PV1 PV2 DB1 OBX Message Header Required one per file Event Type Required Patient Identification Required Additional Demographics Optional not supported by the Hub Patient Visit Data Required Patient Visit Additional Info Optional not supported by the Hub Disability Information Optional not supported by the Hub Observation Result Optional not supported by the Hub In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional Message Segment Specifications This section provides detailed specifications for each segment of an ADT A29 Patient Delete message Message segmen
118. anumeric data only The Hub verifies that the value complies with rules above GT1 04 Guarantor XPN 48 NS Spouse Name ADT A31 Patient Update Message Segment Specifications 213 214 Segment ID Element Name Type Length Comments Req d GT1 05 Guarantor Address 106 No more than 106 characters wide Add1 50 add2 50 city 50 state 2 zip 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above GT1 06 Guarantor Ph Num Home XTN 40 Accepted length of this field is 40 numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM lt area city code NM phone number NM gt extension NM GT1 07 Guarantor Ph Num Business XTN 40 Accepted length of this field is 40 numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM lt area city code NM phone number NM gt extension NM GT1 08 Guarantor Date Time Of Birth TS 26 The date and time of the guarantor s birth Format YY YYMMDDHHMMSS The Hub verifies that the date time is in this format GT1 09 Guarantor Sex IS Val
119. ation Services Administration to enable an authorized external system for example EMR vendor to interact with Care360 Hub Information Services Hub ID A unique identifier assigned by Quest Diagnostics to each EMR system that is registered to receive lab results on behalf of a Quest Diagnostics account This is the identifier given to EMR vendors such as Web based EMRs that retrieve results for several accounts as well as standalone EMRs that retrieve results for a single account See also Account ID Interface The code written and the specifications and protocols used for the electronic data exchange between RxHub and SureScripts and the participants and or vendors computing environments Logical Observation Identifiers Names and Codes LOINC An industry database that is used to facilitate the exchange of pooling results for clinical care outcomes management and research LOINC codes are universal identifiers for laboratory and other clinical observations Management Information System MIS The common term for the computer hardware and software that provides the support of managing the plan Master Files Files containing a current collection of all reference data needed to create a complete and valid electronic order for a specific laboratory either a Quest Diagnostics laboratory or a third party laboratory Master files are converted to the Quest Diagnostics CDC format for use within the Lab Orders component of Ph
120. atory may also optionally include result discrete data The XML file created by the laboratory for each result must conform to the following format lt xml version 1 0 encoding UTF 8 gt lt schema targetNamespace http hub care360 com 5 0 result xmlns tns http hub care360 com 5 0 result xmlns http www w3 org 2001 XMLSchema gt lt element name result gt lt complexType gt lt sequence gt lt element name resultDate type string nillable true gt lt element name sendingFacility type string nillable true gt lt element name receivingFacility type string nillable true gt lt element name accessionNumber type string nillable true gt lt element name messageControllId type string nillable true gt Receiving Third Party Laboratory Results Files 123 124 lt element name h17 type base64Binary gt lt element name primaryReport type base64Binary nillable true element name additionalReports lt complexType gt lt sequence gt lt element name report type base64Binary nillable true minOccurs 0 maxOccurs unbounded gt lt sequence gt lt complexType gt lt element gt lt sequence gt lt complexType gt lt element gt lt schema gt All discrete fields are optional where sendingFacility is the provider and receivingFacility is the provider account as defined in the Hub These discrete fields are opt
121. bability NM OBX 10 Nature of Abnormal Test ID OBX 11 Observ Result Status ID Valid values include Version 2 3 e F Final e P Preliminary C Correction to a previously reported final result e X Result cannot be obtained Typical values for this field include Version 2 3 1 e P Preliminary results I Pending results Other data supported C Correction to results e F Final results e X Test canceled Data also passed in OBR 25 OBX 12 Date Last Obs Normal Values TS 26 OBX 13 User Defined Access Checks ST 20 OBX 14 Date Time of the Observation TS 26 The date and time that the observation was reported Format YYYYMMDDHHMMS S Seconds are always 00 Chapter 4 Care360 Results HL7 Specification Type Segment ID Element Name Length Comments Supported OBX 15 Producer s ID CE 60 The unique identifier of the C responsible filler Version 2 3 Format AT L Version 2 3 1 Format AT Only sub piece one will be passed Note This is the same identifier found in OBR 21 sub field 1 OBX 16 Responsible XCN 80 N Observer OBX 17 Observation Method CE 60 N a For a description of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never NTE Notes and Comments Segment The Notes and Comments N
122. ble Markup Language has become the standard for defining data interchange formats on the internet It is similar to HyperText Markup Language HTML in that it uses tags to encode information But whereas HTML tells browsers how to display information XML defines values for the information XML also lets users create their own tags XML Parser A software application that processes an XML document An XML parser reads the XML document checks its syntax reports any errors and allows programmatic access to the document s contents An XML document is considered well formed if it is syntactically correct meaning no errors are reported by the parser when the document is processed Glossary 243 Index A Abbreviations and acronyms xiii Account see also Hub account Account ID definition 239 Add patient sample patient demographic message 231 Admission Discharge Transfer ADT definition 239 ADT A28 Patient Add message specifications 179 194 ADT A29 Patient Delete message specifications 195 208 ADT A31 Patient Update message specifications 204 220 ADT A39 Patient Merge message specifications 221 230 Alternate Specimen Data dataset Master Files 46 Always definition 100 Ambulatory Care definition 239 Analyte Details dataset Master Files 42 API application programming interface overview 162 168 Patient Demographic Services 169 171 User Summary Services 163 166 Application sample EMR 236 Batch mode patient
123. bmitted via Care360 Hub Information Services to a Quest Diagnostics or third party laboratory for processing Orders must be formatted according to the HL7 2 3 Specification with any exceptions noted in this chapter Supported messages for orders produced by Physician Portal include ORM O01 General Order Message This chapter includes the following sections Order message format requirements For information on the message format requirements see Care360 Order Message Format Requirements on page 59 Order message segment specifications Each order message submitted to the Hub must contain a number of standard sections For requirements on the standard segments of an order message see Care360 Order Message Segment Specifications on page 67 e Sample Order messages For samples of the various order message types see Sample Care360 Order Messages on page 94 Note For a detailed specification of Quest Diagnostics or third party lab results that are received by Care360 Hub Information Services see Chapter 4 Care360 Results HL7 Specification on page 97 Chapter 3 Care360 Order HL7 Specification Care360 Order Message Format Requirements In addition to the field level validation detailed in Care360 Order Message Segment Specifications each inbound ORM message is validated by the Hub to ensure compliance with the rules outlined in this section Message Segment Hierarchy ORM messages must follow the message se
124. cceptable values for this field ORM 00 1 order messages The Hub verifies that the field is populated with the accepted value ORM 001 MSH 10 Message Control ID ST 20 A number or other data that uniquely identifies the message in its transmission to the lab system If not provided the Hub populates with a unique identifier date time stamp followed by a 4 digit random number MSH 11 Processing ID PT The placer system s intent for the message Valid values include e P Production e T Training e D Debug Development The Hub verifies that the value in this field is P T or D MSH 12 Version ID ID The value for this field is 2 3 MSH 13 Sequence Number NM 15 NS MSH 14 Continuation Pointer ST 180 NS Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d MSH 15 Accept ID 2 For valid values refer to HL7 table NS Acknowledgment 0155 Accept application Type acknowledgment conditions MSH 16 Application ID 2 For valid values refer to HL7 table NS Acknowledgment 0155 Accept application Type acknowledgment conditions MSH 17 Country Code ID 2 NS MSH 18 Character Set ID 6 For valid values refer to HL7 table NS 0211 Alternate character sets MSH 19 Principal CE 60 NS Language of Message a For a description of the HL7 dat
125. ceive benefits for healthcare services Electronic Medical Record EMR Technology that meets provider needs for real time data access and evaluation in medical care In concert with clinical workstations point of care devices and clinical data repository technologies the EMR provides the means for longitudinal data storage and access The result will be increased efficiency reduced cost and improved quality of care Emergency Sudden unexpected onset of illness or injury which requires the immediate care and attention of a qualified physician and which if not treated immediately would jeopardize or impair the health of an individual Health Level Seven HL7 A data interchange transaction protocol for healthcare technology applications that simplifies the ability of different vendor supplied IS systems to assure inter operability Although not a software program in itself HL7 requires that each healthcare software vendor program HL interfaces for its products Hospital Any facility duly licensed certified and operated as a hospital Does not include a convalescent facility nursing home or any institution or part thereof which is used principally as a convalescence facility rest facility nursing facility or facility for the aged Hospital Information System HIS The common term for the computer hardware and software that provides the support of the hospital Hub Account Aunique account established using Hub Inform
126. ction provides detailed information necessary for formatting laboratory test orders to be submitted to a third party laboratory from Care360 Integration Services This section includes the following chapter s e Chapter 2 Care360 Master File Specification on page 13 e Chapter 3 Care360 Order HL7 Specification on page 57 Chapter 2 Care360 Master File Specification In This Chapter About the Care360 Master File Specification 04 14 e About the Master File Datasets 0 cece ee eee dete 15 e Master File Dataset File Specifications 0 00000 I7 e Dataset File Details 2 erre RRER ERG Re ROE 19 e Sample Master File Dataset Files isse re eese mes OL e Submitting Third Party Master Files 54 e About the Carrier Edit Patterns sisses oder e em ce DD 13 About the Care360 Master File Specification This chapter provides an overview as well as detailed specifications of the Master Files that can be provided by a third party laboratory Master Files are a current collection of all reference data for example test codes diagnostics codes and Ask on Order Entry AOE questions needed to create a complete and valid electronic order to be submitted to a third party laboratory system for processing Master Files help to improve overall patient care by avoiding potential testing delays and minimizing specimen recollection This chapter specifies the interface
127. d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Dataset 21 DOS Transport Temperature File Name TRANSPORT TXT Description Usage Provides DOS information for the temperature requirements for specimen storage and transport There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None TRANSPORT TEMPERATURE Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset 22 Client Specific Order Code File Name CUSTOMP TXT Description Usage Defines client specific order codes created for ordering convenience In TOPLab these are called custom panels There is one row per client per order cod
128. de resources to vendors who are impementing applications which will connect with care360 for Single Sign On and for Web Services 2007 Care360 production environment has been upgraded to Care360 5 0 first to include Single Sign On and Web Service ability Support Contacts PSG 513 123 4567 wsDL Stage https portal care180 com care360 services UserSummary WebService WSDL Production https portal care360 com care360 services UserSummaryWebService WSDL Documentation Universal LOBR 1 0 prog reference PDF 5 79 MB The documentation for creating and understanding the linking done through Single Sign On and Web Service is contained here Resources Trusted stes In This Chapter About the Care360 SSO and Web Services Site Accessing the Care360 SSO and Web Services Site e About the Sample Application sesso 54 200 ante rH iisti ae e About the WSDL Interface Documents 0 000 e Aboutthe Sample Code es Rp SERE IUE See BA kee RR 233 About the Care360 SSO and Web Services Site The Physician Portal SSO and Web Services site is a companion to the Universal Lab Orders and Results Programmer Reference that provides additional support to vendors who are developing partner applications to interact with Physician Portal The Web site provides sample code documentation and other tools and resources that can be used to understand how to develop a partner app
129. ded formatting instructions Numerical CQ Composite quantity quantity NM units CE gt with units NM Numeric Any of the ASCII numeric characters with an optional leading sign or and or an optional decimal point SI Sequence ID A non negative integer in the form of a NM data type Identifier ID Coded values for String data drawn from an HL7 defined table of legal values see HL tables Appendix A of HL7 2 3 IS Coded values for String data drawn from a site defined table of legal values user defined tables HD Hierarchic namespace ID IS gt universal ID ST gt designator universal ID type ID Used only as part of EI and other data types Chapter 4 Care360 Results HL7 Specification Data Type Category Data Type Name Notes Format EI Entity identifier entity identifier ST namespace ID IS universal ID ST gt universal ID type ID gt PL Person location lt point of care IS room IS bed IS facility HD location status IS gt lt person location type IS building IS gt floor IS location description ST gt PT Processing type Xprocessing ID ID processing mode ID Date Time DT Date YYYY MM DD Time HH MM SS S S S S 2222 TS Time stamp YYYY MM DD HHMM SS S S S S 1 11 7 ZZZzZz degree of precision Code Values CE Cod
130. demographic integration 140 Benefits definition 239 Billing Procedure Code dataset Master Files 34 Bill To dataset Master Files 23 24 Bill To Edit dataset Master Files 24 26 Bill To Edit List dataset Master Files 27 Bill To Eligibility dataset Master Files 27 C Care360 Hub Information Services 4 Care360 Order HL specification message segment requirements 59 66 overview 58 Care360 Patient Demographic HL7 specification message segment requirements 175 overview 174 Care360 Physician Portal see Physician Portal Care360 Result HL7 specification message segment requirements 99 overview 98 Care360 SSO and Web Services site 235 about the sample code 238 overview 234 Carriage return 62 99 Client application sample 236 Client Bill To dataset Master Files 22 Client dataset Master Files 19 22 Client NPP dataset Master Files 50 Client UPIN dataset Master Files 42 ClientSpecific Code XREF dataset Master Files 45 Client Specific Order Code dataset Master Files 39 40 Clinical Data Compendium CDC definition 239 Clinical Significance Data dataset Master Files 46 Code sample 238 Common Order segment see ORC Conditional definition 59 63 100 175 Connectivity orders results and Master Files 9 patient demographic 140 Contact Customer support 235 Container dataset Master Files 35 Copyright text customizing 146 Coverage definition 239 Customer Center overview 234 Customer support contact 235 Customization
131. dentifier MSH 06 Receiving Facility HD 180 The receiving facility The account number defined by Quest Diagnostics for the requester Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 07 Date Time of Message Chapter 9 Care360 Patient Demographic HL7 Specification TS 26 The date and time that the sending system created the message Format YYYYMMDDHHMMSS The Hub verifies that this field is populated and that the value complies with the format above Segment ID Element Name Type Length Comments Req d MSH 08 Security ST 40 NS MSH 09 Message Type CM 7 The type of message being R transmitted and the event leading to the creation of the message Valid value ADT A39 Merge Person Information MSH 10 Message Control ST 20 Anumber or other data that uniquely R ID identifies the message in its transmission to the lab system The Hub verifies that this field is populated MSH 11 Processing ID PT 3 The placer system s intent for the R message Valid values include e P Production e T Training e D Debug Development The Hub verifies that the value in this field is P T or D MSH 12 Version ID ID 8 The value for this field is 2 3 R MSH 13 Sequence NM 15 NS Number MSH 14 Continuation ST 180 NS Pointer MSH 15 Accept ID D NS Acknowledgment Type MSH 16 Application ID 2 NS Ackno
132. e Provider a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported IN1 lInsurance Segment The Insurance IN1 segment contains insurance policy coverage information necessary to produce properly pro rated and patient and insurance bills This segment is applicable only to the inbound order for insurance billing The Hub verifies that all data fields are in uppercase Segment ID Element Name Type Length Comments Req d IN1 00 Segment ST 4 Must be INI R Type ID IN1 01 Set ID SI 4 IN1 message segments should be R numbered sequentially from 1 IN1 02 Insurance Plan CD 60 NS ID IN1 03 Insurance CX 15 This is the ODI Bill mnemonic C Company TD Required only if IN1 47 T Third Party Bill The Hub verifies that this value is present and passes the value through with no validation IN1 04 Insurance XON 25 O Company Name IN1 05 Insurance XAD 106 No more than 106 characters wide O Company Addl 30 add2 30 city 25 state 2 Address Zip 10 A Z 0 9 only in these fields Alphanumeric data only Valid Zip formats NNNNN NNNN 5N or 9N no hyphen If present the Hub verifies that the value complies with rules above IN1 06 Insurance Co XPN 48 NS Contact Person IN1 07 Insurance Co XTN 40 NS Phone Number IN1 08 Group Number ST 10 Characters permitted i
133. e character for first and last name A numeric value cannot be used as the first character of the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above GT1 04 Guarantor Spouse Name XPN 48 NS GT1 05 Guarantor Address 106 No more than 106 characters wide Add1 50 add2 50 city 50 state 2 zip 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d GT1 06 Guarantor Ph Num Home XTN 40 Accepted length of this field is 40 numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt lt area city code NM gt phone number NM extension NM If present the Hub verifies that the value complies with rules above GT1 07 Guarantor Ph Num Business XTN 40 Accepted length of this field is 40 numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code
134. e component Required This dataset is optional for third party laboratory implementations Conditions Client order codes can be in the Order code dataset The existence of a test code in this dataset makes it a custom profile Notes e Note I Columns 10 13 are required except for TOPLab feeds TOPLab sends this information separately e Note 2 Components do not need to be orderable That is they do not have to be in the Order code dataset but they can be e Note 3 A minus sign in front of the Client number field 7 indicates that this client can not order the test CUSTOM PANELS Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI PK2 R char 4 Your performing site code Dataset File Details 39 40 CUSTOM PANELS Column Name CDC Column Name Key Req d Type Length Valid Values Notes 3 Performing site TOPLAB PERFORMING SITE PKI PK2 R char 3 Your performing site code 4 Client order code SCAN ID PKI R char 16 5 Title CUSTOM_PANEL_NAME PK2 R char 175 6 Component TEST_CD PKI PK2 R char 16 Order code component 7 Client number TOPLAB_CLIENT_NO PKI PK2 R char 15 8 Billing client number NBS_CLIENT_NO R char 15 9 Group practice GROUP_PRACTICE O char 15 10 Compon
135. e Each portal page Can be renamed and or linked to a different destination page or removed Logo in Left Hand Navigation Each portal page Can be replaced and or linked to a different Pane destination page Quick View Each portal page Cannot be changed or removed links to Physician Portal internal destination Custom URL Specifications In order for a partner application to link to a custom branded version of Physician Portal the partner application must connect via a custom URL that identifies the branded version of Physician Portal to display The custom URL can be used to programmatically link the applications or to enable an end user to access the branded version of Physician Portal directly outside the context of the partner application The format of the custom URL is as follows https portal server name gt lt port gt login jsp branduid lt brand uid where portal server name gt lt port gt are the server name and optional port number associated with the Physician Portal installation to which the partner application is connecting and e brand uid isarandom number that is generated by MedPlus to identify the branded Physician Portal instance to display For example https www care360 com physicianportal login jsp branduid 12345 Partners that allow their users to access Physician Portal directly outside the context of the partner application can either provide their u
136. e Physician Portal can be changed to include a domain name that reflects the partner organization or application For details see Custom URL Specifications on page 148 User Manual and Help The Care360 Physician Portal User Manual and online help can be replaced with a generic version with Quest Diagnostics references and branding removed For details see User Manual and Help Specifications on page 148 Chapter 5 Linking to Physician Portal Custom UI Specifications The following sections provide detailed specifications of the Physician Portal UI elements that can be customized for use with a partner application Logo and Image Specifications The following Physician Portal logos and or images can be replaced or removed File Dimensions Logo Image Location Type Pixels Physician Portal logo Upper left corner of application GIF 197Wx70H Quest Diagnostics logo Left hand navigation pane of application GIF 125Wx41H Physician Portal logo Upper left corner of login page GIF 302Wx99H Color Palette Specifications The overall color scheme of the Physician Portal user interface including navigational buttons can be customized to reflect the partner organization or application Elements for which color can be defined include the following e Text color e Background colors including lighter middle and darker e Button text color e Button background color Colors for each option a
137. e creation of the message Outbound value for this field ORU RO1 results messages MSH 10 Message Control ST 20 Populated by the Sending A ID Facility with a unique message identifier The Hub checks for the presence of this segment but does perform any validation on the value MSH 11 Processing ID PT 3 The placer system s intent for A the message Valid values include e P Production e T Training e D Debug Development Live messages are populated with P MSH 12 Version ID ID 8 The value for this field is 2 3 A MSH 13 Sequence NM 15 N Number MSH 14 Continuation ST 180 N Pointer Chapter 4 Care360 Results HL7 Specification Segment ID Element Name Type Length Comments Supported MSH 15 Accept ID 2 N Acknowledgment Type MSH 16 Application ID 2 N Acknowledgment Type MSH 17 Country Code ID 2 N MSH 18 Character Set ID 6 N MSH 19 Principal CE 60 N Language of Message a For a description of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never PID Patient Identifier Segment The Patient Identifier PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element
138. e last name The Hub verifies that the value in this field complies with the above conditions and that no reserved characters amp are present PID 06 Mother s XPN 48 NS Maiden Name PID 07 Date of Birth TS 26 Date of birth DOB in YYYYMMDD R format The Hub verifies that the DOB is in this format PID 08 Sex IS 1 Valid values for this field include R e M Male e F Female The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 NS PID 10 Race IS 1 NS PID 11 Patient Address XAD 106 NS PID 12 County Code IS 4 NS Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d PID 13 Phone Number Home XTN 250 PID 13 and GT1 6 will use data type 250 XTN and be sub delimited in pieces 6 and 7 area code and phone number respectively The XTN data type reads as follows Components NNN 999 999 9999 X99999 B99999 C any text telecommunication use code ID lt telecommunication equipment type ID gt lt e mail address ST gt country code NM area city code NM phone number NM extension NM any text ST For backward compatibility phone numbers sent in the 10 NM format e g 3148721727 or any of the following variations for sending data in the XTN data format will also be accepted 3148727112 6 or 3148727127 314 8727127
139. e not supported by the Hub are not included in this section for detailed specifications refer to the HL7 2 3 Specification ADT A39 Patient Merge Message Segment Specifications 221 222 MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID Element Name Type Length Comments Req d MSH 00 Segment Type ID ST 4 Must be MSH R MSH 01 Field Separator ST The separator between the message segment ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value is a vertical bar R MSH 02 Encoding Characters ST Four characters that are used in the following order component separator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by Quest Diagnostics MSH 03 Sending Application HD 180 The name of the sending application MSH 04 Sending Facility HD 180 The sending facility Identifies the owner of the patient data and who initiated the patient demographic request Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 05 Receiving Application HD 180 The receiving application i
140. e of the following ways o With patient context Lab Orders opens with the current EMR patient s data pre populated based on the patient s PID o Without patient context Lab Orders opens with no specific patient pre populated The user can then search for a patient within Lab Orders as needed e Patient Summary The EMR user can directly access Physician Portal s Patient Summary page In the Physician Portal a Patient Summary is essentially a collapsed or summarized view of the patient s complete chart To view a more detailed history for the patient you can access individual items within each section of the Patient Summary to display additional data Chapter 5 Linking to Physician Portal o Patient Summary fully expanded Patient Summary opens with all of the patient s latest data displayed as well as all of the page s navigational features visible o Patient Summary collapsed with Write a Prescription displayed Patient Summary opens with a summarized view of the patient s chart with only the Write a Prescription task link visible Oo Patient Summary collapsed with Write a Lab Order displayed Patient Summary opens with a summarized view of the patient s chart with only the Write a Lab Order task link visible e Action Items Inbox The EMR can directly access the Action Items Inbox screen related to their organization Oo Pending Items Displays a collapsed view of the pending items for the logged in user
141. e placer system s intent for the R message Valid values include e P Production e T Training D Debug Development The Hub verifies that the value in this field is P T or D MSH 12 Version ID ID 8 The value for this field is 2 3 R MSH 13 Sequence NM 15 NS Number MSH 14 Continuation ST 180 NS Pointer MSH 15 Accept ID 2 NS Acknowledgment Type MSH 16 Application ID 2 NS Acknowledgment Type MSH 17 Country Code ID 2 NS MSH 18 Character Set ID 6 NS Segment ID Element Name Type Length Comments Req d MSH 19 Principal CE 60 NS Language of Message a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported EVN Event Type Segment The Event Type EVN segment is used to communicate necessary trigger event information to receiving applications Segment ID Element Name Type Length Comments Req d EVN 00 Segment ST 4 Must be EVN R Type ID EVN 01 Event Type Code ID 3 The second component trigger event R of MSH 09 Message Type should be used to transmit event type code information This field contains the events corresponding to the trigger events described in this section Note This field has been retained for backward compatibility only EVN 02 Recorded TS 26 The date and time that the transaction O Date Time was entered EV
142. e primary identifier or other O Internal ID identifiers used by the facility to identify a patient uniquely for example medical record number billing number birth registry etc PID 04 Alternate CX 20 NS Patient ID PID PID 05 Patient Name XPN 48 No more than 48 characters wide R including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above PID 06 Mother s XPN 48 NS Maiden Name PID 07 Date of Birth TS 26 Date of birth DOB in YYYYMMDD O format The Hub verifies that the DOB is in this format ADT A28 Patient Add Message Segment Specifications 183 184 Segment ID Element Name Type Length Comments Req d PID 08 Sex IS 1 Valid values for this field include O e M Male e F Female e Blank The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 Patient alias name O PID 10 Race IS 1 NS PID 11 Patient Address XAD 106 No more than 106 characters wide O Add1 50 add2 50 city 50 state 2 zp 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above PID
143. e sending facility Identifies the owner of the patient data and who initiated the patient demographic request Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 05 Receiving Application HD 180 The receiving application identifier MSH 06 Receiving Facility HD 180 The receiving facility The account number defined by Quest Diagnostics for the requester Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 07 Date Time of Message Chapter 9 Care360 Patient Demographic HL7 Specification TS 26 The date and time that the sending system created the message Format YYYYMMDDHHMMSS The Hub verifies that this field is populated and that the value complies with the format above Segment ID Element Name Type Length Comments Req d MSH 08 Security ST 40 NS MSH 09 Message Type CM 7 The type of message being R transmitted and the event leading to the creation of the message Valid value ADT A29 Delete Person Information MSH 10 Message Control ST 20 Anumber or other data that uniquely R ID identifies the message in its transmission to the lab system The Hub verifies that this field is populated MSH 11 Processing ID PT 3 The placer system s intent for the R message Valid values include e P Production e T Training e
144. e360 Hub Information Services Hub Database FEVER coim RR 1 Copy of Patient Demographic Updates Portal Forwards Patient Demographic Updates to Hub The following steps outline the procedure and associated systems involved in a partner application receiving patient demographic updates from Physician Portal 1L The Hub receives the patient demographic messages from Physician Portal and verifies the format and content of the patient demographic messages L The Hub records the patient demographic transaction and stores a copy of the discrete content of the patient demographic messages for a minimum of 90 days or longer as specified by the partner L The Hub converts the patient demographic messages to the standard HL7 ADT message format and then forwards the messages to the partner application L The partner application applies the updates to its patient database L Anyvalidation errors that occur within the partner application are returned to the Hub About Patient Demographic Services 145 146 Customizing the Physician Portal User Interface When Physician Portal is linked to a partner application itis possible to customize certain elements of Physician Portal s user interface UI to provide a more seamless experience for users as they move between the two applications Zi Quick View Microsoft Internet Explorer ti Q O ADO Address
145. ed element identifier ST text ST name of coding system ST alternate identifier ST alternate text ST name of alternate coding system ST gt CK Composite ID with ID number NM gt check digit NM code check digit identifying the check digit scheme employed ID gt assigning authority HD gt CX Extended composite ID ST check digit ST gt code ID with check digit identifying the check digit scheme employed ID gt assigning authority HD lt identifier type code IS assigning facility HD XCN Extended composite In Version 2 3 replaces the CN data type ID number and lt ID number ST gt family name ST given Dame name ST middle initial or name ST suffix e g JR or III ST prefix e g DR ST gt degree e g MD ST gt lt source table IS assigning authority HD name type code ID identifier check digit ST gt lt code identifying the check digit scheme employed ID identifier type cod IS gt assigning facility HD gt Generic CM Composite No new CMs are allowed after HL7 Version 2 2 Hence there are no new CMs in Version 2 3 Care360 Result Message Format Requirements 101 102 Data Type Category Data Type Name Notes Format Demographics XAD Extended address In Version 2 3 replaces the AD data type
146. ed with an ORC R segment OBR 02 Placer Order EI 20 The placer application s order number R Number same as ORC 02 All OBRs in the ORM must contain the same value The Hub verifies that this field is present Note The Hub does not require unique order numbers The service provider is responsible for handling any duplicate order numbers that are received OBR 03 Filler Order EI 22 NS Number OBR 04 Universal Service CE 200 Identification code for the ordered test R ID One order code per OBR segment Format Local Order Code Description Note Preserve Incoming Order Data for subsequent inclusion in matching result messages Constraints Rules For each unique occurrence of OBR 4 preserve that OBR 4 value and the corresponding set of OBR 18 and OBR 19 values that are received in an order message The Hub verifies that this value is present and that it contains data only in the 4th and 5th sub fields The 4th sub field must also be unique within the ORM OBR 05 Priority ID 2 NS OBR 27 OBR 06 Requested TS 26 NS Date time Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d OBR 07 Observation TS 26 The specimen collection date and time R Date Time This field is required on ORM messages originating at the ordering facility Format YYY YMMDDHHMM The Hub verifies that the data complies with
147. ement Name Type Length Comments Req d PID 06 Mother s XPN 48 NS Maiden Name PID 07 Date Time of TS 26 Date of birth DOB in O Birth YYYYMMDDHHMMSS format The Hub verifies that the DOB is in this format PID 08 Sex IS 1 Valid values for this field include O e M Male e F Female e Blank The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 Patient alias name O PID 10 Race IS 1 NS PID 11 Patient Address XAD 106 No more than 106 characters wide O Add1 50 add2 50 city 50 state 2 zp 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above PID 12 County Code IS 4 NS PID 13 PhoneNumber XTN 40 Accepted length of this field is 40 O Home numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt area city code NM phone number NM gt extension NM PID 14 PhoneNumber XTN 40 Accepted length of this field is 40 O Business numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt lt area city code NM phone number NM gt extension NM PID 15 Language CE 60 NS Patient PID 16 Marital Status IS 1 NS PID 17 Religion IS 3 NS
148. ending Application HD 180 The name of the sending application MSH 04 Sending Facility HD 180 The sending facility Identifies the owner of the patient data and who initiated the patient demographic request Inbound The Hub verifies that the field is populated Outbound No verification by the Hub ADT A31 Patient Update Message Segment Specifications 205 206 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d MSH 05 Receiving HD 180 The receiving application identifier O Application MSH 06 Receiving Facility HD 180 The receiving facility The account R number defined for the requester Inbound The Hub verifies that the field is populated Outbound No verification by the Hub MSH 07 Date Time of TS 26 The date and time that the sending R Message system created the message Format YYYYMMDDHHMMSS The Hub verifies that this field is populated and that the value complies with the format above MSH 08 Security ST 40 NS MSH 09 Message Type CM 7 The type of message being R transmitted and the event leading to the creation of the message Valid value ADT A31 Update Person Information MSH 10 Message Control ST 20 A number or other data that uniquely R ID identifies the message in its transmission to the lab system MSH 11 Processing ID PT 3 Th
149. ent Context When a user accesses a Physician Portal function via SSO the current patient context is automatically maintained between the two applications whenever possible For example if the user has already searched for a particular patient within the partner application and then wants to place a new lab order for that patient the user clicks the appropriate link and Physician Portal opens to the Lab Orders function with the same patient preselected In order to maintain the patient context the partner application passes a unique patient identifier PID to Physician Portal so that a search for the matching patient can be performed as the linking occurs If an exact PID match is found then the patient context is maintained otherwise the user can access the selected Physician Portal function but will need to manually search for the desired patient Chapter 5 Linking to Physician Portal Process Walkthrough Linking and SSO The diagram below illustrates at a high level the flow of information between Physician Portal and a linked partner application Following the diagram is a step by step walkthrough of the linking and SSO processes illustrated in the diagram Linking to Care360 Physician Portal Physician Office 2 8 DAS Demo Health Assoc User Preferences Support Whats New nep Logout e ind Lab Orders Partner Application dan tn T ns E Show Quick Lists CINew Standing Order Ci Verify Order Requ
150. ent title TEST_CD_DESCRIPTION C char 175 See note 1 1l Component TEST CD SPECIMEN TYPE C char 60 See note 1 specimen type 12 Componentservice TEST CD SERVICE CODE C char 10 See note 1 code 13 Component unit TEST CD UNIT CD C char 10 See note 1 pede LIS code component 14 Unit Code UNIT_CD PKI R char 10 LIS code 15 State Specimen STATE O char 2 Specimen condition of a Condition component code field 13 Example values e FR FZ F Frozen e RT A Room Temperature e RF R Refrigerated e W Wet Ice e S Special a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Dataset 23 Performing Site Code File Name SITES TXT Description Usage Defines service provider laboratory facilities and send out testing site codes Required This dataset is optional highly recommended if using laboratory reporting for third party laboratory implementations Conditions None PERFORMING SITE Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Facility site code FACILITY_CD PKI R char 5 Where the test is performed 4 Country name COUNTRY O char 4 Valid values US blank 5 Active Flag ACTIVE FL
151. eptable ATEMP O char 5 This field can hold up to 5 single Temperatures character temperature codes Current codes in use include e R Refrigerated e F Frozen e A Ambient room temp e S Special e W Wet ice 7 Acceptable ATEMP_COMMENTS O char 30 Temperatures Comments a R Required O Optional C Conditional Dataset 29 Client Specific Code XREF File Name CUSTOMC TXT Description Usage Defines the list of clients allowed to order client specific order codes created for ordering convenience In TOPLab these are called custom panels There is one row per client Required This dataset is optional for third party laboratory implementations Conditions Client order codes should be in Dataset 22 Client Specific Order Code Note The clients indicated for each order code in this optional file will be added to the list of clients indicated in Dataset 22 Client Specific Order Code N A Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PK PKR2 R char 4 3 Performing site TOPLAB PERFORMING SITE PK1 PK2 R char 3 4 Client order code SCAN ID PKI R char 16 5 Billing client number NBS_CLIENT_NO R char 15 a R Required O Optional C Conditional Dataset File De
152. er RPG 2s Gv REREOSEECRSRT EVeRRER VE 99 Field Specifications 15 25 25 csenseserges cs pesbrie er esee RED EEE rh ens 99 Data Type Specifications eiim a em an X Er Rub mete DAE ahah en RS 100 Care360 Result Message Segment Specifications llle 103 Sample Care360 Result Messages 0 cece cece cece cence nnn 120 Receiving Third Party Laboratory Results Files lees 123 Results Formatting Requirement ceca c caw s aes kh kem ey ttid dar eeteag 123 Sample XML Result Piles 25 05 5429 35e G0 80d 59 wiebones ER RR NE ERE ERE eee 124 Linking and Single Sign On About This Section 043 64 6400400054 000 0900004009000 VE ECT VIC V A d P ede OS 128 Chapter 5 Linking to Physician Portal 00 e eee eeeeeeeeee 129 About Linking and Single Sign On SSO 2 0 0 0 0c cece cece ee eee ee eee 130 Physician Portal Functions Available for Linking 00 130 Formatting Requirements for Linking to Care360 Physician Portal 131 About Smpgle Sign On SSO 9 66 2 ois og pr pU I p Ae erdoi e RA TSi Maintaming Patient Context sex RE 4 566 Goel 6 Fer E r E SERES 132 Process Walkthrough Linking and SSO 1 ee ee eee 133 About User Summary Services e ssssesessescososcosccesoscoecocoeeo 136 Process Walkthrough Retrieving User Summary Data 45 137 Table of Contents About Order Echo 3 524 2o 9E He RA RR RR REA I Nai a cdi dr a AL WI e 138 Process Walkthrough
153. er defined NS Classification table 0228 Diagnosis classification DGI1 18 Confidential ID 1 For valid values refer to HL7 table NS Indicator 0136 Yes no indicator DG1 19 Attestation TS 26 NS Date Time a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Chapter 3 Care360 Order HL7 Specification NTE Notes and Comments Segment The Notes and Comments NTE segment contains notes and comments for ORM messages and is optional Segment ID Element Name Type Length Comments Req d NTE 00 Segment ST 4 Mustbe NTE R Type ID NTE 01 Set ID SI 4 May be used to group multiple NTE R segments in a message NTE 02 Source of ID 1 Valid values include R Comment I Implies the data in NTE 03 will be considered internal comments and not returned with the results Limit is 5 lines of 60 characters each e R Impliesreport comments and will be returned with results Limit is 2 lines of 60 characters each NTE 03 Comment ST 60 Comments must not have embedded R control characters Each new line must be defined in a unique NTE segment a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Care360 Order Message Segment Specifications 93 94 Sample Care360 Order Messag
154. er geographic designation ST county parish code IS census tract IS XPN Extended person In Version 2 3 replaces the PN data type name family name ST given name ST middle initial or name ST gt suffix e g JR or III ST gt prefix e g DR ST degree e g MD ST gt name type code ID gt Care360 Order Message Format Requirements 65 66 Data Type Category Data Type Data Type Name Notes Format XON Extended composite organization name ST gt organization name name and ID type code IS ID number NM check number for digit NM code identifying the check digit organizations Scheme employed ID assigning authority HD gt identifier type code IS assigning facility ID HD gt XTN Extended In Version 2 3 replaces the TN data type telecommunications NNN 999 999 9999 X99999 B99999 C any number text telecommunication use code ID lt telecommunication equipment type ID lt email address ST gt country code NM lt area city code NM phone number NM lt extension NM any text ST Time Series TO Timing quantity For timing quantity specifications for orders see Chapter 4 of the HL7 Standard Section 4 4 quantity CQ gt interval duration gt start date time TS end date time TS gt
155. es Following are several sample General Order ORM messages formatted according to the Care360 Order Message Format Requirements on page 59 and Care360 Order Message Segment Specifications on page 67 Sample One Patient Bill MSH amp AaBbCcDd IN1 1 1 CTFW ORDR PVDR ACCT ORDR PVDR 20040714080935 ORM O01 123456789 D 2 3 PID 1 12345678912345 NTE 1 R Comment Comment Comment e me EST GT1 1 T ORC NW 33336 OBR 1 33336 Abcdef Ghijklmnop 20040131 M 4323334832 ELELEEEEEEEELEEEEEEE rr rrr LITT IP ER KID 1905 MAIN STREET Klamath Falls OR 97601 5418824691 A52352 Machado Randal 10124 CARDIO CRP 20040708164727 I111111A52352 Machado Randal l ll II11 R Sample Two Patient Bill MSH amp C1 DFW 789AaBbCcDdEe PID 1 12345 STREET SUITE D 2 3 ORDR PVDR ACCT PSC ORDR PVDR 20040714080935 ORM O01 123456 67891234567 Abcdef Ghijklmnopwwwwwww 20040131 M 1905 MAIN 1234567 SUITE 30 CHARACTERS LONG TODAY Klamathaa Falls City Name OR 97601 1234 4323334832 123456789 NTE l R Comment Comment Comment INTL IIE PPP PPP ELLE EEEEEELEEEEEEEEEEEEE ELE TL tte GT1 1 TESTER KID 1905 MAIN STREET Klamath Falls OR 97601 5418824691 ORC NW 633060062520160341 1 1 1111111A52352 Machado Randal OBR 1 633060062520160341
156. essage Valid values include e P Production e T Training e D Debug Development The Hub verifies that the value in this field is P T or D MSH 12 Version ID ID 8 The value for this field is 2 3 R MSH 13 Sequence NM 15 NS Number MSH 14 Continuation ST 180 NS Pointer MSH 15 Accept ID 2 NS Acknowledgment Type MSH 16 Application ID 2 NS Acknowledgment Type ADT A28 Patient Add Message Segment Specifications 181 182 Segment ID Element Name Type Length Comments Req d MSH 17 Country Code ID 2 NS MSH 18 Character Set ID 6 NS MSH 19 Principal CE 60 NS Language of Message a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported EVN Event Type Segment The Event Type EVN segment is used to communicate necessary trigger event information to receiving applications Segment ID Element Name Type Length Comments Req d EVN 00 Segment ST 4 Must be EVN R Type ID EVN 01 Event Type Code ID 3 The second component trigger event R of MSH 09 Message Type should be used to transmit event type code information This field contains the events corresponding to the trigger events described in this section Note This field has been retained for backward compatibility only EVN 02 Recorded TS 26 The date and time t
157. essage Format Requirements 99 100 Parameter Description Required The fields within each segment are classified based on their support status of Always A Conditional C Never N or Pass Through PT as defined below e Always If the corresponding segment is present the field will also be present within the segment e Conditional The field may or may not be present depending on certain conditions stipulated in the Comments column of each segment table If the field is present the Hub validates it against any stated requirements e Pass Through The information in the field is passed through from the original inbound order ORM message e Never The field is not supported in result ORU messages If a field is described as Neverby the Hub the corresponding row appears grayed in the table the field must not be present within the segment If the field is present the message is rejected by the Hub Data Type Specifications The following table describes the data types that may appear in the message segments Note Brackets indicate that the enclosed data is optional Data Type Category Data Type Name Notes Format Alphanumeric ST String Any ACSII printable characters ASCII decimal values between 32 and 126 with the exception of the defined delimiter characters Left justified with optional trailing spaces FT Formatted text String data with embed
158. et of OBR 18 and OBR 19 values that are received in the order message Outgoing orders from the HUB to IMPACT are to exclude values in OBR 18 and OBR 19 OBR 19 Placer field 2 ST 60 If present the Hub stores this O information and returns it as received with the associated results Notes e For each unique occurrence of OBR 4 the OBR 4 value is to be preserved as is the corresponding set of OBR 18 and OBR 19 values that are received in the order message e Outgoing orders from the HUB to IMPACT are to exclude values in OBR 18 and OBR 19 OBR 20 Filler Field 1 ST 60 NS OBR 21 Filler Field 2 ST 60 NS OBR 22 Results TS 26 NS Rpt Status Chng Date Time OBR 23 Charge to CM 40 NS Practice OBR 24 Diagnostic Serv ID 10 For valid values refer to HL7 table NS Sect ID 0074 Diagnostic service section ID OBR 25 Result Status ID 1 For valid values refer to HL7 table NS 0123 Result status OBR 26 Parent Result CM 400 NS OBR 27 Quantity Timing TQ 200 This is OBR 27 6 Values for this field O include e S Stat e C Call e R Routine OBR 28 Result Copies To XCN 150 NS OBR 29 Parent CM 150 NS Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d OBR 30 Transportation ID 20 For valid values refer to HL7 table NS Mode 0124 Transportation mode OBR 31 Reason for Study CE 300 NS OBR 32 Principal Result CM 200 NS Interprete
159. et is required for third party laboratory implementations Conditions None Note Sites that support SelecTest should provide either Y or N for column 12 and U for column 18 Conversely sites that support the conforming flag should provide either Y or N for column 18 and U for column 12 One or the other of fields 12 and 18 should be supported TEST CODE UNIT CODE XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PK PK2 R char 4 3 Performing site TOPLAB PERFORMING SITE PKI PK2 R char 3 4 Order code TEST CD PKI R char 16 5 Unit code UNIT CD PK2 R char 10 LIS code 6 Order code suffix SUFFIX O char 8 7 Title DESCRIPTION R varchar 175 8 Profile indicator PROFILE_IND R char 1 Valid values Y Profile NI 9 Specimen type SPECIMEN TYPE O char 30 Chapter 2 Care360 Master File Specification TEST CODE UNIT CODE XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes 10 State Specimen STATE O char 2 Specimen condition of an Condition order code Example values e FR FZ F Frozen e RT A Room Temperature e RF R Refrigerated e S Special e W WetIce 11 Billing service code NBS SERVICE CODE R char 10 Must match dataset 10 field 4 12
160. etails about each of the methods listed above Method Description getCounts Summary Retrieves user summary data from Physician Portal for all organizations with which the current partner application user is associated up to the maximum number of organizations allowed Usage The WSUserSummaryData object contains the user summary data that is returned The WSUserSummaryCounts object contained by WSUserSummaryData includes data for up to the maximum number of organizations allowed Method Signature WSUserSummaryData getCounts throws SOAPException User Summary Services API 163 164 Method Description getCountsByOrg Summary Retrieves user summary data from Physician Portal for one or more specific organization s with which the current partner application user is associated Usage The WSUserSummaryData object contains the user summary data that is returned Throws a SOAPException for the following conditions The method is called with an invalid orgUID either the orgUID does not exist in the system or the partner does not have access to the requested organization e The method is called and passes more orgUIDs than the maximum allowed e The method is called without passing in an orgUID Method Signature WSUserSummaryData getCountsByOrg String orgUID throws SOAPException getOrgs Summary Retrieves a list of organizations with which the partner applicat
161. ffice staff and administrative office staff Third Party Internet Resources The following is a list of third party resources available via the Internet that you can access for more information on specific programming subjects Subject Internet Resources Health Level 7 Health Level Seven HL Inc http www hl7 org HL7 SAML Security Assertion Markup http www oasis open org committees Language tc home php wg abbrev security SSL Certificates VeriSign SSL Certificates http www verisign com products services security services ssl uononpogju About This Section This section provides an overview of Care360 Integration Services This section includes the following chapter s e Chapter 1 Universal Ordering and Resulting on page 3 Introduction Chapter 1 Universal Ordering and Resulting Universal Lab Orders and Results Client Hub Infrastructure _ Hub Receives Hub Submits Order to Third Party Lab Order Third Party Lab Physician Office d Hub Echoes one Lab per order Third Party Lab Order Order Copy to Billing System Care360 as needed Physician Portal Lab Orders Hub Database Copy of Order Copy of Results Copy of Master Files Third Party 4 EMR Hub Returns Third Lab Submits Third Independent Party Lab Results Party Results Lab EMR Retrieves and E Lab Submits Applies CDC Files Master Files
162. fied as a viable SAML asserter o Is the asserted partner application user recognized by Physician Portal The NameIdentifier value within the SAML assertion provides unique identification of the user as recognized by the partner application Physician Portal SSO looks up this user identifier in its user mapping table to determine the correlating Physician Portal user identity If found a Physician Portal login session is established for the user If not found Physician Portal SSO presumes the user is accessing Physician Portal via SSO for the first time and directs the user to a one time Physician Portal login page for an overview of this process see Initializing a User s SSO Connection on page 133 O Does the asserted partner application user correlate to the partner providing the assertion When a user s identity from the partner application is correlated to his her Physician Portal user identity the partner application s Issuer is also recorded for that user On subsequent requests to Physician Portal the SAML Issuer is compared to that stored in the user s mapping record If they match Physician Portal SSO is assured that the user does in fact belong to the partner site that is asserting the user s identity L HTTP Response is received The page requested via the targetUri HTTP POST parameter is returned by Physician Portal to the partner application user application within the HTTP Response The returned page reflects the user s
163. field is populated with one of the above values OBX 03 Observation CE 590 Contains a value that reports the results R Identifier for an AOE Required if this segment is present in the ORM Data layout Local Code description If this segment is present the Hub verifies that this field is present OBX 04 Observation ST 20 NS Sub ID OBX 05 Observation ID 72 Contains an answer to an AOE question R Value OBX 06 Units CE 60 NS OBX 07 References ST 10 NS Range OBX 08 Abnormal Flags ID 5 For valid values refer to HL7 table NS 0078 Abnormal flags OBX 09 Probability NM 5 NS OBX 10 Nature of ID D For valid values refer to HL7 table NS Abnormal Test 0080 Nature of abnormal testing OBX 11 Observ Result ID 1 For valid values refer to HL7 table NS Status 0085 Observation result status OBX 12 Date Last Obs TS 26 NS Normal Values OBX 13 User Defined ST 20 NS Access Checks Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d OBX 14 Date Time of TS 26 NS the Observation OBX 15 Producer s ID CE 60 NS OBX 16 Responsible XCN 80 NS Observer OBX 17 Observation CE 60 NS Method a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported DG1 Diagnosis Segment The Diagnosis DG1 segment contains patient d
164. ght appear in these fields if NMS Mapping has been imposed Some lab systems add a suffix to the lab order code in the result messages for example 10165SB where SB is added by the lab system Order code will always be present but description may not be included in some cases A OBR 05 OBR 06 Priority OBR 27 Requested Date time ID TS 26 OBR 07 Observation Date Time TS 26 The specimen collection date and time If present in the inbound order the result echoes this value Format YYY YMMDDHHMMSS Seconds are always 00 OBR 08 Observation End Date Time TS 26 OBR 09 Collection Volume CQ 20 OBR 10 Collector Identifier XCN 60 Care360 Result Message Segment Specifications 111 112 Segment ID Element Name Type Length Comments Supported OBR 11 Specimen Action ID 1 Version 2 3 1 only O Code Typical values are G A or null e G test was reflexed e A add on OBR 12 Danger Code CE 60 N OBR 13 Relevant Clinical ST 300 N Info OBR 14 Specimen TS 26 For observations requiring a R Received specimen this is the actual login Date Time time at the diagnostic service This field must contain a value when the order is accompanied by a specimen or when the observation requires a specimen and the message is a report OBR 15 SpecimenSource CM 300 N Chapter 4 Care360 Resu
165. gment The Merge Patient Information MRG segment provides receiving applications with information necessary to initiate the merging of patient data as well as groups of records Segment ID Element Name Type Length Comments Req d MRG 00 Segment Type ID ST 4 Must be MRG R MRG 01 Prior Patient ID CX 20 The internal prior patient identifier O Internal This field contains a list of potential old numbers to match Only one old number can be merged with one new number in a transaction MRG 02 Prior Alternate CX 20 The prior alternate patient identifier O Patient ID MRG 03 Prior Patient CX 20 The prior patient account number O Account Number MRG 04 Prior Patient ID CX 20 The external prior patient identifier R External Note Must not contain the same value as PID 02 MRG 05 Prior Visit CX 20 The prior visit number O Number MRG 06 Prior Alternate CX 20 The prior alternate visit number O Visit ID ADT A39 Patient Merge Message Segment Specifications 227 228 Segment ID Element Name Type Length Comments Req d MRG 07 Prior Patient Name XPN 48 The prior name of the patient This field is not used to change a patient name No more than 48 characters wide including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of
166. gment hierarchy as specified below MSH Message Header Required PID Patient Identification Required NTE Notes and Comments Optional PV1 Patient Visit Data Optional IN1 Insurance Information Required GT1 Guarantor Information Conditional ORC Common Order Required OBR Observation Request Required NTE Notes and Comments Optional DG1 Diagnosis Optional OBX Observation Result Conditional In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional and or conditional Message Segment Requirements The following table classifies the various ORM message segments based on their requirement status of Required R Optional O or Conditional C as defined below e Required The segment must be present in the ORM message If it is not present the message is rejected by the Hub e Optional The segmentis not required The ORM message is accepted by the Hub whether or not this segment is present If the segment is present the Hub validates the associated field requirements e Conditional The segment may or may not be required depending on certain conditions Conditions are stipulated in the Comments Conditions column of the table below If the segment is present the Hub validates the associated field requirements Note This table is only meant to communicate segment requirements that is whether or not a segment
167. gregated in the database as well as in the Physician Portal user interface according to the performing laboratory from which they are received L Results received from a third party laboratory are stored permanently in the patient s chart Third party lab results can be manipulated within Physician Portal in the same manner as can Quest Diagnostics results that is they can be printed attached to a user message viewed in a graph or flowsheet etc Chapter 1 Universal Ordering and Resulting Universal Ordering and Resulting Connectivity The transfer of all data Master Files orders and results between Care360 Hub Information Services and a third party laboratory will occur via one of the following encrypted data transfer protocols e MLLP Socket over Virtual Private Network VPN Permanent socket based communication protocol that is used extensively in the healthcare industry for transporting HL7 messages FTP Over SSL Traditional port 21 FTP over an SSL encrypted socket Additional connectivity solutions may be considered based upon cost regulatory compliance and the specific capabilities and needs of the laboratory Note For more information on the Web services provided by Care360 Hub Information Services refer to the Care360 Hub Information Services Programmer Reference Universal Ordering and Resulting Connectivity s19p1g Aioje10qe Aueg paru About This Section Third Party Laboratory Orders This se
168. hat the transaction O Date Time was entered EVN 03 Date Time TS 26 The date and time that the event is O Planned Event planned EVN 04 Event Reason IS 3 The reason for the event O Code EVN 05 Operator ID XCN 60 The individual responsible for O triggering the event EVN 06 Event Occurred TS 26 The date and time that the event O actually occurred a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported Chapter 9 Care360 Patient Demographic HL7 Specification PID Patient Identification Segment The Patient Identification PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID O segments within a message Usually a sequential number beginning with 1 PID 02 Patient ID CX 20 When the patient is from another R External ID institution outside office etc the identifier used by that institution can be shown in this field This may bea number that multiple disparate corporations or facilities share PID 03 Patient ID CX 20 Th
169. he facility to identify a patient uniquely for example medical record number billing number birth registry etc PID 04 Alternate CX 20 NS Patient ID PID PID 05 Patient Name XPN 48 No more than 48 characters wide R including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above PID 06 Mother s XPN 48 NS Maiden Name PID 07 Date Time of TS 26 Date of birth DOB in O Birth YYYYMMDDHHMMSS format The Hub verifies that the DOB is in this format PID 08 Sex IS 1 Valid values for this field include O e M Male e F Female e Blank The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 Patient alias name O PID 10 Race IS 1 NS PID 11 Patient Address XAD 106 No more than 106 characters wide O Add1 50 add2 50 city 50 state 2 zip 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above ADT A29 Patient Delete Message Segment Specifications 199 200 Segment ID Element Name Type Length Comments Req d PID 12 County Code IS 4 NS PID 13 Phone Numbe
170. hen you see a caution follow the instructions carefully Abbreviations and Acronyms The following is a list of abbreviations and acronyms that are used in this manual Abhreviation Acronym Description ABN Advance Beneficiary Notice ADT Admission Discharge Transfer AMA American Medical Association AOE Ask on Order Entry Application Programming Interface Application Service Provider B2B Business to Business BIS Billing Information System BU Quest Diagnostics Business Unit CA Certificate Authority CAQH Council for Affordable Quality Healthcare CDC Clinical Data Compendium CLIA Clinical Laboratory Information Act COB Coordination of Benefits DOB Date of Birth DOS Directory of Service EAI Enterprise Application Integration EHR Electronic Health Record EJB Enterprise JavaBeans EMR Electronic Medical Record File Transfer Protocol HIS Hospital Information System HL7 Health Level Seven HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure ICD9 International Classification of Diseases of the World Health Organization 9th Revision IDE Interactive Development Environment Abbreviations and Acronyms xiii xiv About This Manual Abhreviation Acronym Description
171. here is one entry per carrier as identified by the Billing Information System BIS that has such edits Required This dataset is optional not recommended for third party laboratory implementations Conditions There must be a valid carrier type entry in the Bill to dataset Pattern lists referenced must be defined in the Bill to edit list dataset Note See About the Carrier Edit Patterns on page 55 for further explanation and examples of datasets 4 and 5 Also the last six entries are each provided 16 times BILLING_EDITS Column Name CDC Column Name Key Req d Type Length Valid Values Notes Operation R char 1 _ Valid values A C D Legal entity LEGAL_ENTITY PKI R char 4 Chapter 2 Care360 Master File Specification BILLING EDITS Column Name CDC Column Name Key Req d Type Length Valid Values Notes 3 Billing carrier ID THIRD_PARTY_FORMS_CD PKI R char 6 Must match dataset 10 field 3 and dataset 11 field 3 4 Age required AGE_REQ R bit Valid values Y N 5 Birthdate required BIRTHDATE_REQ R bit Valid values Y N 6 Age or birthdate AGEBIRTHDATE_REQ R bit Valid values Y N required 7 Sex required SEX_REQ R bit Valid values Y N 8 Relationship code RELATIONSHIP CD REQ R bit Valid values Y N required 9 Patient signat
172. i norm Oe ave 9 Rm AU eae aaa ea ea xii Abbreviations and Acronyms ccc e cece eet ehh hh nn xiii Related Documentation 5 424 ve ros e eee ue eed REY T y e wars xvi Third Party Internet ResoOUTCOS eui eso sae se y eoa ve adora tese xe E d sd xvi Introduction About This Section 4 prex ER r9 RO GU doe wy Y Y o S ee es 2 Chapter 1 Universal Ordering and Resulting 3 About Universal Ordering and Resulting leere 4 Universal Ordering and Resulting Components 5 0000 eese 4 About the Universal Ordering and Resulting Data Flow Leu 5 Process Walkthrough Universal Ordering and Resulting 5 Universal Ordering and Resulting Connectivity 06 eee ee eee eee 9 Third Party Laboratory Orders About This Section 12x 66000 set SAC ARREST ERATAARCACAGIASPT ERR AS E 12 Chapter 2 Care360 Master File Specification 13 About the Care360 Master File Specification llle 14 About the Master File Datasets 0 0 cece cee cece ee ee eee hh 15 Dataset File List 2 2 04 soccoueo0ke8 HANSA Gh de GEOR eee Re d qr e s 15 Master File Dataset File Specifications ccc cee ee cece eee tener eens 17 Dataset Format Specifications iu exe e dete rr merken e Red Ren Vado eer I7 Dataset Fle D tails 1535523396 ma RR EEE AKRE RAAR EPERERA RA 19 Sample Master File Dataset Files llle
173. iagnosis information Segment ID Element Name Type Length Comments Req d DG1 00 Segment ST 4 Must be DG1 R Type ID DG1 01 Set ID SI 4 Allows identification of multiple R diagnosis segments grouped beneath a single OBR segment Usually a sequential number beginning with 1 DG1 02 Diagnosis ID 3 Literal ICD R Coding Method The Hub verifies that this value is populated with the ICD DG1 03 Diagnosis Code CE 60 Contains the diagnosis code and R diagnosis description This is an ICD 9 diagnostic code No decimal places are allowed DG1 04 Diagnosis ST 140 Diagnosis name and description O Description DG1 05 Diagnosis TS 26 NS Date Time DG1 06 Diagnosis Type IS 2 For suggested values refer to user defined NS table 0052 Diagnosis type DG1 07 Major CE 60 NS Diagnostic Category DG1 08 Diagnostic CE 60 NS Related Group DG1 09 DRG Approval ID 2 For valid values refer to HL7 table NS Indicator 0136 Yes no indicator Care360 Order Message Segment Specifications 91 92 Segment ID Element Name Type Length Comments Req d DG1 10 DRG Grouper IS D NS Review Code DG1 11 Outlier Type CE 60 NS DG1 12 Outlier Days NM 3 NS DG1 13 Outlier Cost CP 12 NS DGl 14 Grouper Version ST 4 NS and Type DG1 15 Diagnosis NM 2 NS Priority DG1 16 Diagnosing XCN 60 NS Clinician DG1 17 Diagnosis IS 3 For suggested values refer to us
174. ial duplicate If Physician Portal finds an ambiguous match between the incoming patient demographics and a single patient in the target organization Physician Portal adds the patient and marks the patient as a potential duplicate Chapter 5 Linking to Physician Portal Fuzzy Matching Request Potential Results Delete Patient If Physician Portal finds no high confidence match between existing patients in the target organization and the incoming patient demographics Physician Portal returns an error to the partner application If Physician Portal finds a high confidence match between a single patient in the target organization and the incoming patient demographics the matching patient is deleted If Physician Portal finds more than one high confidence match between existing patients in the target Organization and the incoming patient demographics Physician Portal returns an error to the partner application Merge Patients If the target organization contains no match for either the correct patient or the incorrect patient Physician Portal returns an error to the partner application If the target organization contains a single high confidence match for the correct patient and a single high confidence match for the incorrect patient those patients are merged If the target organization contains more than one high confidence match for either the correct patient or the
175. ian Portal SSO for Interactive Users 155 156 Physician Portal evaluates the current user session in conjunction with the SAML assertion provided and performs authentication to establish a new session under the following conditions evaluated in the order shown L The partner application link has launched a new browser window Q The partner application link attempts to update the existing browser window for which the Physician Portal session has timed out L A different user has authenticated to the running partner application since the Physician Portal browser window was launched This requires authentication to Physician Portal as the new partner application user About SSO User Initialization Before successful SSO authentication to Physician Portal can occur users of trusted partner applications must be mapped to Physician Portal This process includes verifying that the user knows his her Physician Portal credentials User IDand Password the first time the user accesses Physician Portal via a link from the partner application The first time the user initiates SSO based access to Physician Portal the absence of a user mapping on file for the user elicits a login page displaying a message indicating why the credentials are being requested Both new and existing Physician Portal users will see this page on their first SSO based access attempt Both temporary passwords issued by MedPlus Customer Support and permanent pa
176. ic Services Note Patient demographic update messages provided by the partner application must be formatted according to the specifications detailed in Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 L The Hub receives the patient demographic messages from the partner application and verifies the format and content of the patient demographic messages L The Hub records the patient demographic transaction and stores a copy of the discrete content of the patient demographic messages for a minimum of 90 days or longer as specified by the partner L The Hub converts the patient demographic messages to the Physician Portal format and then forwards the messages to Physician Portal l Physician Portal applies the updates to its patient database L Any validation errors that occur within Physician Portal are returned to the Hub 144 Chapter 5 Linking to Physician Portal Process Walkthrough Outbound Patient Demographic Updates The diagram below illustrates at a high level the flow of information between Physician Portal Care360 Hub Information Services and a partner application Following the diagram is a step by step walkthrough of the patient demographic processes illustrated in the diagram Receiving Patient Demographic Updates from Care360 Physician Portal Physician Office Hub Infrastructure Partner Partner Application apr Receives Patient Application Demographic Updates Car
177. icating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID R segments within a message Usually a sequential number beginning with 1 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PID 02 Patient ID External ID CX 20 When the patient is from another institution outside office etc the identifier used by that institution can be shown in this field This may be a number that multiple disparate corporations or facilities share Note Must not contain the same value as MRG 04 PID 03 Patient ID Internal ID CX 20 The primary identifier or other identifiers used by the facility to identify a patient uniquely for example medical record number billing number birth registry etc PID 04 Alternate Patient ID PID CX 20 NS PID 05 Patient Name XPN 48 No more than 48 characters wide including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name Family n
178. ication A client application created for accessing the User Summary Web service is referred to as a static Web service client because the client knows where the Web service is located without looking up the service in a UDDI registry The client calls the Web services via a known service URL to obtain the WSDL file that describes the Web services AWSDL interface document describes all of the information that is needed by a Web service client to interact with the associated Web service The WSDL document includes the URL to locate the associated Web services Once you have located the Web service or after you have obtained the WSDL you can build a Web service client application that uses the Web service to perform the desired functions The following section describes the process for obtaining the WSDL documents for User Summary Web services Note You must have a valid user name and password issued by MedPlus in order to access the WSDL interface documents For the Physician Portal Production environment a user name and password will be issued once your application has been developed tested and certified Accessing the User Summary Services WSDL Document To access the WSDL service description for the User Summary Services use your browser to access the corresponding URL shown below Using the WSDL that you obtain you can build a client application to access the Web service Staging Environment To access the User Summary Services
179. ications MSH EVN PID Correct MRG and PID Incorrect For more information see ADT A39 Patient Merge Message Segment Specifications on page 221 What s New in This Release xii Documentation Conventions About This Manual This manual uses the following conventions Manual titles special terms Web page and dialog box titles menu items toolbar button names labels that appear on Web pages and dialog boxes and keyboard key names appear in italic Italic is also used to indicate variables For example an e mail address might be presented as name company com When typing the address you would use the actual user name and company name rather than name and company Words that are being emphasized appear in bold Text that you type as well as messages and prompts that appear on the screen appear in this type style The greater than symbol gt indicates a series of menu items to click For example the instructions to click the File menu item and then click Open might be presented in the following way Click File gt Open This manual calls your attention to important information in several ways Note A note indicates exceptions to the stated rule or information that emphasizes or supplements important points in the main text A note can supply information that might apply only in special cases CAUTION A caution indicates that failure to take or avoid a specified action could result in losing data W
180. ice Usage details for each method are provided in the following section Patient Demographic Method Details e submitRealTimeADTMessage Submits a patient demographic update ADT message in HL format to Care360 Hub Information Services in real time e submitBatchADTMessage Submits a patient demographic update ADT message in HL7 format to Care360 Hub Information Services in batch mode Patient Demographic Method Details The following table provides details about each of the methods listed above Method Description submitRealTimeADTMessage Summary Submits a patient demographic update in HL7 format to Care360 Hub Information Services in real time mode Usage The InboundPatientDemographicRequest object contains the inbound patient demographic update Notes e Even if an inbound patient demographic update is accepted by the Hub it still may ultimately be rejected by Physician Portal For detailed specifications on formatting patient demographic update messages that are sent to Care360 Hub Information Services for processing see Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 Preconditions The Demographics service is configured properly in Hub Information Services Administration Method Signature DemographicResponse submitRealTimeADTMessage DemographicRequest request throws SOAPException Patient Demographic Services API 169 Method Description
181. id values for this field include e M Male e F Female e Blank The Hub verifies that one of these values is present in this field GT1 10 Guarantor Type IS NS GT1 11 Guarantor Relationship IS Describes relations to patient Valid values 1 Self 2 Spouse 8 Dependent Blank GT1 12 Guarantor SSN Chapter 9 Care360 Patient Demographic HL7 Specification ST 11 Must contain 9 numeric digits or 11 with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above Segment ID Element Name Type Length Comments Req d GT1 13 Guarantor Date Begin DT NS GT1 14 Guarantor Date End DT NS GT1 15 Guarantor Priority NM NS GT1 16 Guarantor Employer Name XPN 130 Employer name No more than 130 characters wide Alphanumeric data only GT1 17 Guarantor Employer Address 106 No more than 106 characters wide Addl 50 add2 50 city 50 state 2 zip 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above GT1 18 Guarantor Employer Phone Number XTN 40 NS GT1 19 Guarantor Employee ID Number CX 20 NS GT1 20 Guarantor Employment Status IS NS GT1 21 Guarantor Organization Name XON 130
182. ifies the SAML response and authenticates the asserted user based upon the following o Was the SAML response signed by a trusted partner The public key passed within the SAML response is sought in the Physician Portal SSO keystore If found this step succeeds This control prevents rogue third parties from forging the identities of Physician Portal customers and also thwarts man in the middle attacks that attempt to modify the SAML message in transit Implementing SAML 153 154 o Wasthe SAML response created in a timely manner Physician Portal SSO enforces a strict time tolerance window allowing only for a 180 second discrepancy between your clock and ours outside of which a SAML response is not accepted This control prevents the future posting of any intercepted and captured SAML response by a malicious third party should a security breach occur and helps to ensure that timely information transmitted Note You may specify a Conditions node within your SAML assertion to narrow the time tolerance window if you prefer The time tolerance window always reflects the narrower of the two settings o Is the partner s Issuer recognized by Physician Portal Having verified the signature of the SAML response Physician Portal is assured that the Issuer value transmitted within the SAML assertion reflects your partner profile When Physician Portal SSO locates this value in its SAML partner configuration data your site s identity is veri
183. ihood of beneficial health outcomes and minimize risk and other undesired outcomes given the existing state of medical science and art Glossary 241 242 Glossary Request ID A unique identifier that references a specific request for lab results made by an EMR system and received by Care360 Hub Information Services This identifier is assigned to a request upon receipt of the request message The Request ID is unique across all Care360 Hub Information Services accounts SAML Browser POST A data exchange model by which SAML messages are digitally signed and transmitted from the issuer EMR to the consumer Physician Portal via the user s Web browser or through some HTTP connection simulating a browser The consumer does not make a callback request to the issuer and is able to verify the SAML message using the provided signature SAML Browser Artifact A data exchange model by which SAML messages are created by an issuer EMR and an artifact small string token is transmitted to the consumer Physician Portal The consumer is then responsible for making a call back to the issuer site with the artifact so that the issuer can retrieve the actual SAML message for processing Security Assertion Markup Language SAML An XML standard for exchanging authentication and authorization data between security domains that is between an identity provider and a service provider SAML is a product of the OASIS Security Services Technic
184. ile identifieris 20001022 181520 and the data file is being created by the ABC lab abc Itis expected that only one file per dataset will be provided but in case multiple files are provided they must have unique file names e Files must have one entry record per line Data for every column should be provided on each line except when column values are blank in which case the delimiter should be sent e Column values must be delimited with the caret character e There cannot be any double quotes in the data e Following are the formats of the values allowed for the data types listed in the specific dataset formats Data Type Format bit One character 0 False 1 True char length A sequence of up to length number of ASCII characters excluding the column delimiter and double quotes datetime A date time value in the format mm dd ccyy hh mm ss decimal precision scale A number with up to precision total number of digits with up to scale number of digits after the decimal point Master File Dataset File Specifications 17 18 Data Type Format int An integer without decimals range is approximately 2 billion to 2 billion money A number with two digits after the decimal point range is approximately 1 quadrillion numeric precision scale Same as data type decimal precision scale smallint An integer without decimals in the
185. in the Physician Portal Staging environment used to develop test and certify your Web service application access the following link https portal carel80 com care360 services UserSummaryWebService WSDL Production Environment Once you have developed tested and certified your Web service client application in the MedPlus Physician Portal Staging environment you can then update the application to work in the Physician Portal Production environment Connecting a Web service client to the Physician Portal Production environment is similar to connecting to the Staging environment the exposed interfaces are equivalent Note Client applications developed against the Staging environment WSDL documents can also be used to access the Physician Portal Production environment and vice versa the WSDL content is identical in both environments To access the User Summary Services in the Production environment access the following link https portal care360 com care360 services UserSummaryWebService WSDL About the WSDL Interface Documents 237 238 About the Sample Code The Physician Portal SSO and Web Services site provides sample source code to illustrate recommended coding practices for interacting with the various SSO and Web services provided by Physician Portal Though the samples are specific to a particular SSO function or Web service they help illustrate general programming practices that can be used with any of the SSO f
186. in the target organization Physician Portal returns an error to the partner application If the incoming PID matches a single patient in the target organization that patient is deleted If the incoming PID matches more than one existing patient Physician Portal returns an error to the partner application About Patient Demographic Services 141 142 PID Only Matching Request Potential Results Merge Patients If the target organization contains no patient with the same PID for either the correct patient or the incorrect patient Physician Portal returns an error to the partner application If the target organization contains a single patient with the same PID for the correct patient and a single patient with the same PID for the incorrect patient those patients are merged If the target organization contains more than one patient with the same PID for either the correct patient or the incorrect patient Physician Portal returns an error to the partner application a You cannot delete a patient after clinical entries for example lab results have been associated with that patient or if the patient is associated with an alias patient If a delete cannot be performed due to either of these conditions an error message is returned Fuzzy Matching Detail The following table provides additional details on the rules associated with fuzzy matching for
187. insurance group number must be a five digit numeric value Additionally the trailing blanks are optional in this example Example 2 Dataset 4 column 22 is XNNNNNNNNA In this example the guarantor s insurance policy number must be ten or eleven characters Additionally the first character must be a letter or a digit characters two through nine must be digits character ten must be a letter and character eleven can be any character alpha numeric blank omitted or other Example 3 Dataset 4 column 22 is 111 NNNNNNN2 Dataset 4 column 23 is 08C4 Dataset 5 includes the following rows List ID List Value 08 WDX 08 PRX C4 1 C4 2 C4 3 C4 A In this example the guarantor s insurance policy number must be eleven characters The first three characters must be either WDX or PRX characters four through ten must be digits and character eleven must be either 1 2 3 or A About the Carrier Edit Patterns 55 Chapter 3 Care360 Order HL7 Specification In This Chapter e About the Care360 Order HL7 Specification 58 Care360 Order Message Format Requirements 59 Care360 Order Message Segment Specifications 67 e Sample Care360 Order Messages sartis essem hee ete 94 57 58 About the Care360 Order HL7 Specification This chapter provides detailed format specifications for lab orders that are su
188. ion DemographicDemo DemographicDemoOrg 20061211153336 ADT A28 m sgControlID123 P 2 3 EVN A28 199608190820 PID 1 pid123 LH Wally SHERRY M 20000101 F PETRY SHERRY 4690 Parkway Dr address line 2 Mason OH 45040 USA a2 86 999 9999999 99999 513 999 9999 a5 1 FOUND 444 66 9999 PV1 1JO GT1 1 88 Smith John M JR DR MD 3710 Emery Lake Ln Street line2 Cincinnati OH 45010 1 513 8888888 1234 1 238 4444444 5678 1 9960708112233 MJIJ8 287889999 ABC Inc Limited M 4567 Kelly Drive address line 2 Oxford OH 45068 55566677777 4556 FT Guarantor Organization INL 1 INSID123 Insurance Plan ABC INSCOID123 insuranceco 1800 Insurance Rd Detroit MI 45777 1 555 6667777 1234 3433 name 11 19960707 ELELEEEEEELEEEEEEL LEE EFL LLL FIT Sample 2 Delete Patient MSH amp SecondSub DemographicDemo DemographicDemoOrg 20070321000000 AD T A29 1 P 2 3 EVN A29 199608190820 PID 1 pid666 NEWMRN 2 LH Wally SHERRY 1 DR dkdk 20000101000000 F PETRY SHERRY B a2 1 513 8888888 9999 1 520 6666666 7777 a5 X T FOUND PV1 1JO Sample 3 Update Patient SH N amp sending application DemographicDemo DemographicDemoOrg 20061211153336 ADT A31 m sgControlID123 P 2 3 EVN A31 199608190820 PID 1 pid123 LH Wally SHERRY M 20000101153336 F PETRY SHERRY 4690 Parkway Dr Mason OH 45040 USA a2 86 999 9999999 99999 513 999 9999 a5
189. ion user is associated Usage The WSOrgData object contains the list of organizations array of WSOrg objects that is returned Method Signature WSOrgData getOrg throws SOAPException User Summary Objects The User Summary Services API provides the objects described in the following table Object Description Attributes Data Type Req d WSUserSummaryData Contains the user summary data returned from Physician Portal Responses include counts An array of WSUserSummaryCounts O WSUserSummaryCounts objects one for each organization timeStamp The date and time DateTime O at which the query was run warnMesage A message String O indicating an error condition for example the maximum number of organizations was exceeded Chapter 7 User Summary Services API Reference Object Description Attributes Data Type Req d WSUserSummaryCounts Contains the individual data counts returned within the WSUserSummaryData object Responses include newResultCount The number of new results for the organization finalAbnormalResultCount The number of final abnormal results for the organization finalNormalResultCount The number of final normal results for the organization ipAbnormalResultCount The number of abnormal results that are not yet final for the organization ipNormalResultCount The number of normal results that a
190. ional because the Hub obtains them directly from the HL7 message content The optional discrete fields may be helpful for troubleshooting purposes however as the HL7 message fields are encoded Sample XML Result Files Following are several sample third party result XML messages formatted according to the Results Formatting Requirements on page 123 Note The lt h17 gt lt primaryReport gt and lt additionalReports gt segments in the following samples are truncated for the sake of brevity Sample 1 HL7 Message with No Primary Report lt xml version 1 0 encoding UTF 8 gt tns result xmlns tns http hub care360 com 5 0 result xmlns xsi http www w3 org 2001 XMLSchema instance gt lt resultDate gt 20070209101449 lt resultDate gt lt sendingFacility gt ORDR_PVDR lt sendingFacility gt receivingFacility ORDR PVDR ACCT receivingFacility lt accessionNumber gt 1570043 lt accessionNumber gt messageControlld 8565093 messageControlld Xhl7 TVNIfF5 XCZ8TEFCfEO9SRFJfUFZEUnxURVNUSUR8T1JEUI9QVkRSXOFDOIR MDEOND18fE9SVV5SMDF80DU2NTA5M3xQfDIuMyANUELIEfDF8MTIzNDU2g5MTI V8MTU3MDA0M3x8QWJj ZGVmXkdoaWprbGlub3BeQXx8MjAwNDAxMzF8TX h17 XprimaryReport lt additionalReports lt tns result gt Chapter 4 Care360 Results HL7 Specification lt xml version 1 0 tns result xmlns tns http hub care360 com 5 0 result lt xml version 1 0 tns
191. is allowed five attempts to log in using their assigned Physician Portal credentials If the user cannot successfully log in or if the User ID that was entered is already in use a message appears indicating that the user must contact Physician Portal Customer Support in order to proceed About Linking and Single Sign On SSO 133 134 When the user successfully logs in to Physician Portal the first time their user information and obfuscated password are saved to a SAML user mapping table L After the user s information has been successfully saved to the mapping table the password is disabled When the user subsequently links to Physician Portal the Physician Portal login process is completed automatically based on their stored user credentials Q When a user links to Physician Portal via an SSO connection they can then access any Physician Portal functions that are enabled by their user credentials Accessing Physician Portal via An Established SSO Link The following steps outline the procedure and associated systems involved in accessing Physician Portal from a partner application after a user s SSO link has been initialized outlined in Initializing a User s SSO Connection on page 133 d d Chapter 5 Linking to Physician Portal A user logs in to the partner application The partner application user initiates a link to Physician Portal A link to Physician Portal can be established in one of the followi
192. is applicable only to the inbound order for patient and insurance billing The Hub verifies that all data fields are in uppercase Zip 10 A Z 0 9 only in these fields Alphanumeric data only Valid Zip formats NNNNN NNNN 5N or 9N no hyphen The Hub verifies that the value complies with rules above Segment ID Element Name Type Length Comments Req d GT1 00 Segment ST 4 Must be GTI R Type ID GT1 01 Set ID SI 4 GT1 message segments should be R numbered sequentially from 1 GT1 02 Guarantor CX 59 NS Number GT1 03 Guarantor XPN 24 No more than 24 characters wide R Name including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name The Hub verifies that the value complies with rules above GT1 04 Guarantor XPN 48 NS Spouse Name GT1 05 Guarantor XAD 97 No more than 97 characters wide R Address Add1 30 add2 30 city 25 state 2 Care360 Order Message Segment Specifications 79 Segment ID Element Name Type Length Comments Req d GT1 06 Guarantor Ph Num Home XTN 250 GT1 6 and PID 13 will use data type 250 X TN and be sub delimited in pieces 6 and 7 area code and phone number respectively The XTN data type reads as follows Components NNN 999 999 9999 X99999 B99999 C any text telecommunicatio
193. istion gt gt Less CHD CEED CEED User Logs In 5 Type Cen S Be Demo Heath Assoc User Pefernces suport whatstiew Mabe toot v 8 O zamoa d d Smoon ones oL 11 11 23 2005 21869mp a i6101001re0 it Zambrano axei Ki 11 4 10 2005 6101001 User Initiates SSO Link to Portal va reahamooo7 Mi Hampton mocse fon 11 01 02 2005 hamo7001 teahamoons 4 Hampton mogsa wi 11 116 2004 hamp coi A ealtrow iintemasre c V2 3186Patrow E cnn iyo is Specific function or default page i PR MacDonald parm a 11 30 13 2008 S19accT M1001 mohamooos i 9 Hampton mocsse i 11 09 22 2008 hamp5001 sesTWorthnea j S Worth intemakw KL 11 09 22 2004 3947Worth olololo oo oooi New Results Tm T d pinta item ton 11 09 22 2004 8124 rkman Initializing a Users SSO Connection The following steps outline the procedure and associated systems involved in initializing an SSO connection from a partner application to Physician Portal Q MedPlus issues a Physician Portal User ID and temporary Password to the partner application user L The user logs in to the partner application as before using their existing partner application username and password d The first time the user attempts to link to Physician Portal from the partner application a login page appears prompting the user to enter their assigned Physician Portal User ID and Password Note The user
194. iueS OV d ada Eau uL dE 239 IBUBX Laco isa berebiadidad A bre logdddkaeiei dBicsserRibididd ressbXbldd 245 Wed Like to Hear From VOU ousrekeseueredust iai QA wesduc dd oec ad akekes 251 About This Manual In This Section IntroducHOHl 2322 EE GG RI nx3R3eiebe SH CE eS SG Ei Ried SARE ESS e What s New in This Release eee Docuineniation CONVENTIONS e g ue eser diese ae Se Iq EORR E Ug e Abbreviations And ACFODYEHIS snos etie oboe ib eR ande Related Documentawon aw serer ERA VR eU EPOR ewe ew RU Introduction About This Manual This Care360 Universal Ordering and Resulting Programmer Reference provides information on integrating a non Quest Diagnostics service provider laboratory and or third party electronic medical record EMR into the Physician Portal product suite The integration of a third party laboratory or EMR application involves the following primary services Universal Lab Orders The ability to submit lab orders to a third party laboratory via Care360 Physician Portal or via a third party EMR application Universal Lab Results The ability to receive test results generated by a third party laboratory via Physician Portal or via a third party EMR application EMR Linking Single Sign On The ability to directly access specific functions of Physician Portal from a partner application via single sign on SSO Additional services available to a linked application include the following
195. k when it passes them through o The Hub matches the result to the corresponding Order message and inserts the extracted data into the result O Internally the Hub matches the result to the inbound order using the key fields of PID 02 OBR 02 MSH 06 in the ORU message to PID 02 OBR 02 MSH 04 of the ORM message o Ifa result cannot be matched to an order using the method described above the store and forward fields will be blank in the outbound result e The inbound order message can have five NTE internal comment segments of 60 characters each NTE segments can follow PID and OBR segments e Amaximum of 10 unique ICD 9 codes are permitted in an ORM message e Amaximum of two INI segments are permitted an ORM message While two are accepted in the short term only the first INI will be processed for billing therefore the primary insurance information must be in the first INI segment The Hub passes through two INI segments if two are received If only one INI is received only one INI is passed through Care360 Order Message Format Requirements 61 e ORC and OBR segments should be paired as follows A maximum of 35 ORC OBR pairs are permitted MSH PID ORC OBR 1 ORC OBR 1 ORC OBR 1 Q 0 OOP Q9 Q9 Newline Characters Order HL7 messages must use the carriage return CR character ASCII 0x0D to indicate a newline Order messages that contain a line feed LF character ASCII 0x0A to indicate a newline wi
196. king a button or submitting a form that correlates to a feature hosted by Physician Portal This action triggers the SAML authentication process and directs Physician Portal to serve the requested content once authentication has been achieved The requested content contains a target URI targetUri plus possible application context parameters CL The SAML assertion is created Using a SAML library or application installed within the partner application environment a SAML assertion is created This assertion contains the user iden ty Nameldentifier the partner s Issuer value and a precise and current timestamp based on Greenwich Mean Time GMT L The SAML assertion is signed The partner site s private key is used to digitally sign the SAML assertion An encoded copy of the resulting signature and an encoded copy of the partner site s public key are coupled with the SAML assertion to form a SAML response This is referred to as a SAML response as opposed to a request Refer to the Oasis web site for a detailed explanation of each L The SAML response assertion signature is transmitted to Physician Portal via HTTP SSL The SAML response is POSTed to the following URL https portal care360 com care360 Care360SSOSecurityCheck The following parameters are passed within the form using the standard application x www form urlencoded format Parameter Description Example Value Req d Default Process Control Pa
197. l duration gt start date time TS end date time TS gt priority ID gt condition ST text TX gt conjunction ID order sequencing gt Chapter 4 Care360 Results HL7 Specification Care360 Result Message Segment Specifications This section provides detailed specifications for each segment of an HL7 result message Message segments include the following Note The tables shown below contain both the HL7 2 3 and HL7 2 3 1 Specifications In cases where these specifications are identical only one specification is shown In cases where there are differences both the HL7 2 3 and HL7 2 3 1 Specification are shown in order to highlight these differences e MSH Message Header Segment on page 103 e PID Pat ent Identifier Segment on page 105 e ORC Common Order Segment on page 107 e OBR Observation Request Segment on page 110 e OBX Observation Result Segment on page 116 e NTE Notes and Comments Segment on page 119 MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID MSH 00 Element Name Segment Type ID Type ST Length 4 Comments Must be MSH Supported A MSH 01 MSH 02 Field Separator Encoding Characters ST ST 1 The separator between the message segmen
198. l Dataset File Details 47 48 Dataset 34 Setup Days File Name SETUPDAYS TXT Description Usage Provides DOS setup days of the week for the tests There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SETUP DAYS Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT CD PKI R char 10 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 R Required O Optional C Conditional Dataset 35 Setup Times File Name SETUPTIMES TXT Description Usage Provides DOS setup times for the tests There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SETUP_TIMES Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT_CD PK1 R char 10 4 Sequence number SEQUENCE NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Da
199. l Clinical Data Compendium CDO format and then copies the CDC files to its file system L The Hub retrieves the CDC files from the Lab Orders file system and records the CDC file transaction L One of the following occurs L If Lab Orders will be used for third party lab orders Lab Orders applies the updated CDC security and provisioning rules to the ordering process for the associated laboratory L Ifan external EMR will be used for third party lab orders the EMR retrieves the CDC files from the Hub and then applies the updated CDC security and provisioning rules to the ordering process for the associated laboratory Placing a Lab Order The following steps outline the procedure and associated systems involved in placing an order with a third party laboratory LJ A user logs in to Physician Portal or a third party EMR and searches for the desired patient L For Physician Portal the user can access the Lab Orders function either directly or from within the context of a specific patient L The user creates an order and selects the third party laboratory known in Lab Orders as the Performing Lab to which the order will be submitted for processing L The user submits the order and the order is created and stored in HLY format Note Orders submitted to the Hub must be formatted according to the specifications detailed in Chapter 3 Care360 Order HL7 Specification on page 57 L If necessary the
200. led specifications for each segment of an ADT A39 Patient Merge HL7 message The purpose of this message type is to enable a partner application to merge two patient records via the Hub in Physician Portal This can be used for example to merge two patient records for the same patient who was incorrectly filed under two separate PIDs Message Segment Hierarchy An ADT A39 message must follow the message segment hierarchy as specified below MSH Message Header Required one per file EVN Event Type Required PID Patient Identification Correct Required PD1 Additional Demographics Optional not supported by the Hub MRG Merge Information Required PID Patient Identification Incorrect Required Inbound Only PV1 Patient Visit Optional not supported by the Hub In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional Message Segment Specifications This section provides detailed specifications for each segment of an ADT A39 Patient Merge message Message segments supported by the Hub include the following e MSH Message Header Segment on page 222 e EVN Event Type Segment on page 224 e PID Patient Identification Segment Correct on page 224 e MRG Merge Patient Information Segment on page 227 e PID Patient Identification Segment Incorrect on page 228 Note ADT A39 message segments that ar
201. lication to interact with Physician Portal via SSO and Web Services This chapter provides an overview of each of the tools provided on the Physician Portal SSO and Web Services site as well information about accessing the site online Note For information about linking a partner application to Physician Portal see Chapter 5 Linking to Physician Portal on page 129 234 Chapter 10 Care360 SSO and Web Services Site Accessing the Care360 SSO and Web Services Site The Example SSO Care360 Stage application in addition to a number of other resources for partners who are developing applications to interact with Physician Portal is available for download from the Physician Portal SSO and Web Services site The Example SSO application as well as the complete source code are provided as individual zip files and require a valid username and password provided by MedPlus for access In addition to providing access to the Example SSO application the Care360 SSO and Web Services site provides additional Physician Portal related information and resources such as the following e What s New A list of the latest Physician Portal changes and related announcements e Support Contact information for various members of the Physician Portal support team links to the WSDL documents for both the Stage and Production environments and a PDF version of this Programmer Reference e Resources Downloads of the latest Example SSO Care360 Stage
202. lies Al Alergies Patient ID Bridge t Bridge All Messages Faxes Tasks Write a Prescription Write a Lab Order Demography Billing Flowsheet Graph Patient Information Contact Information Last Name Brinkman Address Line 1 222 N Franklin St FirstName Rose Address Line2 ap12 Middle Initial City Winamac Add New Patient Move Clinical Activities Quest Retrieve External History Yes State Province Region Indiana Qe agnostics DateofBirth oznorszs 12 zip PostalCode 47725 Gender Female Country united States EN g Marital Status Email Mathes Manis Nome Uoma Mhann ris cer Eeee B trusted sites In This Chapter e About the Care360 Patient Demographic HL7 Specification 174 e Care360 Patient Demographic Message Format Requirements 175 e ADT A28 Patient Add Message Segment Specifications ADT A29 Patient Delete Message Segment Specifications 195 ADT A31 Patient Update Message Segment Specifications 204 ADT A39 Patient Merge Message Segment Specifications e Sample Care360 Patient Demographic Messages 231 173 174 About the Care360 Patient Demographic HL7 Specification This chapter provides detailed format specifications for patient demographic add delete update and merge requests that are received by Care360 Hub Information Services from a partner application Patient demographic
203. ll be rejected Field Delimiters A delimiter must separate each field Even if a field contains no data it must still be delimited The delimiter for any given HL7 message is always defined in the MSH segment of the message as the first character following the segment identifier MSH 00 See the message segment descriptions for more detail Standard HL7 delimiters are used Note The standard HL7 delimiters amp are not accepted as valid data in any field except MSH 02 Chapter 3 Care360 Order HL7 Specification Field Specifications The following table describes the parameters used to define the data fields within each message segment Parameter Description Type For a description of the data types see Data Type Specifications on page 64 Length The maximum allowed length for the field Required The fields within each segment are classified based on their requirement status of Required R Optional O Conditional C or Not Supported NS as defined below e Required If the corresponding segment is present the field must also be present within the segment and the Hub validates it against any stated requirements If the field is not present the message is rejected by the Hub e Optional The field is not required the segment is accepted by the Hub whether or not this field is present If the field is present the Hub validates it against any stated requirements The contents of this field
204. llector s CE 200 N Comment OBR 40 Transport CE 60 N Arrangement Responsibility OBR 41 Transport ID 30 N Arranged OBR 42 Escort Required ID 1 N OBR 43 Planned Patient CE 200 N Transport Comment a For a description of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never OBX Observation Result Segment This segment is optional AOEs in the order are typically captured as OBX segments observation value OBX 05 Valid values include e ST String data e NM Numeric data e CE Coding element e TX Text data Type Segment ID Element Name a Length Comments Supported OBX 00 Segment Type ID ST 10 Must be OBX A OBX 01 Set ID SI 10 Sequence number for OBX A segments grouped beneath the same OBR segment OBX 02 Value Type ID 2 Defines the structure of the A Chapter 4 Care360 Results HL7 Specification Segment ID Element Name Type a Length Comments Supported OBX 03 03 1 03 2 03 3 03 4 03 5 03 6 Observation Identifier LOINC Code LOINC Description Coding System Name Local Code Local Description Coding System Name CE 590 Contains the analyte number and analyte name Data layout LOINC Code Description Coding System Local Code Description Coding System The Local Code 03 4 must always be present but all other sub fields are optional
205. lts HL7 Specification Segment ID Element Name Type Length Comments Supported OBR 16 Ordering Provider XCN 120 Identifies the provider that ordered the test If present in the inbound order the result echoes this value Version 2 3 e Format for UPIN Only UPIN Number LastName F irstName Middle UP IN e Format for NPI Only NPI Number LastName FirstName Middle N PI e Format for UPIN and NPI UPIN Number LastName F irstName Middle UP IN NPINumber LastName Middle QUSSTSARTRT Version 2 3 1 Literal UPIN or NPI moved from subfield 9 to subfield 13 Example 2 8 RC RE 0001 SL123456A C P12203 BOWKER DA UPIN III III xample 2 3 1 RC RE 0001 SL123456A C Ll 111 P12203 BOWKER DA AAAAAAAAAAUPING IL If the Send Provider Identifier option for a Hub account is set to either UPIN or NPI the Hub removes the opposing identifier if present For example if UPIN is selected the Hub will remove the NPIif it is returned SEO HW SzO If the option is set to Both then the Hub passes it through with no modification C OBR 17 Order Callback Phone Number XTN 40 OBR 18 Placer field 1 ST 60 Used as a store and forward field Not supported for results only interfaces OBR 19 Placer field 2 ST 60 Used as a store and forward field Not supported for re
206. m WebDAV Web based Distributed Authoring and Versioning WSDL Web Services Definition Language XML eXtensible Markup Language Abbreviations and Acronyms XV xvi Related Documentation About This Manual In addition to this Programmer Reference the following resources are also available for the individual components of Care360 Integration Services Care360 Hub Information Services Programmer Reference Provides information on creating client applications that interact with Care360 Hub Information Services It is intended for programmers who write client applications to communicate with Care360 Hub Information Services via the Orders Lab Results and or Prescription Web services Primarily intended for applications that interact with Quest Diagnostics laboratories Care360 Hub Information Services Administrator Manual Provides information on using Hub Information Services Administration to configure and manage Hub accounts providers vendors and users It is intended for MedPlus Professional Services Group PSG personnel or other designated administrative personnel who are responsible for initial and ongoing Care360 Hub Information Services administration Care360 Physician Portal User Manual Provides information on accessing and using the Physician Portal application which includes the integrated Lab Ordersfunction Intended for end users of the application including physicians clinicians phlebotomists clinical o
207. mber PV1 06 Prior Patient PL 80 NS Location PV1 07 Attending XCN 60 NS Doctor PV1 08 Referring Doctor XCN 60 NS PV1 09 Consulting XCN 60 NS Doctor PV1 10 Hospital Service IS 3 NS PV1 11 Temporary PL 80 NS Location PV1 12 Preadmit Test IS 2 NS Indicator PVI 13 Readmission IS 2 NS Indicator PV1 14 Admit Source IS 3 NS PV1 15 Ambulatory IS 2 NS Status PV1 16 VIP Indicator IS 2 NS PV1 17 Admitting XCN 60 NS Doctor PV1 18 Patient Type IS 2 NS PV1 19 Visit Number CX 20 NS PV1 20 Financial Class FC 50 NS PV1 21 Charge Price IS 2 NS Indicator PV1 22 Courtesy Code IS 2 NS PV1 23 Credit Rating IS 2 NS PV1 24 Contract Code IS 2 NS PV1 25 Contract DT 8 NS Effective Date PV1 26 Contract Amount NM 12 NS Segment ID Element Name Type Length Comments Req d PV1 27 Contract Period NM 3 NS PV1 28 Interest Code IS 2 NS PV1 29 Transfer to Bad IS 1 NS Debt Code PV1 30 Transfer to Bad DT 8 NS Debt Date PV1 31 Bad Debt Agency IS 10 NS Code PV1 32 Bad Debt NM 12 NS Transfer Amount PV1 33 Bad Debt NM 12 NS Recovery Amount PV1 34 Delete Account IS 1 NS Indicator PV1 35 Delete Account DT 8 NS Date PV1 36 Discharge IS 3 NS Disposition PV1 37 Discharged to CM 25 NS Location PV1 38 Diet Type IS 2 NS PV1 39 Servicing Facility IS 2 NS PV1 40 Bed Status IS 1 NS PV1 41 Account Status IS D NS PV1 42 Pending PL 80 NS Location
208. mit Test IS 2 NS Indicator PVI 13 Readmission IS 2 NS Indicator PV1 14 Admit Source IS 3 NS PV1 15 Ambulatory IS 2 NS Status PV1 16 VIP Indicator IS 2 NS PV1 17 Admitting XCN 60 NS Doctor PV1 18 Patient Type IS 2 NS PV1 19 Visit Number CX 20 NS PV1 20 Financial Class FC 50 NS PV1 21 Charge Price IS 2 NS Indicator PV1 22 Courtesy Code IS 2 NS PV1 23 Credit Rating IS 2 NS PV1 24 Contract Code IS 2 NS PV1 25 Contract DT 8 NS Effective Date PV1 26 Contract Amount NM 12 NS ADT A31 Patient Update Message Segment Specifications 211 212 Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 27 Contract Period NM 3 NS PV1 28 Interest Code IS 2 NS PV1 29 Transfer to Bad IS 1 NS Debt Code PV1 30 Transfer to Bad DT 8 NS Debt Date PV1 31 Bad Debt Agency IS 10 NS Code PV1 32 Bad Debt NM 12 NS Transfer Amount PV1 33 Bad Debt NM 12 NS Recovery Amount PV1 34 Delete Account IS 1 NS Indicator PV1 35 Delete Account DT 8 NS Date PV1 36 Discharge IS 3 NS Disposition PV1 37 Discharged to CM 25 NS Location PV1 38 Diet Type IS 2 NS PV1 39 Servicing Facility IS 2 NS PV1 40 Bed Status IS 1 NS PV1 41 Account Status IS D NS PV1 42 Pending PL 80 NS Location PV1 43 Prior Temporary PL 80 NS Location PV1 44 Admit TS 26 NS Date Time P
209. n Portal is optional When a user accesses directly there is no connection established to a partner application and Physician Portal may appear in its default format that is with no custom UI branding L The user can access any Physician Portal functions that are enabled by their user credentials About Linking and Single Sign On SSO 135 136 About User Summary Services When new lab results or user messages are received by Physician Portal for a user or an organization the partner application can automatically receive notification of their availability These user summary notifications enable the partner application to display related counts for affected patients rather than requiring users to access Physician Portal on a regular basis to view the information When the user summary notification indicates that new information is available within Physician Portal the user can access the desired Physician Portal function to view the associated data Specific data counts that can be communicated to the partner application include the following e New results including Abnormals Partials Partials Abnormals and Finals Message counts including user messages and failed faxes e Action Items including Failed Faxes Pending Renewals and Pending Approvals If a notification of new results is received for example the user can link directly to the Physician Portal New Results page New results can be viewed for all associated se
210. n Services provides a standards based platform for the submission of lab orders and for the request and delivery of lab results data The Care360 Hub Information Services platform also provides a framework for hosting a number of additional centralized healthcare related services Chapter 1 Universal Ordering and Resulting About the Universal Ordering and Resulting Data Flow Client EMRs This section provides a high level overview of the processes involved in sending orders to and receiving results from third party non Quest Diagnostics laboratories via Universal Ordering and Resulting A Physician Portal or third party EMR user can submit a lab order to a third party laboratory by specifying the desired laboratory when placing the order Valid third party laboratories can include hospital labs physician office labs or independent labs Process Walkthrough Universal Ordering and Resulting The diagram below illustrates at a high level the flow of orders and results to third party laboratories Following the diagram is a step by step walkthrough of each of the three major processes Master Files orders and results illustrated in the diagram Universal Lab Orders and Results Lab Physician Office Care360 Physician Portal Lab Orders Third Party EMR Hub Infrastructure Third Party Labs Hub Receives Hub Submits Order to Third Party Lab Order Third Party Lab Hub Echoes one L
211. n update the application to work in the Hub Production environment Connecting a Web service client to the Production Hub environmentis similar to connecting to the Staging environment the exposed interfaces are equivalent Note Client applications developed against the Staging environment WSDL documents can also be used to access the Production Hub environment and vice versa the WSDL content is identical in both environments To access the Patient Demographic Services in the Production environment access the following link https hubservices medplus com demographic service wsdl Chapter 8 Patient Demographic Services API Reference Chapter 9 Care360 Patient Demographic HL7 Specification Patient Summary Microsoft Internet Explorer File gdt View Favorites Tools Help Q Back DG seach krae 8 3 30D 8 3 ffowew care360 com Be jy Car e360 Welcome Any User Demo Health Assoc User Preferences Support Whats New Help Logout A Medus Solution Quickview SES Name Lab Orders gt Quick View gt New Results gt Find s Patient gt Patient Summary Demographics DOB SSN Search is E Message FG Fax nda Patent p Brinkman Rose vew sumay phr ado Edt Bort cc Patient Sitar Address 222 N Franklin St Apt 12 Winamac IN 47725 Phone 513 555 5555 DOB 02 10 1925 Age 83y Gender F PID 1internalRB Demographics Patient Problems Al Lab Reports All Meds Supp
212. n use code ID gt telecommunication quipment type ID e mail address ST country code NM area city code NM phone number NM gt extension NM gt any text ST For backward compatibility phone numbers sent in the 10 NM format e g 31487217277 or any of the following variations for sending data in the XTN data format will also be accepted 354 8 0277127 5 656 Or 3148727127 314 8727127 or 314 8727121 Or 3148727127 The Hub verifies that the value complies with rules above GT1 07 Guarantor Ph Num Business XTN 40 NS GT1 08 Guarantor Date Time Of Birth TS 26 The date and time of the guarantor s birth Format YY YYMMDDHHMMSS The Hub verifies that the date time is in this format GT1 09 Guarantor Sex IS Valid values for this field include e M Male e F Female The Hub verifies that one of these values is present in this field GT1 10 Guarantor Type IS NS GT1 11 Chapter 3 Care360 Order HL7 Specification Guarantor Relationship IS NS Segment ID Element Name Type Length Comments Req d GT1 12 Guarantor SSN ST 11 NS GT1 13 Guarantor Date Begin DT NS GT1 14 Guarantor Date End DT NS GT1 15 Guarantor Priority NM NS GT1 16 Guarantor Employer Name
213. nal Data Type Category Data Type Name Notes Format Alphanumeric ST String Any ACSII printable characters ASCII decimal values between 32 and 126 with the exception of the defined delimiter characters Left justified with optional trailing spaces FT Formatted text String data with embedded formatting instructions Numerical CQ Composite quantity quantity NM gt units CE gt with units NM Numeric Any of the ASCII numeric characters with an optional leading sign or and or an optional decimal point SI Sequence ID A non negative integer in the form of a NM data type Identifier ID Coded values for String data drawn from an HL7 defined table of legal values see HL tables Appendix A of HL7 2 3 IS Coded values for String data drawn from a site defined table of legal values user defined tables HD Hierarchic namespace ID IS gt universal ID ST gt designator universal ID type ID gt Used only as part of EI and other data types EI Entity identifier entity identifier ST namespace ID IS universal ID ST universal ID type ID PL Person location Xpoint of care IS room IS bed IS facility HD location status IS gt person location type IS building IS floor IS location description ST gt PT Processing type Xprocessing ID ID processing mode ID
214. nal ID identifiers used by the facility to identify a patient uniquely for example medical record number billing number birth registry etc PID 04 Alternate CX 20 NS Patient ID PID PID 05 Patient Name XPN 48 No more than 48 characters wide R including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above PID 06 Mother s XPN 48 NS Maiden Name PID 07 Date of Birth TS 26 Date of birth DOB in YYYYMMDD O format The Hub verifies that the DOB is in this format Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID Element Name Type Length Comments Req d PID 08 Sex IS 1 Valid values for this field include O e M Male e F Female e Blank The Hub verifies that one of these values is present in this field PID 09 Patient Alias XPN 48 Patient alias name O PID 10 Race IS 1 NS PID 11 Patient Address XAD 106 No more than 106 characters wide O Add1 50 add2 50 city 50 state 2 zp 10 country code 3 Alphanumeric data only The Hub verifies that the value complies with rules above PID 12 County Code IS 4 NS PID 13 PhoneNumber XTN 40 Accepted le
215. nclude O A Z and 1 0 IN1 09 Group Name XON 130 NS Care360 Order Message Segment Specifications 76 Segment ID Element Name Type Length Comments Req d IN1 10 Insured s Group CX 12 NS Emp ID IN1 11 Insured s Group XON 18 If present the Hub passes the value O Emp Name through with no validation IN1 12 Plan Effective DT 8 NS Date INI 13 Plan Expiration DT 8 NS Date INI 14 Authorization CM 55 NS Information INI 15 Plan Type IS 3 NS IN1 16 Name Of XPN 24 Should be at most 24 characters wide C Insured including the delimiter between the last and first names At least one character for first and last name A numeric value cannot be used as the first character of the last name The Hub verifies that the value complies with rules above Required only if IN1 47 T Third Party Bill INI 17 Insured s IS 2 Valid values for this field include C Relationship To e Self Patient e 2 Spouse e 8 Dependent The Hub verifies that this value is present Required only if IN1 47 T Third Party Bill INI 18 Insured s Date TS 26 NS Of Birth IN1 19 Insured s XAD 106 No more than 106 characters wide O Address Add1 30 add2 30 city 25 state 2 Zip 10 A Z 0 9 only in these fields Alphanumeric data only Valid Zip formats NNNNN NNNN 5N or 9N no hyphen The Hub verifies that the value complies with rules above IN1 20 As
216. nds a request to Physician Portal for associated user data Q C Physician Portal returns the requested user data to the partner application d During the user s current session the partner application can either allow the user to manually refresh the data displayed or it can send automatic refresh requests on a predefined basis About User Summary Services 137 About Order Echo When the user of a partner application links to Physician Portal to place a lab order that order can be echoed back to the partner application Order echo involves Physician Portal sending a copy of the order back to the partner application so that it can store a record of the order for the associated patient Benefits of order echo include the following e Enables the partner application to store a copy of each order placed through the Lab Orders function of Physician Portal to the patient s chart e Improves patient records management and office workflow e Eliminates the need for redundant data entry e Stores order data in standard HL7 format so that it can be easily reused as needed Order messages that are echoed back to the partner application are formatted according to the specifications detailed in Chapter 3 Care360 Order HL7 Specification on page 57 Process Walkthrough Order Echo The diagram below illustrates at a high level the flow of order data between Physician Portal and a linked partner application Following the diagr
217. ng ways L The link can open Physician Portal directly to a specific function For example the Home page the Lab Orders page the New Results page the Patient Summary page or the Action Items Inbox For Lab Orders the current patient context may be maintained if an appropriate match can be determined based on the supplied patient identifier PID L The link can open Physician Portal with no specific function specified In this case the user s default page as configured in the Physician Portal appears Physician Portal opens either in a separate browser window or framed within the context of the partner application if the required 1024x768 resolution can be maintained The user can then access any Physician Portal functions that are enabled by their user credentials Accessing Physician Portal Directly The following steps outline the procedure and associated systems involved in accessing Physician Portal directly outside the context of a linked application L MedPlus issues a user a separate Password associated with either their existing Physician Portal User ID or a separate User ID L The user logs in to Physician Portal directly with their assigned User ID and Password Note The Physician Portal password is not the same password used to initialize or maintain the SSO link from the partner application The User ID may or may not be the same as used for SSO linking Allowing a user direct access to Physicia
218. ngth of this field is 40 O Home numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt lt area city code NM phone number NM gt extension NM gt PID 14 PhoneNumber XTN 40 Accepted length of this field is 40 O Business numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM lt area city code NM phone number NM gt extension NM gt PID 15 Language CE 60 NS Patient PID 16 Marital Status IS 1 NS PID 17 Religion IS 3 NS PID 18 Patient Account CX 20 NS Number ADT A31 Patient Update Message Segment Specifications 209 Segment ID Element Name Type Length Comments Req d PID 19 SSN Number ST 16 Must contain 9 numeric digits or 11 O Patient with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22 Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 NS Indicator PID 25 Birth Order NM 2 NS PID 26 Citizenship IS 4 NS PID 27 Veterans CE 60 NS Military
219. nition 100 Patient Consent definition 241 Patient context maintaining 132 Patient demographic access the WSDL 172 ADT A28 Patient Add message specifications 179 194 ADT A29 Patient Delete message specifications 195 203 ADT A31 Patient Update message specifications 204 220 ADT A39 Patient Merge message specifications 221 230 Care360 HL7 specification 174 message segment requirements 175 sample messages 231 232 Patient demographic integration x 130 batch mode 140 methods 141 overview 140 process walkthrough 144 real time mode 140 Patient demographic message segment requirements EVN fields ADT A28 182 182 EVN fields ADT A29 198 198 EVN fields ADT A31 207 207 EVN fields ADT A39 224 224 GTI fields ADT A28 188 191 GTI fields ADT A31 213 217 INI fields ADT A28 192 194 IN1 fields ADT A31 217 220 MRG fields ADT A39 227 228 MSH fields ADT A28 180 182 MSH fields ADT A29 196 197 MSH fields ADT A31 205 207 MSH fields ADT A39 222 223 PID fields ADT A28 183 185 PID fields ADT A29 198 201 PID fields ADT A31 208 210 PID fields ADT A39 224 227 228 230 PV1 fields ADT A28 185 188 PV1 fields ADT A29 201 203 PV1 fields ADT A31 210 213 Patient Demographic Services API 169 171 methods 169 objects 170 171 Patient Identifier segment see PID Patient Visit Data segment see PV1 Payor definition 241 Performing Site Code dataset Master Files 41 42 Performing Site dataset Master Files 4
220. nizational 151 Turnaround Times dataset Master Files 49 U UDDI Universal Description Discovery and Integration definition 243 UI customization see Physician Portal UI customization Universal Lab Orders x Universal Lab Orders and Results overview 4 process walkthrough 5 niversal Lab Resulting x pdate patient sample patient demographic message 231 ser definition 243 ser Interface Customization see Physician Portal UI Customization ser Summary Services x 130 access the WSDL 237 API 163 166 methods 163 objects 164 166 overview 136 process walkthrough 137 Ci se G GG V Vendor definition 243 w Walkthrough process see Process walkthrough What s new in this release xi Worklist Components dataset Master Files 43 WSDL Web Services Description Language about obtaining the WSDL document 172 237 access the Patient Demographic Services WSDL documents 172 access the User Summary Services WSDL documents 237 definition 243 patient demographic connectivity 140 WSOrg object description 166 WSOrgData object description 165 WSUserSummaryCounts object description 165 WSUserSummaryData object description 164 X XML definition 243 sample result messages 124 XML Parser definition 243 XML Schema results 123 Index 249 We d Like to Hear From You After you have had a chance to use the Manuals and or Help for this product please take a moment to give us your comments Respond to the
221. nt ID Element Name Type Length Comments Req d PID 25 Birth Order NM 2 NS PID 26 Citizenship IS 4 NS PID 27 Veterans CE 60 NS Military Status PID 28 Nationality CD 80 NS PID 29 Patient Death TS 26 NS Date amp Time PID 30 Patient Death ID 1 NS Indicator a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PV1 Patient Visit Data Segment The Patient Visit Data PV1 segment is used by registration patient administration applications to communicate information on a visit specific basis This segment can be used to send multiple visit statistic records to the same patient account or single visit records to more than one account Segment ID Element Name Type Length Comments Req d PV1 00 Segment Type ID ST 4 Must be PVI1 R PV1 01 Set ID SI 4 Will always be 1 O PV1 02 Patient Class IS 1 Examples of valid values R E Emergency I Inpatient O Outpatient PV1 03 Assigned Patient PL 80 NS Location PV1 04 Admission Type IS 2 NS PV1 05 Preadmit CX 20 NS Number PV1 06 Prior Patient PL 80 NS Location PV1 07 Attending XCN 60 NS Doctor PV1 08 Referring Doctor XCN 60 NS PV1 09 Consulting XCN 60 NS Doctor PV1 10 Hospital Service IS 3 NS ADT A29 Patient Delete Message Segment Specifications 201 202
222. ntsByOrg method description 164 getOrgs method description 164 GTI field requirements order 79 83 field requirements patient demographic 188 191 213 217 segment requirements order 60 Guarantor segment see GT1 Hand Written Order dataset Master Files 49 HI Health Level 7 Care360 Order specification 58 Care360 Patient Demographic specification 174 Care360 result specification 98 definition 240 newline character 62 99 order message segment requirements 59 66 patient demographic message segment requirements 175 result message segment requirements 99 Hold PSC orders 68 Hospital Information System HIS definition 240 Hospital definition 240 Hub Production environment 172 Staging environment 172 Hub account definition 240 Hub ID definition 240 Hub Information Services 4 l INI field requirements order 75 78 field requirements patient demographic 192 194 217 220 segment requirements order 60 Initialize SSO connection 133 Insurance segment see IN1 Interface definition 240 L Lab Orders page linking to 130 130 LCP MN CPT To ICD9 dataset Master Files 33 LCP MN Service To CPT Dataset dataset Master Files 32 Line feed 62 99 Linking available functions 130 formatting requirements 131 overview 130 135 process walkthrough 133 Logical Observation Identifers Names and Codes LOINC definition 241 Logo customizing 146 M Management Information System MIS definition 241 Master Files Alte
223. ollowing updates Outbound Patient Demographic Updates Patient demographic updates can now be received by partner applications from Physician Portal Outbound patient demographic updates are communicated to the partner application through Care360 Hub Information Services which maintains a record of all patient demographic transactions Any errors that occur when the updates are communicated to the partner application are returned to the Hub For more information see About Patient Demographic Services on page 140 e Patient Demographic HL7 Specification The Care360 Patient Demographic HL7 Specification has been modified The field lengths and or comments have been changed in the following sections o ADT A28 Patient Add Message Segment Hierarchy Updated Message Segment Specifications MSH EVN PID GTI and INI For more information see ADT A28 Patient Add Message Segment Specifications on page 179 o ADT A29 Patient Delete Message Segment Hierarchy Updated Message Segment Specifications MSH EVN and PID For more information see ADT A29 Patient Delete Message Segment Specifications on page 195 O ADT A31 Patient Update Message Segment Hierarchy e Updated Message Segment Specifications MSH PID GT1 and INI For more information see ADT A31 Patient Update Message Segment Specifications on page 204 O ADT A39 Patient Merge Message Segment Hierarchy e Updated Message Segment Specif
224. ompliance review and approval About Single Sign On SSO When a partner application establishes a link to Physician Portal the user of the partner application can transparently log in to Physician Portal via the SSO capability That is the user is not required to log in separately to Physician Portal in order to use its services This allows the user s workflow to continue uninterrupted and reduces the number of steps and pages necessary for the user to complete a task About Linking and Single Sign On SSO 131 132 The basic steps to establish an SSO connection to Physician Portal are as follows L An authorized user logs in to the partner application L The partner application performs user authentication in the background to Physician Portal L Within the partner application the user activates a link to the desired Physician Portal function and is immediately redirected to the appropriate area of Physician Portal If possible the user s current patient context is maintained within the selected Physician Portal function see Maintaining Patient Context below Note Authentication to Physician Portal is managed through the Sun Java System Access Manager which utilizes the Security Assertion Markup Language SAML single sign on protocol using 128 bit encryption For details on establishing an SSO connection to Physician Portal see Chapter 6 Physician Portal SSO Specification on page 149 Maintaining Pati
225. order can be printed and delivered manually to the third party laboratory rather than being submitted electronically Chapter 1 Universal Ordering and Resulting Q Ata predefined time interval the Hub retrieves the HL7 order and verifies the format and content of the order L The Hub records the order transaction and stores a copy of the discrete content of the order for a minimum of 90 days or longer as specified by the laboratory L For orders placed using Lab Orders the Hub can echo return a copy of the order to a partner application L The Hub submits the order to the specified third party laboratory file system for processing Note The order that is submitted to the laboratory is formatted according to the specifications detailed in Chapter 3 Care360 Order HL7 Specification on page 57 L If the third party laboratory requires a separate billing feed the Hub can deliver a copy of the order to the lab s billing system L The third party laboratory retrieves the order from its file system and processes the order Receiving Lab Results The following steps outline the procedure and associated systems involved in accessing and viewing results received from a third party laboratory L After the third party laboratory has processed the order it copies the results to its file system Notes e Results submitted to the Hub must be formatted according to the specifications detailed in Chapter 4
226. owser process for use on subsequent requests After the user has accessed Physician Portal from the partner application link the user may remain within Physician Portal and perform any other tasks he she is authorized to perform based upon the Physician Portal user access rights previously configured About Session Timeouts and Terminations A user who connects to Physician Portal via an SSO link is subject to the same timeout conditions as they would if they were to access Physician Portal directly When a directly accessed session times out Physician Portal displays the login page For an SSO authenticated session Physician Portal displays a page indicating that the user has timed out but it does not allow the user to re enter their login credentials A similar message appears if the user clicks Log Out within Physician Portal after authenticating via SSO The message presented to the user indicates that in order to begin a new session the user must return to the partner application and click a Physician Portal link Doing so results in a new SSO authentication request to Physician Portal It is quite possible that users who interact with Physician Portal only via links from the partner application will not be aware that a session timeout has occurred Each time a link from the partner application to Care360SSOSecurityCheck is invoked a new SAML assertion is passed using an HTML FORM of the type discussed above Usage Scenario 1 Physic
227. p equiv Content Type content text html charset UTF 8 gt lt meta gt lt title gt Care360 lt title gt lt head gt lt body bgcolor FFFFFEF gt lt body gt lt html gt Usage Scenario 2 Physician Portal SSO for Web Services 157 158 Following are a few details from the traffic example on the previous page e AUser Agent header must be specified Physician Portal authentication will fail if this header is not provided The header value is not important so you may specify anything you want as long as it is unique and does not match that of any popular Web browser e A X Care360 IsForWebService header must be specified in order to prevent concurrentsession termination issues as the user will likely be using Physician Portal within a Web browser as well e The targetUri parameter is not needed However if provided it will be ignored A blank HTML page is returned regardless upon successful authentication Only the Physician Portal session cookies Set Cookie response headers are important within an HTTP response indicating success The session cookies are passed back to the Physician Portal server on a subsequent Web service request Example 2 Traffic of HTTP SSL Request to User Summary Service Following Authentication REQUEST POST care360 services UserSummaryWebService HTTP 1 0 Host localhost 7001 Content Type text xml charset UTF 8 Content Length 400 Connection Keep Alive SOA
228. page 231 Chapter 9 Care360 Patient Demographic HL7 Specification Care360 Patient Demographic Message Format Requirements In addition to the field level validation detailed in this chapter each patient demographic message is validated by the Hub to ensure compliance with rules outlined in this section The following requirements apply to all of the patient demographic message types supported by the Hub Newline Characters Patient demographic HL7 messages must use the carriage return CR character ASCII 0x0D to indicate a newline Patient demographic messages that contain a line feed LF character ASCII 0x02 to indicate a newline will be rejected Field Delimiters A delimiter must separate each field Even if a field contains no data it must still be delimited The delimiter for any given HL message is always defined in the MSH segment of the message as the first character following the segment identifier MSH 00 See the message segment specifications later in this chapter for more detail Standard HL7 delimiters are used Field Specifications The following table describes the parameters used to define the data fields within each message segment Parameter Description Type For a description of the data types see Data Type Specifications on page 176 Length The maximum allowed length for the field Required The fields within each segment are classified based on their requirement status of Required R
229. parator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by the Hub MSH 03 Sending EI Application MSH 04 The sending facility This is the account Sending Facility EI 180 180 The name of the sending application The Hub verifies that this field is populated number s defined for the placer The Hub verifies that this field is populated Care360 Order Message Segment Specifications 67 68 Segment ID Element Name Type Length Comments Req d MSH 05 Receiving Application EI 180 The receiving application identifier For Basic Lab Orders the Hub verifies that this field is blank For PSC Hold Orders this field must be populated with PSC C MSH 06 Receiving Facility EI 180 The receiving facility The three letter ID of the facility that performs the test The Hub verifies that this field is populated MSH 07 Date Time of Message TS 26 The date and time that the sending system created the message Format YYYYMMDDHHMMSS The Hub verifies that this field is populated and that the value complies with the format above MSH 08 Security ST 40 NS MSH 09 Message Type CM The type of message being transmitted and the event leading to the creation of the message A
230. patient demographic updates Fuzzy Matching Request Potential Results Add Patient If Physician Portal finds no high confidence match between existing patients in the target organization and the incoming patient demographics the patient is added If Physician Portal finds a high confidence match between a single patient in the target organization and the incoming patient demographics the matching patient is updated If Physician Portal finds more than one existing patient that has a high confidence or ambiguous match with the incoming patient demographics Physician Portal adds the patient and marks the patient as a potential duplicate If Physician Portal finds an ambiguous match between the incoming patient demographics and a single patient in the target organization Physician Portal adds the patient and marks the patient as a potential duplicate Update Patient If Physician Portal finds no high confidence match between existing patients in the target organization and the incoming patient demographics the patient is added If Physician Portal finds a high confidence match between a single patient in the target organization and the incoming patient demographics the matching patient is updated If Physician Portal finds more than one existing patient that has a high confidence or ambiguous match with the incoming patient demographics Physician Portal adds the patient and marks the patient as a potent
231. priority ID gt condition ST text TX gt conjunction ID order sequencing Chapter 3 Care360 Order HL7 Specification Care360 Order Message Segment Specifications This section provides detailed specifications for each segment of an HL7 order message Message segments include the following e MSH Message Header Segment on page 67 e PID Pat ent Identifier Segment on page 69 e PV Patient Visit Data Segment on page 72 e INI Insurance Segment on page 75 e GT1 Guarantor Segment on page 79 e ORC Common Order Segment on page 84 e OBR Observation Request Segment on page 86 e OBX Observation Result Segment on page 90 e DGl Diagnosis Segment on page 91 e NTE Notes and Comments Segment on page 93 MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID Type Element Name MSH 00 Segment Type ID ST Length 4 Comments Must be MSH Req d R MSH 01 Field Separator ST 1 The separator between the message segment ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value isa vertical bar R MSH 02 Encoding ST Characters Four characters that are used in the following order component se
232. provides detailed specifications for each segment of an ADT A28 Patient Add message Message segments supported by the Hub include the following e MSH Message Header Segment on page 180 e EVN Event Type Segment on page 182 e PID Pat ent Identification Segment on page 183 e PV Patient Visit Data Segment on page 185 e GT1 Guarantor Segment on page 188 e INI Insurance Segment on page 192 Note ADT A28 message segments that are not supported by the Hub are not included in this section for detailed specifications refer to the HL7 2 3 Specification MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID Element Name Type Length Comments Req d MSH 00 Segment Type ID ST 4 Must be MSH R MSH 01 Field Separator ST 1 The separator between the message segment ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value isa vertical bar R MSH 02 Encoding Characters ST Four characters that are used in the following order component separator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by Quest Diagnostics MSH
233. ption of the HL7 data types see Data Type Specifications on page 100 b A Always C Conditional PT Pass Through N Never OBR Observation Request Segment One OBR segment must be transmitted for each Order Code associated with any PID segment This segment is mandatory in ORU messages Segment ID Element Name Type Length Comments Supported OBR 00 Segment Type ID ST 4 Must be OBR A OBR 01 Set ID SI 4 OBR segments grouped under a A PID are numbered sequentially beginning with 1 OBR 02 Placer Order EI 22 The placer application s order PT Number number Same as ORM If different values are present in the ORM in ORC 02 and OBR 02 then all values are rolled into a single value OBR 03 Filler Order EI 22 The order number associated A Number with the filler s application Same as ORC 03 Chapter 4 Care360 Results HL7 Specification Segment ID Element Name Type Length Comments Supported OBR 04 Universal Service ID CE 200 Identification code for the ordered test One order code per OBR segment Version 2 3 Format Local Order Code Description Local Order Code Description Version 2 3 1 OBR 4 1 subpart will now include the order code without a suffix Suffix codes will be retained if sent in subpart OBR 4 4 Example OBR 4 7600 LIPID PROFILE 7600SB LIPID PANEL Note Content other than that noted mi
234. questions below and return this form or send comments via e mail to MedPlus at your convenience Thank you WY What MedPlus product are you using Please provide version number WY What documentation do you refer to most often Manuals Help v What chapters or topics do you refer to most often V How often do you expect to refer to the Manuals Often Occasionally Never The Reference Guide Often Occasionally Never The Help Often Occasionally Never YW How is the level of detail in the Manuals Toolitle Just right Too much In the Reference Guide Toolitle Just right Too much In the Help Too little Just right Too much WY Does the documentation adequately explain how to get started using the product Yes No If not what information is missing 251 252 WY How do you normally search for information in the Manuals and or Help Scan Table of Contents Index V Was there an index entry you looked for in the Manuals or Help but couldn t find Yes No If so what was it Y Did you find any errors in the Manuals Reference Guide or Help Yes No If so please list the page number or topic and describe the error v Any other comments about the documentation Please tell us about yourself optional Name Title position Company name Address Country Phone E mail May we contac
235. r XTN 40 Accepted length of this field is 40 O Home numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored lt country code NM gt lt area city code NM gt phone number NM gt lt extension NM gt The Hub verifies that the value complies with rules above PID 14 Phone Number XTN 40 Accepted length of this field is 40 O Business numeric characters No dashes or other separating characters The following elements are required and passed to Physician Portal any additional elements are ignored country code NM gt area city code NM phone number NM gt extension NM The Hub verifies that the value complies with rules above PID 15 Language CE 60 NS Patient PID 16 Marital Status IS 1 NS PID 17 Religion IS 3 NS PID 18 Patient Account CX 20 NS Number PID 19 SSN Number ST 16 Must contain 9 numeric digits or 11 O Patient with hyphens Cannot be all zeros and first three numbers cannot be 666 800 or 900 If present the Hub verifies that the value complies with rules above PID 20 Driver s Lic DLN 25 NS Num Patient PID 21 Mother s CX 20 NS Identifier PID 22 Ethnic Group IS 3 NS PID 23 Birth Place ST 60 NS PID 24 Multiple Birth ID 2 NS Indicator Chapter 9 Care360 Patient Demographic HL7 Specification Segme
236. r OBR 33 Assistant Result CM 200 NS Interpreter OBR 34 Technician CM 200 NS OBR 35 Transcriptionist CM 200 NS OBR 36 Scheduled TS 26 NS Date Time OBR 37 Number of NM 4 NS Sample Containers OBR 38 Transport CD 60 NS Logistics of Collected Sample OBR 39 Collector s CE 200 NS Comment OBR 40 Transport CE 60 NS Arrangement Responsibility OBR 41 Transport ID 30 For valid values refer to HL7 table NS Arranged 0224 Transport arranged OBR 42 Escort Required ID 1 For valid values refer to HL7 table NS 0225 Escort required OBR 43 Planned Patient CE 200 NS Transport Comment a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Care360 Order Message Segment Specifications 89 90 OBX Observation Result Segment This segment is optional AOEs in the order are typically captured as OBX segments Segment ID Element Name Type Length Comments Req d OBX 00 Segment ST 10 Must be OBX R Type ID OBX 01 Set ID SI 10 Sequence number for OBX segments R grouped beneath the same OBR segment OBX 02 Value Type ID 2 Defines the structure of the observation O value OBX 05 Valid values include e ST String data e NM Numeric data e CE Coding elements e TX Text data If this segment is present the Hub verifies that this
237. r File Specification CLIENT BILL TO XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes 6 Client mnemonic TOPLAB_CLIENT_MNEMONIC R char 8 7 Billing client number NBS_CLIENT_NO R char 15 a R Required O Optional C Conditional Dataset 3 Bill To File Name BILL_TO TXT Description Usage Provides data about insurance carriers agencies and clients that can be billed as carriers There is one entry per carrier and one per billable client For each site there are also entries for C P and T Required This dataset is conditionalfor third party laboratory implementations it is required for Third party bill and optional for Client bill Conditions None BILL TO Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PK1 R char 4 3 Performing site TOPLAB_PERFORMING_SITE PKI R char 3 4 Bill to ID BILLING_ID PKI R char 9 Carrier agency billing ID or billable client number 5 Billing client number NBS_CLIENT_NO PK1 C char 15 Client number for billable clients 6 Client mnemonic TOPLAB_CLIENT_MNEMONIC O char 8 Client mnemonic for billable clients otherwise blank 7 Billing carrier ID THIRD PARTY FORMS CD PKI C char 6 Billing ca
238. rameters SAMLResponse A Base64 encoded copy Base64 encoded copy of the Y of the SAML response lt saml Response gt lt saml Re XML message sponse gt payload Chapter 6 Physician Portal SSO Specification Parameter Description Example Value Req d Default targetUri A Physician Portal page One of the following N Home identifier indicating the preferred landing page e NewResults e LabOrders e Home e BlankPage e PatientSummary e RxPad e ActionItems e ActionItemFailedFaxes e ActionItemsPendingRenewals e ActionItemsPendingApprovals Notes Home specifies the user s default page BlankPage is valid only for Web service calls branduid A string value indicating 2c9252d710e58d150110e58d671 N Physician the preferred UI brand 90001 Portal default brand TARGET A SAML 1 1 parameter any value N that identifies a target page This parameter is not used by Physician Portal SSO even though it is in the standard If your SAML implementation or library requires this name value pair specify it with any arbitrary value the value is ignored Application Context Parameters ctx patientId A Physician Portal patient 23456 N identifier PID Note Valid only for the LabOrders PatientSummary and RxPad landing pages L The SAML response is authenticated by Physician Portal Physician Portal SSO ver
239. raphicResponse Represents the response elements for a demographic update request This includes the Hub transaction ID and any validation errors that occur Responses include messageControlUid The message String O control ID included in the patient demographic update message that was submitted to the Hub hubTransactionUid The Hub String O transaction ID for the response 170 Chapter 8 Patient Demographic Services API Reference Object Description Attributes Data Type Req d DemographicResponse continued errors The array of validation and String authorization errors returned if the patient demographic update message is returned based on validation status The status of the transaction String response Valid values SUCCESS or FAILURE O a R Required O Optional C Conditional Patient Demographic Services API 171 172 About the WSDL Interface Document In order to consume a Web service you must develop a Web service client application A client application created for accessing the Patient Demographic Web service is referred to as a static Web service client because the client knows where the Web service is located without looking up the service in a Universal Description Discovery and Integration UDDI registry The client calls the Web services via a known service URL to obtain the WSDL file that describes the Web services A
240. re not final for the organization userFailedFaxCount The number of faxes that have failed for the user from the specified organization orgFailedFaxCount The number of faxes that have failed for the specified organization newUserMessageCount The number of user messages for the user from the specified organization prescripPendingApprovalCount The number of prescriptions for the user pending approval from the specified organization prescripPendingRenewalCount The number of prescriptions for the user pending renewal from the specified organization prescripFailedFaxCount The number of faxed prescriptions that have failed for the user from the specified organization Int Int Int Int Int Int Int Int Int Int Int WSOrgData Contains the organization data returned by the getOrgs method Responses include maxOrgs The maximum number of organizations that can be queried in a single call orgList An array of WSOrgs one for each organization Long WSOrg User Summary Services API 165 166 the organization is associated Object Description Attributes Data Type Req d Y timeStamp The date and time DateTime O at which the query was run WSOrg Contains information returned about a particular organization Responses include orgName The common name String O of the organization orgUID The UID with which String
241. re specified using one of the following three color formats RGB composed of three number or percentage values hexadecimal a 3 or 6 digit hex value or color name standard colors defined by the World Wide Web Consortium W3C Copyright and Trademark Text Specifications The Quest Diagnostics copyright and trademark text that appears along the bottom of each Physician Portal page can be changed to reflect the applicable copyright trademark or disclaimer text up to 500 characters of the partner organization The text can also contain HTML tags which enables additional formatting or linking options to be included Link Name and Destination Specifications The following hypertext links which appear along the bottom of each page can be customized to display a different link name up to 30 characters each and or to link to a different destination or they can be removed altogether Physician Portal Link Location Customization Options About Care360 Login page Can be renamed and or linked to a different destination page or removed Forgot Password Login page Can be renamed or removed Customizing the Physician Portal User Interface 147 148 Physician Portal Link Location Customization Options Contact Us Login page Can be renamed and or linked to a different Each portal page destination page or removed Feedback Each portal page Can change e mail recipient Quest Diagnostics Resourc
242. red O Optional C Conditional Dataset 8 Order Code AOE File Name AOE TXT Description Usage Provides data about ask at order entry AOE questions on order codes There is one entry per AOE question Required This dataset is optional highly recommended for third party laboratory implementations Conditions There must be a parent entry in the Order code dataset AOE Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PK PK2 R char 4 3 Performing site TOPLAB PERFORMING SITE PKl PK2 R char 4 4 Order code TEST_CD PKI R char 16 5 Unit code UNIT CD PK2 R char 10 LIS code 6 Analyte code ANALYTE CD PK PK2 R char 11 7 Component PROFILE COMPONENT PKI PK2 O char 15 Can be order code or units that make up the profile Chapter 2 Care360 Master File Specification AOE Column Name CDC Column Name Key Req d Type Length Valid Values Notes 8 AOE question AOE QUESTION R char 30 9 AOE question AOE QUESTION DESC R char 50 prompt 10 AOE question help RESULT FILTER O varchar 250 11 Order code suffix SUFFIX O char 8 12 Order code with TEST_CD_MNEMONIC R char 16 If suffix is not available suffix this will be the same as Order code 13 Special test flag TEST FLAG R char 1 Valid values P
243. result xmlns tns http hub care360 com 5 0 result ncoding UTF 8 xmlns xsi http www w3 org 2001 X Sample 2 HL7 Message with a Primary Only Report File 2 gt LSchema instance lt resultDate gt 20070209101449 lt resultDate gt lt sendingFacility gt NOR lt sendingFacili ty gt lt receivingFacility gt 1746 lt receivingFacility gt lt accessionNumber gt 2523807 lt accessionNumber gt messageControlld 55674841 messageControlId lt h17 gt TVNI F5 XCZ8TEFC E5 PUNXURVN JVXlIwMXw1NjcOODOxfFB8Mi4zIA10QSU USUR8MTCONnwyMDA3MDIWwWOTEwMTQOOXx R8MXwxMjMONTY3ODkxMjMONXwyNTI 3fHxBYmNkZWZeR2hpamtsbW5vcF5BfHwyMDAOMDEzMXxNfHx8fHx8fHx h1l7 XprimaryReport JVBERi0xLjMNJeLjz AvU21uZ2xlUGFnZQovUGFnZU1vZGUgL1 9MNMSAwIG9iago8PAovUGFnZUxheW91d VzZU5vbmUKL1BhZ2VzIDIgMCBSCi9 l1IC9DYXRhbG9nCj4 CmVuZG9iag0l1IDAgb2JqCjw8Ci9CY primaryReport lt additionalReports lt tns result gt Sample 3 HL7 Message with Primary ncoding UTF 8 xmlns xsi http www w3 org 2001 X and Secondary Report Files 2 gt LSchema instance lt resultDate gt 20070209101449 lt resultDate gt lt sendingFacility gt NOR lt sendingFacili ty gt lt receivingFacility gt 1746 lt receivingFacility gt lt accessionNumber gt 2523807 lt accessionNumber gt messageControlld 55674841 messageControlId Xh17 TVNIfF54 XCZ8TEFCfE5PUnxURVN JVXlIwMXw1NjcOODOxfFB8Mi4z
244. rmation Services provides operations for receiving and processing patient demographic updates from a partner application and forwarding those updates to Care360 Physician Portal For details about the Patient Demographic Services API refer to Patient Demographic Services API on page 169 An authorized user name and password are required for accessing this Web service For More Information e For detailed specifications on formatting HL7 Patient Demographic Message ADT messages that are sent to Care360 Hub Information Services for processing see Chapter 9 Care360 Patient Demographic HL7 Specification on page 173 e For information about accessing the WSDL documents for Care360 Hub Information Services see About the WSDL Interface Document on page 172 Chapter 8 Patient Demographic Services API Reference Patient Demographic Services API This section provides details on the methods and objects provided by each service within the Patient Demographic Services API Patient Demographic Services enables the submission of patient demographic updates from a partner application which are then forwarded to Physician Portal Demographic updates can be submitted either in real time or batch mode For more information about the Patient Demographic Services see About Patient Demographic Services on page 140 Patient Demographic Methods Following is a brief overview of each method provided by the Patient Demographic Services Web serv
245. rming site code 3 Unit code UNIT_CD PK1 R char 10 4 Sequence number SEQUENCE NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset File Details 37 38 Dataset 19 DOS Reject Thaw Other File Name THAWOTHER TXT Description Usage Provides DOS information for rejection for thaw cycles and other criteria There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SPECIMEN_REJECT_THAW_OTHER Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 Your performing site code 3 Unit code UNIT_CD PKI R char 10 LIS code 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 R Required O Optional C Conditional Dataset 20 DOS Specimen Stability File Name SPECIMENSTAB TXT Description Usage Provides DOS information for the length of time a specimen can remain at given temperatures and still produce accurate results There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None SPECIMEN_STABILITY Column Name CDC Column Name Key Req
246. rnate Specimen Data dataset 46 Analyte Details dataset 42 Bill To dataset 23 24 Bill To Edit dataset 24 26 Bill To Edit List dataset 27 Bill To Eligibility dataset 27 Client Bill To dataset 22 Client dataset 19 22 Client NPP dataset 50 Client UPIN dataset 42 Client Specific Code XREF dataset 45 Client Specific Order Code dataset 39 40 Clinical Significance Data dataset 46 datasets 15 16 definition 241 DOS Billing Procedure Code dataset 34 DOS Container dataset 35 DOS Methodology dataset 35 DOS Minimum Volume dataset 36 DOS Performing Site dataset 47 DOS Preferred Requirement dataset 36 DOS Reject Hemolysis dataset 37 DOS Reject Lipemia dataset 37 DOS Reject Thaw Other dataset 38 DOS Specimen Stability dataset 38 DOS Transport Temperature dataset 39 Hand Written Order dataset 49 LCP MN CPT To ICD9 dataset 33 LCP MN Service To CPT Dataset dataset 32 Medical Manager Updates dataset 50 Order Code Alias dataset 43 Order Code AOE dataset 30 Master Files Continued Order Code Component dataset 31 Order Code dataset 28 30 overview 14 Performing Site Code dataset 41 42 Reference Ranges dataset 47 retrieving data files 54 sample data files 51 53 Setup Days dataset 48 Setup Times dataset 48 Temperatures dataset 44 Turnaround Times dataset 49 Worklist Components dataset 43 Master Patient Member Index definition 241 Medical Manager Updates dataset Master Files 50 Merge patient sample patient demographic message 232 Me
247. rrier ID for carriers agencies 8 Name NAME C char 50 Required except where billing id is C P or T 9 Address 1 ADDR LINE 1 C char 30 Required except where billing id is C P or T 10 Address 2 ADDR LINE 2 O char 30 11 City CITY O char 30 12 State STATE O char 2 18 Zip code ZIP_CD O char 10 Dataset File Details 23 24 BILL TO Column Name CDC Column Name Key Req d Type Length Valid Values Notes 14 Country name COUNTRY O char 4 15 Phone number PHONE NO O char 16 16 Fax number FAX_NO O char 16 17 HMO carrier flag THIRD_PARTY_HMO_FLAG O char 1 Valid values Y N 18 Carrier type BILLING_TYPE C char 1 Required only for carriers agencies Valid values 2 Patient 3 MediCare 4 MedicAid 5 Med Med 6 Private 19 Selectable flag SELECTABLE_FLAG R char 1 Valid values Y for bill to s that are selectable on electronic interfaces N 20 Alternate bill to ID ORDER BILLING ID O char 9 Bill to used for electronic orders Cf CCLink 2 Alternate bill to ID ORDER BILLING ALIAS O char 3 Bill to alias used for electronic alias orders Cf CCLink a R Required O Optional C Conditional Dataset 4 Bill To Edit File Name BILLEDIT TXT Description Usage Specifies the billing data requirements for insurance carriers T
248. rtable test code dataset 11 Component COMPONENT_SPECIMEN_TYPE O char 130 specimen type 12 State Specimen STATE O char 2 Specimen condition of Condition of Component Unit Code Component unit code field 8 Example values e FR FZ F Frozen e RT A Room Temperature e RF R Refrigerated e S Special e W Wet Ice a R Required O Optional C Conditional Dataset 10 LCP MN Service To CPT File Name ORDERCPT TXT Description Usage Identifies CPT codes that are covered under Limited Coverage Policy Medical Necessity or that are not FDA approved and the corresponding order codes There is one entry per such CPT code per order code per carrier as identified by the BIS Required This dataset is optional for third party laboratory implementations required if billing Medicare Advance Beneficiary Notice ABN limited coverage frequency Conditions There must be a parent entry in the Order code dataset NBS SERVICE CPT XREF Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Legal entity LEGAL_ENTITY PKI R char 4 Your performing site code 3 Billing carrier ID THIRD PARTY ID PKI R char 8 Must match dataset 4 field 3 and dataset 11 field 3 4 Billing service code SERVICE CD PKI R char 10 Must match dataset 7 field 11 5 CPT code
249. rules for an ORM message include the following Notes and Internal comments NTE 02 is set to I Internal comments are Comments comments that provide additional information helpful in the proper testing or reporting of the patient s report Internal comments will not appear on the report The limit is five NTE segments of 60 characters each NTE 03 field width The Hub verifies that there are no more than five NTE segments in the ORM with NTE 02 set to I e Report Comments NTE 02 is set to R Report comments are sent to the laboratory to be placed on the report The limit is two NTE segments of 60 characters each NTE 03 field width The Hub verifies that there are no more than two NTE segments in the ORM with NTE 02 set to R NTE segments can follow PID and OBR segments in the order message The Hub verifies that the rules stated above are complied with in the ORM message Note The Hub only checks the total number of the Internal 5 maximum and Report 2 maximum NTE segments Internal and report comments can occur either after the PID or OBR segments a R Required O Optional C Conditional Additional segment requirements include the following e Fach ORM message sent can contain only one PID and the associated sets of Order segments e OBR 18 and OBR 19 are used as store and forward fields by the Hub The Hub extracts and stores the data sent in these fields and verifies that the fields are blan
250. rvice providers including Quest Diagnostics regional hospital laboratories or independent laboratories For detailed specifications of the User Summary Services see Chapter 7 User Summary Services API Reference on page 161 Chapter 5 Linking to Physician Portal Process Walkthrough Retrieving User Summary Data The diagram below illustrates at a high level the flow of user summary data between Physician Portal and a linked partner application Following the diagram is a step by step walkthrough of the user summary data retrieval illustrated in the diagram Retrieving User Summary Data from Care360 Physician Portal Physician Office Partner Application User Logs In Partner Application Requests User VRBE cs Summary Data You 10 est Younis no fied fx messages There are no faled fax messages for this org You have no total tasks You have no new tasks Youhave no pending tasks Last Logn Dates 02 13 08 0307 PM esT at ven Ql b Portal Returns User BART PERT mass Ont me tona eget ower 000505 QU Crees rad A ST Summary Data Quick View The following steps outline the procedure and associated systems involved in communicating user data for example result and user message counts from Physician Portal to a partner application L A user with an established SSO connection logs in to a partner application The partner application se
251. s 9 Address 1 ADDRESS 1 R char 30 10 Address 2 ADDRESS 2 R char 30 11 Address 3 ADDRESS 3 O char 30 12 Address 4 ADDRESS_4 O char 30 13 City CITY R char 30 14 State STATE R char 2 15 Zip code ZIP R char 10 16 Country name COUNTRY O char 50 17 Latitude LATITUDE O numeric 7 4 Of post office Dataset File Details 19 20 TOPLAB CLIENT Column Name CDC Column Name Key Req d Type Length Valid Values Notes 18 Longitude LONGITUDE O numeric 7 4 Of post office 19 Phone number PHONE NUMBER O char 20 20 After hours phone AFTER_HOURS O char 20 number 21 Contact name CONTACT O char 25 22 Contact name 2 CONTACT2 O char 25 23 Default physician DEFAULT PHYSICIAN O char 25 24 Fee schedule FEE_SCHEDULE O char 10 25 Description DESCRIPTION O char 10 26 Sales area SALES_AREA O char 7 27 Master client MASTER_CLIENT O char 15 28 PAP reminder PAP_REMINDERS O char 2 N No 6 Every 6 reports months 12 Every 12 months 29 Area route stop AREA_ROUTE_STOP O char 7 30 Alternate route area ALT_AREA_ROUTE_STOP O char 7 stop 31 Autodial group AUTODIAL_GROUP O char 10 32 Report to client REPORT TO CLIENT O char 10 33 Abnormals ABNORMALS R char 1 Valid values Y N 34 Partials PARTIALS R char 1 Valid values Y N 35
252. s detailed specifications for each segment of an ADT A31 Patient Update message Message segments supported by the Hub include the following e MSH Message Header Segment on page 205 e EVN Event Type Segment on page 207 e PID Patent Identification Segment on page 208 e PV Patient Visit Data Segment on page 210 e GTI1 Guarantor Segment on page 213 e INI Insurance Segment on page 217 Note ADT A31 message segments that are not supported by the Hub are notincluded in this section for detailed specifications refer to the HL7 2 3 Specification MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID Element Name Type Length Comments Req d MSH 00 Segment Type ID ST 4 Must be MSH R MSH 01 Field Separator ST 1 The separator between the message segment ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value is a vertical bar R MSH 02 Encoding Characters ST Four characters that are used in the following order component separator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by Quest Diagnostics MSH 03 S
253. sers with the MedPlus supplied URL or they can create a custom URL by aliasing a more appropriate domain name User Manual and Help Specifications The Care360 Physician Portal User Manual and online help can be replaced with a generic user manual and help which contain no references to Quest Diagnostics and no Physician Portal or Quest Diagnostics branding such as logos or images Note The Care360 Physician Portal Reference Guide cannot be customized Chapter 5 Linking to Physician Portal Chapter 6 Physician Portal SSO Specification Zi Patient Summary Microsoft Internet Explorer file Edit View Favorites Tools Help Qs O NAA D sexh kroes A BDH DS NL p wi Bae K Demo Health Assoc User Preferences Support v Whats New Help Logout Care36C Welcome Any User l l im ANNE GRUR Quick view ERE Patients Lab Orders Prescriptions Reports References 2b Orders gt Quick View gt New Results gt Find a Patient gt Patient Summary Demographics Eprints message SG Fa Brinkman Rose vewsumey pup add edit Qh Exoort cor Find a Patient Patient Summary Demographics Patient Problems All Lab Reports E Bridge All Meds Supplies Al Allergies Patient ID Bridge t All Messages Faxes Tasks Address 222 N Frankin St Apt 12 Winamac IN 47725 Phone 513 555 5555 DOB 02 10 1925 Age 83y Gender F PID iintemaRE Write a Prescription Write a Lab
254. set 38 Client NPP File Name CLIENTNPP TXT Description Usage Provides NPP numbers for clients Required This dataset is optional for third party laboratory implementations Conditions None NPP Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site TOPLAB_PERFORMING_SITE PKI R char 3 Your performing site code 3 Client number CLIENT_NO PKI R char 10 Client number for billable clients 4 NPP NPP PK1 R char 10 5 Name NAME R char 30 a R Required O Optional C Conditional Dataset 39 Medical Manager Updates File Name N A Description Usage Provides an audit for the changes in QLS Required This dataset is not supported for third party laboratory implementations Conditions None MED_MGR_UPDATES Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site TOPLAB PERFORMING SITE PKl R char 3 Your performing site code 3 Test code TEST_CD PKI R char 16 Updated test code 4 Change type ACTION PK1 R char 1 Type of update to code Valid values A C D a R Required O Optional C Conditional Chapter 2 Care360 Master File Specification Sample Master File Dataset Files
255. signment Of IS 2 For suggested values refer to user defined NS Benefits table 0135 Assignment of benefits IN1 21 CoordinationOf IS 2 For suggested values refer to user defined NS Benefits table 0173 Coordination of benefits Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d IN1 22 Coord Of Ben ST 2 NS Priority IN1 23 Notice Of ID 2 For valid values refer to HL7 table NS Admission Flag 0136 Yes no indicator IN1 24 Notice Of DT 8 NS Admission Date IN1 25 Report Of ID 2 For valid values refer to HL7 table NS Eligibility Flag 0136 Yes no indicator IN1 26 Report Of DT 8 NS Eligibility Date IN1 27 Release IS 2 For suggested values refer to user defined NS Information table 0093 Release information code Code IN1 28 Pre Admit Cert ST 15 NS PAC IN1 29 Verification TS 26 NS Date Time IN1 30 Verification By XCN 60 NS IN1 31 Type Of IS 2 For suggested values refer to user defined NS Agreement table 0098 Type of agreement Code IN1 32 Billing Status IS 2 NS IN1 33 Lifetime Reserve NM 4 NS Days IN1 34 Delay Before NM 4 NS L R Day IN1 35 Company Plan IS 8 Further identifies an insurance plan O Code IN1 36 Policy Number ST 20 Individual policy number of the C insured Required for Medicare submissions Required only if IN1 47 T Third Party Bill IN1 37 Policy CP 12 NS Deductible
256. sit Additional Info Optional not supported by the Hub Disability Information Optional not supported by the Hub Observation Result Optional not supported by the Hub Allergy Information Optional not supported by the Hub Diagnosis Information Optional not supported by the Hub Diagnosis Related Group Optional not supported by the Hub Procedures Optional not supported by the Hub Role Optional not supported by the Hub Guarantor Optional forwarded to portal if provided The system can only handle one GTI at this time You can have 1 Guarantor with 2 insurances but not 2 Guarantors Insurance Optional forwarded to portal if provided The first IN1 Primary Insurance for Guarantor The second IN1 Secondary Insurance for Guarantor if provided In order for the IN1 information to be stored by the portal the IN1 47 field must be populated with a T ora P Insurance Additional Info Optional not supported by the Hub Insurance Additional Info Optional not supported by the Hub Accident Information Optional not supported by the Hub Universal Bill Information Optional not supported by the Hub Universal Bill 92 Information Optional not supported by the Hub In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional Chapter 9 Care360 Patient Demographic HL7 Specification Message Segment Specifications This section provide
257. specifications are identical only one specification is shown In cases where there are differences both the HL7 2 3 and HL7 2 3 1 Specification are shown in order to highlight these differences Supported messages for results include ORU R01 Observational Report Unsolicited Message This chapter includes the following sections e Result message format requirements For information on the message format requirements see Care360 Result Message Format Requirements on page 99 e Result message segment specifications Each result message received by the Hub contains a number of standard sections For requirements on the standard segments of a result message see Care360 Result Message Segment Specifications on page 103 e Sample Result messages For samples of the various result messages see Sample Care360 Result Messages on page 120 e Receiving third party results files For information about transferring results data between the Hub and a third party laboratory see Receiving Third Party Laboratory Results Files on page 123 Chapter 4 Care360 Results HL7 Specification Care360 Result Message Format Requirements In addition to the field level validation detailed in Care360 Result Message Segment Specifications each Observational Report Unsolicited ORU message is validated by the Hub to ensure compliance with rules outlined in this section Note For a detailed specification of lab orders that are sent to
258. ssage Header segment see MSH Messages sample ORM 94 94 ORU 120 122 patient demographic 231 232 result XML 124 Methodology dataset Master Files 35 Methods getCounts 163 getCountsByOrg 164 getOrgs 164 submitBatchADTMessage 170 submitRealTimeADTMessage 169 Minimum Volume dataset Master Files 36 MRG field requirements patient demographic 227 228 MSH field requirements order 67 69 field requirements patient demographic 180 182 196 197 205 207 222 223 field requirements result 103 105 segment requirements order 60 segment requirements result 99 N Never definition 100 New features xi New Results page linking to 130 Newline character 62 99 Not required definition 59 Not Supported definition 63 175 Notes and Comments segment see NTE NTE field requirements order 93 93 field requirements result 119 119 segment requirements order 61 0 Objects DemographicRequest 170 DemographicResponse 170 WSOrg 166 WSOrgData 165 WSUserSummaryCounts 165 WSUserSummaryData 164 OBR field requirements order 86 89 field requirements result 110 116 OBR Continued segment requirements order 60 Observation Request segment see OBR Observation Result Detail segment see OBX OBX field requirements order 90 91 field requirements result 116 119 segment requirements order 60 Optional definition 63 175 ORC field requirements order 84 85 field requirements result 10
259. ssible values include but are not limited to MC MS AP and the AL sequences e g ALIA Segment ID Element Name Type Length Comments Supported OBR 25 Result Status ID 1 Valid values for this field include A Version 2 3 e C Correction to results e F Final results e P Preliminary results e X Test canceled Typical values for this field include Version 2 3 1 P Preliminary results I Pending results Other data supported e C Correction to results e F Final results e X Test canceled Data also passed in OBX 11 Note A status of X indicates that all observations for the test identified have been canceled OBR 26 Parent Result CM 400 Version 2 3 1 only O Contains order code that caused reflex test to be performed OBR 27 Quantity Timin TQ 200 N g OBR 28 Result Copies To XCN 150 N OBR 29 Parent CM 150 N OBR 30 Transportation ID 20 N Mode OBR 31 Reason for Study CE 300 N OBR 32 Principal Result CM 200 N Interpreter OBR 33 Assistant Result CM 200 N Interpreter OBR 34 Technician CM 200 N OBR 35 Transcriptionist CM 200 N OBR 36 Scheduled TS 26 N Date Time OBR 37 Number of NM 4 N Sample Containers Care360 Result Message Segment Specifications 115 116 Segment ID Element Name Type Length Comments Supported OBR 38 Transport CE 60 N Logistics of Collected Sample OBR 39 Co
260. sswords set by the user via the Change Password function are accepted on this page Upon successful authentication of a user s Physician Portal User ID and Password a mapping record is stored within Physician Portal that relates the Physician Portal user identity to the partner application user identity passed within the SAML assertion At the same time the user s Physician Portal password is obfuscated so the user will only be able to access Physician Portal via SSO from that point forward If the user requires both SSO based and password based authentication MedPlus Customer Support may be contacted to request a password reset Existing Physician Portal practices are employed for password resets that is the user must change the password upon the first password based login following a password reset Chapter 6 Physician Portal SSO Specification Usage Scenario 2 Physician Portal SSO for Web Services A partner application can leverage SSO in the process of invoking Physician Portal Web services on behalf of a previously mapped user see About SSO User Initialization on page 156 Establishing a session using SSO enables the partner application to establish a user specific context to Physician Portal without having to know or store the user s Physician Portal password For this release the only Web service available for integration is the User Summary service which is referenced in the following sections From the Physician Por
261. ster File Dataset Files 53 54 Submitting Third Party Master Files In order to ensure that the most current Master File data is available within the Lab Orders component of Physician Portal Care360 Hub Information Services initiates a secure connection to a third party laboratory on a predefined schedule for example weekly to retrieve and process the latest dataset files The secure transfer of Master File data between the Hub and a third party laboratory can be accomplished by a number of different methods for example via SSH File Transfer Protocol SFIP For more information on possible connectivity methods see Universal Ordering and Resulting Connectivity on page 9 Chapter 2 Care360 Master File Specification About the Carrier Edit Patterns This section provides an explanation of the carrier edit patterns that are included in Dataset 4 Bill To Edit and Dataset 5 Bill To Edit List Carrier edit patterns include the following e Edit patterns which are a sequence of the characters A for alpha N for numeric X for alphanumeric B for blank for wildcard and the digits 1 through 5 Digits positionally refer to the two character edit pattern list in the corresponding list field e Edit pattern lists which are a sequence of zero to five two character alphanumeric identifiers Example 1 Dataset 4 column 24 is NNNNNBBBBB In this example the guarantor s
262. sults only interfaces Care360 Result Message Segment Specifications 113 114 Segment ID Element Name Type Length Comments Supported OBR 20 Filler Field 1 ST 60 The component code for profiles only Includes the component order code in sub field 4 and the component order name in sub field 5 Version 2 3 Format Component Code without Suffix Description Component Code with Suffix if sent Description Version 2 3 1 Some lab systems add a suffix to the component code in the result message for example 10165SB where SB is added by the lab system Example OBR 20 896 TRIGLICERIDES 896S B TRIGLYCERIDES Note Content other than that noted might appear in these fields if NMS Mapping has been imposed C OBR 21 Filler Field 2 ST 200 Site ID as defined in the database Format SiteID Lab Name Lab Address City State Zip Note Sub field 1 is the same identifier found in OBX 15 sub field 1 OBR 22 Results Rpt Status Chng Date Time TS 26 The date and time that the observation was reported Communicates when the result file was created in the lab system Format YYY YMMDDHHMMSS Seconds are always 00 OBR 23 Charge to Practice CM 40 OBR 24 Chapter 4 Care360 Results HL7 Specification Diagnostic Serv Sect ID ID 10 Version 2 3 1 only Po
263. t ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value is a vertical bar Four characters that are used in the following order component separator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by the Hub A MSH 03 Sending Application EI 180 The outbound result feed This field is populated with LAB Note While HL allows for a length of 180 this is currently populated only with LAB Care360 Result Message Segment Specifications 103 104 Segment ID Element Name Type Length Comments Supported MSH 04 Sending Facility EI 180 The performing facility The A three letter ID of the facility that performed the test Note While HL7 allows for a length of 180 this is currently populated only with the three letter ID MSH 05 Receiving HD 180 N Application MSH 06 Receiving Facility EI 180 The receiving facility The A account number defined for the placer same as MSH 04 in the ORM MSH 07 Date Time of TS 14 The date and time that the A Message sending system created the message Format YYYYMMDDHHMMSS MSH 08 Security ST 40 N MSH 09 Message Type CM T The type of message being A transmitted and the event leading to th
264. t Person s XTN 40 NS Telephone Number GT1 47 Contact Reason CE 80 NS GT1 48 Contact IS 2 NS Relationship GT1 49 Job Title ST 20 NS GT1 50 Job Code Class JCC 20 NS GT1 51 Guarantor XON 130 NS Employer s Organ Name GT1 52 Handicap IS 2 NS GT1 53 Job Status IS 2 NS GT1 54 Guarantor FC 50 NS Financial Class GT1 55 Guarantor Race IS 1 NS a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported IN1 lInsurance Segment The Insurance IN1 segment contains insurance policy coverage information necessary to produce properly pro rated and patient and insurance bills This segment is applicable only for insurance billing Segment ID Element Name Type Length Comments Req d IN1 00 Segment ST 4 Must be INI R Type ID IN1 01 Set ID SI 4 IN1 message segments should be R numbered sequentially from 1 IN1 02 Insurance Plan CD 50 The Hub verifies that the field is R ID populated IN1 03 Insurance CX 59 This is the QDI Bill mnemonic O Company ID Note Required only if IN1 47 T Third Party Bill IN1 04 Insurance XON 130 Note Required only if IN1 47 O Company Name T Third Party Bill ADT A31 Patient Update Message Segment Specifications 217 218 Segment ID Element
265. t requirements MSH fields 103 105 NTE fields 119 119 OBR fields 110 116 OBX fields 116 119 ORC fields 107 110 PID fields 105 107 Results Care360 HL7 specification 98 message segment requirements 99 retrieving result files 123 Retrieve Master Files 54 results 123 S SAML 150 definition 242 implementing for SSO 152 154 SAML Browser Artifact definition 242 SAML Browser POST definition 242 Sample EMR application 235 Master Files 51 53 ORM messages 94 94 ORU messages 120 122 patient demographic messages 231 232 result XML messages 124 SSO and Web services code 238 Schema result XML 123 Service Scope definition 242 Setup Days dataset Master Files 48 Setup Times dataset Master Files 48 Single Sign On see SSO SOAP definition 242 Source code EMR Sample application 236 Specimen Stability dataset Master Files 38 SSO definition 242 establishing organizational trust 151 implementing 150 implementing SAML 152 154 initializing connection 133 overview 130 135 process walkthrough 133 Staging environment Hub 172 Physician Portal 237 submitBatchADTMessage method description 170 submitRealTimeADTMessage method description 169 Subscriber definition 242 Support contact 235 T Technology Provider definition 243 Temperatures dataset Master Files 44 Test EMR application 236 Third Party Payment definition 243 Time Scope definition 243 Transport Temperature dataset Master Files 39 Trust orga
266. t supported by the Hub OBX Observation Result Optional not supported by the Hub AL1 Allergy Information Optional not supported by the Hub DG1 Diagnosis Information Optional not supported by the Hub DRG Diagnosis Related Group Optional not supported by the Hub PR1 Procedures Optional not supported by the Hub ROL Role Optional not supported by the Hub GT1 Guarantor Optional forwarded to portal if provided The system can only handle one GTI at this time You can have 1 Guarantor with 2 insurances but not 2 Guarantors IN1 Insurance Optional forwarded to portal if provided The first IN1 Primary Insurance for Guarantor The second IN1 Secondary Insurance for Guarantor if provided In order for the IN1 information to be stored by the portal the IN1 47 field must be populated with a T or a P IN2 Insurance Additional Info Optional not supported by the Hub IN3 Insurance Additional Info Optional not supported by the Hub ACC Accident Information Optional not supported by the Hub UB1 Universal Bill Information Optional not supported by the Hub UB2 Universal Bill 92 Information Optional not supported by the Hub In the hierarchy shown above braces indicate where multiple items are allowed and brackets indicate items that are optional ADT A28 Patient Add Message Segment Specifications 179 180 Message Segment Specifications This section
267. t you for additional feedback Yes No Send your comments to MedPlus Please send your comments in any of the following ways By Mail By Fax MedPlus Inc 800 381 4048 Attn Technical Communications Manager Bv E mail 4690 Parkway Drive PERMET Mason OH 45040 USA doc medplus com We d Like to Hear From You Care360 A MedPlus Solution MedPlus Inc a Quest Diagnostics Company 4690 Parkway Drive Mason OH 45040 P 513 229 5500 F 513 229 5505 www medplus com
268. tName Middle UPIN e Format for NPI Only NPI Number LastName FirstName Middle NPI e Format for UPIN and NPI UPIN Number LastName FirstName Middle UPIN NPINumber LastName Middle BOON Version 2 3 1 Literal UPIN or NPI moved from subfield 9 to subfield 13 Example 2 3 ORC RE 0001 SL123456A CM P12203 BOWKER DAWN UPINI 1111 Example 2 3 1 ORC RE 0001 SL123456A CM IIIIIP12203 BOWKER DAWN UPINI LII If the Send Provider Identifier option for a Hub account is set to either UPIN or NPI the Hub removes the opposing identifier if present For example if UPIN is selected the Hub will remove the NPI if it is returned If the option is set to Both then the Hub passes it through with no modification C ORC 13 Enterer s Location PL 80 ORC 14 Call Back Phone Number XTN 40 ORC 15 Order Effective Date Time TS 26 Care360 Result Message Segment Specifications 109 110 Segment ID Element Name Type Length Comments Supported ORC 16 Order Control CE 200 Version 2 3 1 only N Gode Reason ORC 16 valid data for a reprinted report Id text assigning authority alterId text null when original report R REPRINT ORC 17 Entering CE 60 N Organization ORC 18 Entering Device CE 60 N ORC 19 Action By XCN 120 N a For a descri
269. tails 45 46 Dataset 30 Alternate Specimen Data File Name ALTSPEC TXT Description Usage Provides DOS alternate specimen data for each test There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None ALTERNATE SPECIMEN DATA Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT CD PKI R char 10 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset 31 Clinical Significance Data File Name CLINSIG TXT Description Usage Provides DOS information for each test s clinical significance There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None CLINICAL_SIGNIFICANCE_DATA Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT_CD PK1 R char 10 4 Sequence number SEQUENCE NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional
270. tal server perspective the SSO handshake for Web service usage is identical to the handshake for browser usage The primary difference from the partner application perspective is that instead of sending an HTML form to a Web browser the application opens a direct HTTPS connection to the Physician Portal server It can then invoke a POST request to send the authentication information and receive a landing page response along with the Physician Portal session cookie Example 1 Traffic of HTTP SSL Request to Care360SSOSecurityCheck REQUEST POST care360 Care360SSOSecurityCheck HTTP 1 0 Host care360 dev medplus com Content Length 6810 Content Type application x www form urlencoded User Agent SOATest X Care360 SessionForWebService tru SAMLResponse PFJlc3BvbnNlIHhtbG5zPSJlom RESPONSE HTTP 1 1 200 OK Date Mon 19 Mar 2007 15 28 42 GMT Pragma no cache Content Length 350 Content Type text html Expires Thu 01 Jan 2008 00 00 00 GMT Last Modified Mon 20 Nov 2006 16 23 24 GMT Set Cookie JSESSIONID F2sq7JLqOs19hkGfOflv7qhlw2LrLgJT5NBz4HLYlYZybgPJr 2y4198796407 path Set Cookie securityCheckUri Care360SSOSecurityCheck Set Cookie IsSSOClient true Set Cookie sso lastKnownSessionId F2sq7JLqOs19hkGfOflv7qhlw2LrLgJT5NBz4 HLYlYZybgPJr2y4 987964007 1174318122760 path Accept Ranges bytes Cache Control no cache Connection Close html head meta htt
271. taset 36 Turnaround Times File Name TAT TXT Description Usage Provides DOS turnaround times for the tests There is one row per line of text per unit code Required This dataset is optional for third party laboratory implementations Conditions None TURNAROUND TIMES Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site LABORATORY_CD PKI R char 3 3 Unit code UNIT CD PKI R char 10 4 Sequence number SEQUENCE_NO PKI R smallint 5 Text COMMENT_TXT O char 60 a R Required O Optional C Conditional Dataset 37 Hand Written Order File Name HOTT TXT Description Usage Provides DOS handwritten order data for the tests There is one row per line of text per test code Required This dataset is optional for third party laboratory implementations Conditions None HOTT Column Name CDC Column Name Key Req d Type Length Valid Values Notes l Operation R char 1 Valid values A C D 2 Performing site TOPLAB PERFORMING SITE PK1 R char 3 National Standard DB NSD 3 Test code TEST CD PKI R char 16 4 Handwritten text HANDWRITTEN TEXT R char 100 5 Comment text COMMENT TXT O char 200 a R Required O Optional C Conditional Dataset File Details 49 50 Data
272. ted values refer to user NS Status defined table 0009 Ambulatory status GT1 35 Citizenship IS 4 NS GT1 36 Primary CE 60 NS Language GT1 37 Living IS 9 For suggested values refer to user NS Arrangement defined table 0220 Living arrangement GT1 38 Publicity CE 80 NS Indicator GT1 39 Protection ID 1 For valid values refer to HL7 table NS Indicator 0136 Yes no indicator GT1 40 Student IS 9 For suggested values refer to user NS Indicator defined table 0231 Student status GT1 41 Religion IS 3 NS GT1 42 Mother s XPN 48 NS Maiden Name GT1 43 Nationality CE 80 NS GT1 44 Ethnic Group IS 3 NS GT1 45 ContactPerson s XPN 48 NS Name Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d GT1 46 Contact Person s XTN 40 NS Telephone Number GT1 47 Contact Reason CE 80 NS GT1 48 Contact IS 2 NS Relationship GT1 49 Job Title ST 20 NS GT1 50 Job Code Class JCC 20 NS GT1 51 Guarantor XON 130 NS Employer s Organ Name GT1 52 Handicap IS 2 NS GT1 53 Job Status IS 2 NS GT1 54 Guarantor FC 50 NS Financial Class GT1 55 Guarantor Race IS 1 NS a For a description of the HL7 data types see Data Type Specifications on page 64 b R Required O Optional C Conditional NS Not Supported Care360 Order Message Segment Specifications 83 ORC Common Order Segment The Common Order ORC
273. ternate identifier ST alternate text ST name of alternate coding system ST gt CK Composite ID with ID number NM gt check digit NM code check digit identifying the check digit scheme employed ID gt assigning authority HD gt CX Extended composite XID ST gt check digit ST code ID with check digit identifying the check digit scheme employed ID gt assigning authority HD identifier type code IS assigning facility HD XCN Extended composite In Version 2 3 replaces the CN data type ID number and lt ID number ST gt family name ST given Dame name ST middle initial or name ST suffix e g JR or III ST prefix e g DR ST gt degree e g MD ST gt lt source table IS gt assigning authority HD name type code ID identifier check digit ST gt lt code identifying the check digit scheme employed ID identifier type cod IS gt assigning facility HD gt Generic CM Composite No new CMs are allowed after HL7 Version 2 2 Hence there are no new CMs in Version 2 3 Demographics XAD Extended address In Version 2 3 replaces the AD data type lt street address ST gt lt other designation ST gt lt city ST gt lt state or province ST gt zip or postal code ST gt country ID gt address type ID oth
274. the last name Family name 50 given name 50 middle name or init 1 suffix 10 prefix 10 degree 10 name type code 6 Alphanumeric data only The Hub verifies that the value complies with rules above a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PID Patient Identification Segment Incorrect The Patient Identification PID segment is used by all applications as the primary means of communicating patient identification information This segment contains permanent patient identifying and demographic information that for the most part is not likely to change frequently Note This segment is used on inbound transactions only Segment ID Element Name Type Length Comments Req d PID 00 Segment ST 4 Must be PID R Type ID PID 01 Set ID SI 4 Allows identification of multiple PID R segments within a message Usually a sequential number beginning with 1 Must be set to 2 to identify incorrect person information The Hub verifies that the value complies with rules above PID 02 Patient ID CX 20 NS External ID PID 03 Patient ID CX 20 NS Internal ID PID 04 Alternate CX 20 NS Patient ID PID PID 05 Patient Name XPN 48 NS Chapter 9 Care360 Patient Demographic HL7 Specification Segment ID El
275. tion PV1 43 Prior Temporary PL 80 NS Location PV1 44 Admit TS 26 NS Date Time PV1 45 Discharge TS 26 NS Date Time PV1 46 Current Patient NM 12 NS Balance PV1 47 Total Charges NM 12 NS PV1 48 Total NM 12 NS Adjustments PV1 49 Total Payments NM 12 NS PV1 50 Alternate VisitID CX 20 NS PV1 51 Visit Indicator IS 1 NS PV1 52 Other XCN 60 NS Healthcare Provider a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported ADT A29 Patient Delete Message Segment Specifications 203 204 ADT A31 Patient Update Message Segment Specifications This section provides detailed specifications for each segment of an ADT A31 Patient Update HL7 message The purpose of this message type is to enable a partner application to modify an existing patient via the Hub in Physician Portal Message Segment Hierarchy An ADT A31 message must follow the message segment hierarchy as specified below MSH EVN PID PD1 NK1 PV1 Pv2 DB1 OBX AL1 DG1 DRG PR1 ROL GT1 IN1 IN2 IN3 ACC UB1 UB2 Message Header Required one per file Event Type Required Patient Identification Required Additional Demographics Optional not supported by the Hub Next of Kin Associated Parties Optional not supported by the Hub Patient Visit Data Required Patient Vi
276. ts supported by the Hub include the following e MSH Message Header Segment on page 196 e EVN Event Type Segment on page 198 e PID Pat ent Identification Segment on page 198 e PV Patient Visit Data Segment on page 201 Note ADT A29 message segments that are not supported by the Hub are notincluded in this section for detailed specifications refer to the HL7 2 3 Specification ADT A29 Patient Delete Message Segment Specifications 195 196 MSH Message Header Segment The Message Header MSH segment defines the intent source destination and some specifics of the syntax of a message Segment ID Element Name Type Length Comments Req d MSH 00 Segment Type ID ST 4 Must be MSH R MSH 01 Field Separator ST The separator between the message segment ID MSH and the first real data field MSH 02 Defines the character to be used as a separator for the rest of the message The value is a vertical bar R MSH 02 Encoding Characters ST Four characters that are used in the following order component separator repetition separator escape character and sub component separator Format amp These values are recommended by HL7 and are the only values supported by Quest Diagnostics MSH 03 Sending Application HD 180 The name of the sending application MSH 04 Sending Facility HD 180 Th
277. ult quall attributeF ormDefault qualified targetNamespace java com medplus care360 ws org model lt xsd import namespace http schemas xmlsoap org soap encoding gt lt xsd complexType name ArrayOfWSOrg gt lt xsd complexContent gt lt xsd restriction xmlns soapenc http schemas xmlsoap org soap encoding base soapenc Array gt xsd attribute xmins wsdl http schemas xmlsoap org wsdl ref soapenc arrayType wsdl arrayType stns WSOrg gt lt xsd restriction gt sd complexContent gt lt xsd complexType gt xsd complexType name WSOrg gt lt xsd sequence gt lt xsd element type xsd boolean name accessible minOccurs 1 maxOccurs 1 gt cued clamant tnemlvedsctine mn orcotareRiam grer vietptdunt n qe rings Done Bj Trusted sites In This Chapter About the User Summary Services API Reference 162 e User Summary Services API 2 5 525 054 25 20000 2s RGoeseivewes tee 163 161 162 About the User Summary Services API Reference This section provides details about the User Summary Services API calls provided by Physician Portal The User Summary Services component of Physician Portal provides operations for receiving notification of the availability of user messages new results and pending prescriptions within Physician Portal For more information about the User Summary Services see About User Summary Services on page 136 For details about the
278. unctions or Web services provided by Physician Portal A Readme file is included with the sample application describing the application and how itis to be used In addition detailed comments are provided throughout the sample code to illustrate the implementation of key functions MedPlus Disclaimer All sample code referenced in this Programmer Reference and the Physician Portal SSO and Web Services site is provided for example purposes only and it may need to be modified to work in your environment It is provided as is without warranty of any kind or support from MedPlus Inc Third Party Disclaimer MedPlus has a software license to use a library written by ComponentSpace It is used by the sample application to create assertions and other SAML features in Cf In order to use the sample application a third party application developer must download and install the ComponentSpace library for SAML 30 trail version 1 1 For more information refer to the following ComponentSpace Web site http www componentspace com saml net aspx Chapter 10 Care360 SSO and Web Services Site Glossary Account ID A unique identifier for a care site that uses Quest Diagnostics laboratory services This is the identifier used by Quest Diagnostics for billing each care site Admission Discharge Transfer ADT A type of HL7 message used to communicate patient details to external applications Patient Administration ADT messages are
279. ure SIGNATURE REO R bit Valid values Y N required 10 Written diagnosis WRITTEN DIAG REQ R bit Valid values Y N required 11 Service required SERVICE_REQ R bit Valid values Y N 12 Patient name PATIENT_NM_REQ R bit Valid values Y N required 13 Patient address PATIENT ADDR REQ R bit Valid values Y N required 14 Subscriber name SUBSCRIBER NM REQ R bit Valid values Y N required 15 Bill type required BILL TYPE REO R bit Valid values Y N 16 Bill type value BILL TYPE VALUE R char 1 Valid values 2 Patient 3 MediCare 4 MedicAid 5 Med Med 6 Private 17 Required REQUIRED R bit Valid values Y N 18 Diagnosis code DIAG CD REQ R bit Valid values Y N required 19 Commercial carrier COMM INS NAME ADDR R bit Valid values Y N name and address required 20 Medicare explosion MEDICARE EXPLOSION REQ R bit Valid values Y N required 21 Workman s comp WORKMAN COMP IND R bit Valid values Y N indicator Dataset File Details 25 26 BILLING EDITS Column Name CDC Column Name Key Req d Type Length Valid Values Notes 22 37 Policy number CERT_NO_PATTERN_1 16 O char 28 See About the Carrier pattern Edit Patterns on page 55 38 53 Policy number list CERT_NO_PATTERN_LIST_1 16 O char 10 See
280. urtesy Code IS 2 NS PV1 23 Credit Rating IS 2 NS PV1 24 Contract Code IS 2 NS PV1 25 Contract DT 8 NS Effective Date PV1 26 Contract Amount NM 12 NS PVI 27 Contract Period NM 3 NS PV1 28 Interest Code IS D NS PV1 29 Transfer to Bad IS 1 NS Debt Code PV1 30 Transfer to Bad DT 8 NS Debt Date Care360 Order Message Segment Specifications 73 74 Segment ID Element Name Type Length Comments Req d PV1 31 Bad Debt Agency IS 10 NS Code PV1 32 Bad Debt NM 12 NS Transfer Amount PV1 33 Bad Debt NM 12 NS Recovery Amount PV1 34 Delete Account IS 1 NS Indicator PV1 35 Delete Account DT 8 NS Date PV1 36 Discharge IS 3 NS Disposition PV1 37 Discharged to CM 25 NS Location PV1 38 Diet Type IS 2 NS PV1 39 Servicing Facility IS 2 NS PV1 40 Bed Status IS 1 NS PVI 41 Account Status IS 2 NS PV1 42 Pending PL 80 NS Location PV1 43 Prior Temporary PL 80 NS Location PV1 44 Admit TS 26 NS Date Time PV1 45 Discharge TS 26 NS Date Time PV1 46 Current Patient NM 12 NS Balance PV1 47 Total Charges NM 12 NS PV1 48 Total NM 12 NS Adjustments PV1 49 Total Payments NM 12 NS PV1 50 Alternate Visit ID CX 20 NS PV1 51 Visit Indicator IS 1 NS Chapter 3 Care360 Order HL7 Specification Segment ID Element Name Type Length Comments Req d PV1 52 Other XCN 60 NS Healthcar
281. used to exchange the patient state within a healthcare facility ADT messages keep patient demographic and visit information synchronized across healthcare systems See Health Level Seven HL7 Ambulatory Care Healthcare services provided without the patient being admitted to a facility Also called outpatient care The services of ambulatory care centers hospital outpatient departments physicians offices urgent care centers and home healthcare services fall under this heading provided that the patient remains at the facility less than 24 hours No overnight stay in a hospital is required Benefits Specific areas of plan coverages for example outpatient visits hospitalization or pharmaceuticals that make up the range of medical services that a payer markets to its subscribers Clinical Data Compendium CDC A current collection of all reference data for example test codes diagnosis codes and Ask at Order Entry AOE questions needed to create a complete and valid electronic order for submission to a Quest Diagnostics or to a third party laboratory system Coverage Services provided within a given health or pharmacy care plan Healthcare and drug benefit services provided or authorized by the payer s medical staff or payment for healthcare services Diagnosis The identification of a disease or condition through analysis and examination by a physician 239 240 Glossary Eligibility A person entitled to re
282. utable client application shown below for linking to Physician Portal via SSO in the Physician Portal Staging environment Once connected the Example SSO Care360 Stage application demonstrates the use of the User Summary Web services for retrieving user data and the Branding options for linking to Physician Portal with specific product branding displayed Pant Landing Page Pater ID EMR aa Branding Brand fx ENR None x Web Senice C sebcetors o orgun o Get Corts Get Mar Counts walCani Dig CowtsKroare 0 Conector Sau New ess Fresco Fral nona Resut Can Fiet Fra Noral Rest Cort Fresco bee om Catal es Count This sample application can be used to help understand SSO workflow as well as to verify responses to User Summary requests It can also be used to help troubleshoot issues for example to determine whether a problem exists within a vendor application or message format as opposed to within Physician Portal itself Sample Source Code The Physician Portal SSO and Web Services site also provides code samples and supporting project files as applicable to demonstrate the working Example SSO Care360 Stage application For more information about the sample code see About the Sample Code on page 238 Chapter 10 Care360 SSO and Web Services Site About the WSDL Interface Documents In order to consume a Web service you must develop a Web service client appl
283. uthentication action is made on a new session each time a Web service is called The example application code above demonstrates this model However following is some background as to how Physician Portal Web service usage is impacted e Sessions established on behalf of Physician Portal user for Web service usage as indicated by the X Care360 IsForWebService header are managed separately from sessions established for Web browser usage This means that user browser sessions to Physician Portal will not be terminated due to a multiple login condition if the partner application invokes a Web service call in the background on the user s behalf e Web service sessions are limited to 60 seconds by default in order to avoid the proliferation of abandoned non interactive sessions on the Physician Portal server Sessi part ons created for Web service usage neither support nor require a log out feature in due to the 60 second limit on Web service oriented sessions Usage Scenario 2 Physician Portal SSO for Web Services 159 160 About SSO User Initialization SSO authentication will not succeed when executed on behalf of a yet unmapped user for Web service usage that is an HTTP 401 status will be returned with appropriate response text The partner application will need to gracefully handle this condition This differs from the Web browser usage scenario where the user is directed to a login verification page
284. will not be reflected in the result e Conditional The field may or may not be required depending on certain conditions stipulated in the Comments column of each segment table If the stated conditions are not met the message is rejected by the Hub If the field is present the Hub validates it against any stated requirements The contents of this field may or may not be reflected in the result e Not Supported If a field is described as Not Supported by the Hub the corresponding row appears grayed in the table the content of the field is not used by the Hub but it is validated for field type and length as well as conformance to the specified HL7 table or user defined table as applicable If all fields are successfully validated the content is passed through otherwise the message is rejected by the Hub Care360 Order Message Format Requirements 63 64 Data Type Specifications The following table describes the data types that may appear in the message segments Note Brackets indicate that the enclosed data is optional Data Type Category Data Type Data Type Name Notes Format Alphanumeric ST String Any ACSII printable characters ASCII decimal values between 32 and 126 with the exception of the defined delimiter characters Left justified with optional trailing spaces FT Formatted text String data with embedded formatting instructions
285. wledgment Type MSH 17 Country Code ID 2 NS MSH 18 Character Set ID 6 NS MSH 19 Principal CE 60 NS Language of Message a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported ADT A39 Patient Merge Message Segment Specifications 223 224 EVN Event Type Segment The Event Type EVN segment is used to communicate necessary trigger event information to receiving applications Segment ID Element Name Type Length Comments Req d EVN 00 Segment ST 4 Must be EVN R Type ID EVN 01 Event Type Code ID 3 The second component trigger event R of MSH 09 Message Type should be used to transmit event type code information This field contains the events corresponding to the trigger events described in this section Note This field has been retained for backward compatibility only EVN 02 Recorded TS 26 NS Date Time EVN 03 Date Time TS 26 NS Planned Event EVN 04 Event Reason IS 3 NS Code EVN 05 Operator ID XCN 60 NS EVN 06 Event Occurred TS 26 NS a For a description of the HL7 data types see Data Type Specifications on page 176 b R Required O Optional C Conditional NS Not Supported PID Patient Identification Segment Correct The Patient Identification PID segment is used by all applications as the primary means of commun
286. y E 59T 2 Cervical Cytology Smear E 59T 3 Genital Cytology Female E 59T 4 PAP Smear E 59T 5 Papanicolaou Smear E 5538T l PAP E 5538T 2 CYTOLOGY E 5538T 3 THINPREP E 83337T 1 PAP E 83337T 2 CYTOLOGY E 83337T 3 THINPREP E 87122A l Breast Discharge E 87122A 2 Breast FNA or Nipple Discharge E 89953A l Cytology Prostatic Smear E 89953A 2 Endometrial Smear Cytology E 89953A 3 Fine Needle Aspiration Cytology E 89953A 4 Prostatic Smear Cytology 105262kE l Sputum Cytology 10684R l Ascitic Fluid Cytology 10684R 2 Cytology Gastrointestinal 10684R 3 Cytology Genital Male 10684R 4 Fluid Cytology 10684R 5 Pericardial Fluid Cytology 10684R 6 Peritoneal Fluid Cytology 10684R 7 Pleural Fluid Cytology 0684R 8 Spinal Fluid Cytology 10684R 9 Spinal Fluid Cytology 10684R 10 Synovial Fluid Cytology 10684R ll Thoracic Fluid Cytology 10700E l Urine Cytology 15003X 1 THINPREP WITH HPV HIGH RISK 15003X 2 THINPREP AND HPV HIGH RISK 125F 1 Cell Block and Smears 125F 2 Bone Marrow Aspirate 4861A l Pemphigoid Tissue E 4812A l Immunohistochemistry E 4812A 2 Immunohistology E 4812A 3 Immunoperoxidase E 66472A l Pneumocystis Carinii Stain E 66472A 2 Silver methenamine Stain E 66472A 3 Special Stains for Histopathology 66472A 4 Stain Special for Tissue Pathology P1568 1 ABO Rh and antibody screen P1568 2 Type and hold P1568 3 Type and screen P2261 1 9872 P2707 1 HYPOTHYROID PROF
287. y company that develops applications to support physicians with practice management electronic prescribing electronic medical records or similar office automation products Third Party Payment Payment or reimbursement amounts that are established by third party drug programs for prescriptions and services dispensed to recipients UDDI Universal Description Discovery and Integration is an XML based specification for a registry of businesses and the Web services they offer By providing the necessary translations it enables software to automatically discover Web services and integrate with them User An administrator who is authorized to access Hub Information Services Administration to perform management tasks or an authorized account used by a vendor to interact with Care360 Hub Information Services Vendor An organization that connects to providers to distribute information or data to their customers Customers of vendors typically include physicians offices IPAs clinics and hospitals Also referred to as EMR vendor WSDL Web Services Description Language lets developers expose the syntax of a Web service Using an XML format it describes network services as a set of endpoints operating on messages containing either document or procedure oriented information The operations and messages are described abstractly and then bound to a concrete network protocol and message format to define the endpoints XML Extensi
288. y existing data in Physician Portal e Fuzzy Matching This method requires the partner application to pass a minimum set of patient demographic data in addition to the PID to identify the patient Physician Portal uses the supplied patient demographic data to attempt to identify the matching patient s to complete the patient demographic update request For additional information see PID Only Matching Detail on page 141 and 6666 Fuzzy Matching Detail on page 142 PID Only Matching Detail The following table provides additional details on the rules associated with PID only matching for patient demographic updates PID Only Matching Request Potential Results Add Patient If the incoming PID matches no existing patient in the target organization the patient is added If the incoming PID matches a single patient in the target organization that patient is updated If the incoming PID matches more than one existing patient Physician Portal returns an error to the partner application Update Patient If the incoming PID matches no existing patient in the target organization the patient is added If the incoming PID matches a single patient in the target organization that patient is updated If the incoming PID matches more than one existing patient Physician Portal returns an error to the partner application Delete Patient If the incoming PID matches no existing patient
289. ysician Portal Master Patient Member Index An index or file with a unique identifier for each patient or member that serves as a key to a patient s or member s health record Patient Consent The written or verbal permission given by a patient for the release and use of their personal information Payor The party or group an individual contracts with to cover healthcare services unless the patient is paying out of pocket This is sometimes referred to as a third party payor Physician Practice Management System PPMS Technology Provider A physician practice management system company who supports medical office administration with applications and support Provider An organization that provides information or data to Care360 Hub Information Services Organizations can include reference labs esoteric labs hospitals payers radiology clinics clearinghouses pharmacies or PBMs Also referred to as service provider Provider Account An organization that uses the services of a provider such as a physician s office an IPA a clinic or a hospital The provider account uniquely defines the organization allowing accurate distribution of data to an authorized entity Quality Can be defined as a measure of the degree to which delivered health services meet established professional standards and judgments of value to the consumer Quality may also be seen as the degree to which actions taken or not taken impact the likel

Message Segment Specifications

Contents

Download Pdf Manuals

Related Search

Related Contents