This wiki has undergone a migration to Confluence found Here

20150107 PLA call

From HL7Wiki
Jump to navigation Jump to search

return to HL7 Product Line Architecture Meeting Minutes and Agendas
Return to HL7 Product Line Architecture Program

HL7 PLA Call Minutes

Location: Phone: +1 770-657-9270, Participant Code: 985371,

Date: 2015-01-07
Time: 2PM
Facilitator Mary Kay/ Austin Note taker(s) Anne
Attendee Name

Calvin Beebe
Woody Beeler
Lorraine Constable
Bo Dagnall
Jean Duteau,
Rick Haddorff
x Tony Julian
Paul Knapp
x Austin Kreisler,
x Anne Wizauer
x Mary Kay McDaniel
Brian Pech
John Quinn
x John Roberts
x Andy Stechishin
no quorum definition


Agenda review

  • Notes of 20141210_PLA_call review
  • Set up a task or project to pilot managing the product and the family and then moving into lines as we go.
  • notional division of products into product families and lines, to provide examples for peer review.
    • Level of granularity
    • Identify which pieces are orphaned, and the political elements to be surfaced.
    • Positioning cross-product family artifacts (standards naming)
  • BAM-lite feedback and review
    • Governance on V2.x (v2.9 substantive changes)
    • develop form to request establishing a Product Family


Convened at 2:05 At the end of last call there was an idea of using UDI as a task group to understand how we will take this forward. Mary Kay went through list of individuals to invite. Meeting on Tuesday night. Anyone else we should reach out to that we’ve missed? We’ll do a brief intro, discussion of challenges, the use of the standards, the scope for HL7, how do we engage across HL7 (how big is this project?), and how do we manage it. We should go in with a suggested solution/rule. Governance would be TSC in absence of another overarching group. How do we make sure everyone implements it the same way? Already a TSC task force in place to deal with that, although activity has dwindled. So we’re all in agreement that this is a cross-cutting item; that we certainly need to engage with TSC. Mary Kay will be there on Sunday pm meeting to talk about where we’re at and where governance stands. All Hl7 groups are impacted by this. Visio diagram – issue with roles. Products fall into a line with the WGs; families with common methodology works very well. Do you manage the product or the product line (organized from a consumer perspective)? Originally intended to manage product families (things that are developed in a similar fashion). How do we recognize families vs. WG silos? We have a number of WGs that are product line oriented, but some that look at families. Have been collisions before. Projects are owed by the WGs, where the methodology gets executed. However, project teams are instead doing much of the work outside of HL7 at times and not going back to the WGs. How do we manage consistency across families? Governance sets rules that need to be followed to maintain consistency. There are some situations where the product family is small and has been centralized within a WG and the WG acts as management for the family. One idea is dissolving the WGs and organize around product families – a v3 family, FHIR family, etc. An issue with that is you could end up with duplicate and overlapping work. We don’t have an issue with governance, management, and methodology – the problem that we really have to be able to solve is a communication issue. Communication not on a broad enough platform; Andy feels that part of the communication issue is a governance issue. Next steps: 1) Product families and what their de facto governance and methodology group is – make it official. For example: for v3, methodology is MnM. Governance is technically the TSC (reactive). Management (of product) happens at the WG level. V2 – management of product is WG, product family and line management, governance and methodology is Structured Documents. CDA is a separate product family? Yes, it is a v3 RIM-based standard. Structured doc does governance, methodology, and product family management of v3 CDA. Distinct methodology for templating. V3 structured documents comprises more than CDA. One might say that CQI is the management, but the methodology and governance still rests with structured documents. C-CDA may be a product line, because it has multiple products focused on us-realm consumer market for a series of CDA products. Further discussion over v2. Adjourned

Meeting Outcomes

Next Meeting/Preliminary Agenda Items

© 2014 Health Level Seven® International. All rights reserved