Roadmap Projects

From HL7 TSC
Revision as of 18:39, 30 December 2008 by Llaakso (talk | contribs) (New page: Return to TSC Main Page <p class=MsoNormal align=center style='text-align:center'><b style='mso-bidi-font-weight: normal'><span style='font-size:14.0pt'>Roadmap Plan, Task List </span...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Return to TSC Main Page

Roadmap Plan, Task List

11-September 2008

TSC Tasks

Completed tasks will be moved to the Completed Task List.  Tasks will NOT be renumbered.

 

ID

Due Date

Milestone

Strategy

Section

Pri-ority

Category

Status

Leader

Work

Group

Deliverables

41

2008 Q4

TSC review and comment on the HL7 Roadmap.  TSC should specifically evaluate due dates and work group.

1.2

1.6.4.1

H

Roadmap

 

CTO

TSC

Feedback on roadmap

1

2009 Q1

Define new balloting procedures based on better interpretation of ANSI requirements.  The procedure should include a plan for managing change to the normative ballot.

1.2

1.3.1

1.6.4.7

M

Balloting

 

CTO

CTeam

TSC

New Balloting Proposal

42

2009 Q1

The TSC shall provide a Project Registry of all the Work Groups’ planned deliveries, spanning the next three years, highlighting any areas of potential conflict or inconsistencies.

1.2

1.6.4.3

H

Roadmap

 

CTO

TSC

Project Registry

47

2009 Q2

Deliver a first balloted reference architecture document to include a services delivery approach as a means of using HL7 Standards in SOA.

1.4

2.6.3.1

 

Technical

 

CTO

TSC

Reference Architecture Document

23

2009 Q2 Assign

2009 Q3 Report

The TSC will establish criteria for prioritizing new projects.

1.1

5.1

1.9.3.3

H

Management

 

CTO

TSC

Criteria for prioritizing new projects

50

2010 Q2

Develop appropriate work products in areas where gaps have been identified, and continue the process as an on-going operational effort

4.1

1.7.3.2

H

Technical

 

CEO

TSC

Plan to deal with gaps

49

2009 Q1

Complete the complete landscape of standards necessary for effective and interoperable HIT.  Identify where HL7 standards fit; identify where other appropriate standards fit.  From this landscape map, identify gaps in required standards; then determine which standards HL7 should pursue.  This landscape map can also be used to identify existing tools and where they fit, and to identify additional tools that might be required.

4.1

1.7.3.1

H

Technical

 

CEO

TSC, commissioned work $$

Report on gap analysis, including opportunities for development of  new standards