Santa Cruz Health Information Exchange Transitioning HIE Platform

Similar documents
Clinical Information Systems

Nortec. ACT Now! Nortec EHR. Qualify & Receive $44,000. A Integrated Electronic Health Record Software.

Health Information Exchange (HIE) Community of Practice (CoP) Medicaid EHR Incentive Program April 21, 2015

Surescripts Community Education Kit EDUCATE IDENTIFY ENGAGE

A Merge White Paper. Closed Loop Referral Management: A Cost-Effective Strategy for Meaningful Interoperability

Phase I 1st Stage Requirements

Infor Cloverleaf Integration Suite

The Evolution of the Referral Process

SUBMITTED BY RHIO WORKGROUP MEMBERSHIP

Create interoperability in a MEDITECH environment

The New World of Unified Image Management

MEANINGFUL USE AND PQRS

Healthcare Integration. Lab data solutions with one simple connection

WEDI 2015 Health Information Exchange Value and ROI Survey

HEALTHCARE CASE STUDY

Industry efforts to drive interoperability progress

Patient Engagement in Imaging

Health Information. for Government. Maximize the Value of Your Health Information Exchange

Confidence is contagious; it empowers your staff, encourages your patients, and infuses your practice.

From Interaction to Integration to Transformation: Healthcare s Journey & Information s Role

Consolidating clinical content in truly vendor-neutral platform

Advancing Health IT Beyond Organizational EHRs

INVESTOR PRESENTATION. November 2012

There Has to Be More:

Duane Steward, DVM, MSIE, PhD Nemours, Chief Computer Scientist for Clinical Informatics University Central Florida, Assistant Professor

RHAPSODY VISION & ROADMAP FIORA AU, TIM WHITTINGTON OCT 2017

CIO Executive Forum. September 15 17, 2010 Newport Beach, California

Clinical Messaging in Mendocino and Lake County

Request for Proposals Baltimore Accountable Health Communities - Technical Infrastructure

Regional Extension Center Request for Information Meaningful Use EHR Vendors July 26, 2010

The Role of Integration in Radiology: Moving from Necessity to Leverage

Quality Orders = Quality Data = Quality Process QUALITY LAB ORDERS START IN THE DOCTOR S OFFICE

EHR Site Visit Questionnaire

RE: Written Testimony to the Information Exchange Workgroup s Provider Directory Task Force

Think Locally, Connect Nationally

Mach7 Enterprise Imaging Platform UnPAC and Build Your Own

THE ESSENTIAL ELEMENT of a

VITERA (GREENWAY) INTERGY 9.0 MEDICAL REVIEW

Eight User Secrets for Community Health Centers EIGHT E EIGHTEIG EIGHT. Why more community health centers choose NextGen solutions

Taking the HITECH Ground. Understanding Meaningful Use, Health Information Exchange and the Future of Lab Outreach

Overview of Health Information Exchange (HIE) in the Era of Meaningful Use December, 2010

useit in Cath Lab & IR

Innovative technology. Advancing patient care.

GE Healthcare. ICD-10 Prep: ICD-10 Services Centricity Practice Solution v12 and Centricity EMR v9.8

Presenter(s): Ken Banks Database Manager -- Peninsula Community Health Services. Topic Making the Most of Mirth Connect. Level 300

System Overview and Features Prepared for AceScript

Four Rights Can t Be Wrong:

SOME OF THE HEALTHCARE VERTICES WHERE WE HAVE WORKED ON.

Lexmark esf Applications. Product Demonstration Guide

ENGAGE USERS TO IMPROVE HEALTH CARE

RIS / PACS A WEB-BASED APPLICATION DESIGNED TO AUTOMATE YOUR WORKFLOW

Advanced healthcare solutions for

Healthcare Solutions Nuance PowerShare Network. PowerShare. The industry s largest medical imaging network.

DPH Information Systems Update. April 5, 2011

The MSO (Management Services Organization) Concept

SRISESHAA IN HEALTHCARE

Interoperability Robin Breslin

EHR 2.0 Collaboration

White Paper Searchable Data:

HIE.Next: Building an API-centric Infrastructure for Health Information Exchange

Eastern Massachusetts Healthcare Initiative

Orchard Software More than 25 Years Dedicated to Laboratories.

Enterprise XDS based VNA

Technology Models for Building Health Information Infrastructure I. John Lightfoot VP Technology Healthvision, Inc.

Data Integration, Management, & Visualization for Healthcare Organizations

Clinical Data Architecture for Business Intelligence and Quality Reporting

ATTACHMENT D Integration Broker Services

Components of a Comprehensive Legacy Data Management Strategy: Challenges and Strategic Considerations

Top 5 Must Do IT Audits

Get Connected. Be Interoperable. Start now.

Selecting the Right EHR System for Your Practice

FIVE STEPS TO AN ENTERPRISE IMAGING STRATEGY. Jon DeVries, Vice President, Solutions Management Merge Healthcare October 18 th, 2013

We know doctors. isalus.

SOA in the pan-canadian EHR

Reimagine: Healthcare

INTUITIVE, INTELLIGENT, INDIVIDUAL

All-in-One. Oncology EHR Chemotherapy Management Practice Management Revenue Cycle Management

ecarenotes Clinical Documentation. Simplified

Software Solution. Get the data where and when you need it.

Driving Down Network Cost Through Enhanced Interoperability

Addendum No. 2 to RFP

Transformational Data-Driven Solutions for Healthcare

Clinical Telepharmacy

Current State of Progress Towards Achieving True Interoperability: Results of 2016 Survey DRAFT

IT Managed Services Portfolio

National Learning Consortium

Implementing ecr Through a Digital Bridge: The Public Health Experience. CSTE Annual Conference June 5, 2017

PACS A WEB-BASED APPLICATION DESIGNED TO AUTOMATE YOUR WORKFLOW

EHR AND ERP INTEGRATION. January 25, 2018

STRIKING A BALANCE ADMINISTRATIVE COST-SHARING IN SCHOOL HEALTH CENTERS. Thursday, June 15, 2006

PHClinic Interoperability with KHIN/HIE and Functionality Improvements

ELECTRONIC MEDICAL RECORDS. Selec g and zing an Electronic Medical Records. A WHITE PAPER by CureMD. CureMD Healthcare

MEANINGFUL USE CRITERIA PHYSICIANS

Delaware Health Information Network Town Hall Wednesday, February 10, :00 a.m. 12:00 p.m.

Working with Health IT Systems is available under a Creative Commons Attribution-NonCommercial- ShareAlike 3.0 Unported license.

Presenter(s): Ted McCain Bob Koman. Topic Rosetta Interfaces. Level 200

Context. Accessibility. Relevance.

Using Infrastructure & Application Monitoring to Assure an Optimal User Experience. September 19, 2013 Presented by

Connectivity Strategy for Ehealth in Ontario. Version: 1.0

Why emds and Why emds Plus?

Transcription:

Santa Cruz Health Information Exchange Transitioning HIE Platform Santa Cruz HIE (SCHIE) has selected Mirth Corporation of Irvine, California to provide HIE software and support services, replacing the Optum/Axolotl HIE solution. This change was endorsed by the SCHIE Board of Directors in April 2013. The migration and implementation of Mirth was launched in June 2013 with a planned completion date of June 2015. Existing HIE data feeds with connected sources and a subset of the existing patient data in the Axolotl HIE will be migrated and re-directed to the new SCHIE. The existing data feeds from our connected data providers will not require any change, they have been re-directed to the New Santa Cruz HIE. The SCHIE will have a new interface for accessing consolidated patient records. The SCHIE Team will be sending out communications and announcing training sessions, keeping you apprised of what you need to do to prepare for the transition. This change will require user access re-authorization and training for the new interface. This change is very positive for the region and builds upon the trust and support of existing participants and patients. It provides us with a flexible and scalable solution that will provide not only current functionality and data to our users, but also a platform for needed functionality and information requirements. We have developed an FAQ that will address many questions regarding this important change. ********************************

FAQ The Change 1. What drove the need to seek a new HIE solution? 2. Why move away from the Axolotl solution? 3. What other drivers, besides Axolotl, were important in making the decision to change? 4. Will there be a cost to participants for the transition to the new SCHIE? 5. Who is Mirth? 6. Will Mirth be hosting our HIE solution? Data and Integration 7. What about all the data we currently have in the HIE? 8. Do the current data feeds coming into the HIE from hospitals, laboratories, radiology centers, practices have to be re-implemented? Implementation and Migration 9. Will all the current integrations and services migrate over to the new SCHIE? 10. Will the HIE be down when this change occurs? 11. Will users of the HIE need to be re-validated for use? 12. Will this change affect the current consent process? 13. What are the plans to communicate this change to all participants? Functionality and Capability 14. What other additional functionality/features will be available with the new SCHIE? 15. Will there be a new user interface to view consolidated patient records? 16. Will any functionality be lost with this change? 17. Will the change to the new SCHIE increase the pace of connecting physician practices to the HIE? 18. Will the change to the new SCHIE benefit those that do not use an electronic health record system or cannot connect to an HIE? Connecting to Others 19. Will the new SCHIE be connecting to other health information networks? 20. Will a web portal be offered for patients to view their own records in the new SCHIE?

1. What drove the need to seek a new HIE solution? The Change Challenges with Axolotl and substantial resources and increasing costs with slow innovation standards led the board of directors to investigate HIE alternatives. This process began in early 2013 and subsequently launched a formal RFQ process with qualified vendors to evaluate the best solution to meet our current and future needs. Moving the 10 years of information in the HIE to a new solution and limiting disruption with the existing data feeds and services were most important in the evaluation process. 2. Why move away from the Axolotl solution? There were three primary reasons: 1) Cost, Functionality and Value: The on-going operational cost of the Axolotl platform is very high for the value delivered. Close to 100% of our HIE software and services costs go toward Axolotl and its core HIE functions (data repository, consolidated patient record viewer, and results delivery capability). In order to support other needed HIE functionality and services, our cost on core services needs to be less. These capabilities include alerts and triggers, CCD exchange, clinical messaging, DIRECT mail exchange internal and external, Meaningful Use Stage 2 compliance, flexible and more responsive integration capabilities to increase EMR integration and the growing need to provide analytic and reporting services. 2) Service and Support: Over the last 18 months, vendor service and support has eroded and impacts our ability to deliver reliable and responsive services. 3) Long-term vision and viability: Axolotl is built upon an aging infrastructure that they are planning to replace. The plans to make this change are a year behind schedule and represent a significant risk to our business. 3. What other drivers, besides Axolotl, were important in making the decision to change? a. Direct access to the inbound and outbound data; in raw and translated forms; along with access to the data translation tables for each source. Axolotl maintains this information today and we have limited visibility. b. Need for HIE functions and capabilities not available from Axolotl including: alerts and triggers, CCD exchange, clinical messaging, DIRECT mail exchange with providers HIE participating providers and external providers. c. Need to support Meaningful Use Stage 2. d. Need to drive cost down for core HIE services. e. Need to invest in foundational analytics capabilities to support population health and other requested and expected information needs. f. Ensure Santa Cruz HIE services are available and benefit all clinical users in the region.

g. Ensure that our HIE vendor has the flexibility and long-term focus on delivering HIT solutions that benefit the region. 4. Will there be a cost to participants for the transition to the new Santa Cruz HIE? Participants that are already connected to the SCHIE will be moved from Axolotl to the new SCHIE at no charge by the SCHIE. Most EHR vendors charge physician practices for HIE integration and support. There is a charge for new interface connections to SCHIE. 5. Who is Mirth? Mirth is a global leader in Health Information Technology, delivering solutions that dramatically reduce the time, cost, and technology barriers to healthcare transformation. Mirth Products are used by several wellknown Healthcare Organizations such as: Mayo Clinic, HealthBridge, Southern Piedmont Beacon Community, Lone Star Circle of Care, Crescent City Beacon Community, Colorado Beacon Community (QHN), San Diego Beacon Community, Redwood MedNet, OCPHRIO (Orange County) Founded in 1993 and headquartered in Irvine, California, Mirth aims to transform health information technology by making high-value information technology solutions available to the healthcare community on an open source basis. Its service-backed open source offerings break through the cost barriers to achieve more cost-effective and responsive HIT solutions. Mirth Corporation was recognized as one of the top vendors in HIE Client Satisfaction according to the market research firm Black Book, one of the nation s top measurements of independent technology and services in the healthcare industry. Mirth is privately held with strong revenues, bookings and cash positions. 6. Will Mirth be hosting our HIE solution? Yes. Mirth will be hosting our HIE solutions on our own provisioned servers in their data centers which are SAS-70 and HIPAA compliant.

Data Integration 7. What about all the data we currently have in the HIE? Provider, patient data, and required audit data for patients still living who have had activity in the past three (3) years, that are California residents, the prior ten (10) years will be migrated to the new SCHIE platform. 8. Do the current inbound and outbound data feeds to the HIE from hospitals, laboratories, radiology centers, practices have to be re-implemented? As we implement the new SCHIE platform, the existing inbound data feeds will be routed not only to Axolotl, but also to the new SCHIE. The new SCHIE will be built in parallel to Axolotl. Re-direction, testing and validation of the data feeds into the new SCHIE will be done by Axesson Integration staff; thereby, minimizing the need for data source staff efforts. Existing VPN connections between SCHIE and the data sources will need to be updated/re-directed but this work is minimal. All practices receiving results from SCHIE will continue to do so going forward with the new SCHIE, too.

Implementation and Migration 9. Will all the current integrations and services migrate over to Mirth? Yes. Current data and feeds will be migrated to the new SCHIE. The new SCHIE has a clinical viewer for consolidated patient records. Existing EMRs will be integrated into the new SCHIE for sending data to the HIE and for the delivery of results (lab, radiology and transcribed reports) from the HIE. Referral capability will be implemented for existing EMRs and participants. 10. Will the HIE be down when this change occurs? Yes. The new SCHIE HIE solution is being built in parallel to our current Axolotl HIE. Existing data will be extracted, transformed and loaded into the new SCHIE as defined above. Existing data feeds will be redirected to the new SCHIE in parallel as well. The only downtime that will occur is when the data feeds are switched over into the production. Axolotl HIE (Elysium & the Virtual Health Record) will be shut down on June 19 th at 7:00pm. You will be able to view records but no new data will be delivered to Axolotl HIE after 7:00pm. The new SCHIE will be available at 7:00am on June 22, 2015. 11. Will users of the HIE need to be re-validated for use? Yes. SCHIE will work with participating organization to re-validate their users and associated rights. Users will be given new passwords and requisite training. With the SCHIE, users will only need one ID to access the HIE. 12. Will this change affect the consent process in place? No. There are no laws set by the state of California, at this time, for consent policies; however SCHIE currently has a pilot program for consent with a limited number of practices. There is no change for those practices that are participating in the demonstration project. All forms and process remain the same. 13. What are the plans to communicate this change to participants? We are developing a detailed communication and training plan for participants. The SCHIE staff will be arranging information and planning sessions to discuss the change and to plan its implementation. We will also use our website and email as communication vehicles for this change.

Functionality and Capability 14. What other additional functionality/features will be available with the new SCHIE? While the initial focus with the transition to the new SCHIE will be to ensure that all current functionality is in place when launched, there will be some new features and functions that will be part of the overall SCHIE solution. Some of this functionality will be available immediately; some will be rolled-out after the launch. Based on what the sources can send to the HIE the patient consolidated record will include: diagnoses, medications, conditions, allergies, immunizations, social histories, vitals and custodians. Additional functions that will be implemented over time will include configurable clinical alerts and triggers, CCD/CCDA exchange, clinical messaging/chat between providers and DIRECT secure mail exchange with regional participating providers and national participating providers. We are designing the new SCHIE to be a clinical workspace for users to be able to manage patient consent, view consolidated patient records, send/receive referrals, send/receive clinical messages/email, view radiology images and request and download clinical documents in various formats (PDF, CCD/CCDA, HL7, etc.) 15. Will there be a new user interface to view consolidated patient records? Yes. There will be a new user interface for the HIE. This new interface will require re-authorization and retraining for use. The interface is Windows based and intuitive to use. The SCHIE team will be providing training sessions and materials for this new user interface. 16. Will any functionality be lost with this change? Yes. When we launch, we will not have the Surescripts interface for medication fills. Physicians will use their own EHR s for e-prescribing. 17. Will the change to Mirth assist the pace of connecting physician practices to the HIE? Yes. The new SCHIE s strength is connectivity it has strong capabilities to receive and send information to physician practices. With the new SCHIE, we will be implementing CCD/CCDA exchange between participants and the HIE. Many EMR vendors exchange information with HIEs using CCD/CCDA exchange (continuity of care document -- an industry standard). We see this capability being extremely important for bi-directional exchange of patient clinical histories and for the implementation of referrals. Additionally, we plan to increase the use of the HIE with physicians that do not have an EMR or who have an EMR that does not support HIE connectivity, through their use of the HIE for secure messaging, referrals and viewing the consolidated patient record. 18. Will the change to the new SCHIE benefit providers who do not use an electronic health record system or cannot connect to an HIE? Yes. For providers that do not have an EMR or who have an EMR that does not support HIE connectivity we offer access to the consolidated patient record. Providers will have the ability to print and download patient clinical summaries and will be able to have a secure mailbox for the delivery of results and for sending/receiving referrals.

Connecting to Others 19. Will the new SCHIE be connecting to other state s health information network? SCHIE is in the process of joining ehealth Exchange. Once onboarded to the ehealth Exchange SCHIE will be able to query other systems and HIE s on the exchange. Currently there are about 200 entities already onboarded or in the process of onboarding. Dignity Health, OCHIN and Kaiser are a few that are already connected to the ehealth Exchange. 20. Will a web portal be offered for patients to view their own records in the new SCHIE? Yes. With Meaningful Use Stage 2 requirements, there is a need for patients to increase interaction with their providers for care. This includes the patient s ability to view, download and transmit their health information in a timely fashion and to communicate with their provider using secure messaging on relevant health information. SCHIE does offer a community patient portal, visit our Personal Health Record website page for more information.