OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ihc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Updated outline plan for HL7 Services project - for review at OMG meeting


From: Alan.P.Honey@kp.org [SMTP:Alan.P.Honey@kp.org]  
To: healthcare@omg.org 
Cc: servicesBOF@lists.hl7.org 
Subject: Updated outline plan for HL7 Services project - for review at OMG meeting 
Sent: 2/2/05 2:33 PM 
Importance: Normal 

Attached is the draft updated outline plan for the HL7 Services work. The intent is to review this (among other things) at the OMG Healthcare event tomorrow - Thursday). It will also be included on the agenda for the HL7 project teleconference on Monday,



Regards,

Alan Honey
Enterprise Architect.
925 979 7459  (tl 474)
Alan.P.Honey@kp.org

Services Project Approach and Plan v1.1.rtfServices Project Approach and Plan v1.1.rtf

 
 

 

 

Healthcare Services

Project Approach and Plan

 

Version No. 1.1

Date: 2/2/2005

 

 

 

Document Version History

Version Number

Version Date

Revised By

Description

1.0

10/25/2004

Alan Honey, Ken Rubin

Initial Draft Version

1.1

02/02/2005

Alan Honey

Revised after Orlando meeting

 

 

 

 

 

 

 

 

 

 

 

 

 

Project Coordinators:

 

Name:

Alan Honey

Name:

Ken Rubin

Organization

Kaiser-Permanente

Organization

Veterans Health Administration

Address: 

2880 Shadelands Dr, Walnut Creek, CA 94598

Address: 

5109 Leesburg Pike, Suite 414

Falls Church, VA 22041

Phone: 

925/979-7459 

Phone: 

703/845-3299

E-mail: 

Alan.P.Honey@kp.org

E-mail: 

ken.rubin@med.va.gov

 


Table of Contents

1      Introduction............................................................................................................................................... 3

1.1       Background and Purpose..................................................................................................................... 3

2      Approach and Plan................................................................................................................................... 3

2.1       Project Approach..................................................................................................................................... 3

2.2       Project Initiation – Early Steps......................................................................................................... 4

2.3       Outline Plan for remainder of project.......................................................................................... 5

 

 


1                             Introduction

1.1                          Background and Purpose

This document defines an outline project plan for  the HL7 Healthcare Standard Services Project.  This effort is the outcome of a number of “Birds of a Feather” sessions that have been held at HL7 Working Group meetings, culminating in formal chartering as a “project” by the HL7 EHR TC on Jan 26th 2005. Due to the number of participants and the voluntary nature of this work, this plan is more informal than is typical, but is aimed to ensure that the major work tasks are identified and resourced.

The first formal project meeting took place on the evening of 1/26 in Orlando at the HL7 WG. Notes and actions from the meeting were circulated on the list server servicesBOF@lists.hl7.org.

 

2                             Approach and Plan

2.1                         Project Approach

This section firstly sets out some of the general principles by which this work will be carried out. It is formatted as a set of statements or assumptions.

1.       There is sufficient support and momentum to make this successful

2.       All participants are volunteers

3.       The work will not be completed unless a sufficient number of people and organizations commit resources to it.

4.       Overall, this work is seen as a joint effort between HL7 and the Object Management Group (OMG).  At a high level, HL7 will produce “Computationally Independent” specifications and the OMG oversee the technology specific specifications via their RFP process. However, the HL7 specific effort is not dependent on the OMG work and the output from this project will stand in its own right.

5.       Clear roles and responsibilities must be defined and fulfilled.

Given the above statements, the general approach will be to run this work as a project under the auspices of the Electronic Health Record Technical Committee of HL7. A project proposal was put together and approved by that committee at the January Working Group meeting in Orlando. The project proper will last from January through December 2005. Towards the latter part of the project, consideration will be given to any work that needs to continue after the life of the project. This will obviously depend upon perceived success of the project by many organizations and the HL7 group itself.

The plan for achieving this is set out in the next section of this document. This is split into two subsections, firstly initial steps that were identified in the January WG meeting, where specific actions have been identified, and secondly an outline timeline for remaining activities in the project.

Please also refer to the formal minutes of the January WG produced by Ken Rubin and his paper outlining the proposed HL7-OMG relationship and responsibilities.

Note – this plan is scope only to HL7 project tasks, and does not include OMG activities.


2.2                         Project Initiation – Early Steps

 

Task Id

Task Name

Due Date

Completion Date

Owner

Other Participants

Comments

1

Select services pilots

 

 

 

 

 

 

  a

Identify and describe candidate services (long list) – in progress

2/8/2005

 

Various

 

Each group/organization to provide description for its chosen services

  b

Define criteria for selection

2/8/2005

 

Robert Greenes

 

 

  c

Evaluate list and select pilot services

2/22/2005

 

All

 

Start discussion in teleconference on 2/7 – finalize in 2/21/ call

  D

Publish chosen services (descriptions)

3/1/2005

 

Co-chairs

 

 

2

Define and agree scope in terms of HL7-OMG relationship

 

 

 

 

 

 

  a

Define relationship (Ken’s initial paper)

 

 

-

-

Ken Rubin

 

Done

  b

Review/rework paper

Agree

 

3/7/2005

 

All

 

Process to be agreed during 2/7 call

  c

Review with HL7 Board and Publish

 

3/14/2005

 

Co-chairs

 

 

 

 

 

 

 

 

 


2.3                         Outline Plan for remainder of project

This is a high level plan. This will be successively refined over time as the project proceeds.

A) Work activities

 

  1. Define Format for HL7 Service Specification                         (Ownership – “Infrastructure Sub-group” – led by Ken Rubin  - V1.0 by 3/11)
    1. Define general requirements / characteristics / constraints for the HL7 specifications

(e.g. Rigorous, Testable, Implementable, Concise, MDA Apporach - Platform independent then Platform Specific,

Edge conditions / architecture boundary – platform independent (HL7), Conformance measurement.

·         Define principles/characteristics / Define constraints

·         Define detailed requirements

·         Review/agree requirements

·         Publish Requirements

    1. Define the specification template / pattern (including concept for the information carrier (e.g., archetype/ template / pattern /CMET/…}  {information viewpoint will be part of the work product within HL7, e.g., the relationship to constructs of the RIM in whatever manifestation.  Clarify that this is the information viewpoint engineering/this should be driven by (or in the context of) use case engineering}  )

·         Identify existing candidate templates

·         Select/define / refine format

·         Review/agree format

·         Publish format

 

  1. Produce pilot specifications                                                                                        Ownership and timing tbd

{this will need to address the “touchpoint” between HL7 and OMG so that the specification is usable for the OMG RFP process.  The piloting itself will occur within the OMG technology adoption process}

·         Define service specific requirements

·         Research other existing / related specifications

·         Define specification

·         Review/agree specification

·         Publish specification

 

 

B) Planning / Project Management Activities

 

  1. Start process of defining next round of specs / priorities  (post 2005)                                    Ownership and dates tbd

 

  1. Create/Maintain overall project plan                                                                          Ongoing – Co-chairs

 

  1. OMG Liaison                                                                                                              Ongoing – Ken Rubin

 

  1. Communications activities                                                                                          Ongoing – Co-chairs

 

GIF image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]