Difference between revisions of "Roadmap Projects"

From HL7 TSC
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
 
==Roadmap Plan, Task List 20090202==
 
==Roadmap Plan, Task List 20090202==
 
From [http://www.hl7.org/documentcenter/public/strategic/roadmap/Roadmap_Projects_High_Priority_By_Tgt_Date_20090202.xls Roadmap_Projects_High_Priority_Sorted_By_Tgt_Date_20090202.xls]
 
From [http://www.hl7.org/documentcenter/public/strategic/roadmap/Roadmap_Projects_High_Priority_By_Tgt_Date_20090202.xls Roadmap_Projects_High_Priority_Sorted_By_Tgt_Date_20090202.xls]
 +
 +
http://www.hl7.org/documentcenter/public/strategic/roadmap/Roadmap_Projects_High_Priority_By_Priority_20090607.xls.
 +
 +
  
 
{|border="1"
 
{|border="1"
Line 18: Line 22:
 
!Objectives/ Deliverables
 
!Objectives/ Deliverables
 
!Project Status Comment
 
!Project Status Comment
−
|-
+
 
−
| 395
 
−
| 2009 September WGM
 
−
|Criteria for prioritizing new projects (Roadmap Pjt #23)
 
−
|The TSC will establish criteria for prioritizing new projects.
 
−
|High-04
 
−
|Management
 
−
|Technical (Roadmap Subgroup)
 
−
|Grouping: 395, 407, 408
 
−
|TSC, (Roadmap Leader: CTO)
 
−
|Criteria for prioritizing new projects
 
−
|TSC Tracker # 734
 
 
|-
 
|-
 
|442
 
|442
 
|2009 September WGM
 
|2009 September WGM
 
|Deliver a first balloted reference architecture document (Roadmap Project #47)
 
|Deliver a first balloted reference architecture document (Roadmap Project #47)
−
|Deliver a first balloted reference architecture document to include a services delivery approach as a means of using HL7 Standards in SOA. (Re: Pjt 444 - Healthcare SOA Reference Architecture (H-SOA-RA) V 2.0 and EHR System Design Reference Model (EHR-SD RM))
+
|Deliver a first balloted reference architecture document to include a services delivery approach as a means of using HL7 Standards in SOA. (Re: Pjt 469 - Enterprise Architecture Implementation Project (EA IP) Phase 1)
 
|High-09
 
|High-09
 
|Technical
 
|Technical
 
|Technical (Roadmap Subgroup)
 
|Technical (Roadmap Subgroup)
 
|"Grouping: 441 442"
 
|"Grouping: 441 442"
−
|TSC (Roadmap Leader: CTO)
+
|TSC, Marc Koehn, Lynn Laakso (Roadmap Leader: CTO)
 
|Reference Architecture Document
 
|Reference Architecture Document
 +
|Feb 2009:  Marc Koehn has been assigned as project leader for this work.  Holding their 1st advisory group call on Tuesday 2/24/09 and will be joining the ArB call on Thursday to see if we can begin to identify some dates and also discuss the engagement process for candidate Alpha Projects
 
|-
 
|-
 
|408
 
|408
Line 52: Line 46:
 
|TSC, (Roadmap Leader: CTO)
 
|TSC, (Roadmap Leader: CTO)
 
|Feedback on roadmap
 
|Feedback on roadmap
−
|"12/3/08 JQ: Changed target date from Q4 2008 to May2009 WGM."
+
|Apr 2009: On the TSC Agenda for the May 2009 WGM in Kyoto, Japan.
 
|}
 
|}
  
Line 70: Line 64:
 
!Objectives/ Deliverables
 
!Objectives/ Deliverables
 
!Project Status Comment
 
!Project Status Comment
 +
|-
 +
| 395
 +
| 2009 September WGM
 +
|Criteria for prioritizing new projects (Roadmap Pjt #23)
 +
|The TSC will establish criteria for prioritizing new projects.
 +
|was High-04, no longer high priority
 +
|Management
 +
|Technical (Roadmap Subgroup)
 +
|Grouping: 395, 407, 408
 +
|TSC, (Roadmap Leader: CTO)
 +
|Criteria for prioritizing new projects
 +
|TSC Tracker # 734
 
|-
 
|-
 
|407
 
|407
Line 104: Line 110:
 
!Project Name
 
!Project Name
 
!Description
 
!Description
−
!Pri (none)
 
 
!Roadmap category
 
!Roadmap category
 
!Implementers
 
!Implementers
−
!Group
 
 
!Project Facilitator
 
!Project Facilitator
 
!Objectives/ Deliverables
 
!Objectives/ Deliverables
 
!Project Status Comment
 
!Project Status Comment
 +
|-
 +
|377
 +
| 2009 May WGM
 +
| Define new balloting procedures (Roadmap Pjt #01)
 +
|Define new balloting procedures based on better interpretation of ANSI requirements. The procedure should include a plan for managing change to the normative ballot.
 +
| Roadmap
 +
| Strategic/Operations (Roadmap Subgroup)
 +
|CTeam, TSC, (Roadmap Leader: CTO)
 +
|New Balloting Proposal
 +
| Feb 2009 : Karen indicated the following has been completed:
 +
*Eliminated Committee Level Ballots
 +
*Will be balloting continuous maintenance of the RIM<br/>
 +
Lynn Laakso: Woody and Austin to draft a proposal for ballot-level coordination for ISO/JIC work, attached to TSC Tracker #332.
 
|-
 
|-
 
|409
 
|409
Line 116: Line 133:
 
| SWOT and 3 Year Plans (Roadmap Pjt #42)
 
| SWOT and 3 Year Plans (Roadmap Pjt #42)
 
| "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."
 
| "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."
−
|
 
 
| Roadmap
 
| Roadmap
 
| Technical (Roadmap Subgroup)
 
| Technical (Roadmap Subgroup)
−
|
 
 
| "TSC,  (Roadmap Leader: CTO)"
 
| "TSC,  (Roadmap Leader: CTO)"
 
| Project Registry
 
| Project Registry
−
| 12/3/08 JQ: Work is being done by the TSC analyst. Get % complete from Lynn.  LL: As of JanWGM, 16 of 42 WG had completed their plans
+
| Feb 2009:  On track
 
|-
 
|-
 
|414
 
|414
Line 128: Line 143:
 
| Complete the landscape of standards necessary for effective and interoperable HIT (Roadmap Pjt #49)
 
| Complete the landscape of standards necessary for effective and interoperable HIT (Roadmap Pjt #49)
 
| "Complete the 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."
 
| "Complete the 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."
−
|
 
 
| Technical
 
| Technical
 
| Technical (Roadmap Subgroup)
 
| Technical (Roadmap Subgroup)
−
|
 
 
| "TSC, (Roadmap Leader: CTO)"
 
| "TSC, (Roadmap Leader: CTO)"
 
| "Report on gap analysis, including opportunities for development of  new standards"
 
| "Report on gap analysis, including opportunities for development of  new standards"
−
| 12/3/08 JQ: Kind of requesting to define something that's not definable.  Needs to get on a TSC agenda for discussion.  Forward it to Lynn to get it on the WGM TSC agenda in Orlando (15 minute discussion)
+
|Feb 2009:  Lynn Laakso has been assigned to facilitate TSC Roadmap projects (finding leaders for them as the first step).  For this particular project, a leader has not yet been determined.
 
|-
 
|-
 
|415
 
|415
Line 140: Line 153:
 
| Develop work products in areas where gaps have been identified (Roadmap Pjt #50)
 
| Develop work products in areas where gaps have been identified (Roadmap Pjt #50)
 
| "Develop appropriate work products in areas where gaps have been identified,  and continue the process as an on-going operational effort"
 
| "Develop appropriate work products in areas where gaps have been identified,  and continue the process as an on-going operational effort"
−
|
 
 
| Technical
 
| Technical
 
| Technical (Roadmap Subgroup)
 
| Technical (Roadmap Subgroup)
−
|
 
 
| "TSC, (Roadmap Leader: CTO)"
 
| "TSC, (Roadmap Leader: CTO)"
 
| Plan to deal with gaps
 
| Plan to deal with gaps
 
| "Roadmap Strategy: 4.1
 
| "Roadmap Strategy: 4.1
 
|}
 
|}

Latest revision as of 14:45, 1 July 2009

Return to TSC Main Page

Roadmap Plan, Task List 20090202

From Roadmap_Projects_High_Priority_Sorted_By_Tgt_Date_20090202.xls

http://www.hl7.org/documentcenter/public/strategic/roadmap/Roadmap_Projects_High_Priority_By_Priority_20090607.xls.


TSC Tasks
ID Target Date Project Name Description Roadmap priority (high: 1-27) Roadmap category Implementers Group Project Facilitator Objectives/ Deliverables Project Status Comment
442 2009 September WGM Deliver a first balloted reference architecture document (Roadmap Project #47) Deliver a first balloted reference architecture document to include a services delivery approach as a means of using HL7 Standards in SOA. (Re: Pjt 469 - Enterprise Architecture Implementation Project (EA IP) Phase 1) High-09 Technical Technical (Roadmap Subgroup) "Grouping: 441 442" TSC, Marc Koehn, Lynn Laakso (Roadmap Leader: CTO) Reference Architecture Document Feb 2009:  Marc Koehn has been assigned as project leader for this work.  Holding their 1st advisory group call on Tuesday 2/24/09 and will be joining the ArB call on Thursday to see if we can begin to identify some dates and also discuss the engagement process for candidate Alpha Projects
408 2009 May WGM TSC review/comment on the HL7 Roadmap (Roadmap Project #41) TSC review and comment on the HL7 Roadmap. TSC should specifically evaluate due dates and work group. High-15 Roadmap Technical (Roadmap Subgroup) "Grouping: 395, 407, 408" TSC, (Roadmap Leader: CTO) Feedback on roadmap Apr 2009: On the TSC Agenda for the May 2009 WGM in Kyoto, Japan.


Associated Roadmap grouping items, from Task List 20090202

ID Target Date Project Name Description Roadmap priority (high: 1-27) Roadmap category Implementers Group Project Facilitator Objectives/ Deliverables Project Status Comment
395 2009 September WGM Criteria for prioritizing new projects (Roadmap Pjt #23) The TSC will establish criteria for prioritizing new projects. was High-04, no longer high priority Management Technical (Roadmap Subgroup) Grouping: 395, 407, 408 TSC, (Roadmap Leader: CTO) Criteria for prioritizing new projects TSC Tracker # 734
407 2009 January WGM Roadmap Process (Roadmap Pjt #38) Develop and implement a process to track progress and manage Roadmap Task list High-02 Operational Strategic/Operations (Roadmap Subgroup) "Grouping: 395, 407, 408" Staff, (Roadmap Leader: CEO) Roadmap tracking system 2009: Karen/Dave Hamill: Mark, Dave and Karen will revisit the process they documented prior to the RTF meetings and address what needs modifications.
441 2009 January WGM Initiate the adoption of an approved HL7 Reference Architecture (Roadmap Pjt #44) Position the ArB to work with all relevant committees of HL7 to proactively champion the adoption of an approved HL7 Reference Architecture and establish a process for its continuous review and update. (Re: Pjt 365 - Enterprise Architecture Specification ) High-16 Technical Technical (Roadmap Subgroup) Grouping: 441, 442 ArB, (Roadmap Leader: CTO) Plan and process document. 12/3/08 JQ: Target to initate this project by the end of the Orlando WGM.


Additional TSC Roadmap Tasks (non high-priority)

ID Target Date Project Name Description Roadmap category Implementers Project Facilitator Objectives/ Deliverables Project Status Comment
377 2009 May WGM Define new balloting procedures (Roadmap Pjt #01) Define new balloting procedures based on better interpretation of ANSI requirements. The procedure should include a plan for managing change to the normative ballot. Roadmap Strategic/Operations (Roadmap Subgroup) CTeam, TSC, (Roadmap Leader: CTO) New Balloting Proposal Feb 2009 : Karen indicated the following has been completed:
  • Eliminated Committee Level Ballots
  • Will be balloting continuous maintenance of the RIM

Lynn Laakso: Woody and Austin to draft a proposal for ballot-level coordination for ISO/JIC work, attached to TSC Tracker #332.

409 2009 May WGM SWOT and 3 Year Plans (Roadmap Pjt #42) "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." Roadmap Technical (Roadmap Subgroup) "TSC, (Roadmap Leader: CTO)" Project Registry Feb 2009:  On track
414 2009 May WGM Complete the landscape of standards necessary for effective and interoperable HIT (Roadmap Pjt #49) "Complete the 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." Technical Technical (Roadmap Subgroup) "TSC, (Roadmap Leader: CTO)" "Report on gap analysis, including opportunities for development of new standards" Feb 2009:  Lynn Laakso has been assigned to facilitate TSC Roadmap projects (finding leaders for them as the first step).  For this particular project, a leader has not yet been determined.
415 2010 September WGM Develop work products in areas where gaps have been identified (Roadmap Pjt #50) "Develop appropriate work products in areas where gaps have been identified, and continue the process as an on-going operational effort" Technical Technical (Roadmap Subgroup) "TSC, (Roadmap Leader: CTO)" Plan to deal with gaps "Roadmap Strategy: 4.1
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=Roadmap_Projects&oldid=5093"