HIE Ready 2.0
HIE Ready 2.0
Entity Name:
Street Address:
City, State, Zip:
Point of Contact Name:
E-mail & Phone:
Alternate Contact Name:
Alternate E-mail & Phone:
Product Name:_______________________________________ Version Number: _________
Please indicate "Yes" in the column labeled "Does EHR meet this standard?" based on your organization's capabilities. A "Yes" signifies that your organization receives, stores, consumes, creates, sends, transmits, and/or submits a particular message (which can be inbound or outbound or both) in the respective context, and using the standard stated.
Preferred Message and Trigger
Does EHR meet this standard?
(Yes / No)
1.0
1.1.a
1.1.b
1.2.a
1.2.b
1.3
1.4.a
1.4.b
1.5
1.6
Patient Encounter, Person Maintenance, and Patient Merge ADT Messages
HL7 2.5.1 ADT^A01 Receive Hospital Admission (Inbound)
HL7 2.5.1 ADT^A01 Send Hospital Admission (Outbound)
HL7 2.5.1 ADT^A03 Receive Hospital Discharge (Inbound)
HL7 2.5.1 ADT^A03 Send Hospital Discharge (Outbound)
HL7 2.5.1 ADT^A03 Receive Emergency Discharge (Inbound)
HL7 2.5.1 ADT^A04 Receive Register Patient message from
Ambulatory or Emergency Department setting (Inbound)
HL7 2.5.1 ADT^A04 Send Register Patient message, that is automatically generated upon completion of a registration process
(Outbound)
HL7 2.5.1 ADT^A04 Send Register Outpatient Visit message
(Outbound)
HL7 2.5.1 ADT^A04 Send Emergency Registration (Outbound)
Copyright © 2013 The California Health and Human Services Agency (CHHS). All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"), you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0
.
Unless required by applicable law or agreed to in writing, content (including but not limited to software, documentation, information, and all other works distributed under the License) is distributed on an "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE CONTENT OR THE USE OR OTHER DEALINGS IN THE CONTENT. IN NO EVENT SHALL CHHS HAVE ANY OBLIGATION TO PROVIDE SUPPORT, UPDATES,
AND/OR UPGRADES FOR CONTENT. See the License for the specific language governing permissions and limitations under the License.
This publication/product was made possible by Award Number 90HT0029 from Office of the National Coordinator for Health Information Technology (ONC), U.S. Department of Health and
Human Services. Its contents are solely the responsibility of the authors and do not necessarily represent the official views of ONC or the State of California.

HIE Ready 2.0
1.8.a
1.8.b
1.9.a
1.9.b
1.10.a
1.10.b
2.0
2.1.a
2.1.b
3.0
3.1.a
3.1.b
3.2.a
3.2.b
3.3.a
3.3.b
Preferred Message and Trigger
HL7 2.5.1 ADT^A08 Receive Update of Patient Demographic
Information (Inbound)
HL7 2.5.1 ADT^A08 Send Update of Patient Demographic Information
(Outbound)
HL7 2.5.1 ADT^A31 Receive Person Update (Inbound)
HL7 2.5.1 ADT^A31 Send Person Update (Outbound)
HL7 2.5.1 ADT^A40 Receive Patient Merge (Inbound)
HL7 2.5.1 ADT^A40 Send Patient Merge (Outbound)
Does EHR meet this standard?
(Yes / No)
Master File Updates for Patient Locations
HL7 2.5.1 MFN^M05 Receive Update of Patient Location Master File
(Inbound)
HL7 2.5.1 MFN^M05 Send Update of Patient Location Master File
(Outbound)
Laboratory Results as Electronic Structured Data
§170.205(j)
1
Receive and incorporate clinical lab-test results as structured data. Standard: HL7 version 2.5.1 AND Implementation
Guide: S&I Framework Lab Results Interface (incorporated by reference in §170.299), AND §170.207(c)(2) Receive and consume lab
® test results. LOINC Database version 2.40 (incorporated by reference in §170.299) (Inbound)
§170.205(j) Create and transmit clinical lab-test results as structured data. Standard: HL7 version 2.5.1 AND Implementation Guide: S&I
Framework Lab Results Interface (incorporated by reference in
§170.99), AND §170.207(c)(2) Receive and consume lab test results.
LOINC
®
Database version 2.40 (incorporated by reference in §170.299)
(Outbound)
§170.207(a)(3) Receive and consume IHTSDO SNOMED CT
®
International Release July 2012 (incorporated by reference §170.299) and US Extension to SNOMED CT
®
March 2012 Release (Inbound)
§170.207(a)(3) Create and send IHTSDO SNOMED CT
®
International
Release July 2012 (incorporated by reference §170.299) and US
®
Extension to SNOMED CT March 2012 Release (Outbound)
Receive and consume HL7 2.5.1 "no growth" and "preliminary" result messages and update the order status appropriately (OBR Result Status
= I, S, A, P and, depending upon usage, R) (Inbound)
Create and send HL7 2.5.1 "no growth" and "preliminary" result messages and update the order status appropriately (OBR Result Status
= I, S, A, P and, depending upon usage, R) (Outbound)
1
Unless otherwise indicated, all code section numbers refer to the United States Federal Register, 45 CFR 170, et seq .
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 2 of 11

HIE Ready 2.0
4.0
4.1.a.1
4.1.a.2
4.1.b
5.0
5.1.a
5.1.b
6.0
6.1.a
6.1.b
6.2.a
6.2.b
6.3.a
6.3.b
6.4.a
6.4.b
6.5.a
6.5.b
Preferred Message and Trigger
Radiology Reports
HL7 2.5.1 ORU^R01 Receive and store Radiology Report as HL7 2.5.1
ORU or MDM (Inbound)
HL7 2.5.1 ORU^R01 Receive and consume Radiology Report as HL7
2.5.1 ORU or MDM (Inbound)
HL7 2.5.1 ORU^R01 Create and send Radiology Report as HL7 2.5.1
ORU or MDM (Outbound)
Corrected and Canceled Result Messages
Receive and consume HL7 2.5.1 result correction messages (OBR
Result Status = C) and order cancel messages received (OBR Result
Status = X) AND update the order status appropriately based on the message (Inbound)
Create and send HL7 2.5.1 result correction messages (OBR Result
Status = C) AND create and send order cancel messages (OBR Result
Status = X) (Outbound)
Does EHR meet this standard?
(Yes / No)
Text Reports
(e.g., H&P, ECG, Discharge Summary, Colonoscopy Report,
Progress Notes, Consult Notes, Other Hospital Discharge Summary, etc.)
HL7 2.5.1 MDM^T02 Receive and store original document notification and content, OR , alternative method for receiving text reports: HL7
2.5.1 ORU^R01 Unsolicited transmission of an observation message
(result status is in OBR) (Inbound)
HL7 2.5.1 MDM^T02 Send original document notification and content,
OR , alternative method for sending text reports: HL7 2.5.1 ORU^R01
Unsolicited transmission of an observation message (result status in in
OBR) (Outbound)
HL7 2.5.1 MDM^T04 Receive and store document status change notification and content (Inbound)
HL7 2.5.1 MDM^T04 Send document status change notification and content (Outbound)
HL7 2.5.1 MDM^T06 Receive and store document addendum notification and content (Inbound)
HL7 2.5.1 MDM^T06 Send document addendum notification and content (Outbound)
HL7 2.5.1 MDM^T08 Receive and store document edit notification and content (Inbound)
HL7 2.5.1 MDM^T08 Send document edit notification and content
(Outbound)
HL7 2.5.1 MDM^T10 Receive and store document replacement notification and content (Inbound)
HL7 2.5.1 MDM^T10 Se nd document replacement notification and content (Outbound)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 3 of 11

HIE Ready 2.0
7.0
7.1.a
7.1.b
8.0
8.1.a
8.1.b
8.2.a
8.2.b
8.3.a
8.3.b
8.4.a
8.4.b
8.5.a
8.5.b
9.0
9.1.a
9.1.b
9.2.a
9.2.b
Preferred Message and Trigger
Transcription
HL7 2.5.1 MDM^T02 Receive and store original document notification and content for Transcription (Inbound)
HL7 2.5.1 MDM^T02 Create and send original document notification and content for Transcription (Outbound)
Does EHR meet this standard?
(Yes / No)
Electronic Orders
HL7 2.5.1 ORM^O01 Receive and store order messages (Inbound)
HL7 2.5.1 ORM^O01 Create and send order messages (Outbound)
HL7 2.5.1 ORM^O01 Receive and store laboratory order messages
(Inbound)
HL7 2.5.1 ORM^O01 Create and send laboratory order messages
(Outbound)
HL7 2.5.1 ORM^O01 Receive and store radiology order messages
(Inbound)
HL7 2.5.1 ORM^O01 Create and send radiology order messages
(Outbound)
HL7 2.5.1 ORM^O01 Receive and store other ancillary services order messages (Inbound)
HL7 2.5.1 ORM^O01 Create and send other ancillary services order messages (Outbound)
Receive and consume HL7 2.5.1 ORM messages with 3 or more "Copy to" providers (Inbound)
Create and send HL7 2.5.1 ORM messages with 3 or more "Copy to" providers (Outbound)
Patient Referral Request
HL7 2.5.1 REF^I12 Receive and store patient referral request, OR , alternatively, HL7 2.5.1 ORM^O01 is used for this action (Inbound)
HL7 2.5.1 REF^I12 Automatically send patient referral request, OR , alternatively, HL7 2.5.1 ORM^O01 is used for this action (Outbound)
HL7 2.5.1 RRI^I12 Receive and consume acknowledgement of patient referral request response (Inbound)
HL7 2.5.1 RRI^I12 Create and send acknowledgement of patient referral request received (Outbound)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 4 of 11

HIE Ready 2.0
Preferred Message and Trigger
10.0
10.1.a.1
10.1.a.2
10.2.a.1
10.2.a.2
10.2.b
10.3.a.1
10.3.a.2
10.3.b
10.4
Transitions of Care Using CCD C32
Receive and store a CCD C32 document as specified in the CDA
Release 2.1 as further refined by HITSP in its component specification
(Inbound)
Receive and consume the discrete and textual sections of a CCD C32 document as specified in the CDA Release 2.1 as further refined by
HITSP in its component specification (Inbound)
Receive and store a CCD according to Direct Project standards
Applicability Statement for Secure Health Transport, Version 1.1, 10
July 2012 (incorporated by reference in §170.299) (Inbound)
Receive and consume a CCD according to Direct Project Applicability
Statement for Secure Health Transport, Version 1.1, 10 July 2012
(incorporated by reference in §170.299) (Inbound)
Send CCD according to Direct Project Applicability Statement for
Secure Health Transport, Version 1.1, 10 July 2012 (incorporated by reference in §170.299) (Outbound)
Receive and store CCD via IHE XDS.b standards as a Document
Consumer (Inbound)
Receive and consume CCD via IHE XDS.b standards as a Document
Consumer (Inbound)
Send CCD via IHE XDS.b standards as a Document Source or
Integrated Document Source Repository (Outbound)
Provide a configurable ability to automatically create and transmit a
CCD (Outbound)
11.0
11.1.a.1
11.1.a.2
11.1.b
Transitions of Care Using Consolidated CDA Documents
§170.205(a)(3) Receive and store clinical summary: HL7
Implementation Guide for CDA
®
Release 2: IHE Health Story
Consolidation, (incorporated by reference in §170.299) (Note: The use of the “unstructured document” document level template is prohibited)
(Inbound)
§170.205(a)(3) Receive and consume clinical summary: HL7
Implementation Guide for CDA
®
Release 2: IHE Health Story
Consolidation, (incorporated by reference in §170.299) (Note: The use of the “unstructured document” document level template is prohibited)
(Inbound)
§170.205(a)(3) Create and send clinical summary: HL7
Implementation Guide for CDA
®
Release 2: IHE Health Story
Consolidation, (incorporated by reference in §170.299) (Note: The use of the “unstructured document” document level template is prohibited)
(Outbound)
Does EHR meet this standard?
(Yes / No)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 5 of 11

HIE Ready 2.0
11.2.a.1
11.2.a.2
11.2.b
11.3.a.1
11.3.a.2
11.3.b
11.4
11.5
11.6
11.7
Preferred Message and Trigger
§170.202(a) Receive and store Consolidated CDA documents according to Direct Project Applicability Statement for Secure Health Transport,
Version 1.1, 10 July 2012 (incorporated by reference in §170.299)
(Inbound)
§170.202(a) Receive and consume Consolidated CDA documents according to Direct Project Applicability Statement for Secure Health
Transport, Version 1.1, 10 July 2012 (incorporated by reference in
§170.299) (Inbound)
§170.202(a) Create and send Consolidated CDA documents according to Direct Project Applicability Statement for Secure Health Transport,
Version 1.1, 10 July 2012 (incorporated by reference in §170.299)
(incorporated by reference in §170.299) (Outbound)
Does EHR meet this standard?
(Yes / No)
§170.202(b) Receive and store Consolidated CDA documents using transport standards: ONC XDR and XDM for Direct Messaging
Specification, version 1, finalized 9 March 2011 (incorporated by reference in §170.299) (Inbound)
§170.202(b) Receive and consume Consolidated CDA documents using transport standards: ONC XDR and XDM for Direct Messaging
Specification, version 1, finalized 9 March 2011 (incorporated by reference in §170.299) (Inbound)
§170.202(b) Create and send Consolidated CDA documents using transport standards: ONC XDR and XDM for Direct Messaging
Specification, version 1, finalized 9 March 2011 (incorporated by reference in §170.299) (Outbound)
§170.207(a)(3) Within a Consolidated CDA regarding a Problem List :
IHTSDO SNOMED CT® International Release July 2012
(incorporated by reference in §170.299) and US Extension to
SNOMED CT
®
March 2012 Release (incorporated by reference in
§170.299)
§170.207(c)(2) Within a Consolidated CDA regarding Laboratory
Tests : LOINC
®
Database version 2.40 (incorporated by reference in
§170.299)
§170.207(d)(2) Within a Consolidated CDA regarding Medications :
RxNorm, a standardized nomenclature for clinical drugs produced by the United States National Library of Medicine, August 6, 2012 Release
(incorporated by reference in §170.299)
§170.207(e)(2) Within a Consolidated CDA regarding Immunizations :
LOINC
®
Database version 2.40 (incorporated by reference in
§170.299)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 6 of 11

HIE Ready 2.0
Preferred Message and Trigger
11.8
11.9
11.10
§170.207(f) Within a Consolidated CDA regarding Race and Ethnicity :
The Office of Management and Budget Standards for Maintaining,
Collecting, and Presenting Federal Data on Race and Ethnicity,
Statistical Policy Directive No. 15, as revised, October 30, 1997 (see
“Revisions to the Standards for the Classification of Federal Data on
Race and Ethnicity,” available at http://www.whitehouse.gov/omb/fedreg_1997standards)
§170.207(g) Within a Consolidated CDA regarding Preferred
Language : As specified by the Library of Congress, ISO 639-2 alpha-3 codes limited to those that also have a corresponding alpha-2 code in
ISO 639-1 (incorporated by reference in §170.299)
§170.207(h) Within a Consolidated CDA regarding Smoking Status :
Smoking status must be coded in one of the following SNOMED CT® codes: (1) Current every day smoker. 449868002; (2) Current some day smoker. 428041000124106; (3) Former smoker. 8517006; (4) Never smoker. 266919005; (5) Smoker, current status unknown. 77176002;
(6) Unknown if ever smoked. 266927001; (7) Heavy tobacco smoker.
428071000124103; (8) Light tobacco smoker. 428061000124105
11.11
11.12.a.1
§170.207(i) Within a Consolidated CDA regarding Encounter
Diagnoses : Properly utilize and employ the code set specified at 45
CFR §162.1002(c)(2) for the indicated conditions [45 CFR
§162.1002(c)(2) International Classification of Diseases, 10th Revision,
Clinical Modification (ICD–10–CM) (including The Official ICD–10–
CM Guidelines for Coding and Reporting), as maintained and distributed by HHS, for the following conditions: (i) Diseases. (ii)
Injuries. (iii) Impairments. (iv) Other health problems and manifestations. (v) Causes of injury, disease, impairment, or other health problems]
Document Consumer: Retrieve and store documents via IHE XDS.b standards as a Document Consumer from one or more Document
Repository (IHE IT Infrastructure Technical Framework, Vol. 1
Integration Profiles, Rev. 9.0 Final Text - 2012-08-31) (Inbound)
11.12.a.2 Document Consumer: Retrieve and consume documents via IHE XDS.b standards as a Document Consumer from one or more Document
Repository (IHE IT Infrastructure Technical Framework, Vol. 1
Integration Profiles, Rev. 9.0 Final Text - 2012-08-31) (Inbound)
11.13.b Document Source: Create and send documents via IHE XDS.b standards as a Document Source to a Document Repository (IHE IT
Infrastructure Technical Framework, Vol. 1 Integration Profiles, Rev.
9.0 Final Text - 2012-08-31) (Outbound)
Does EHR meet this standard?
(Yes / No)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 7 of 11

HIE Ready 2.0
11.14
11.15
11.16
12.0
12.1
13.0
13.1
13.2
14.0
14.1
14.2
14.3
Preferred Message and Trigger
Document Repository: Receive and store documents via IHE XDS.b standards as a Document Repository (IHE IT Infrastructure Technical
Framework, Vol. 1 Integration Profiles, Rev. 9.0 Final Text - 2012-08-
31) (Inbound)
Document Registry: Respond to queries from Document Consumers for documents via IHE XDS.b standards as a Document Registry (IHE IT
Infrastructure Technical Framework, Vol. 1 Integration Profiles, Rev.
9.0 Final Text - 2012-08-31) (Outbound)
Provide a configurable ability to automatically create and transmit
Consolidated CDAs (Outbound)
Does EHR meet this standard?
(Yes / No)
Transfer Context and Control
Provide capability to transfer context and control using context-aware interfaces: HL7 Context Management "CCOW" Standard Version 1.6,
February 2011
Patient Engagement
Provide web-access for patients to Transmit Data § 170.204(a) – Web
Content Accessibility Guidelines (WCAG) 2.0, Level A Conformance
Alignment with all BlueButton+ Content Standards: http://bluebuttonplus.org/
Immunization Registries Data Submission
Create and submit electronic immunization data to immunization registries or immunization information systems: §170.205(e)(3) HL7
2.5.1 (incorporated by reference §170.299), and Implementation specifications in Implementation Guide for Immunization Messaging
Release 1.4) (Outbound)
Create and submit electronic immunization data: §170.207(e)(2) HL7
Standard Code Set CVX - Vaccines Administered, updates through July
11, 2012 (incorporated by reference §170.299) (Outbound)
Create and submit electronic immunization data in compliance with
California Department of Public Health (CDPH) FAQs re
Immunization Electronic Data Submission: http://cairweb.org/images/docs/CAIR_HL7v251_Spec_for_web.pdf
(Outbound)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 8 of 11

HIE Ready 2.0
15.0
15.1
15.2
15.3
16.0
16.1
17.0
17.1
17.2
17.3
Preferred Message and Trigger
Lab Results to Public Health Agencies
§170.205(g) Create and send lab results to public health agencies using
HL7 2.5.1 and Implementation specifications: Implementation Guide:
Electronic Laboratory Reporting to Public Health, Release 1 (US
Realm) (incorporated by reference in §170.299) with Errata and
Clarifications, and ELR 2.5.1 Clarification Document for EHR
Technology Certification) (Outbound)
§170.207(a)(3) Create and send lab results to public health agencies
® using: IHTSDO SNOMED CT International Release July 2012
(incorporated by reference §170.299) and US Extension to SNOMED
CT
®
March 2012 Release (incorporated by reference §170.299) AND
§170.207(c)(2)LOINC
®
Version 2.40 (Outbound)
Create and send lab results to public health agencies using California requirements: California Reportable Disease Information Exchange
(CalREDIE) Electronic Laboratory Records (ELR) User Guide August
2013, AND California Reportable Disease Information Exchange
(CalREDIE) HL7 2.5.1 ELR2PH Companion Guide Version 1.02, July
2012 (Outbound)
Does EHR meet this standard?
(Yes / No)
Syndromic Surveillance Data Submission
§170.205(d)(2) AND §170.205(d)(3) Create and submit syndromic surveillance data using (ambulatory setting only): HL7 2.5.1
(incorporated by reference in §170.299) AND Implementation specifications: PHIN Messaging Guide for Syndromic Surveillance and
Conformance Clarification for EHR Certification of Electronic
Syndromic Surveillance, Addendum to PHIN Messaging Guide for
Syndromic Surveillance) (Outbound)
Cancer Registries (Report Cancer Cases)
Identify and report cancer cases to State cancer registry (except where prohibited, and in accordance with applicable law and practice), see
California Cancer Registry at http://www.ccrcal.org/ (Outbound)
Create and send cancer information to State cancer registry:
§170.205(i) HL7 Clinical Document Architecture (CDA), Release 2.0,
Normative Edition (incorporated by reference in §170.299) AND
Implementation specifications in Implementation Guide for Ambulatory
Healthcare Provider Reporting to Central Cancer Registries, HL7
Clinical Document Architecture (CDA) (Outbound)
Create and send cancer information to State cancer registry:
§170.207(a)(3) IHTSDO SNOMED CT
®
2012 and US Extension to SNOMED CT
International Release July
®
March 2012 Release AND
§170.207(c)(2) LOINC
®
Version 2.40 (Outbound)
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 9 of 11

HIE Ready 2.0
Preferred Message and Trigger
18.0 Clinical Quality Measures (CQMs)
18.1 §170.204(c) Create and send Clinical quality measure-by-measure data:
Data Element Catalog) [http://www.nlm.nih.gov/healthit/dec/]
(Outbound)
Does EHR meet this standard?
(Yes / No)
Interfaces and Hosting Yes / No
Interface is integral to the EHR software. No additional hardware, software, or hosting components required.
Interface is a separate software component. Software costs are included in the interface cost, but additional hardware may be required.
Interface is a separate appliance. Hardware and software costs are included in the interface cost.
Interface is a separate hosted service. Software and hosting services are included in the interface cost.
Interface is a separate hosted service. Software is included in the interface cost; however, a hosting company MAY charge extra.
Pricing Details:
ENTITY-EHR Provider catalog HIE Ready price per instance in
California for any client on maintenance with ENTITY-EHR
Provider and on the currently supported product version for items listed above as EHR meeting this standard:
Annual Maintenance cost to the client:
$_______________
$_______________
Additional explanation of pricing if any: _____________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 10 of 11

HIE Ready 2.0
For ENTITY:
Signed By:
Name:
Title:
Date:
January 21, 2014
HIE R EADY 2.0
S PECIFICATIONS
Page 11 of 11