Transcript Introduction to the HITSP

2009 Webinar Series
HITSP Real World Sites
Health Information Exchanges
Webinar 6
July 9th, 2009 | 2:00 – 3:30 pm (Eastern)
Laurance Stuntz, NEHEN Technical Architect, Partner, CSC
Jim Younkin, KeyHIE Project Director
Noam H. Arzt, PhD, FHIMSS, VITL Consultant
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
0
Learning Objectives
 During this 90-minute webinar, participants will:
— Learn how HITSP products are being used today by NEHEN,
KeyHIE and VITL
— Learn how NEHEN used standards to deliver a sustainable,
growing Health Information Exchange (HIE) for administrative
and clinical data
— Learn about KeyHIE adoption of national models and standards
in the implementation of an HIE providing timely information for
patient care
— Learn about VITL’s use of standards and success with results
delivery, medication history, disease management, and
other functions
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 1
Agenda
 What is HITSP?
 New England Healthcare EDI Network (NEHEN)
 Keystone Health Information Exchange (KeyHIE)
 Vermont Information Technology Leaders (VITL)
 Overview of the 2009 Webinar Series
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 2
Mission
To serve as a cooperative partnership between the public and
private sectors for the purpose of achieving a widely accepted
and useful set of standards specifically to enable and support
widespread interoperability among healthcare software applications,
as they will interact in a local, regional, and national health
information network for the United States.
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 3
Overview
 HITSP is a volunteer-driven, consensus-based organization
that is funded through a contract from the Department of
Health and Human Services
—
Created in 2005
 HITSP develops Interoperability Specifications (IS) – documents
that harmonize and recommend the technical standards that are
necessary to assure the interoperability of electronic health records
—
Production to date:13 IS and 60 related constructs
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 4
HITSP
Stakeholders

Patients

Specialists

Review Boards

Consumers

Payers

Practice


Employers
General



Residential
Care Providers
Practitioners
Outpatient
Healthcare
Providers
Guidelines
Suppliers
Hospitals


Government
Agencies
Current Participation in HITSP:
724 organizations
800+ individuals
Over 25,000 volunteer hours
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 5
HIT Standardization
HITSP members agreed that a standard is a
well-defined approach that supports a business
process and . . .
—
has been agreed upon by a group of experts
—
has been publicly vetted
—
provides rules, guidelines, or characteristics
—
helps to ensure that materials, products, processes
and services are fit for their intended purpose
—
is available in an accessible format
—
is subject to an ongoing review and revision
process
Standards Harmonization is required when a proliferation of
standards prevents progress rather than enabling it.
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 6
HITSP
Interoperability
Specifications (IS)
Recognized
Accepted
IS 01
Electronic Health Record (EHR) Laboratory Results
Reporting
IS 02
Biosurveillance
IS 03
Consumer Empowerment
IS 04
Emergency Responder Electronic Health Record
(ER-EHR)
IS 05
Consumer Empowerment and Access to Clinical
Information via Media
IS 06
Quality
IS 07
Medication Management
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 7
HITSP
Interoperability
Specifications (IS)
Released /
Panel
Approved
IS 08
Personalized Healthcare
IS 09
Consultations and Transfers of Care
IS 10
Immunizations and Response Management
IS 11
Public Health Case Reporting
IS 12
Patient – Provider Secure Messaging
IS 77
Remote Monitoring
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 8
HITSP
Interoperability
Specifications (IS)
HITSP
Interoperability
Specifications (IS)
Recognized
Accepted
IS 01
Electronic Health Record (EHR) Laboratory Results
Reporting
IS 08
Personalized Healthcare
IS 02
Biosurveillance
IS 09
Consultations and Transfers of Care
IS 03
Consumer Empowerment
IS 10
Immunizations and Response Management
IS 04
Emergency Responder Electronic Health Record (EREHR)
IS 11
Public Health Case Reporting
IS 05
Consumer Empowerment and Access to Clinical
Information via Media
IS 12
Patient – Provider Secure Messaging
IS 06
Quality
IS 77
Remote Monitoring
IS 07
Medication Management
Released /
Panel
Approved
“Meaningful Use”
From existing Interoperability
Specifications, determine subset
required for “meaningful use” as
called for in the American Recovery
and Reinvestment Act (ARRA)
HITSP – enabling healthcare interoperability
9
2009 Webinar Series
Slide 9
ARRA Led to Creation of HITSP Capabilities
HITSP Capabilities
CAP140 Exchange Administrative Benefits/Eligibility transactions specification
ADMINISTRATIVE and
FINANCIAL
CAP141 Exchange Administrative Referral/Authorization Transactions Specifications
CAP142 Retrieve Communications Recipient
CAP143 Consumer Preferences and Consent Management
CAP146 Identification of communications Recipient Specifications
Medication
Management
CAP117 Communicate Ambulatory and Long Term Care Prescription Specification
CAP118 Communicate Hospital Prescription Specification
CAP119 Communicate Structured Document Specification
CAP120 Communicate Unstructured Document Specification
All based
on previous
HITSP work
CLINICAL
OPERATIONS
(Care Delivery,
Emergency Responder
and Consumer
Empowerment)
CAP121 Communicate Clinical Referral Request Specification
Exchange of
Clinical Data
CAP122 Retrieve medical Knowledge Specifications
CAP123 Retrieve existing data Specifications
CAP124 Establish Secure web access Specifications
CAP125 Retrieve Genomic Decision Support Specifications
Exchange of
Laboratory and
Imaging Data
Quality
Management
CAP126 Communicate Lab Results Message Specifications
CAP127 Communication of Lab Results Document Specifications
CAP128 Communicate Imaging Information Specifications
CAP129 Communicate Quality Measure Data Specifications
CAP130 Communicate Quality Measure Specification Specifications
CAP131 Immunization Registry update Specifications
CLINICAL
QUALITY AND
PUBLIC
HEALTH
Immunization
CAP132 Immunization Registry Query Specifications
CAP133 Communication of Immunization Summary Specifications
CAP135 Retrieve Pre-populated Form for Data Capture Specifications
Case Reporting
and
Bio-surveillance
Emergency
CAP136 Emergency Alerting Specifications
CAP137 Send and Receive clinical data message Specifications
CAP138 Assign pseudo-identity Specifications
CAP139 Communicate Resource Utilization Specifications
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 10
2009 Webinar Series
NEHEN – New England
Healthcare EDI Network
Use of HITSP IS
Laurance Stuntz - NEHEN Technical Architect
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
11
Massachusetts Healthcare Information
Exchange History
 1997: New England Healthcare EDI Network (NEHEN) founded
—
5 members concentrating on implementation of HIPAA
Administrative Simplification
 2003: MA-SHARE founded
—
Clinical Data Exchange started in with MedsInfo-ED pilot
 2004 – 2005: NHIN Architecture Prototype
 2006: Rx Gateway
 2008: Discharge Summary Pilot
 2009: Clinical Data Delivery
 June 2009 Clinical (MA-SHARE) and Admin (NEHEN) Merge
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 12
MA-SHARE / NEHEN Merger Background
 NEHEN had a strong cost savings focus and has been sustainable
through member fees since 1999
 MA-SHARE relied on grant and “angel” funding for 2003 – 2008
 In 2009, clinical services are mature enough to be sustainable through
member fees
 Organizations decided to merge and form a new not-for-profit for a
variety of reasons
—
Economies of scale relative to governance, management, and support
—
Take advantage of shared technical infrastructure
—
Positioning for HIE / Stimulus funding
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 13
What is NEHEN?
 NEHEN is a collaborative, payor and provider-owned solution for
healthcare data exchange that has:
—
—
—
—
—
50+ hospitals, 5,000+ physicians, 4.5M+ health plan members
8 health plan participants
Delivers more than 7 million total transactions per month
Delivers more than $15 billion in claims per year
Delivers more than 100,000 new prescriptions
Benefits:
per month
 Purpose
— Shared development effort / exchange best practices
— Coordinated project planning and prioritization
— Dedicated exchange technical support
— Coordinated exchange testing and implementation
HITSP – enabling healthcare interoperability
2009 Webinar Series
 Simplified
Administrative
Processes
 Increased Net
Revenue
 Reduced Costs
Slide 14
Member Overview
 Founding Members
 Provider Members
 Payor Members
 Vendor Members
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 15
NEHEN Functions
 Administrative Information Exchange
— NEHEN delivers all of the HIPAA administrative transactions with a flat
subscription fee, allowing members to use a single, integrated solution for
communicating with their payors, at a fraction of the cost of using
traditional healthcare clearinghouses
 Ambulatory and Long Term Care ePrescribing
— NEHEN provides a utility to link homegrown EMR systems to the
SureScripts pharmacy network and other medication history information
sources to help providers receive ePrescribing incentive payments
 Clinical Data Delivery
— NEHEN connects hospitals, physician practices, and other providers via
the HIE to exchange clinical data, including discharge summary and
continuity of care documents
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 16
Capability: Exchange of Administrative Benefits /
Eligibility Transactions
Harvard Pilgrim
NEHEN Contract Affiliates
Automatic transmittal
Tufts Health Plan
Network Health
BMCHP
Hospital or
Physician Practice
NHP
NEHEN Network
• Transactions are transmitted
to NEHEN eGateways at
other members
• Providers are directly
connected with each payer
or via NEHEN Hub
NEHEN Reports
NEHEN
Database
Patient Accounts
NEHEN
eGateway
creates the
standard
transactions
NEHEN Payor Services
Non-NEHEN Payor
Non-NEHEN Clearinghouse
NEHEN Express
Provider-side
HITSP – enabling healthcare interoperability
Payor-side
2009 Webinar Series
Slide 17
Capability: Issue Ambulatory and Long Term
Medications (ePrescribing)
Payor
Prescriber
Point of Care
Information
System
Secure Internet
Pharmacy Dispenser
(Retail or
Mail Order)
Rx Gateway
Data Provider
HITSP – enabling healthcare interoperability
Data Router
2009 Webinar Series
Slide 18
Capability: Clinical Data Delivery Using CCD
Receiver: Payor / Physician / Hospital
Sender: Physician / Hospital
EMRs and
Other Enterprise
Systems
Interface
Engine
or Portal
Interface
Engine
or Portal
HIE
Application
Server /
Gateway
EMRs and
Other Enterprise
Systems
HIE
Application
Server /
Gateway
Secondary Local System
Secondary Local System
CCD Standard Document
Secure
Internet
CCD Standard Document
NEHEN
CCD Standard Document,
HTTP encapsulation
HITSP – enabling healthcare interoperability
HIE
Application
Server /
Gateway
2009 Webinar Series
Community
Participant Locator
Slide 19
Capability: Screen Shot Communication of
Clinical Data Using CCD
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 20
HITSP Capabilities Used by NEHEN
 Exchange of Administrative Benefit Eligibility Transaction
—
X12 270-271 Eligibility Inquiry and Response
—
Utilizes business rule from CAQH CORE leading to T85 –
Administrative Transport to Health Plan for new connections
 Issue of Ambulatory and Outpatient (ePrescribing)
—
Industry has standardized on NCPDP specifications and SureScripts
communication formats
 Clinical Data Delivery
—
C32 / Summary Documents using HL7 Continuity of Care Document
(CCD) Component
—
C83 / Clinical Document Architecture (CDA) Content Modules Component
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 21
HITSP Constructs Under Consideration for
Future Clinical Data Exchange
 Quality Reporting
— C 38: Patient Level Quality Data Document Using IHE
Medical Summary (XDS-MS)
 Research Reporting
— C 25: Anonymize
 General Transaction Delivery
— C 26: Nonrepudiation of Origin
 Maintain Privacy and Security
— TP13: Sharing of documents
— TP20: Access Control Transaction
Package
— T 15: Collect and Communicate Security
Audit Trail Transaction
— TP30: Manage Consent Directives
Transaction Package
— T 16: Consistent Time
— T 17: Secured Communication Channel
— T 31: Document Reliable Interchange
— T 29 : Notification of Document Availability
— C 44 : Secure Web Connection
— C 62 : Unstructured Document
— C 80: Clinical Document and Message Terminology
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 22
HITSP Solution & Benefits
 HITSP Descriptions of Use Cases are valuable to help educate
members and new participants
 Plan to leverage components identified by HITSP
—
C32 / C83 concepts relative to the CCD
—
T85 relative to new health plan trading partners (based on CORE)
 Tracking and planning to implement HITSP constructs as use cases
indicate a documented interaction, data format, or transport
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 23
The Future
 Currently developing priority and planning for implementation
of the following:
—
Expand use of visit/discharge summaries
—
Sending data in support of consultation
—
Sending data in support of quality reporting
—
Integration with personal health records
 Expanding connectivity to external, non-local trading partners
—
Connectivity to Aetna, United, and other national payors
—
Connectivity to software vendors and hosted EMRs
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 24
Lessons Learned – HIE Creation and Governance
 Concentrate on sustainability
—
—
Pick use cases that save money so that new organizations will willingly fund
ongoing operations
NEHEN started with administrative exchange and those successes have led
to annual budget of > $3MM completely from member contribution
 Get executive commitment
—
—
Policy groups must have C-level representation to commit their organizations
Organizations must commit tangible dollars or dedicated resources; this can’t
be a part time or “volunteer” job
 Don’t try to boil the ocean
—
—
—
Start with small projects
Pilot with 2-3 participants
Learn from the pilot, adjust, and expand
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 25
Lessons Learned – Standards
 HITSP Constructs provide value in organizing concepts and linking to
recognized standards
 NEHEN has tended to take pieces of the Interoperability
Specifications rather than implement them in whole cloth
 NEHEN experience supporting both clinical and administrative
workflows points to a need for common transport specifications
—
T85 starts down this path, but needs to be extended to
data-agnostic transport
—
Tracking the common data transport model under development by
the Security, Privacy and Infrastructure Technical Committee
 It will be important to simplify the presentation of HITSP concepts and
make them accessible to non-experts
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 26
2009 Webinar Series
KeyHIE
Use of HITSP IS
Jim Younkin - KeyHIE Project Director
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
27
KeyHIE® June 2009
Twelve member organizations
- hospitals, clinics, skilled care,
home health, LTC
Data from 7 hospitals / 42 clinics
Used in three emergency departments
2.5+ million patient records in MPI
130+ Users
317,000+ Patient Authorizations
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 28
KeyHIE® Implementation Strategy
 Leverage systems and data sources already in place to
avoid high start-up costs (MPI, web-portals, etc.)
 Build incrementally: 4 phases
 Adopt national models and standards
— Initially: Connecting for Health
— Now: IHE and HITSP
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 29
KeyHIE® History
2005
2006
2007
2008
6/2009
1st Regional Survey
Phase 1 Portal Live
Single Sign-on Live
(2 hospitals)
Document Store Live
(3 hospitals,
2 documents)
Regional Symposium
Master Patient Index
Live (3 hospitals)
Portal Phase 2 Live
Record Locator
Document Store Live
Service Live
(2 additional hospitals,
(4 additional hospitals) 1 additional document)
AHRQ grant award
Record Locator
Service Live
(3 hospitals)
Master Patient
317,000 Total Patient
Index Live
Authorizations
(3 additional hospitals)
Governance formed
Portal Phase 3 Live
Single Sign-on Live
(1 additional hospital)
Document Store RFP
265,000 Total Patient
Authorizations
Master Patient
Index Live
(1 additional hospital)
2nd Regional Survey
Phase 4 Portal Live
Community Lab
Interface Live
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 30
KeyHIE® Implemented Use Cases/Capabilities
 Portal access to regional data sources
— Emergency department physicians, nurses, staff
— Primary care and specialty practices
— Case managers
 Regional link from Electronic Health Records (EHRs)
 Laboratory results sent to external EHR
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 31
KeyHIE® Use of HITSP Standards
 Current
—
C 62 Unstructured Document
—
T 15 Collect and Communicate Security Audit Trail
—
T 16 Consistent Time
—
T 17 Secured Communication Channel
—
TP 13 Manage Sharing of Documents
—
TP 22 Patient ID Cross Referencing (equivalent)
—
TP 30 Manage Consent Directives (equivalent)
—
C 35 HITSP EHR Lab Result Terminology Component
—
C 36 HITSP Lab Result Message Component
 Planned
—
T 23 Patient Lookup by Demographics
—
C 37 HITSP Lab Report Document Component
—
C 48 Encounter Document Using IHE Medical Summary (XDS-MS)
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 32
Demographics – HITSP TP22 (equivalent)
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 33
Patient Authorization–
HITSP TP30 (equivalent)
 Opt-in
 No authorization,
no access
 Authorization at
each organization
 Real-time authorization
 Patient education
 Rigorous information
security practices
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 34
Encounters
(Record Locator from “Connecting for Health”)
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 35
Clinical Documents – HITSP TP13, C62
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 36
Standard Lab Coding – HITSP C35
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 37
KeyHIE® Successes
 Community Master Patient Index with 2.5+ million patients
 KeyHIE portal live in April 2007
 Now receiving data from seven hospitals and 40-clinics
 4.7+ million encounters recorded annually
 317,000+ patient authorizations signed by June 2009
 Began document repository in October 2008
 82,000+ documents published by June 2009
 97% of labs from one hospital now file
electronically to EHR
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 38
Lessons Learned
 Technical readiness of communities to use HIE standards
 Patient authorizations
 RFP development
 Operational costs (e.g. MPI maintenance)
 Value to case managers
 HITSP allows rapid deployment
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 39
Document Store Selection Process
 Started with participants in HIMSS interoperability showcase
 Contracted with IHE-vetted professional to navigate
RFP process
 Developed requirements
 Request for Proposal sent to vendors…
— IHE “certified” for PIX and XDS Registry/Repository
— Hosting capabilities
— Grant-related time constraints
 Got solid responses from 7 vendors
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 40
Document Store Requirements
 Provide and Register Documents (any content)
 Query and Retrieve Documents
 Interface set up with Registry / Repository
 Document Sources
 Document Consumers
 Integrate with KeyHIE Infrastructure
CMPI, RLS, Network
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 41
KeyHIE® Future
More Stakeholders:
More Documents:
 Emergency Departments
 Laboratory Results
 Case managers (Medical Home)
 Medication Lists
 PCPs
 Consults
 Home Health
 Pathology Results
 Long Term Care / Assisted Living
 Allergies
 Emergency Responders
 Problem Lists
 Patient Summaries
(Continuity of Care Documents)
 Electrocardiogram Tracings (EKGs)
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 42
Contact Information
Jim Younkin – Project Director, KeyHIE
IT Program Director, Geisinger Health System
[email protected]
This project was supported by grant number UC1HS016162 from the Agency for Healthcare Research and Quality, and
in part, under a contract with the Pennsylvania Department of Health, Harrisburg, Pennsylvania. The department
specifically disclaims responsibility for any analysis, interpretations or conclusions. Edward G. Rendell, GOVERNOR.
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 43
2009 Webinar Series
VITL – Vermont Information
Technology Leaders
Use of HITSP IS
Noam H. Arzt, PhD, FHIMSS, VITL Consultant
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
44
Background: What is VITL?
 A non-profit public-private partnership located in Montpelier, VT
 Started by VAHHS (hospital association)
 Incorporated on July 22, 2005
 Declared by Vermont Legislature to be only statewide RHIO
 11 member board of directors representing various stakeholder
groups – physicians, hospitals, insurers, employers, state government,
and consumers
 Awarded non-profit status by IRS in March 2009
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 45
VITL’s Projects and Services
 Developed original Vermont Health Information Technology Plan
 Health Information Exchange Network
—
Build secure interfaces to data sources/sites
—
Provide data, storage and messaging
—
Data normalization and matching services for Department of Health’s
Blueprint for Health (Chronic disease management/medical home
project) and immunization information system
 Results delivery for lab tests, radiology reports
 Electronic health record adoption and clinical transformation
 Medication history service
 E-prescribing adoption incentive program
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 46
Functions
 Results Delivery
— Hospitals are connected to the VITL HIE to send HL7 messages
containing results to EHRs. Local lab codes translated to LOINC standard.
 Medication Histories for Emergency Departments
— Medication data from Pharmacy Benefit Manager (PBM) databases is
obtained through the SureScripts network and routed to hospital
emergency department through the VITL HIE.
 EHR Grant Program
— Independent practices receive grants to acquire EHRs, redesign workflow,
and connect to the VITL HIE.
 Public Health Registries
— VITL connects practice EHRs to public health registries, including
immunization reporting, health maintenance tracking, and others.
 Clinical Data Sharing
— VITL connects hospitals, physician practices, and other providers via
the HIE to exchange clinical data, including continuity of care (CCD)
documents.
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 47
Continuity of Care Document Data Sharing Example
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 48
HITSP & IHE Standards Used
HITSP TP22
IHE-PIX
Patient lookup by ID
HITSP C32
IHE XDS-MS
Medical summary
HITSP TP23
IHE-PDQ
Patient lookup by
demographics
HITSP C37
IHE XD*-Lab
Lab data exchange
XDS HITSP TP23
IHE XDS
Document storage/
retrieval
HITSP T14
HL7 V2.4
Exchange lab results
HITSP T17
IHE ATNA
Secure node
Future
HITSP TP30
IHE BPPC
Consent
HITSP T15
IHE ATNA
Audit logging
HITSP T16
IHE CT
Consistent time
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 49
Benefits & Successes
 7 hospitals connected to the HIE
 12 provider practices connected to the HIE,
including 4 EHR-S grantees
 4 hospital labs connected to the HIE;
70,000 results delivered to date
 3 hospitals using Medication History service;
100,000 histories delivered to date
 1 disease management registry connected to the HIE;
900,000 transactions processed through HIE
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 50
Lessons Learned
 HITSP specifications are not always a perfect fit, but contain the
necessary building blocks for most interfaces
 Difficult to match lab results to lab orders when single system not
implemented end-to-end
 Standard interfaces take less time to implement and 80% less
expensive than non-standard interfaces
 Five vendors tested EHRs for interoperability with VITL HIE and
demonstrated clinical document sharing.
— Project was done in 30 days because of HITSP spec
 Data sharing agreements are difficult to write and get approved
 Some services may not start out on the HIE (e.g., RxHx)
 Clinical transformation is key!
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 51
The 2009 Webinar Series
www.HITSP.org/webinars
Webinar 1
Advances in Sharing Information in Healthcare IT

Thursday, January 15, 2009 — 2:00-3:30 pm Eastern
Webinar 2

Webinar 3

Personalized Healthcare Interoperability
Specification (IS 08)
Consultations and Transfers of Care
Interoperability Specification (IS 09)
Thursday, August 27, 2009 — 2:00-3:30 pm Eastern
Webinar 8
Medication Management Real World Sites
Thursday, September 10, 2009 — 2:00-3:30 pm Eastern
Webinar 9
HITSP EHR Centric Interoperability Specification
Thursday, March 12, 2009 — 2:00-3:30 pm Eastern
NHIN Real World Sites

Thursday, April 16, 2009 — 2:00-3:30 pm Eastern
Webinar 5
HITSP eTown Hall I with Dr. John Halamka

Thursday, June 18, 2009 — 2:00-3:30 pm Eastern

HITSP eTown Hall II with Dr. John Halamka
Thursday, February 12, 2009 — 2:00-3:30 pm Eastern
Webinar 4
Webinar 6
Webinar 7
Health Information Exchange (HIEs)
in the Real World
Thursday, July 9, 2009 — 2:00-3:30 pm Eastern
HITSP – enabling healthcare interoperability
Thursday, October 8, 2009 — 2:00-3:30 pm Eastern
Webinar 10
Security, Privacy, and Infrastructure
Thursday, November 12, 2009 — 2:00-3:30 pm Eastern
Webinar 11
Real World Sites – TBA
Thursday, December 10, 2009 — 2:00-3:30 pm Eastern
NOTE:
Recent schedule changes reflect HITSP’s response to new efforts in
HIT based on the ARRA Stimulus bill provisions. Further changes are
possible due to priority changes and availability of speakers.
2009 Webinar Series
Slide 52
Questions Welcomed
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 53
View the Complete Set of HITSP Deliverables
www.HITSP.org
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 54
How YOU can
become involved
 Use or specify recognized HITSP Interoperability Specifications in your HIT
efforts and in your Requests for Proposals (RFPs)
 Ask for CCHIT certification
 Leverage Health Information Exchanges to promote HITSP specifications to
make connections easier in the future
 Ask . . . Is there a HITSP standard we could be using?
 Get involved in HITSP . . . Help shape the standards
Implementation feedback to HITSP is welcome
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 55
Join HITSP in developing a safe and
secure health information network
for the United States
Visit www.hitsp.org or contact:
Michelle Deane, ANSI
[email protected]
Re: HITSP, its Board and Coordinating Committees
Jessica Kant, HIMSS
[email protected]
Theresa Wisdom, HIMSS
[email protected]
Re: HITSP Technical Committees
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 56
Sponsor
Strategic Partners
www.HITSP.org
HITSP – enabling healthcare interoperability
2009 Webinar Series
Slide 57