Difference between revisions of "Roadmap Project SubGroup 1"

From HL7 TSC
Jump to navigation Jump to search
(Created page with '==Members== Ed Tripp, Woody Beeler, Gregg Seppala, John Quinn, Charlie McCay ==Near term assigned task== * Were assigned Strategic Initiatives 2 and 4 in [http://gforge.hl7.org/g…')
 
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
__NOTOC__
 
==Members==
 
==Members==
 
Ed Tripp, Woody Beeler, Gregg Seppala, John Quinn, Charlie McCay
 
Ed Tripp, Woody Beeler, Gregg Seppala, John Quinn, Charlie McCay
 +
 +
'''Mini Mail List:''' Edward Tripp <edward.tripp@estripp.com>, Charlie McCay <charlie@ramseysystems.co.uk>, Gregg Seppala <gregg.seppala@gmail.com>, Woody Beeler <woody@beelers.com>, John Quinn <john.f.quinn@accenture.com>, "Karen Van Hentenryck (HL7)" <karenvan@hl7.org>
 +
 
==Near term assigned task==
 
==Near term assigned task==
 
* Were assigned Strategic Initiatives 2 and 4 in [http://gforge.hl7.org/gf/download/docmanfileversion/5437/6857/SMARTobjectives.doc TSC Smart Objectives for Strategic Initiatives] ('''''Caution:''''' The format of this document is "fragile" and Word will restructure it if you attempt to change the bullet lists.)
 
* Were assigned Strategic Initiatives 2 and 4 in [http://gforge.hl7.org/gf/download/docmanfileversion/5437/6857/SMARTobjectives.doc TSC Smart Objectives for Strategic Initiatives] ('''''Caution:''''' The format of this document is "fragile" and Word will restructure it if you attempt to change the bullet lists.)
Line 16: Line 20:
 
#:
 
#:
 
#Requirements and traceability -  
 
#Requirements and traceability -  
−
#*How to understand the customer needs and document them
+
#* Establish a template and an underlying methodology that enables tracing requirements to/from a "product" by peer review by January 2011 WGM
−
#*How to trace the requirements to the end result (and back)
+
#**Analysis of the relationships between requirements and solutions
 +
#**Define information content to match that analysis
 +
#**Establish process for collecting and publishing the data
 
#:
 
#:
 
#Templates -  
 
#Templates -  
Line 28: Line 34:
 
Initial topic list for SMART objectives:
 
Initial topic list for SMART objectives:
 
#Identify and "manage" inconsistency within a product "family" and between families (CDA, messages, services)
 
#Identify and "manage" inconsistency within a product "family" and between families (CDA, messages, services)
 +
#*Convene meetings of SOA, SD and Domain work groups to identify potential information overlaps
 +
#**Identify information overlaps in current products
 +
#***Extract formal information models (including vocabulary bindings) for overlapping content
 +
#***Compare information models for inconsistencies
 +
#**Identify potential information overlaps in future products
 +
#***Review plans for requirements
 +
#***Document information overlaps
 +
#*Document instances where information models for current products conflict and define projects to resolve
 +
#**Decide which product must change to resolve conflict based on normative status and market penetration
 +
#**Responsible work group to create project plan and schedule work
 
#:
 
#:
 
#Set Architecture to use "common" models for all three families
 
#Set Architecture to use "common" models for all three families

Latest revision as of 18:16, 1 April 2010

Members

Ed Tripp, Woody Beeler, Gregg Seppala, John Quinn, Charlie McCay

Mini Mail List: Edward Tripp <edward.tripp@estripp.com>, Charlie McCay <charlie@ramseysystems.co.uk>, Gregg Seppala <gregg.seppala@gmail.com>, Woody Beeler <woody@beelers.com>, John Quinn <john.f.quinn@accenture.com>, "Karen Van Hentenryck (HL7)" <karenvan@hl7.org>

Near term assigned task

  • Were assigned Strategic Initiatives 2 and 4 in TSC Smart Objectives for Strategic Initiatives (Caution: The format of this document is "fragile" and Word will restructure it if you attempt to change the bullet lists.)
  • Meet in between Roadmap Committee meetings; meet twice before April.
  • Come up with 3-4 SMART objective per Strategic Initiative
    • SMART is: specific, measurable, attainable, realistic, trackable

SI 2. Streamline the HL7 standards development process

Description

Optimize HL7 internal processes to more effectively deliver global and realm-specific standards particularly in response to new "customer" requirements.

SMART Objectives

Initial topic list for SMART objectives:

  1. Process and quality improvement
    • Enhance ability to quickly develop low-error "output" products
    • Configuration management in development process
  2. Requirements and traceability -
    • Establish a template and an underlying methodology that enables tracing requirements to/from a "product" by peer review by January 2011 WGM
      • Analysis of the relationships between requirements and solutions
      • Define information content to match that analysis
      • Establish process for collecting and publishing the data
  3. Templates -
    • Finish the definition of templates and position them relative to (in contrast to) full-blown "domain-topic" specification.

SI 4. Define an overarching and internally consistent interoperability framework

Description

Maximize design reuse by ensuring consistency of models across HL7 specifications

SMART Objectives

Initial topic list for SMART objectives:

  1. Identify and "manage" inconsistency within a product "family" and between families (CDA, messages, services)
    • Convene meetings of SOA, SD and Domain work groups to identify potential information overlaps
      • Identify information overlaps in current products
        • Extract formal information models (including vocabulary bindings) for overlapping content
        • Compare information models for inconsistencies
      • Identify potential information overlaps in future products
        • Review plans for requirements
        • Document information overlaps
    • Document instances where information models for current products conflict and define projects to resolve
      • Decide which product must change to resolve conflict based on normative status and market penetration
      • Responsible work group to create project plan and schedule work
  2. Set Architecture to use "common" models for all three families
  3. Establish process for eliminating extant inconsistencies over time.
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=Roadmap_Project_SubGroup_1&oldid=6215"