Building Bridges System Interoperability

1
Building Bridges System Interoperability

• Dr. Richard Swafford
• Chief Information Officer
• Community Clinics Health Network (CCHN)

2
Definition of Interoperability

• According to the IEEE
• The ability of two or more systems or
  components to exchange information and to use the
  information that has been exchanged.
• According to James OBrien
• Being able to accomplish end-user
  applications using different types of computer
  systems, operating systems, and application
  software, interconnected by different types of
  local and wide area networks.

3
Practical Example
Richs Excellent Adventure/Bogus Journey
Business Practicality IT Technology-base
d Education Facts Counseling Feelings
Behavior Justice and Security Law Enforcement
4
Practical Example
Richs Excellent Adventure/Bogus Journey
Interoperable Philosophy
My goal is to provide Practical, Technology-Based
Facts that will make you Feel good but not so
good that it lands me in Jail
5
Real Example of Interoperability
6
Overview

• Why Interoperability?
• Interfaced versus Integrated
• Technologies to provide Interoperability
• Impact on the Clinic
• Time
• Cost
• Productivity
• Wrap up

7
Why Interoperability?

• Issues that drive separation
• Diverse/Special Needs
• Market or Industry specialization
• Lack of integrated platforms
• Issues that maintain separation
• Difficult to Integrate
• Change
• Functionality

8
Types of Interoperability
Ensures that the information sent and received
between systems is unaltered in its meaning. It
is understood in exactly the same way by both the
sender and receiver.
Is the degree to which the integrity of workflow
processes can be maintained between systems. This
includes maintaining/conveying information such
as user roles between systems.
Ensures that systems can send and receive data
successfully. It defines the degree to which the
information can be successfully transported
between systems.
Reference CyrusXp
9
Interfaced versus Integrated

• Interfaced
• Diverse Platforms
• External Connectivity
• 3rd Party Involvement
• Integrated
• Single Application Model
• No 3rd Party Involvement

10
Interface
11
Interface
12
Integrated
13
Technologies to Provide Interoperability

• Interface Types
• Point to Point
• Interface Engine
• Interface Standards
• HL7 (2.3, 2.4, 2.5)
• ANSI X12
• DICOM
• CCD/CDA

14
Technologies to Provide Interoperability
15
Impact on the Clinic

• Time
• Be prepared for development time
• Technical staff involvement
• Testing, testing, testing
• Cost
• Two-sides to every interface
• Initial interface development versus modified
  existing interface

16
Impact on the Clinic

• Productivity
• Impact of a poor interface
• Testing does not always catch every issue
• Load testing is critical
• Pressure vendors to provide a quality product

17
Final Thoughts

• Integration is often better then interfacing.
• Not all integrated products do everything well or
  at all.
• Developing interfaces is painful.
• Force vendors to deliver on promises.
• Ask for Help!

18
Summary and Wrap Up

• Why Interoperability?
• Interfaced versus Integrated
• Technologies to provide Interoperability
• Impact on the Clinic
• Time
• Cost
• Productivity

19
Contact Info

• Dr. Richard Swafford, PhD
• Chief Information Officer
• 800-640-1662 x 311 or 619-542-4311
• rswafford_at_ccc-sd.org