Request for Information NJ Health Information Network. State of New Jersey. New Jersey HIT Coordinators Office. Request for Information

Similar documents
ONC Cooperative Agreement HIE Program Update. Arizona Rural & Public Health Policy Forum January 19, 2012

Texas Approach to Supporting Statewide Health Information Exchange. January 2013

Patient Unified Lookup System for Emergencies (PULSE) System Requirements

Nonprofit partnership. A grass roots organization where Board of Directors have vested interest in its success.

Medicaid EHR Incentive Program Health Information Exchange Objective Stage 3 Updated: February 2017

Roll Out of the HIT Meaningful Use Standards and Certification Criteria

Agenda. NE CAH Region Discussion

during the EHR reporting period.

The American Recovery and Reinvestment Act: Incentivizing Investments in Healthcare

Health Information Exchange. Anne Dobbins, RN Operations Director Minnesota Health Information Exchange (MN HIE)

SUBMIT/RECEIVE STATEWIDE ADMISSION, DISCHARGE, TRANSFER (ADT) NOTIFICATIONS

1. What are the requirements for Stage 1 of the HITECH Act for CPOE to qualify for incentive payments?

The Road to Innovation: An Update on NJ s Health and Healthcare Initiatives June 23, 2015

Tools for Providers. Clinical Care and Practice AdvancementElectronic Health Records (EHR)

HIE & Interoperability: Roadmap to Continuum of Care Michael McPherson MU Coordinator KDHE

Pharmacy Health Information Exchange The promise. The reality. The future.

Accessing HEALTHeLINK

Building Blocks for HIE in California

ESRD Network 14. Supporting Quality Care

Drew McNichol Director of Technology. HIMSS NY Chapter June 17, 2015

Pennsylvania Patient and Provider Network (P3N)

Missouri Health Connection. One Connection For A Healthier Missouri

Health Information Exchange 101. Your Introduction to HIE and It s Relevance to Senior Living

The Massachusetts ehealth Institute

Medicaid and HIT: EHR s s for Medicaid Providers

Transforming Health Care with Health IT

Health Information Exchange and Telehealth: Opportunities for Integration!

Alaska Medicaid Program

Maryland s Health Information Exchange 6 th National Medicaid Congress

HIE Implications in Meaningful Use Stage 1 Requirements

Eligible Professionals. How can the West Virginia Health Information Network (WVHIN) assist you in meeting Meaningful Use requirements?

Data Sharing Consent/Privacy Practice Summary

Health Current: Roadmap Practice Transformation using Information & Data

California s ehealth Planning Approach. June 30, 2010 National Governor s Association Webinar

SWAN Alerts and Best Practices for Improved Care Coordination

CIO Legislative Brief

How to Participate Today 4/28/2015. HealthFusion.com 2015 HealthFusion, Inc. 1. Meaningful Use Stage 3: What the Future Holds

THE MEANING OF MEANINGFUL USE CHANGES IN THE STAGE 2 MU FINAL RULE. Angel L. Moore, MAEd, RHIA Eastern AHEC REC

Measures Reporting for Eligible Providers

Florida Health Information Exchange Status FHA AHCA Harris Meeting August 23, 2012

What Does HIE (verb) Do?

STAGE 2 PROPOSED REQUIREMENTS FOR MEETING MEANINGFUL USE OF EHRs 1

Memorial Hermann Information Exchange. MHiE POLICIES & PROCEDURES MANUAL

The Future of HIE in Alaska

Medicare and Medicaid EHR Incentive Program. Stage 3 and Modifications to Meaningful Use in 2015 through 2017 Final Rule with Comment

PBSI-EHR Off the Charts Meaningful Use in 2016 The Patient Engagement Stage

Meaningful Use Stage 2

Kentucky HIE Examples of Successful Interoperability Description Template

Calibrating your tablet allows you to ensure accuracy as you handwrite on the screen and/or select items on the screen. Prime Clinical Systems, Inc 1

Medicaid EHR Provider Incentive Payment Program. January 2011

Overview of the EHR Incentive Program Stage 2 Final Rule published August, 2012

Policies Targeting Payer Harmonization: The Provider Perspective

EHR Incentive Programs for Eligible Professionals: What You Need to Know for 2016 Tipsheet

HIE/HIO Organizations Supporting Meaningful Use (MU) Stage 2 Goals

Welcome to Rochester RHIO s GET DIRECTed! Denise DiNoto Director of Community Services March 2014

2016 MEANINGFUL USE AND 2017 CHANGES to the Medicare EHR Incentive Program for EPs. September 27, 2016 Kathy Wild, Lisa Sagwitz, and Joe Pinto

Measures Reporting for Eligible Hospitals

Trends in Health Information Exchange (HIE) and Links to Medicaid Led Quality Improvement

Care360 EHR Frequently Asked Questions

HIE-HIT Advisory Committee Kickoff Meeting. June 15, 2011 MTC Office, 2 Center Plaza, Suite 440, Boston

Meaningful Use Hello Health v7 Guide for Eligible Professionals. Stage 2

WV MEDICAID PROVIDER WORKSHOPS & TRAINING SESSIONS. Amber Nary Business Development Manager

Staff Training. Understanding Healthix Patient Consent

San Diego Beacon Community Collaborative. James Killeen, MD

HITECH Act. Overview and Estimated Timeline

Meaningful Use Reporting period for 2017: Change: Any consecutive 90 days in 2017 for Medicaid customers only.

New York State Department of Health Innovation Initiatives

CHIME Concordance Analysis of Stage 2 Meaningful Use Final Rule - Objectives & Measures

HIE Implications in Meaningful Use Stage 1 Requirements

Iatric Systems Supports the Achievement of Meaningful Use

WHO SHARES? A look at the status of HIT and HIE in Arkansas

Michigan s Statewide Health Information Network

Medicare and Medicaid Programs: Electronic Health Record Incentive Program -- Stage 3 and Modifications to Meaningful Use in 2015 through 2017

2015 MEANINGFUL USE STAGE 2 FOR ELIGIBLE PROVIDERS USING CERTIFIED EMR TECHNOLOGY

Overview of the Changes to the Meaningful Use Program Called for in the Proposed Inpatient Prospective Payment System Rule April 27, 2018

STATE OF TEXAS TEXAS STATE BOARD OF PHARMACY

Meaningful Use Certification Details

Quanum Electronic Health Record Frequently Asked Questions

Medicaid Health Information Technology Plan (MHP)

MEANINGFUL USE STAGE 2

Meaningful Use Update: Stage 3 and Beyond. Carla McCorkle, Midas+ Solutions CQM Product Lead

Medicaid EHR Provider Incentive Payment Program. September 26, 2011

Final Meaningful Use Rules Add Short-Term Flexibility

American Recovery & Reinvestment Act

Community Health Centers. May 6, 2010

Electronic Health Records and Meaningful Use

Personal Information Banks Directory as of January 1, 2012

Medicaid EHR Incentive Program Electronic Submission of Clinical Quality Measures Request for Information (RFI) RFI # DHCAA

Meaningful Use Modified Stage 2 Roadmap Eligible Hospitals

University of Maine System Electronic Medical Record (EMR) Cloud Solution - RFP# ADDENDUM #01

Proposed Regulations NEW YORK STATE DEPARTMENT OF HEALTH Return to Public Health Forum

Clinical Staffing. Primary Reviewer: Clinical Expert Secondary Reviewer: Governance/Administrative Expert, if needed

INFORMATION ABOUT YOUR OXFORD COVERAGE REIMBURSEMENT PART I OXFORD HEALTH PLANS OXFORD HEALTH PLANS (NJ), INC.

Meaningful Use What You Need to Know for December 6, 2016

Healthcare Identifiers Service Information Guide

The results will also be used for public reporting for MN Community Measurement on mnhealthscores.org.

Delaware Health Information Network Town Hall Wednesday, July 13, :00 a.m. 12:00 p.m.

Medicaid EHR Incentive Program Audits. CMS Multi-Regional Meeting - Regions 1, 2 & 3 September 4, 2014

Meaningful Use Stage 2. Physicians February 2013

Patient Centered Data Home. David Kendrick, MD, MPH CEO, MyHealth Access Network SHIEC Board of Directors

Transcription:

State of New Jersey New Jersey HIT Coordinators Office Request for Information New Jersey s Health Information Exchange The New Jersey Health Information Network (NJHIN) July 1, 2011 Page 1 of 11

Table of Contents 1.0 PURPOSE... 3 2.0 DESCRIPTION OF THE NEW JERSEY HEALTH INFORMATION NETWORK (NJHIN)... 3 2.1 BACKGROUND AND CURRENT ENVIRONMENT... 4 2.2 NJHIN TECHNOLOGY FRAMEWORK... 4 2.3 CORE TECHNICAL SERVICES... 6 2.4 CLINICAL FUNCTIONALITY AND PRIORITY USE CASES... 7 3.0 VENDOR RESPONSE INSTRUCTIONS... 8 3.1 DISCLAIMERS... 9 3.2 RFI RESPONSES... 9 4.0 TERMS AND CONDITIONS... ERROR! BOOKMARK NOT DEFINED.13 5.0 STATE OF NEW JERSEY FACT SHEET... 10 6.0 STATE OF NEW JERSEY HEALTH INFORMATION TECHNOLOGY OPERATIONAL PLAN. 11 Page 2 of 11

1.0 PURPOSE The State of New Jersey envisions a statewide Health Information Exchange -- the New Jersey Health Information Network (NJHIN) -- which will facilitate data exchanges among the HIEs operating in the state, as well as with HIEs in other states and the Nationwide Health Information Network (NwHIN). The high-level functions of NJHIN and the services it will provide are described in the State of New Jersey HIT Operational Plan, as approved by the Office of the National Coordinator, and have been further defined in Appendix A of this RFI The goal of this RFI is to obtain information regarding component functions and general pricing ranges, so that we may consider various models based on our desired functionality and our available budget. This RFI is an initial step in New Jersey s implementation process and may be followed by a request for proposal (RFP). The RFP to contract with a partner to design, develop and implement the NJHIN may be issued at a future stage. Respondents are expected to describe a single, complete solution. Indicate if your response requires collaboration with or inclusion of additional partners as well as whether you have a relationship with identified partners. The collaboration should demonstrate the capability to provide a comprehensive solution and should describe the specific detail regarding how product(s) will be integrated. Further, New Jersey encourages respondents to provide innovative approaches related to the financial sustainability of the services being provided. In that context, Respondents should provide approaches to funding the core services and the clinical functionality requirements as outlined in this request. Further, additional services outside of those requested, that support sustainability, may be proposed as well. 2.0 DESCRIPTION OF THE NEW JERSEY HEALTH INFORMATION NETWORK (NJHIN) The following sections provide an overview of the services to be provided through the NJHIN. Additionally, information has been provided which outlines the background and current environment, the proposed technical framework of the NJHIN, the core services, and the required clinical functionality as outlined through priority use cases. Respondents should address whether they can provide the defined functionality or offer alternatives. Respondents may also offer alternative models for the clinical functionality. Note that the core services are intended to form the foundation for additional future health information Page 3 of 11

exchange services. Responses to the RFI should include how your approach satisfies the stated requirements while, at the same time, establishes a foundation for future HIE services. 2.1 BACKGROUND AND CURRENT ENVIRONMENT The NJHIN is envisioned as a network of networks, providing connectivity between the existing regional Health Information Exchanges (HIEs), the Nationwide Health Information Network (NwHIN) and prioritized state databases such as immunization registries and selected data in the Medicaid Management Information System (MMIS). The NJHIN is planning to provide shared services including, but not limited to, record location services, master patient index and discovery, master provider registries, auditing functions, consent management and security and trust management. The New Jersey Health Information Technology Operational Plan (Plan) was approved on January 13 th, 2011 by the federal Office of the National Coordinator. The Plan outlines an assessment of the current environment, the planned NJHIN architecture, communications and outreach efforts, and an overview of the relationship between the NJHIN and the regional HIEs. The Plan, along with additional information about related HIT programs, is provided in Section 6. The Plan can also be accessed here: http://www.nj.gov/njhit/. Further, a fact sheet outlining provider, hospital and regional HIE statistics and demographic information is provided in Section 5. Along with the approval of the Operational Plan, the ONC released $11,408,594 in grant funds to accomplish the goals outlined in the Plan. These funds are allocated toward two primary purposes first, the support of the HIT Coordinator s Office and second, the support of four regional HIEs. Grant funding was allocated based on the recognition that the success of the regional HIEs must be a priority. As such, in order to finance the services for the NJHIN, New Jersey is seeking innovative funding approaches that will provide for the initial and ongoing financial sustainability of the NJHIN. 2.2 NJHIN TECHNOLOGY FRAMEWORK The NJ Health Information Network (NJHIN) is part of a larger Health IT strategy being enacted by the State of New Jersey. The NJHIN is intended to enable a secure, statewide, interoperable health information infrastructure that will connect providers, consumers, and others involved in supporting health and healthcare and will serve as a gateway to the Nationwide Health Information Network (NwHIN). This framework is depicted below. Page 4 of 11

Out-of-State HIEs Federal Agencies NwHIN Nationwide Health Information Network Providers Hospitals EMRx HIE NJHIN Shared Services State Data Sources State Health Related Registries Providers Hospitals Hospitals Providers Home Health Providers Health-e-Citi HIE Jersey Health Connect HIE Camden HIE Master Patient Index and Discovery Record Location Services Audit and Security Functions Interoperability Services Entity-Level/Provider-Level Directory Consent Management State Supplemental Data Registries Medicaid Management Information System Nursing Homes Hospitals EMS Trenton HIE Monmouth-Ocean HIE Labs, Pharmacies and Payers Hospital Labs Commercial Labs SureScripts Hub Healthcare Payers Commercial Claims Providers Hospitals Regional HIEs, Hospital Systems and IDNs The regional HIEs provide information exchange services to their subscribers (i.e., hospitals and healthcare providers interacting with their own EMR/HIT systems) and provide the gateway to the NJHIN. Examples include Health-e-cITI, EMRX, New Jersey Health Connect HIE and Camden HIE. The NJHIN will exist to provide a set of core services that enable the statewide exchange of clinical data as well as access to a variety of state databases including the Medicaid Management Information System (MMIS), Immunization Registry, Blood Lead Screening Registry, and the Vital Statistics Registry. NJHIN would also provide for an on boarding service which would be comprised of a testing and validation process for HIE s to join the NJHIN and have their HIE included in the Services Registry. As currently envisioned, no individual provider will be able to connect to the NJHIN. Access to NJHIN will be through a qualified entity. Page 5 of 11

2.3 CORE TECHNICAL SERVICES The core technical service requirements are: Master Patient Index and Discovery An algorithm-based application that provides for a single patient/individual that might exist in multiple source systems with potentially different information in each (e.g., different last names, addresses, etc.) to be identified and linked together. This allows the information for the person to be accessed in a holistic manner rather than forcing the end-user to attempt to determine the correct identity in each source system of the patient/individual. Record Location Services This service facilitates access to patient records through gateway services that allow the requestor to query and retrieve data for a specific person from one or more source repositories following the use of the Patient Index and Discovery service. Consent Management This is a uniform statewide patient consent and authorization process to allow electronic access to, review of, or disclosure of a patient s identifiable health care information. The approach should support "break the glass" (BTG) access control. The BTG privilege should be restricted based upon roles and an auditable trail. Provider Directories This service provides for both an Entity Level Provider Directory (ELPD) as a secure repository of information specific to entities and nodes, and an Individual Level Provider Directory (ILPD) as a secure directory of information about providers themselves. The ILPD provides search functions that enable the discovery and lookup of provider information. The ILPD also specifies the Entity or Entities with whom providers are associated. This service can be algorithm-based similar to a master patient index, or be vendor list managed where a vendor maintains a complete list of providers that is compiled from various sources (e.g., NPI, DEA, etc.) and the vendor makes the match against their master lists. This service indexes and authenticates all providers within the state of NJ as well as out of state providers who may share NJ patients. Interoperability Services and Security Authentication Support of HIE to NJHIN and HIE to HIE connectivity through the implementation of technology that conforms with a common set of standards that governs the authentication of systems allowing them to interoperate for the exchange of data. This service could also be utilized by an HIE to allow a user to gain secure access to its HIE. Security Authorization This service determines what information the user is authorized to view within the HIE. This service would work in conjunction with the Consent Management service to support an authorized access to patient/individual information in an HIE and the NJHIN. Auditing Service This service takes on different characteristics depending on the level within the technology hierarchy. At the NJHIN level this service is simply a log of each data request Page 6 of 11

including who requested what information and when the request was made and serviced. At the community HIE level; this could also include all of the aforementioned information along with a more detailed listing or document containing exactly what information was viewed by the requestor as it looked at the time of the viewing. Gateway Connectivity with the NwHIN This service allows for gateway connectivity to the NwHIN through the NJHIN with the intent of accessing other state level HIEs as well as Federal agencies. Additionally, it would act as a gateway into the State of New Jersey in order to access patient information through the NJHIN to the regional HIEs. In this regard, this service would need to perform as pass through data access service whereby external patient discovery and information query requests would trigger and support corresponding transactions across the NJ HIE s. Provider Credentialing This service provides a central facility for providers to manage their credentialing information with payers. This service should be designed to simplify the process of collecting provider information and allow the provider to manage the data for the purpose of supplying information to a health care organization. Specifically, the service should provide for the ability to complete and submit one application to multiple payers, allow the provider control over their data including managing who has access to the data, utilize a standard data set accepted by New Jersey payers for the collection and delivery of provider information and the ability to send attachments electronically such as License, DEA certificate, Controlled Dangerous Substance Certificate, Professional Liability Insurance Face Sheet and Board Certifications. Common Presentation Service This service provides for a common, standardized presentation of data acquired through the query/retrieve process for a specific person from one or more source repositories following the use of the Patient Index and Discovery service. The requestor will be provided the opportunity to select the data to import into their system. 2.4 CLINICAL FUNCTIONALITY AND PRIORITY USE CASES The State of New Jersey has developed a set of priority use cases which are designed to guide service development at both the regional HIEs as well as the NJHIN. This information is presented to provide the context for the core services and to outline the initial exchanges that the core services should enable. The requirements related to the use cases are: Medication History Patient medication histories are made available for Emergency Room admissions only. This Use Case will include the Cross Community Patient Discovery (XCPD) Profile to support accurate patient identification. Data Sources: State/Medicaid Page 7 of 11

Surescripts Existing in an EHR Public Health Data (Immunization Data) To provide patient immunization history directly to the physician s EHR. The State registry connection will be direct to the physician EHR. Note: This is a foundational Use Case to allow access to all other State Registries. The HIEs will become eventual brokers for all DHSS state registries. Diagnostic Results Available to All HIE Customers To provide patient laboratory test and radiology imaging results (later Use Case will address the Order side as well as open order/pending result). This Use Case will include the diagnostic results only (image access and/or exchange will be addressed in a subsequent Use Case). Data Sources: Existing in an EHR Hospital Lab/Imaging Dept Commercial Lab Imaging Clinic ED/Acute Discharge Summary The transfer of patient information in the form of discharge notes to the PCP or specialists at the time of discharge. ED/Acute Hospital discharge information only. Send the information to the PCP or Specialist via an HIE in the form of discharge notes, instructions and discrete data documents. Transition of Care-Referral Information This Use Case is intended to enhance communications between PCP and specialist with an opportunity to use Direct as a near-term way to conduct secure exchange of health information. Direct specifies a simple, secure, scalable, standardsbased way for participants to send authenticated, encrypted health information directly to known, trusted recipients over the Internet 3.0 VENDOR RESPONSE INSTRUCTIONS Interested vendors should submit a response to this RFI not to exceed a total of fifty (50) pages. Respondents are not required to respond to all sections of this RFI. All submissions should refer to the section number being addressed. Responses should be submitted in electronic format. All responses must be submitted in Word 97 or greater or as a PDF document. Page 8 of 11

3.1 DISCLAIMERS Specific technical requirements related to use cases and the full scale deployment of the NJHIN are not currently available. Overall budget will be determined based upon cost information provided relevant to related experience in other states and the impact of sustainability planning. This RFI does not require or assume a vendor demonstration; however, respondents may be asked to provide demonstrations based upon a review of their responses. 3.2 RFI RESPONSES The response should include the following: Section 1: An overview of your proposed solution, including technical solution, cost model, sustainability options, timeline and contracting relationships. Section 2: A description of how the entity will address one or more of the Core Technical Services described in Section 2.3. Section 3: An explanation of fixed and variable costs for all technical services, implementation and system interfaces. The cost of a proposed and/or awarded similar HIE project for another state. Section 4: A description of your approach to financial sustainability and any additional services proposed to support the initial and long-term sustainability of the NJHIN. Section 5: A brief statement indicating interest in any subsequent solicitation for services as outlined in this request. Section 6: A brief profile of the entity responding, including information indicating capabilities and experience in successfully completing a planning project of this description. If applicable, a brief profile should be included for any sub-contractors or partners that may be part of the collaboration. Please include a company mailing address, telephone and fax numbers, point of contact name and email address. Please provide the requested information no later than 5:00 P.M., EST on August 19, 2011. Responses should be sent via email to: colleen.woods@gov.state.nj.us. Any questions related to this RFI should be directed to Colleen Woods at 609-777-2609. Page 9 of 11

4.0 STATE OF NEW JERSEY FACT SHEET POPULATION 8,791,894 PROVIDERS Total Physicians 29,486 Primary Care Physicians 8,912 NJ-HITEC Target: 5,000 PCPs Signed Up 1,372 Max EHR Incentive Payments Per Medicare Provider (4 yrs) $44,000 Max EHR Incentive Payments Per Medicaid Provider (4 yrs) $63,750 HOSPITALS Hospitals 73 Staffed Beds 21,228 Total Discharges 1,073,561 Patient Days 4,972,094 Est. Medicare EHR Incentive Payments (4 yrs) $420,006,728 Average Per Hospital $6,268,757 Estimated Medicaid EHR Incentive Payments (4 yrs) $110,855,648 Average Per Hospital $1,654,562 Medicaid Beneficiaries 2,209,952 Medicaid's Active Servicing Providers 15,337 Managed Care Organizations (Medicaid) 6 HEALTH INFORMATION EXCHANGES ONC-funded HIEs 4 Jersey Health Connect (McKesson) 15 Orgs 20 Hospitals Health-e-Citi-NJ (IGI Orbit) 9 Orgs 8 Hospitals Camden (Noteworthy) 3 Orgs 3 Hospitals EMRX-SJ (Wellogic) 5 Orgs 5 Hospitals Other HIEs 2 Trenton Health Team (Noteworthy) 3 Orgs 3 Hospitals MOHIE (ICA) 2 Orgs 7 Hospitals FEDERAL FUNDS Awarded to New Jersey State Health Information Exchange Program $11.4 million NJ-HITEC Regional Extension Center 23.0 million NJ Medicaid (SMHP Planning Paid) 4.9 million Community College HIT Training 4.4 million Page 10 of 11

5.0 STATE OF NEW JERSEY HEALTH INFORMATION TECHNOLOGY OPERATIONAL PLAN The Operational Plan can be found at: http://www.nj.gov/njhit/ Page 11 of 11