Webinar Series
Consumer Access to
Clinical Information
Webinar 3
June 26, 2008 | 2:00 – 3:30 pm (Eastern)
Presenters Co-chairs of HITSP Consumer Perspective Technical Committee

Charles Parisot, Manager, Standards and Testing,
GE Healthcare Integrated IT Solutions

Scott Robertson, Standards Architect, Information Technology /
Health IT Strategy and Policy, Kaiser Permanente
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
0
Learning Objectives
a webinar series on U.S. healthcare interoperability
 During this 90-minute webinar, participants will explore the consumer side
of health information sharing, gaining a basic knowledge of:
— the Personal Health Record (PHR) as the consumer’s collection point
for his or her health information;
— consumer-controlled access to PHR-based information;
— HITSP specifications for PHR health information sharing over a network
or on physical media;
— the use of Medical Summary Documents and Laboratory Results
documents in information exchanges involving PHRs.
HITSP – enabling healthcare interoperability
Slide 1
Agenda
a webinar series on U.S. healthcare interoperability
 Consumer Access to Clinical and Demographics Information
— The PHR as collector and source of consumer’s health information
— Security and privacy requirements for PHR information sharing
 HITSP Specifications for Consumer Empowerment and Access to Clinical
Information via Networks (HITSP IS 03) and portable Media (HITSP IS 05)
 Units of Exchange
— Health Information Summary Documents
— Laboratory Results Documents
 Conformance Subsets
 Questions and Answers / Open Dialogue
HITSP – enabling healthcare interoperability
Slide 2
Introduction: Steve’s Story . . . part three
 Patient is a 26-year-old male coping with the
long-term effects of a brain tumor that was
removed during his childhood
 Access to data from previous care providers
has become increasingly difficult
— Required by both healthcare and
insurance providers
 Calendaring and coordination of upcoming
appointments and procedures is needed
 Patient’s self observations of lifestyle, illness,
reactions to medications, etc. are not being
tracked effectively
HITSP – enabling healthcare interoperability
Slide 3
Introduction: Steve’s story (continued)
 The Future Healthcare in an interoperable world
— With patient’s consent, personal health records can be seamlessly and
securely exchanged between and among diverse systems, including
providers and care settings where the patient has previously gone for
testing or treatment
— Patient will be empowered to access, control, and contribute to his or her
own medical data
— Care providers will have the most up-to-date records available because
healthcare data will be retrieved electronically from its source
HITSP – enabling healthcare interoperability
Slide 4
Overview
 HITSP is a volunteer-driven, consensus-based organization that is funded
through a contract from the Department of Health and Human Services.
 The Panel brings together public and private-sector experts from across
the healthcare community to harmonize and recommend the technical
standards that are necessary to assure the interoperability of electronic
health records.
HITSP – enabling healthcare interoperability
Slide 5
Deliverables and
Mode of Operation
 The HITSP Standards Harmonization Framework
— Identify a pool of standards for an AHIC (American Health Information
Community) Use Case
— Identify gaps and overlaps in the standards for this specific Use Case
— Make recommendations for resolution of gaps and overlaps
— Select standards using HITSP-approved Readiness Criteria
— Develop Interoperability Specifications (IS) that use the selected
standard(s) for the specific context
— Test the IS
HITSP – enabling healthcare interoperability
Slide 6
Current
Interoperability
Specifications (IS)
IS 01
Electronic Health Record (EHR) Laboratory Results Reporting
IS 02
Biosurveillance
IS 03
Consumer Empowerment and Access to Clinical Information
via Networks
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
Slide 7
Current
Interoperability
Specifications (IS)
IS 01
Electronic Health Record (EHR) Laboratory Results Reporting
IS 02
Biosurveillance
IS 03
Consumer Empowerment and Access to Clinical Information
via Networks
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
Slide 8
Consumer Empowerment
 HITSP IS 03 and HITSP IS 05:
Overall Objectives
— Harmonize standards pertaining to the collection and (controlled) sharing
of clinical information in Personal Health Records (PHRs)
— Create consumer-directed secure electronic registration summaries with
links to medication history and laboratory results
— Enable general EHR-to-EHR information exchange for interoperable
patient charts with meds, allergies, problems, registration information, etc.
HITSP – enabling healthcare interoperability
Slide 9
What is a Personal
Health Record (PHR)?
 Summary: A private and secure
Electronic Health Record (EHR)
that is managed, shared and
controlled by the consumer *
 Used to collect, retain and share
critical information, including:
— Clinical notes and results
— Demographics
— Family and social history
— Insurance information
— Medications and allergies
— Laboratory and other test results
— Procedures
— More …
*See the official definition of a PHR at the National Alliance for Health Information Technology
HITSP – enabling healthcare interoperability
Slide 10
Personal Health Record (PHR)
Purpose and Use
Consumer
patient maintains his/her own well-being
 Primary Care Provider
— coordinating overall healthcare
— providing optimal care
— reducing duplicate and adverse events
 Specialist Providers
— complete information leads to more
complete assessments and better
plan for care
— reduced duplicative therapy and
fewer adverse events
 Pharmacies
— medication lists reduce duplicate
therapies, reduce interactions
— complete problem and allergy lists
 Additional Providers of Care
— Imaging centers, long term care
providers, and many more providers
of care
prevent adverse events
 Others
— Quality of Healthcare Reporting
— Post-market Drug Monitoring
— Research
— Biosurveillance
— Public Health
— Disaster Management
HITSP – enabling healthcare interoperability
Slide 11
Personal Health Record (PHR)
Secure and Private
 Consumer defines access rights to PHR information
— The consumer owns and control his or her own health information.
— All sensitive communications are secured.
— All users are authenticated.
— Access is granted based upon the role of the user.
 Security and Privacy are common across HITSP specifications
Learn more about HITSP’s activities in the area of
Security, Privacy and Infrastructure
Webinar 7: Thursday, August 21, 2008 — 2:00-3:30 pm EDT
HITSP – enabling healthcare interoperability
Slide 12
IS 03
Consumer Empowerment and
Access to Clinical Information
via Networks
 This Interoperability Specification defines specific standards needed
to enable the exchange of data between patients and their caregivers
via an electronic network
— Version: 2.1*
Recognized
— Version: 3.0
Accepted
* previously referred to as “Consumer Empowerment”
IS 03
VIA AN
ELECTRONIC
NETWORK
HITSP – enabling healthcare interoperability
Slide 13
HITSP IS 03
Consumer Empowerment and Access to Clinical
Information via Networks
 Consumer establishes an account to host his patient registration summary
and clinical information
 Consumer provides registration summary and self-entered/externally sourced
clinical information during visit with Healthcare Providers
 Authorized Healthcare Providers can review patient’s clinical information
 Healthcare Provider distributes clinical information, lab and other results
(radiology, cardiology, prescriptions, health prevention reminders, referrals to
specialists, etc.) to patient
 Reconciles identifiers for the same consumer/patient
 Queries other organizations for data for that individual
HITSP – enabling healthcare interoperability
IS 03
VIA AN
ELECTRONIC
NETWORK
Slide 14
Sharing clinical information
 The sharing of documents is done using HITSP Transaction
Package 13 (TP 13), Manage Sharing of Documents
 New documents are registered in a Record Locator
Record Locator
(index of all documents available for a patient)
 Documents are stored in a Document Repository
Document
Repository
 To get information about a patient
1. Ask the Record Locator if and where any information can be found
2. Go to a Document Repository to actually retrieve the information
HITSP – enabling healthcare interoperability
Slide 15
IS 03 – Main Business Actors
Hospital
Physician
PHR System
Health Plan
Document
Repository
Pharmacy
etc.
Record
Locator
Other Communities
HITSP – enabling healthcare interoperability
Slide 16
Implementation Architecture Flexibility
 Several instances of each Business Actor can be implemented
 Business Actors can be grouped:
— PHR System may also be a Document Repository
— PHR System may also be a Record Locator
— EMR/EHR System may also be a Document Repository within or across
healthcare organizations
— etc.
 Several such communities or Health Information Exchanges (HIEs)
may be interconnected (e.g. NHIN)
HITSP – enabling healthcare interoperability
Slide 17
HITSP TP 13, Manage Sharing of Documents
Based on IHE XDS Profile
Provide and Register
Document Set-b
Document Source
Document Consumer
Document Consumer
PHR System
Retrieve
Document Set
Document Source
Document
Repository
Registry
Stored
Query
Retrieve
Hospital, Physician,
DocumentHealth
Set Plan, Pharmacy, etc.
Registry
Stored
Query
Document
Registry
Record Locator
Other Communities
HITSP – enabling healthcare interoperability
Slide 18
Verifying Patient Identity
 Need
— Link patient identifiers from multiple sources
— Query for demographics to ensure and verify patient identity
 Solution
— HITSP TP 22 – Patient ID Cross-Referencing Transaction Package
 IHE Patient Cross-Referencing Transaction (PIX)
— HITSP T 23 – Patient Demographics Query Transaction
 IHE Patient Demographics Query Transaction (PDQ)
HITSP – enabling healthcare interoperability
Slide 19
TP22, Patient Id Cross Referencing and
T23, Query Demographics
Based on IHE PIX and PDQ Profiles
Patient X-ref Consumer
Patient X-ref Consumer
Patient Demo Consumer
Patient Demo Consumer
PHR System
Document
Repository
Either PIX or PDQ Query
Hospital, Physician,
Health Plan, Pharmacy, etc.
Either PIX or PDQ Query
Patient Id X-Ref Mgr
Patient Demo Supplier
Record Locator
Other Communities
HITSP – enabling healthcare interoperability
Slide 20
IS 03 – Complete
Document Source
Provide and Register
Document Set-b
Retrieve
Document Set
Retrieve
Document Set
Document Consumer
Document Consumer
Registry Stored Query
Patient X-ref Consumer
Document Source
Document
Repository
Patient Demo Consumer
Registry Stored Query
Patient X-ref Consumer
Patient Demo Consumer
Hospital, Physician,
Health Plan, Pharmacy, etc.
PHR System
Document
Registry
Patient Id X-Ref Mgr
Patient Demo Supplier
Record Locator
HITSP – enabling healthcare interoperability
Initiating
Gateway
Accepting
Gateway
Other Communities
Slide 21
IS 03
Complete set of constructs
Document
Document Description
HITSP/TP13
HITSP Manage Sharing of Documents Transaction Package
HITSP/TP22
HITSP Patient ID Cross-Referencing Transaction Package
HITSP/T23
HITSP Patient Demographics Query Transaction
HITSP/C32
HITSP Summary Documents Using HL7 Continuity of Care Document (CCD)
HITSP/C37
HITSP Lab Report Document Using IHE XD* Lab Component
HITSP/C35
HITSP Lab Report Terminology Component
HITSP/T15
HITSP Collect and Communicate Security Audit Trail Transaction
HITSP/T16
HITSP Consistent Time Transaction
HITSP/T17
HITSP Secured Communication Channel Transaction
HITSP/TP20
HITSP Access Control Transaction Package
HITSP/TP30
HITSP Manage Consent Directives Transaction Package
HITSP/C19
HITSP Entity Identity Assertion Component
HITSP/C26
HITSP Non-repudiation of Origin Component
HITSP – enabling healthcare interoperability
Slide 22
IS 05
Consumer Empowerment and
Access to Clinical Information
via Media
 This Interoperability Specification defines specific standards needed to assist
patients in making decisions regarding care and healthy lifestyles (i.e.,
registration information, medication history, lab results, current and previous
health conditions, allergies, summaries of healthcare encounters and
diagnoses).
— Version: 1.0
Accepted
IS 05
HITSP – enabling healthcare interoperability
VIA MEDIA
Slide 23
HITSP IS 05
Consumer Empowerment and Access to
Clinical Information via Portable Media
 Consumer establishes an account to host a patient registration summary
AND clinical information
 Consumer brings registration and clinical information via media
(CD-R or USB key) to visit with Healthcare Providers
 Authorized Healthcare Provider reviews patient’s clinical information
 Healthcare Provider distributes new/updated clinical information and
lab results by Healthcare Provider to patient on portable electronic media
 Patient identification reconciliation and most
privacy/security requirements accomplished via
human-to-human interaction
HITSP – enabling healthcare interoperability
Slide 24
IS 05
Main Business Actors and Technical Actors
PHR System
Portable Media
Creator
Portable Media
Importer
EHR System
Distribute
Document Set on Media
Distribute
Document Set on Media
Portable Media
Importer
Portable Media
Creator
Implementation Flexibility:
 Media (CD-R and/or USB Key) to be
carried by the patient or exchanged
via a secured means.
Uses HITSP T-33 Transfer of Documents on Media
Transaction Based on IHE XDM
HITSP – enabling healthcare interoperability
Slide 25
IS 05
Complete set of constructs
Construct
Description
HITSP/T33
HITSP Transfer of Documents on Media Transaction
HITSP/TP22
HITSP Patient ID Cross-Referencing Transaction Package
HITSP/T23
HITSP Patient Demographics Query Transaction
HITSP/C32
HITSP Summary Documents Using HL7 Continuity of Care Document (CCD) Component
HITSP/C37
HITSP Lab Report Document Using IHE XD* Lab Component
HITSP/C35
HITSP Lab Result Terminology Component
HITSP/T15
HITSP Collect and Communicate Security Audit Trail Transaction
HITSP/T16
HITSP Consistent Time Transaction
HITSP/C19
HITSP Entity Identity Assertion Component
HITSP/TP20
HITSP Access Control Transaction Package
HITSP/TP30
HITSP Manage Consent Directives Transaction Package
HITSP – enabling healthcare interoperability
Slide 26
HITSP IS 03
HITSP IS 05
Consumer Empowerment and Access
Consumer Empowerment and Access
to Clinical Information via Networks
to Clinical Information via Media
 Unit of Information Exchange for Personal Health Records
Standard structured electronic documents (XML Format)
— Uses HL7 Clinical Document Architecture (CDA) and HL7 Continuity of Care
Document (CCD) – standard structured electronic document representing clinical
information for a patient
HITSP – enabling healthcare interoperability
Slide 27
Units of Information Exchange
Type 1: Base or Composite Standards
HITSP
IS Constructs - Re-Use and Re-Purpose
 Re-Use
Applying an existing
construct to more than one IS
 Re-Purpose
Constructs
(single purpose
or reusable)
Updating a construct to
meet the needs of a
new Use Case
 Can extend or constrain when reusing or re-purposing
—
Specifications contain a common superset
—
Superset can be extended as new requirements are encountered
—
Superset can be constrained with use-specific constraints
HITSP – enabling healthcare interoperability
Slide 28
Units of Information Exchange
 HITSP C32 (Component)
Summary Document
—
—
—
Summarizes a consumer’s
medical status for the purpose of
information exchange
May include administrative
(e.g., registration, demographics,
insurance, etc.) and clinical (problem list,
medication list, allergies, test results,
etc.) information
Re-Use: Originally developed for
Registration and Medical Summary
HITSP – enabling healthcare interoperability
 HITSP C37 (Component)
Laboratory Report Document
— Specifies content for Laboratory Results
data in a document-based functional flow
scenario
— Re-Use: Originally developed for the
Biosurveillance and EHR-Lab Use Cases
 Constrained when reused by
Consumer Empowerment to require
fully computable information
 Necessary because Document
Consumer (usually the PHR) must be
able to import discrete lab data into the
patient record.
Slide 29
Example: Continuity of Care Document (CCD)
HITSP – enabling healthcare interoperability
Slide 30
Example: Lab Report
HITSP – enabling healthcare interoperability
Slide 31
C37 Laboratory Report Document Structure
 Key Concepts
pkg C37
— Information is fully computable
«component»
Lab Report Document Structure
+
(not free text)
docId = C37
references
 In HL7 CDA terms, this is referred
to as “Level 3” data encoding
constrains
«component»
EHR Lab Terminology
+
docId = C35
 Constrains the use of the IHE XD*-
Lab Profile which itself is a constrained
implementation of HL7 CDA R2
«composite standard»
IHE XD*-Lab
constrains
constrains
 Refers to C35 for terminology and
«base standar...
HL7 CDA R2
«base standar...
HL7 V3 Lab
HITSP – enabling healthcare interoperability
vocabulary support
Slide 32
Examples: Terminology and Vocabulary
This will be useful for the next slide
 LOINC
Logical Observation Identifiers Names and Codes
Identifies laboratory and other clinical observations
— www.loinc.org
 HEDIS
Healthcare Effectiveness Data and Information Set
Tool to measure care are service performance
— www.ncqa.org
 SNOMED-CT Systematized Nomenclature of Medicine-Clinical Terms
Comprehensive clinical terminology
— www.ihtsdo.org
 HL7
Health Level Seven
Develops healthcare informatics standards, mostly for interoperability
— www.hl7.org
HITSP – enabling healthcare interoperability
Slide 33
C35 EHR Lab Terminology
 Key Concept
pkg C35
«component»
EHR Lab Terminology
+
docId = C35
— Augments minimum terminologies
and vocabularies required by the
base standard
constrains
«base standard»
LOINC
— Specifies vocabulary for Laboratory
Results data
«base standard»
SNOMED-CT
constrains
«base standard»
HL7 V2.5 Code Sets
constrains
«base standards»
HL7 V3.0 Code Sets
constrains
 LOINC for top 95% of routine tests
reported in HEDIS, plus microbiology
and cytology
 SNOMED-CT for Problem List (VA-KP
Subset), Lab Test Findings & Organisms
 HL7 V2.5 Code Sets and HL7 V3.0
Code Sets
HITSP – enabling healthcare interoperability
Slide 34
Content Module
C32
Summary Document
 Module Requirements
— Requires Person and Information
Source Modules
— Constraints may include the use of
specific code systems, requiring some
fields if module is present, other
module-specific constraints
— Other CCD information modules
permitted but interoperability is not
guaranteed for those modules
 The document, as a whole, contains a
designated author that is the consumer
and/or their designated agent, such as the
parent of a minor child
HITSP – enabling healthcare interoperability
HITSP
Opt
Person Information
R
Language Spoken
R2
Support
R2
Healthcare Provider
O
Insurance Provider
O
Allergy / Drug Sensitivity
O
Condition
O
Medication – Prescription and NonPrescription
O
Pregnancy
O
Information Source
R
Comment
O
Advance Directive
O
Immunization
O
Vital Sign
O
Result
O
Encounter
O
Procedure
O
Slide 35
C32 – Summary Documents Using HL7 Continuity of
Care Document (CCD) Component
 Key Concepts
— HL7 Clinical Document Architecture
«component»
Summary Document Using
HL7 Continuity of Care (CCD)
+ docId = C32
maps to
constrains
constrains constrains
«composite stand...
CAQH CORE
«base stand...
LOINC
«composite standard»
maps to
«composite standard»
Federal Medication
Terminologies
constrains
«base stand...
X12N 270/271
IHE IT Infrastructure
«base standard»
NCPDP SCRIPT
constrains
references
«base stand...
ASTM/HL7 CCD
maps to
«base standard»
NDC RxNorm SPL
constrains
«base stand...
HL7 CDA R2
«base standard»
ASTM E2369
HITSP – enabling healthcare interoperability
Release2, HL7 V3 Reference
Information Model (RIM), Continuity
of Care Medical Summary,
Implementation Guide, Object
Identifier (OID)
 Uses document content description
for the required data elements
provided in:
— HL7 Implementation Guide:
CDA Release 2 – Continuity of
Care Document (CCD),
Release 1.0, April 01, 2007
with additional clarifications and
specifications as appropriate
Slide 36
D a ta E le m e n t
F re e T e x t S ig
In d ic a te M e d ic a tio n
S to p p e d
Medications –
Prescription and Non-Prescription Module
A d m in is tra tio n T im in g
F re q u e n c y
Key Specifications that extend CCD for medications:
In te rv a l
 Route of Administration:
D u ra tio n
Value drawn from FDA route of administration
R o u te
 Dose:
D ose
Unit attribute, if present, coded using Unified Code for Units of Measures
S ite
D o s e R e s tric tio n
P ro d u c t F o rm
D e liv e ry M e th o d
C o d e d P ro d u c t N a m e
C o d e d B ra n d N a m e
F re e T e x t P ro d u c t N a m e
F re e T e x t B ra n d N a m e
D ru g M a n u fa c tu re r
P ro d u c t C o n c e n tra tio n
T y p e o f M e d ic a tio n
S ta tu s o f M e d ic a tio n
In d ic a tio n
P a tie n t In s tru c tio n s
 Site:
Value descending from the SNOMED CT Anatomical Structure
(91723000) hierarchy
 Product Form:
From dosage form - FDA dosage form – source NCI Thesaurus
 Product name or brand name:
Coded using RxNorm, or NDC. When only the class of the drug is
known, it shall be coded using NDF-RT. FDA Unique Ingredient Identifier
codes (UNII) codes may be used when there are no suitable codes in
the other vocabularies to identify the medication
 Indication:
Coded using the VA/KP Problem List Subset of SNOMED CT
(terms descending from clinical finding (404684003) concept
HITSP – enabling healthcare interoperability
Slide 37
Data Element
Adverse Event Date
Allergies and Drug Sensitivities Module
Adverse Event Type
Key Specifications that extend CCD for allergies and drug sensitivities:
Product Free-Text
Product Coded
 Adverse Event Type: See below. Support tiered level of specifics
Reaction Free-Text
 Severity: See below
Reaction Coded
 Product causing the adverse event: Coded to UNII for Food and
Severity Free-Text
substance allergies, or RxNorm when to medications, or NDF-RT when
to classes of medications
Severity Coded
 Reaction: coded using the VA/KP Problem List Subset of SNOMED CT
(terms descending from clinical finding (404684003) concept
SNOMED CT
P referred T erm s
for S everity
SNOMED
C T C ode
S N O M E D C T P referred Term s for A dverse
E vent T ype
propensity to adverse reactions
SNOMED
C T C ode
U sage
420134006
U sed to record an adverse reaction.
418038007
U sed to record an adverse reaction to an environm ental agent.
m ild
255604002
m ild to m oderate
371923003
propensity to adverse reactions to drug
419511003
U sed to record an adverse reaction to a drug.
m oderate
673600 7
propensity to adverse reactions to food
418471000
U sed to record an adverse reaction to a food.
m oderate to severe
371924009
allergy to substance
419199007
U sed to record an allergy to an environm ental agent.
severe
24484000
drug allergy
416098002
U sed to record an allergy to a drug.
fatal
399166001
food allergy
414285001
U sed to record an allergy to a food.
drug intolerance
59037007
U sed to record intolerance to a drug.
food intolerance
235719002
U sed to record intolerance to a food.
propensity to adverse reactions to substance
HITSP – enabling healthcare interoperability
Slide 38
A Successful
Collaboration
 Interweaving many different standards to address business needs
 A successful collaboration between HITSP and several HITSP
member organizations developing base standards and implementation
guides/profiles
HITSP – enabling healthcare interoperability
Slide 39
Strengths of IS 03 and IS 05

Effective interoperability
— Independent conforming implementations will interoperate
 all dimensions of interoperability covered, including sharing/selective
access, transport and identity management
— Semantic Interoperability with core clinical content
 medications, allergies, problems/ conditions, and real-world clipboard
information
— Designed to equally empower the consumers and their providers
(PHR-PHR, PHR-EHR, EHR-EHR) with the same level of robustness
(continued)
HITSP – enabling healthcare interoperability
Slide 40
Strengths of IS 03 and IS 05

(continued)
Practical interoperability
— Standards that already have “implementation feasibility” validated
 IHE Connectathon, HIMSS Interoperability Demonstration
— Significant number of implementations
 prototype and commercial
 Flexible interoperability
— Designed to allow “receivers of information” to operate at various
levels of richness (explicitly defined IS conformance subsets):
 display (browser+any CDA style sheet)
 Import the “entire document”
 Import discrete coded data
 Secured and Private interoperability
— Encryption, patient consent, user authentication
HITSP – enabling healthcare interoperability
Slide 41
A concrete achievement for Steve
 Implementation of HITSP Interoperability Specifications will allow
Steve to have his records exchanged seamlessly and securely
between and among diverse systems
— Create a personal health record to access his registration
summary and medication history
— Establish permissions and access rights for viewing his data
— Authorize healthcare provider to review medication history
— Retrieve, store, graph and share laboratory test results
— Retrieve and store:
 Lists of current and previous health conditions
 Lists of current medications, current environment,
dietary, medication or medical supply allergies
 Test results and medical procedures
 A list of diagnosis codes
HITSP – enabling healthcare interoperability
Slide 42
How YOU can
become involved
 Use or specify 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
HITSP – enabling healthcare interoperability
Slide 43
How YOU can
become involved
Learn more about specific HITSP activities during these upcoming webinars:
Webinar 1
Standardizing How We Share Information in
Healthcare: An Introduction to HITSP
Thursday, June 5, 2008 — 2:00-3:30 pm EDT
Webinar 2

Biosurveillance
Thursday, July 10, 2008 — 2:00-3:30 pm EDT
Webinar 5
Electronic Health Record (EHR) and
Lab Reporting
Thursday, July 24, 2008 — 2:00-3:30 pm EDT
HITSP – enabling healthcare interoperability
Security, Privacy and Infrastructure
Thursday, August 21, 2008 — 2:00-3:30 pm EDT
Webinar 8

Quality
Thursday, August 7, 2008 — 2:00-3:30 pm EDT
Webinar 7
Consumer Access to Clinical Information
Thursday, June 26, 2008 — 2:00-3:30 pm EDT
Webinar 4

HITSP Foundational Components
Thursday, June 19, 2008 — 2:00-3:30 pm EDT
Webinar 3
Webinar 6
EHR and Emergency Response
Thursday, September 4, 2008 — 2:00-3:30 pm EDT
Webinar 9
Medication Management
Thursday, September 18, 2008 — 2:00-3:30 pm EDT
www.HITSP.org/webinars
Slide 44
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
Slide 45
Sponsor
Strategic Partners
www.HITSP.org
HITSP – enabling healthcare interoperability
Slide 46
Webinar Series
Consumer Access to
Clinical Information
Questions and Answers
Sponsored by the HITSP Education, Communications and Outreach Committee
enabling healthcare interoperability
47
Descargar

Introduction to the HITSP - ANSI Public Portal