This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

20130814 BAM Modeling

From HL7Wiki
Revision as of 20:53, 19 August 2013 by Llaakso (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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