2005-10 hssp public slide deck version 1

8/8/2019 2005-10 HSSP Public Slide Deck Version 1

1/24

10/11/10 09:15

Healthcare Services Specification Project

The Business Case and Importance of Services

Healthcare Services Specification Project

The Business Case and Importance of Services

HL7 Services Specification Project Workgroup

OMG Healthcare Domain Task Force

HL7 Services Specification Project Workgroup

OMG Healthcare Domain Task Force

October 2005October 2005


2/24

Pag

BackgroundBackground

This presentation represents the collective input and thinking

from the collective participants involved in the Healthcare

Services Specification Project.

Represented were members from

Object Management Group (OMG)

Health Level Seven (HL7)

Integrating the Healthcare Enterprise (IHE)

This presentation is intended to describe the purpose, role,

and importance of industry-standard service interface

specifications


3/24

Pag

Why common services and not just

messages?*

Why common services and not just

messages?*

A common practice in healthcare, just not yet in healthcare IT

Many key products use them but do not expose interfaces

Ensures functional consistency across applications

Accepted industry best practice

Furthers authoritative sources of data

Minimizes duplication across applications, reuse

Messages can be either payloads in or infrastructure beneath

services

Service-oriented architecture is just automation of common

services

*slide adapted from a Veterans Health Administration Presentation, used with permission


4/24

Pag

What is the Healthcare Service Specification

Project?

What is the Healthcare Service Specification

Project?

An effort to create common service interface specificationstractable within Health IT

A joint standards development project involving Health Level 7(HL7) and the Object Management Group (OMG)

Its objectives are: To create useful, usable healthcare standards that address

functions, semantics and technologies

To complement existing work and leverage existing standards

To focus on practical needs and not perfection

To capitalize on industry talent through open communityparticipation


5/24

Pag

Where would these specifications be usedWhere would these specifications be used

Inter-Enterprise (such as NHIN, RHIOs, LHINs)

By functionally specifying behavior, roles between applications and productsare clarified, and the technologies supporting them can be profiled andsharpened

Intra-Enterprise

Standardization on functionality allows for better integration of off-the-shelf

and custom development environments, and promotes more of a plug andplay environment

Intra-Product

Facilitates vendors ability to integrate third-party value-add components andspeed design phase with higher confidence

Custom-Implementation

Affords organizations wishing to custom-develop the opportunity to laterintegrate off-the-shelf


6/24

Pag

The ApproachThe Approach

HL7 to lead in service selection, functional elaboration, and

conformance criteria

OMG to lead in technical specification

Both organizations jointly participate in all activities Work products will be owned by only one organization but

used collaboratively

Operate as one project as a principle

Actively seek vendor participation Engage IHE community


7/24

Pag

The Value of CollaborationThe Value of Collaboration

HL7 brings Healthcare semantic interoperability expertise

Rich, extensive international community perspective

Diverse membership base

OMG brings

distributed systems architecture and modeling excellence

Effective, efficient, rapid process

Premise that standards mustbe implemented

Resulting in

Services will be identified by the community needing them

Improved methodology resultant from functional and architectural merging ofthe two groups

Facilitation of multi-platform implementation and broader implementationcommunity


8/24


9/24

Pag

HSSP Stakeholder Benefits and ImpactsHSSP Stakeholder Benefits and ImpactsHSSP Stakeholder Benefits and ImpactsHSSP Stakeholder Benefits and Impacts


10/24

Page

For Product Consumers and Users

The Impacts and Rationale of HSSP Specifications

For Product Consumers and Users


Impacts Rationale

Promotes deployment ease andflexibility

Specifications will support multiple topologies

Consistency at the interface levelassures asset protection

Standard interfaces means that conformantcomponents are substitutable

Multiple vendor product use/

interoperability

Using compliant products means side-by-side

interoperation of multiple product offerings

Increased buyer/product offerings Consumer demand will create increased marketplacecompetition

Facilitates integration Unity in purpose and consistency in interface easesintegration burden

Time to market Availability of an industry-accepted componentinterface eases product development burden

Requirements definition influencevendors in a direct way

Participation by provider and payer community isdirect expression of business need

Lower cost = wider deployment =higher quality service


11/24

Page

Product Vendor


Product Vendor


Impacts RationaleMarket opportunity ability to growbusiness / Grow the pie

Standardization of interfaces eases cost-of-entry tomarkets

Conformance adds legitimacy toproduct offering

Consumers view conformance as a confidence metric

Reduced time and cost to market Use of 3rd party components

Simplify / reuse of design

Ability to reuse design ideas, incorporate off-the-shelfcomponents into value-add offerings

Participation provides the ability toinfluence the standard

You can shape the standard to be supportive of yourproduct architecture


12/24

Page

Regulatory/Policy/Legislative


Regulatory/Policy/Legislative


Impacts Rationale

Establishing objective assessmentcriteria:

Measurement criteria for regulatorycompliance

Inclusion of rigorous conformance assertionsbenefits compliance and verification

Allows for technology change within the

regulation

Concurrent support of multiple technologies

allows for technology evolution

Offering an easy/easier solution that iscomplete and actionable / ease the pathto adoption:

How do we Pick the winninghorse?

Opportunity cost of using the wrongstandard has big implications

HSSP integrates function/ behavior, data, andprotocol promoting an integrated solution set

Solution that complements existingstandards

HSSP is using HL7 semantics, OMGprocesses, IHE testing, and established

technology protocols


13/24

Page

Research


Research


Impacts Rationale

Promotes accessibility to rawinformation

Strong emphasis on semantically rigorous dataand query/retrieval

Enabler for collaborative studies, e.g.de-identification, retrieval, etc.

Leveraged use of identity service enables de-identification

Enlarges cell and sample sizes basedon interoperability

Facilitates responsiveness to bio-surveillance requirements

Standard interfaces accommodate dynamic andemerging strategies and tools

Enables construction of higher-orderservice stacks with less investment

Composable nature of services promotesconstruction


14/24

Page

Implementer/Integrator


Implementer/Integrator


Impacts RationaleReduced integration time and costresulting from the use of standard tooling

Use of standard in off-the-shelf tools facilitatestheir use

Risk mitigation (skill portability/ trainingadvantage, vendor independence,substitutability)

By training staff in the standard, skills areportable across tools

Creates a value offering opportunity basedon the ability to deliver using these servicestandards

Allows staff and solutions to build upon the useof the standard and not technologies

Improved ability to deliver and supportinterfaces that have been implemented

Using services speeds project design phasesand promotes reuse


15/24

Page

SDOs


SDOs


Impacts RationaleUseable standards Emphasis on practicality

Market-focused standards based oncommercial implementations

Shortens time required to develop specificationsand encourages collaboration

Promotes harmonization, cooperation,cohesion among standardscommunities

Integration of function, data, and technologypromotes leveraged reuse

More members/involvement =more revenue & better specs

Practical, market-focus and iterative timelinepromotes participation and results


16/24


17/24


18/24

Page

Project Timeline and RoadmapProject Timeline and Roadmap

1996: First OMG Healthcare Service Spec Adopted (PIDS?)

2003: HL7 ServicesBOF formed

2005 September: HL7, OMG Collaboration MOU

2005 January: Joint Project Chartered

2005 April: Project Kickoff

2006 January: Functional Specs Ballot (planned)

2006 Q4: Technical Specs RFP (planned)

2005 September: Methodology and MetaSpecs Baselined (planned)

2005 October: Interoperability Services Workshop & Conference


19/24

Page

How is this project different?How is this project different?

Active participation from three continents and 15+organizations

Significant cross-cutting community involvement

Providers (Kaiser, VHA, Intermountain Health, Mayo)

Vendors (CSW Group, IBM, PatientKeeper, Universata)

Value-added Providers (MedicAlert, Ocean Informatics, EclipseFoundation, etc.)

Payers (Blue Cross/Blue Shield, Kaiser)

Integrators (IBM, EDS)

Governments (Veterans Health Administration, Canada HealthInfoway, HealthConnect (Australia), SerAPI (Finland))

Managing differences between SDOs in terms ofmembership, intellectual property, and cost models


20/24

Page

Why should I participate? [One]Why should I participate? [One]

This effort is focused on and driven by business-need

It is not an academic exercise striving for perfection

Acknowledgement that for standards to be useful they must be

used

Focused on the practical and achievable

Short timelines

Based upon business value and ROI

Leveraging talent from two standards communities

Up-front commitment ensures community engagement

Being run like a project and not a committee

Recognize participation as an investment and not an expense


21/24

Page

Why should I participate? [Two]Why should I participate? [Two]

This is happeningthe only way to influence the outcome is

to engage

Significant networking opportunitiesyou will gain access

to the best and brightest in the industry and the world

Prime opportunity to directly engage with complementing

stakeholder groups (provider-to-vendor, vendor-to-payer,

SDO-to-SDO, etc)

Benefit from lessons learned from others

Reduce design burden

Establish market presence and mindshare as industry leader


22/24

Page

How do I Participate?How do I Participate?

Join appropriate standards organizations

HL7 for functional work

OMG for technical specification work

Join both

Allocate resources to actively engage in the project

Engage existing, knowledgeable resources in the areas

they are working already.

Subgroups form based on industry need and priority

Teleconferences are weekly; meetings approximately

bimonthly


23/24

Page

Who should I involve?Who should I involve?

Involve the staff that can best address your

business needs:

The benefits you receive will depend upon your

investment Organizations that commit resources garner

more influence and more mindshare

Your business interests are being represented

by your attendees


24/24

ReferencesReferences

HL7 Website:

http://www.hl7.org

OMG Website:

http://www.omg.org

Services Project Homepage

http://groups.yahoo.com/group/ServicesSpec
http://www.hl7.org/http://www.omg.org/http://www.omg.org/http://www.hl7.org/

2005-10 hssp public slide deck version 1

Documents