Rapid Response Manufacturing

Download Report

Transcript Rapid Response Manufacturing

A TELEHEALTH DATA EXCHANGE
STANDARD
ATA June 5, 2001
Dale Bergman, P.Eng, Dean Yergens,
Ralph Ulmer, & Dr. Peter Sargious
TELEHEALTH INTEROPERABILITY LAB
OVERVIEW

Why is a Telehealth Data Exchange Standard
required?

Challenges and issues involved

An approach to developing a Telehealth Data
Exchange Standard

Benefits of using the this approach.
TELEHEALTH INTEROPERABILITY LAB
WHY A TELEHEALTH DATA EXCHANGE
STANDARD?
INTEROPERABILITY
TELEHEALTH INTEROPERABILITY LAB
WHY INTEROPERABILITY

Enable connecting outside a homogeneous
Telehealth environment (Health District).

Project Expansion

Physician Referral Patterns Change

Access Educational Resources

Protecting the investment of equipment.

Integration into a complex healthcare
environment
TELEHEALTH INTEROPERABILITY LAB
TELEHEALTH INTEROPERABILITY: PROBLEM
Wide Area
Network
!
!
(WAN)
Format of Data
Format of Data
-Still Images
-Video Clips
-Audio Clips
-Patient demographics
-X-Ray Images
-Still Images
-Video Clips
-Audio Clips
-Patient demographics
-X-Ray Images
TELEHEALTH INTEROPERABILITY LAB
TELEHEALTH INTEROPERABILITY: SOLUTION
Wide Area
Network
(WAN)
STANDARD
Format of Data
-Still Images
-Video Clips
-Audio Clips
-Patient demographics
-X-Ray Images
TELEHEALTH INTEROPERABILITY LAB
CHALLENGES AND ISSUES

Telehealth is broad in scope.


Integration into a health care environment.


Teledermatology, Teleultrasound, Telepsychiatry
Variety of information systems: HIS, LIS, RIS, PACS
Difficulty in obtaining consensus on how medical
information is managed.

Buy in and support from the vendor community

Standards that can allow for the incorporation of
rapidly developing new technologies
TELEHEALTH INTEROPERABILITY LAB
WHAT IS REQUIRED?
Selection and integration of the following:

Vocabulary/Coding Standards



Data Model Standards

Electronic Patient Record (EPR)?

Tools to create data models: UML, RIM
Data Interchange Standards


SNOMED, ICD9, ICD10, DRG, LIONC, etc.
HL7, DICOM, XML, etc.
Communication Standards

TCP/IP, FTP, ITU-T T.120, etc.
TELEHEALTH INTEROPERABILITY LAB
APPROACH

Not to create new standards but leverage off of
existing standards.

Create “profiles” of existing standards to be used
for Telehealth.

Where needed and only where needed create “new
elements” in relation to existing standard(s).

Use proper procedures to move these “new
elements” to become a part of the standard(s).
TELEHEALTH INTEROPERABILITY LAB
EXAMPLE IMPLEMENTATION
Urban Hospital
PACS
RIS
HIS
Rural Hospital/Clinic
TELEHEALTH
SYSTEM
TELEHEALTH
SYSTEM
XML
DICOM
HL7
LIS
TELEHEALTH INTEROPERABILITY LAB
XML
Wide
Area
Network
(WAN)
DICOM
HL7
TELEHEALTH DATA EXCHANGE STANDARD
PROCESS

Step 1: Develop the components of the standard

Step 2: Create a practical implementation of the
standard

Step 3: Create a development toolkit

Step 4: Provide a remote testing environment

Step 5: Perform conformance and certification
testing
TELEHEALTH INTEROPERABILITY LAB
BENEFITS OF A TELEHEALTH
DATA EXCHANGE STANDARD
INTEROPERABILITY
Questions?
http://www.telehealthlab.com
TELEHEALTH INTEROPERABILITY LAB