Difference between revisions of "Strategic Initiatives TSC Dashboard"

From HL7 TSC
Jump to navigation Jump to search
Line 87: Line 87:
 
*See [http://gforge.hl7.org/gf/download/docmanfileversion/6866/9456/StrategicInitiatives_dashboard_metrics.xls draft metrics]
 
*See [http://gforge.hl7.org/gf/download/docmanfileversion/6866/9456/StrategicInitiatives_dashboard_metrics.xls draft metrics]
 
*Staff Support: Dave Hamill
 
*Staff Support: Dave Hamill
 +
 +
 +
  
 
===Dashboard===
 
===Dashboard===
Line 129: Line 132:
 
'''Cross-Artifact Consistency'''
 
'''Cross-Artifact Consistency'''
 
*V3 Standards - Measure - Green: All new standards have one or more of the following checked; Yellow: 1-2 standards have none of the following checked; Red: 3 or more standards have none of the following checked  
 
*V3 Standards - Measure - Green: All new standards have one or more of the following checked; Yellow: 1-2 standards have none of the following checked; Red: 3 or more standards have none of the following checked  
*:2012Sep: RED (8 standards had none checked)
+
*:2012Sep: RED (4 standards had none checked)
 
*Adopted 2012-09-08, there were 11 eligible publication requests on which this measure could be checked
 
*Adopted 2012-09-08, there were 11 eligible publication requests on which this measure could be checked
** Standard uses CMETs from HL7-managed CMETs in COCT, POCP (Common Product) and other domains - one standard
+
** Standard uses CMETs from HL7-managed CMETs in COCT, POCP (Common Product) and other domains - five standard
**Standard uses harmonized design patterns (as defined through RIM Pattern harmonization process) - no standards
+
**Standard uses harmonized design patterns (as defined through RIM Pattern harmonization process) - four standards
**Standard is consistent with common Domain Models including Clinical Statement, Common Product Model and "TermInfo" - four standards
+
**Standard is consistent with common Domain Models including Clinical Statement, Common Product Model and "TermInfo" - eight standards
  
  

Revision as of 17:30, 18 December 2012

HL7 Strategic Initiatives Dashboard Project

At Project Insight # 799

Project Scope: The scope of this project to implement a dashboard showing the TSC progress on implementing the HL7 Strategic Initiatives that the TSC is responsible for. The HL7 Board of Directors has a process for maintaining the HL7 Strategic Initiatives. The TSC is responsible for implementing a significant number of those initiatives. As part of developing a dashboard, the TSC will need to develop practical criteria for measuring progress in implementing the strategic initiatives. There are two aspects to the project. First is the process of standing up the dashboard itself. This may end up being a discrete project handed off to Electronic Services and HQ. That dashboard would track progress towards all of HL7's strategic initiatives (not just those the TSC is responsible for managing.) The second part of this project will be focused on the Strategic Initiatives for which the TSC is responsible.

In discussion at 2011-09-10_TSC_WGM_Agenda in San Diego, a RASCI Chart showing which criteria under the Strategic Initiatives the TSC would take responsibility for.

From those, the TSC accepted volunteers to draft metrics with which to measure the TSC criteria.


Industry responsiveness and easier implementation

Requirements traceability and cross-artifact consistency

  • Tracker #2059 Austin will create Strategic Dashboard criteria metrics for: Requirements traceability and cross-artifact consistency
    • Requirements traceability - Tied to HL7 roll out of SAIF ECCF. measure is the number of milestones completed
      • Informative SAIF Canonical document published
      • DSTU SAIF Canonical document published
      • Normative SAIF Canonical document published
      • Peer Reviewed HL7 SAIF IG including ECCF chapter and draft SAIF Artifact Definitions
      • DSTU HL7 SAIF IG published
      • Normative HL7 SAIF IG published
      • SAIF Architecture Program experimental phase of HL7 SAIF ECCF implementation completed
      • SAIF AP trial use phase of HL7 SAIF ECCF implementation completed
      • HL7 SAIF ECCF rolled to all work groups working on applicable standards (V3 primarily)
    • Cross-artifact consistency
      • (per TSC decision 2012-03-26)
        • Standards that include V3 RIM-Derived information models.
        • Percent of Work groups in FTSD, SSDSD and DESD participating in RIM/Vocab/Pattern Harmonization meetings, calculated as a 3 trimester moving average - Green of 75% or better participation. Yellow 50-74%. 0-49 is red.
      Other metrics considered
      • Survey of newly published standards via the publication request form
        • V3 Standards - Measure - Green: All new standards have one or more of the following checked; Yellow: 1-2 standards have none of the following checked; Red: 3 or more standards have none of the following checked
          • Standard uses CMETs from HL7-managed CMETs in COCT, POCP (Common Product) and other domains
          • Standard uses harmonized design patterns (as defined through RIM Pattern harmonization process)
          • Standard is consistent with common Domain Models including Clinical Statement, Common Product Model and "TermInfo"
    • Austin notes that these are not necessarily automated metrics for the criteria.
  • Staff Support: Lynn Laakso

Product Quality

  • Tracker #2058 Woody will create Strategic Dashboard criteria metrics for: Product Development Effectiveness
    • Measure is the average number of ballot cycles necessary to pass a normative standard. Calculated as a cycle average based on publication requests. Includes:
      (Note: This metric uses "ballots" rather than ballot cycles because more complex ballots frequently require two-cycles to complete reconciliation and prepare for a subsequent ballot.)
      1. Projects at risk of becoming stale 2 cycles after last ballot
      2. Two cycles since last ballot but not having posted a reconciliation or request for publication for normative edition
      3. items going into third or higher round of balloting for a normative specification;
        (Note: This flags concern while the process is ongoing; it is not necessarily a measure of quality once the document it has finished balloting).
      • Green: 1-2 ballots
      • Yellow: 3-4 ballots
      • Red: 5+ ballots
      • 2012Sep Release includes trend on the average of cycles to reach normative status and ANSI publication. (T1 = Jan-May, T2 = May-Sep, T3 = Sep-Jan) -
      • 2012T3 2012Sep-2013Jan average -> #DIV/0! (no ANSI publications this period so far)
      • 2012T2 May-Sep average -> 1.33 = Green light
      • 2012T2 Jan-May average -> 2.71 = Yellow light?
      • Past 1 year average -> 1.35 = Green light
  • Publishing will also create a "Product Ballot Quality" metric (at the level of the product, but generated for each Ballot) that creates a green/yellow/red result by amalgamating specific elements such as:
    • Content quality, including:
      1. ability to create schemas that validate (metric of model correctness) [where failure could have been prevented by the product developer],
      2. the presence of class- and attribute-level descriptions in a static model (metric of robust documentation)
  • Staff Support: Lynn Laakso

WGM Effectiveness

  • Tracker #2057 Patrick will create Strategic Dashboard criteria metrics for: WGM Effectiveness
    • Draft Criteria
      • % of WG’s attending
      • % of WG’s who get agenda posted in appropriate timeframe
      • % of WG’s who achieve quorum at WGM
      • Number of US-based attendees
      • Number of International attendees
      • Number of non-member attendees
      • Profit or Loss
      • Nbr of FTAs
      • Nbr of Tutorials Offered
      • Nbr Students Attending Tutorials
      • Nbr of Quarters that WG's had agenda for; but did not make quorum
    • For US-Based Locations: one set of %’s for success
    • For International Locations: a different set of %’s for success
    • Metrics may also be based on each WG's prior numbers
  • See draft metrics
  • Staff Support: Dave Hamill



Dashboard

Industry responsiveness and easier implementation Requirements Traceability
and cross-artifact consistency
Product Quality WGM Effectiveness

SI Project assessment

  • TBD

Requirements traceability

Product Development Effectiveness

  • 2012T3 2012Sep-2013Jan average -> #DIV/0! (no ANSI publications this period)
  • 2012T2 May-Sep average -> 1.33 = Green light
  • 2012T2 Jan-May average -> 2.71 = Yellow light?
  • Past 1 year average -> 1.35 = Green light (no change from T2 to T3)

Key:

  • Green: 1-2 ballots
  • Yellow: 3-4 ballots
  • Red: 5+ ballots


WGM Effectiveness- U.S. meetings

  • TBD

TBD

Cross-Artifact Consistency

  • V3 Standards - Measure - Green: All new standards have one or more of the following checked; Yellow: 1-2 standards have none of the following checked; Red: 3 or more standards have none of the following checked
    2012Sep: RED (4 standards had none checked)
  • Adopted 2012-09-08, there were 11 eligible publication requests on which this measure could be checked
    • Standard uses CMETs from HL7-managed CMETs in COCT, POCP (Common Product) and other domains - five standard
    • Standard uses harmonized design patterns (as defined through RIM Pattern harmonization process) - four standards
    • Standard is consistent with common Domain Models including Clinical Statement, Common Product Model and "TermInfo" - eight standards


Product Ballot Quality

WGM Effectiveness - International meetings

  • TBD