Standards and EHR Interoperability

Download as pdf or txt
Download as pdf or txt
You are on page 1of 26

Standards and EHR Interoperability

Author: Zhan Caplan


June 14, 2012

Establishing the Building Blocks for Interoperability:


Overview of ONC's Office of Science & Technology

ONC Organizational Chart


National Coordinator

Office of Economic Analysis and Modeling

Office of the Chief Privacy Officer

Principal Deputy National Coordinator


Office of Communications Office of Science & Technology Office of Oversight Office of Mission Support Office of Strategic Initiatives Office of Grants Management

Deputy National Coordinator for Programs & Policy

Office of Policy and Planning

Office of Certification

Office of Provider Adoption Support Office of State and Community Programs

Office of Science & Technology


Enable stakeholders to come up with simple, shared solutions to common information exchange challenges Curate a portfolio of standards, services, and policies that accelerate information exchange

Team convened to solve problem

Solutions & Usability

Research & Development

Support Innovation through SHARP program, Innovation/Challenge Grants, and interfacing with international Standards community

OSTs Guiding Principles


Interoperability is a journey, not a destination Leverage government as a platform for innovation to create conditions of interoperability Health information exchange is not one-size-fits-all Build in incremental steps dont let the perfect be the enemy of the good

What is the S&I Framework?


The Standards and Interoperability (S&I) Framework represents one investment and approach adopted by the Office of Science & Technology (OST) to fulfill its charge of prescribing health IT standards and specifications to support national health outcomes and healthcare priorities The S&I Framework is an example of government as a platform enabled by integrated functions, processes, and tools for the open community* of implementers and experts to work together to standardize
* As of April 2012, 1100+ people had registered on the S&I Framework wiki, and 450+ people representing 300+ organizations had committed to the S&I Framework.

Why the S&I Framework Approach?


S&I Framework Approach: Create a collaborative, coordinated incremental standards process,
Guided by ONC, with input from Federal Advisory Committees, Enabled and led by an open community of industry participants who are interested in solving real world problems

Value created through this approach: Solve real-world issues to enable health information exchange Harness the expertise and passion of the community to solve problems Empower the community to create the best solutions for interoperability and standards adoption
7

S&I Initiative Portfolio Snapshot


Pre-Discovery
Direct Project (S&I Archetype) Transitions of Care Lab Results Interface Query Health Provider Directories Data Segmentation for Privacy Pilots Underway 2nd IG Ballot Publication (4/9/12) Plan to begin piloting in April 2012 Looking at potential pilots and reference implementation Targeting completion of pilot(s) and initial evaluation by September 2012 Community-Led initiative 1st (of 3) use cases consensus-approved; Targeting completion of pilot(s) and initial evaluation by October 2012 Working on Extension of the ToC Use Case for LCC (reuse); Limited Support Initiative Finalizing Initiative Charter and drafting Use Case; S&I Community Launched 3/30 S&I Community launching early June 2012

Use Case

Harmonization

RI, Test & Pilot

Evaluation

Public Health Reporting


esMD Longitudinal Coordination of Care Laboratory Orders Interface Health eDecisions 8

Current S&I Initiatives: Operating Metrics

How long has it been? Framework Launch Date First Initiatives Launched Elapsed Time (as-of today) Jan 7, 2011 Jan 31, 2011 17 months

How much have we accomplished? # Use Case Artifacts # Harmonized Segments/Sections # RI/Test Artifacts # Pilots Committed or In Discovery # Pilot Vendors # Pilot Healthcare Organizations (e.g. hospitals, HIEs) HL7 Ballots # Ballot Comments Received # Ballot Comments Resolved 33 150 64 20+ 25+ 35+ 3 1,854 1,479

How much effort have we put in? # Wiki Registrants # Committed Members # Committed Organizations # Working Sessions Held # Days Between Sessions* 1268 502 376 799 0.5

* Assumes 260 working days per year

Office of Science & Technology

Team Solutions convened to & Usability solve problem

Research & Development

Curate a portfolio of standards, services, and policies that accelerate information exchange

10

Nationwide Health Information Network

A portfolio of services, standards and policies that enable secure health information exchange over the Internet.

11

Transport is necessary, but not sufficient


How should well-defined values be coded so that they are universally understood? How should the message be formatted so that it is computable? How does the message move from A to B? Direct and NwHIN Exchange focus at these levels

Vocabulary & Code Sets Content Structure

Transport

Security

How do we ensure that messages are secure and private?


How do health information exchange participants find each other?

Services

12

A Sample Patient Scenario


A primary care doctor orders a lab test and gets the test back from the lab. She schedules the patient to be seen in the office to discuss the results. Based on the results of the test, the primary care doctor decides to send the patient to a subspecialist. She sends a summary of care record to the subspecialist electronically with a summary of the most recent visit. When the patient sees the subspecialist, it becomes apparent that there is a missing test that was done at a different hospital that would be helpful in taking care of the patient. Rather than repeating the test, the doctor queries the outside hospital for the lab test that she needs.

13

What will this transaction require?


The physician ordered an outpatient lab test on a patient, and the lab sends the information to your office. The patient is here to discuss the results.
Vocabulary & Code Sets Content Structure

How should well-defined values be coded so that they are universally understood? How should the message be formatted so that it is computable? How does the message move from A to B? How do we ensure that messages are secure and private? How do health information exchange participants find each other?

LOINC: to code lab results & observations

HL7 2.5.1: to format the lab result so EHRs can incorporate it


Direct: to securely send the lab result from the lab to the EHR X.509: to ensure it is safely transmitted to the intended recipient DNS+LDAP: to find the recipients X.509 certificate
14

Transport

Security

Services

What will this transaction require?


Rather than repeating the test, the doctor queries the outside hospital for the lab test that she needs.
Vocabulary & Code Sets Content Structure

How should well-defined values be coded so that they are universally understood? How should the message be formatted so that it is computable? How does the message move from A to B? How do we ensure that messages are secure and private? How do health information exchange participants find each other?

LOINC: to code lab results & observations

HL7 2.5.1: to format the lab result so EHRs can incorporate it


NWHIN secure messaging (SOA): to issue query to NWHIN participants X.509: to ensure it is safely transmitted to the intended recipient Services Directory: to find certificates and web services
15

Transport

Security

Services

Direct Project Spring 2012 Update


The Direct Project began as an independent, open government project to specify a standard for secure, directed health information exchange. Based on its success, OST modeled the S&I Framework after Direct, and Direct has now become one of the S&I Initiatives. More than 38 vendors are in production or are about to be in production. Direct is part of the core strategy of 51 State HIE Grantees, 28 of which have already implemented Direct. Current number of providers signed up with state HISPs: 5129.

16

NwHIN Exchange: Success is a Reality


Exchange is now evolving to an independent business to maintain a trajectory of growth. Contract/Grant requirement for participation has been lifted There is a rapidly growing community of federal agencies, states, health systems and HIOs using the Exchange shared infrastructure and oversight. As of September 2011, Exchange participants represented:
500 hospitals 4,000+ provider organizations (physician practices, clinics, etc.) 30,000 users 1 million shared patients / beneficiaries covered via current connectivity ~65 million people in population coverage area
17

NwHIN Exchange: Success is a Reality


Technology providers support Exchange:
The EHR Association (EHRA) is at the table; membership represents 90% of US providers. Technology providers who support Exchange participants are among the largest players.

Participants are realizing value from Exchange:


Faster Social Security benefits determination (45% faster). Expedited benefit payments to the disabled. Revenue enhancement of $2.1M for Bon Secours (hospital system in Virginia). High rate of veterans, patients and individuals consent / authorize exchange. Clear clinical benefits and improved decision making:
Avoided prescribing multiple narcotics; Enabled focused follow-up questions that helped narrow down treatment options; Detected life-threatening allergic reactions.

Exchange is very supportive of the Care Connectivity Consortium (CCC) efforts and will continue to collaborate and align.
18

Direct and Exchange Planned Activities

Directed Exchange
Develop specifications and implementation support for Certificate Discovery and Provider Directories for Directed Exchange Support adoption of Directed Exchange in federal agencies Continue working with State HIE program to support Direct implementations

Query/Web Services Exchange


Simplification of specifications around discovering patients and query/retrieve of patient health information Development of Exchange Business Plan for long term sustainability Bridge support for Certificate Authority to ensure continuity of operations for Exchange until transition is completed

19

Office of Science & Technology

Team Solutions convened to & Usability solve problem

Research & Development

Support Innovation through SHARP program, Innovation/Challenge Grants, and interfacing with international Standards 20

Investing in Innovation (i2)

ONCs Challenges and Prizes program spurring privatesector innovation and engaging developers to address health problems that touch every person in America: Care Transitions Cancer Research Heart Disease Population Health Sexual Abuse Disabilities
Over 100 new applications developed Winners have received $195,000 in prizes Over 25 new challenges planned

SHARP Strategic Health IT


Advanced Research Projects

Security of Health IT - Innovations in security and privacy required to build public trust in health IT systems

Automated complex decisions around health record exchange, assuring regulation compliance Developed techniques to analyze health records access logs to catch policy violations

Patient-Centered Cognitive Support Innovations in health IT usability and clinical decision support

Piloted Rapid Usability Assessment Protocol for EHRs

Comparing usability across EHR systems via Usability Lab

SHARP Strategic Health IT


Advanced Research Projects

Healthcare Applications New health IT architectures enabling substitutable applications

Created SMART platform a test-bed for the substitutable app development SMART-enabled i2b2, a data analytics platform, and Indivo, a PHR

Secondary Use of EHR Data Enabling exchange through creating tools, services for large-scale data sharing

Conversion and normalization of lab messages & medication orders Extraction of medication from narrative clinical documents

Key Takeaways
1. Although not perfect, does it represent the best we have so far?

2. Is it the next step in an incremental approach to refining the standards and implementation guides?
3. Does it support our policy objectives? 4. Interoperability is not one size fits all: Create modular standards and specifications that allow for innovation i.e. Internet: were not building AOL; were creating the building blocks to make it possible for Facebook, Twitter, etc. to flourish

5. We are on a journey together!


24

Stay connected, communicate, and collaborate


Browse the ONC website at: www.healthit.gov
click the Facebook Like button to add us to your network

Contact us at: [email protected] Subscribe, watch, and share: @ONC_HealthIT Htt Channel: HHSONC Health IT and Electronic Health Records http://www.scribd.com/HealthIT/ http://www.flickr.com/photos/healthit

Questions/Discussion

Learn more at:


ONC website: www.healthit.gov
Direct Project website: www.directproject.org

S&I Framework wiki: http://wiki.siframework.org

You might also like