2013-01-14 TSC WGM Luncheon Agenda

From HL7 TSC
Jump to navigation Jump to search

TSC Monday Luncheon Meeting for 2013Jan Phoenix WGM

back to TSC Minutes and Agendas

TSC WGM Agenda/Minutes

HL7 TSC Meeting Minutes

Location: Sonora

Date: 2013-01-14
Time: 12:30 PM
Facilitator: Austin Kreisler Note taker(s): Lynn Laakso
Attendee Name Affiliation
x Calvin Beebe HL7 SSD SD Co-Chair
x Woody Beeler HL7 FTSD Co-Chair
Bob Dolin HL7 Board Vice Chair (member ex officio w/o vote)
x Jean Duteau HL7 Affiliate Representative
x Freida Hall HL7 TSS SD Co-Chair
Chuck Jaffe HL7 CEO (member ex officio w/o vote)
x Tony Julian HL7 FTSD Co-Chair
x Austin Kreisler (Chair) HL7 TSC Chair, Ad-hoc member
x Lynn Laakso (scribe, non-voting) HL7 HQ
x Charlie Mead HL7 ArB Chair
Don Mon HL7 Board Chair (member ex officio w/ vote)
Ravi Natarajan HL7 Affiliate Representative
x Ron Parker HL7 ArB Alternate
x Melva Peters HL7 DESD Co-Chair
regrets John Quinn HL7 CTO (TSC member ex officio w/vote)
x Andy Stechishin HL7 T3SD Co-Chair
x Pat Van Dyke HL7 SSD SD Co-Chair
Mead Walker HL7 DESD Co-Chair
x Bo Dagnall ArB
Quorum Requirements (Co-chair +5 with 2 SD Reps) Met: (yes)

Agenda Topics

BAM discussion continued

Minutes/Conclusions Reached:

Austin calls to order at 12:46 PM

  • Visitors: Bo Dagnall attended to help explain the BAM modeling
  • BAM
    • Ron narrates the HL7 BAM Input Worksheet 2013-01-13.xlsx.
    • They are ready to have the organization provide content in the framework. This is an input tool.
    • They are happy if folks wanted to diagram it instead.
    • Product lines and families are different collections of products. Product line should have some traceability and interoperability among the products. The development process of a product doesn't stand on its own so the product family must be determined and which line it may belong to asserted. Calvin seeks the way we will establish consistency across product families. Organizational governance processes might be an important addition to the model. Product family nominally established as "building blocks" in which consistency can be established. That would be a good governance precept at an organizational level. Calvin notes that you need to have only one instance of a certain product in a product family at a certain level, e.g. only one conceptual level model for Allergy.
  • Next steps according to Charlie are non-ArB project contributions, and clearly the cross-product family consistency enhancements.
    • Earlier today Austin notes that SDWG bought into the idea of a CDA IG Product Family which does not include the base standard. Charlie notes we should formalize relationships between product families. He suggested that the guinea pig is to restrict it to a couple of instances of IGs. As it's expanded we may expose and better describe differences in the way IGs are developed Jean adds.
    • Austin finds this will happen in the Product Line Architecture Program, kickoff Weds Q3. We need ArB contribution. We will start fleshing out the next steps, using the diagrams as well as the spreadsheet.
    • Charlie notes he'd like to separate process flows in the lifecycle diagrams from the state diagram parts; the documents shown Sunday night will change before Wednesday.
  • Adjourned 1:31 PM

Actions (Include Owner, Action Item, and due date)
  • .
Next Meeting/Preliminary Agenda Items
  • .