Difference between revisions of "2013-08-14 TRAC"

From HL7 TSC
Jump to navigation Jump to search
Line 1: Line 1:
−
==TSC Risk Assessment Committee (TRAC) Agenda/Minutes ==
+
TSC representatives and ArB to jointly develop content for the BAM for the Product Line Architecture Program
−
back to [[TRAC|TRAC page]]
 
−
 
 
−
===Meeting Info/Attendees===
 
−
 
 
−
  [[Category:2013 TSC Minutes]]
 
−
 
 
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
−
| width="0%" colspan="2" align="left" style="background:#f0f0f0;"|'''TRAC Meeting Minutes''' <br/>
+
<!---=======================================================================
−
'''Location: call 770-657-9270 using code 985371#'''<br/> GoToMeeting ID: [https://www.gotomeeting.com/join/660939197 660-939-197 ]
+
|                                                                          |
−
| width="0%" colspan="1" align="left" style="background:#f0f0f0;"|'''Date: 2013-08-07 '''<br/> '''Time: 10:00 AM U.S. Eastern'''
+
|  MM    MM  TTTTTT  GGGGG        IIIIII  NN    NN  FFFFFF  OOOOO      |
 +
|  MMM  MMM    TT    GG              II    NNN  NN  FF      OO  OO    |
 +
|  MM MMM MM    TT    GG  GGG        II    NN NN NN  FFFF    OO  OO    |
 +
|  MM  M  MM    TT    GG  GG        II    NN  NNN  FF      OO  OO    |
 +
|   MM    MM    TT    GGGGG        IIIIII  NN    NN  FF      OOOOO      |
 +
|                                                                          |
 +
========================================================================--->
 +
| colspan="2" align="left" style="background:#f0f0f0;"|'''HL7 BAM Modeling Call Minutes''' <br/>
 +
'''Location: '''call 770-657-9270 using code 985371#<br/> [https://global.gotomeeting.com/join/111567781 GTM 111-567-781]
 +
| colspan="2" align="left" style="background:#f0f0f0;"|'''Date: 2013-08-14'''<br/> '''Time: 2 pm Eastern Time'''
 +
|-
 +
| colspan="1" align="right"|'''Facilitator'''
 +
| colspan="1" align="left"|Austin Kreisler
 +
| colspan="1" align="right"|'''Note taker(s)'''
 +
| colspan="1" align="left"| Lynn
 +
|-
 +
| border="4" cellpadding="1" colspan="4" style="background:#f0f0f0;"|
 
|-
 
|-
−
| width="0%" colspan="2" align="right"|'''Facilitator''': Pat Van Dyke
 
−
| width="0%" colspan="1" align="right"|'''Note taker(s)''': Lynn
 
 
|}
 
|}
 +
{|border="1" cellpadding="2" cellspacing="0"
 +
| border="1" cellpadding="2" colspan="1" align="left"|'''Attendee'''
 +
| '''Name'''
  
−
{|border="1" cellpadding="2" cellspacing="0"
 
−
|colspan="4" align="center" style="background:#f0f0f0;"| Quorum
 
−
|colspan="2" align="center" style="background:#f0f0f0;"| '''n/a'''
 
  
 +
<!---==============================================================================
 +
|                                                                                |
 +
|    AAAA  TTTTTT  TTTTTT  EEEEEE  NN    NN  DDDDD    EEEEEE  EEEEEE  SSSSS    |
 +
|  AA  AA    TT      TT    EE      NNN  NN  DD  DD  EE      EE      SS        |
 +
|  AAAAAA    TT      TT    EEEE    NN NN NN  DD  DD  EEEE    EEEE    SSSS      |
 +
|  AA  AA    TT      TT    EE      NN  NNN  DD  DD  EE      EE          SS    |
 +
|  AA  AA    TT      TT    EEEEEE  NN    NN  DDDDD    EEEEEE  EEEEEE  SSSSS      |
 +
|                                                                                |
 +
===============================================================================--->
 
|-
 
|-
−
|colspan="2"|Chair/CTO ||colspan="2"|Members ||colspan="2"|Members
+
|x || Calvin Beebe
 
|-
 
|-
−
|x ||Pat Van Dyke||x ||Rick Haddorff||  ||Melva Peters
+
| || Woody Beeler
 
|-
 
|-
−
| ||John Quinn ||x ||Austin Kreisler|| || Ken McCaslin
+
| || Jane Curry
 +
|-
 +
| ||Bo Dagnall
 +
|-
 +
| || Jean Duteau,
 +
|-
 +
| || Tony Julian
 +
|-
 +
|x || Austin Kreisler,
 +
|-
 +
|x || Lynn Laakso
 +
|-
 +
| || Cecil Lynch
 +
|-
 +
|regrets || Ron Parker
 +
|-
 +
| || Brian Pech
 +
|-
 +
| || Melva Peters
 +
|-
 +
|colspan="4" style="background:#f0f0f0;"|
 +
|-
 +
|colspan="4" style="font-style:italic; color:green;" |''no quorum definition''
  
−
|-
 
−
|colspan="3" style="background:#f0f0f0;"|
 
 
|}
 
|}
 +
<!---=======================================================
 +
|                                                          |
 +
|    AAAA    GGGGG  EEEEEE  NN    NN  DDDDD    AAAA      |
 +
|  AA  AA  GG      EE      NNN  NN  DD  DD  AA  AA    |
 +
|  AAAAAA  GG  GGG  EEEE    NN NN NN  DD  DD  AAAAAA    |
 +
|  AA  AA  GG  GG  EE      NN  NNN  DD  DD  AA  AA    |
 +
|  AA  AA  GGGGG  EEEEEE  NN    NN  DDDDD    AA  AA    |
 +
|                                                          |
 +
========================================================--->
 +
===Agenda===
 +
*Agenda
 +
**PSS development for CDA R2 IG Product Family.
 +
**Continue discussion on model diagram
  
−
===Agenda===
+
*Continued discussion on the [http://gforge.hl7.org/gf/download/docmanfileversion/7421/10670/TSC_Org_Chart_20130712.vsd model diagram]
−
*Agenda review and approval - Pat Van Dyke
 
−
*Review minutes of [[2013-08-07 TRAC]]
 
−
*Action Items:
 
−
**Pat will invite Ken to join with background documentation package
 
−
**Pat will work on developing a straw man for separate criteria for informative ballot reconciliation in 6 months, for example.
 
−
*Firm up what we want to have as deliverables at the September, 2013 WGM in Cambridge
 
−
<!--    Complete risk assessment round 1 (other things have been added on) with mitigation strategies for likelihood critical
 
−
    Governance points around mitigation strategies
 
−
    Show a process of how things are identified and brought into TRAC and brought to resolution, e.g. CDS issues.
 
−
    Process needs to show the continuous feedback loop.
 
−
    Discuss further next week. Pat will work up a skeleton on what's being done on critical/critical.
 
−
    Rick asks if we'd be doing a presentation to TSC on the governance points. Need to estimate time for agenda planning, perhaps 30 minutes. -->
 
−
*Document risks/ mitigation strategies for the recent CDS projects' issues
 
−
* Governance Point development see
 
−
*[http://gforge.hl7.org/gf/download/docmanfileversion/7448/10738/%43%6f%6e%73%6f%6c%69%64%61%74%65%64%52%69%73%6b%41%73%73%65%73%73%6d%65%6e%74%32%30%31%33%30%37%31%30%2e%78%6c%73%78 updated spreadsheet]
 
−
** referred item on precept for a statement on whether an R2 project supersedes prior releases.
 
−
*Continue reviewing the Risks that Melva identified from the survey
 
  
  
 
===Minutes===
 
===Minutes===
 +
Convened 2:06 PM
 +
*Discuss what we need for WGM
 +
**Should BAM meet in Cambridge? SAIF AP on Weds Q4 and BAM/PLA on Weds Q3. Agenda for meeting needs ArB participation so wait until Ron comes back.
 +
*Are product families for multiple products or a single product. CDS issues involve CDA< 2.x, HQMF etc. How does that fit into BAM concept.
 +
**HL7 project management group doesn't manage others' projects except some key strategic ones. They are a tiny group and do more to define best practices for project management.
 +
*PSS on CDA R2 IG Product Family was discussed on CDA R3 call and might be the better place for identifying templating on CDA (CDA R3 IG Product Family). They will probably take it up at the WGM. FHIR does templating but they call it profiling. A profile is just another resource.
 +
*diagram reviewed. Product family on mechanism for production, product line on coherence of marketing-related requirements. US Realm product line is one example but a poor one. Other types of product lines more singularly domain focused. Austin notes that of 200+ active projects, there are 40+ US Realm and that will grow. Other realm activity went on in their realm and was brought back to the HL7 international group. US activity has already resulting in two "point" releases to v2, (V2.5.1 and v2.7.1). US Realm is consuming ¼ of our bandwidth.
 +
*Argument against it as a product line as it doesn't solve a singular use case. However it is a single consumer perspective. Sub-product lines within it are focused on individual use cases. This is an instance where the product line is recursive.
 +
*For FHIR, FMG has a goal to get the standard out the door. For CDA IG's does it make sense to have its management in a product management group? The management group is to ensure the projects meet their milestones.
 +
*It's not a steering division, but perhaps it's a US Realm Program, using program management to shepherd a set of projects in a coordinated fashion and meet schedules. Extramural coordination is required and should be flagged in the PSS. Calvin suggests that coordination groups identify a contact person and be sent a packet on what the procedure is for how such a project moves through the organization.
 +
*Conformance to procedure is a challenge even for some HL7 cochairs, so enlisting the help of extramural participants would be iffy.
 +
*Dashboards for project status discussed, along with project facilitator commitment agreements to follow the process.
  
−
'''Minutes/Conclusions Reached:'''<br/> convened 10:05 AM
+
Austin and Calvin not available next week; cancel the call.  
−
*Agenda review and approval - Pat Van Dyke - Austin has some new items to discuss.
+
Adjourned 2:49 PM
−
*Firm up what we want to have as deliverables at the September, 2013 WGM in Cambridge
 
−
**Pat was going to develop a skeleton on what is being done for critical/critical; this has not been done
 
−
*Austin states that new risks should be evaluated as the Board rolls out new membership benefits. One example is the 90-day access window for member access to new standards, before accessibility by the public. Publication processes are fraught with changes to reconcile comments and the final production won't necessarily look like the ballot version. Some throw the material on a wiki, email it to a list, and so on for review prior to publication and this must be curtailed. FHIR is being implemented from the development material but this has a specific exception to the HL7 IP policy. How do you identify the point at which the material is "locked down" for distribution beyond members.
 
−
**New risks discussed, methods for access to ballot material discussed. Ballot site is secured for members or ballot pool subscribers only. SVN access can be controlled in GForge. Use of GForge is not widely adopted and even a cheat sheet, or a set of instructions may not work. Web site documents can be marked as members-only but that is not the default and can be overridden by WG cochairs. They are already using wikis and external cloud drives. One mitigation for cochairs that won't discontinue these practices is the TSC could unseat them as cochairs or revoke their membership. Easiest tack is to change default on web site to be members-only. Override might require a note of why the document should be publicly available and notice to cochairs/staff. Could also use a dropbox sponsored by HL7 to facilitate the ease with which others are using that site. Pat will check with Karen on options for locking down access to pre-publication materials without violating ANSI openness policies.
 
−
**Additional risks of the new member benefits discussed. ACTION ITEM: Pat will discuss with Board a companion committee to perform risk assessment on proposed member benefits and provide risk assessment to Board along with membership benefit proposal
 
−
*[http://gforge.hl7.org/gf/download/docmanfileversion/7476/10812/%43%6f%6e%73%6f%6c%69%64%61%74%65%64%52%69%73%6b%41%73%73%65%73%73%6d%65%6e%74%32%30%31%33%30%38%31%34%2e%78%6c%73%78 updated spreadsheet]
 
  
−
Adjourned 11:05 AM
 
  
−
===Next Steps===
+
===Meeting Outcomes===
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
|-
 
|-
−
|colspan="4" |'''Actions''' ''(Include Owner, Action Item, and due date)''<br/>
+
<!---==============================================================
−
**Pat will invite Ken to join with background documentation package
+
|                                                                |
−
**Pat will work on developing a straw man for separate criteria for informative ballot reconciliation in 6 months, for example.
+
|    AAAA    CCCCC  TTTTTT  IIIIII  OOOOO  NN    NN  SSSSS    |
−
* Pat will discuss with Board a companion committee to perform risk assessment on proposed member benefits and provide risk assessment to Board along with membership benefit proposal
+
|  AA  AA  CC        TT      II    OO  OO  NNN  NN  SS        |
−
*Pat will check with Karen on options for locking down access to pre-publication materials without violating ANSI openness policies.
+
|  AAAAAA  CC        TT      II    OO  OO  NN NN NN  SSSS      |
 +
|   AA  AA  CC        TT      II    OO  OO  NN  NNN      SS    |
 +
|  AA  AA  CCCCC    TT    IIIIII  OOOOO  NN    NN  SSSSS      |
 +
|                                                                |
 +
===============================================================--->
 +
 
 +
| width="100%" align="left" style="background:#f0f0f0;"|'''Actions''' ''
 +
*
 +
 
 +
|-
 +
<!---=======================================================================
 +
|                                                                          |
 +
|  NN    NN  EEEEEE  XX  XX  TTTTTT      MM    MM  TTTTTT  GGGGG      |
 +
|  NNN  NN  EE      XX XX    TT        MMM  MMM    TT    GG          |
 +
|  NN NN NN  EEEE      XXX      TT        MM MMM MM    TT    GG  GGG    |
 +
|  NN  NNN  EE      XX XX    TT        MM  M  MM    TT    GG  GG    |
 +
|  NN    NN  EEEEEE  XX  XX    TT        MM    MM    TT    GGGGG      |
 +
|                                                                          |
 +
========================================================================--->
 +
 
 +
|width="100%" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 +
*[[20130828 BAM Modeling]]
  
−
|-
 
−
|colspan="4" |'''Next Meeting/Preliminary Agenda Items'''<br/>
 
−
*[[2013-08-21 TRAC]].
 
−
*Austin offers regrets next week and will be on vacation the first two weeks of September.
 
−
<!--    Complete risk assessment round 1 (other things have been added on) with mitigation strategies for likelihood critical
 
−
    Governance points around mitigation strategies
 
−
    Show a process of how things are identified and brought into TRAC and brought to resolution, e.g. CDS issues.
 
−
    Process needs to show the continuous feedback loop.
 
−
    Discuss further next week. Pat will work up a skeleton on what's being done on critical/critical.
 
−
    Rick asks if we'd be doing a presentation to TSC on the governance points. Need to estimate time for agenda planning, perhaps 30 minutes. -->
 
−
*Document risks/ mitigation strategies for the recent CDS projects' issues
 
−
* Governance Point development
 
−
** referred item on precept for a statement on whether an R2 project supersedes prior releases.
 
−
*Continue reviewing the Risks that Melva identified from the survey
 
 
|}
 
|}
  
−
©2013 Health Level Seven® International. All rights reserved.
+
© 2013 Health Level Seven® International. All rights reserved

Revision as of 18:52, 14 August 2013

TSC representatives and ArB to jointly develop content for the BAM for the Product Line Architecture Program

HL7 BAM Modeling Call Minutes

Location: call 770-657-9270 using code 985371#
GTM 111-567-781

Date: 2013-08-14
Time: 2 pm Eastern Time
Facilitator Austin Kreisler Note taker(s) Lynn
Attendee Name


x Calvin Beebe
Woody Beeler
Jane Curry
Bo Dagnall
Jean Duteau,
Tony Julian
x Austin Kreisler,
x Lynn Laakso
Cecil Lynch
regrets Ron Parker
Brian Pech
Melva Peters
no quorum definition

Agenda

  • Agenda
    • PSS development for CDA R2 IG Product Family.
    • Continue discussion on model diagram


Minutes

Convened 2:06 PM

  • Discuss what we need for WGM
    • Should BAM meet in Cambridge? SAIF AP on Weds Q4 and BAM/PLA on Weds Q3. Agenda for meeting needs ArB participation so wait until Ron comes back.
  • Are product families for multiple products or a single product. CDS issues involve CDA< 2.x, HQMF etc. How does that fit into BAM concept.
    • HL7 project management group doesn't manage others' projects except some key strategic ones. They are a tiny group and do more to define best practices for project management.
  • PSS on CDA R2 IG Product Family was discussed on CDA R3 call and might be the better place for identifying templating on CDA (CDA R3 IG Product Family). They will probably take it up at the WGM. FHIR does templating but they call it profiling. A profile is just another resource.
  • diagram reviewed. Product family on mechanism for production, product line on coherence of marketing-related requirements. US Realm product line is one example but a poor one. Other types of product lines more singularly domain focused. Austin notes that of 200+ active projects, there are 40+ US Realm and that will grow. Other realm activity went on in their realm and was brought back to the HL7 international group. US activity has already resulting in two "point" releases to v2, (V2.5.1 and v2.7.1). US Realm is consuming ¼ of our bandwidth.
  • Argument against it as a product line as it doesn't solve a singular use case. However it is a single consumer perspective. Sub-product lines within it are focused on individual use cases. This is an instance where the product line is recursive.
  • For FHIR, FMG has a goal to get the standard out the door. For CDA IG's does it make sense to have its management in a product management group? The management group is to ensure the projects meet their milestones.
  • It's not a steering division, but perhaps it's a US Realm Program, using program management to shepherd a set of projects in a coordinated fashion and meet schedules. Extramural coordination is required and should be flagged in the PSS. Calvin suggests that coordination groups identify a contact person and be sent a packet on what the procedure is for how such a project moves through the organization.
  • Conformance to procedure is a challenge even for some HL7 cochairs, so enlisting the help of extramural participants would be iffy.
  • Dashboards for project status discussed, along with project facilitator commitment agreements to follow the process.

Austin and Calvin not available next week; cancel the call. Adjourned 2:49 PM


Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items

© 2013 Health Level Seven® International. All rights reserved

Retrieved from "https://tscwiki.hl7.org/w/index.php?title=2013-08-14_TRAC&oldid=12027"