HL7 Product Line Architecture – 2013-01-15 Meeting

Attendees: Austin, Rick Haddorff, Lynn

Roll Call
Agenda Review
BAM Overview (15 min) (Parker)
- BAM landing - review scope document.
Identify candidates for Product Families and Product Lines (so far we have FHIR)
How to take an existing set of products and make it into a Product Family/Product Line (e.g. CDA)
Next WGM Needs

Ron is not available - they are not as far along as they thought they would be on the BAM
We're not ready to offer sufficient guidance to SDWG in standing up CDA IGs as product family
ArB is re-evaluating product family/line definition or approach
Product Family candidate suggestions based on methodologies and how they are produced.
- V2
- V2.x IG
- Arden Syntax
- EHR FPs
- EHR
- V3
- CDA IGs
- SOA
Current focus is on product family and not devoted to definition of product lines at this time.
- Cross-paradigm project done by Alean is an excellent example of analysis for product line across interoperability paradigms.
- Austin sees a product line forming around the CCDA effort with CCDA-related products including the base CCDA itself. They have related use cases, and foundation of the CCDA header and the U.S. market segment.
- Other Meaningful Use product line requirements are forming around V2 IGs such as LRI, LOI, ELR-PH, eDOS set of products. CDS MU support may be included with Infobutton. QRDA, eMeasure, HQMF evolving.
- May need to develop a form to describe and propose a product line from an existing set of products.
- With establishment of a product family we need some assignment of governance, management, and methodology with SAIF-CD precepts.
- S&I Framework might have held interest for U.S. Affiliate but has lost financial support. only 90 international attendees would not support separation of an U.S. Affiliate.

further analysis of product line development will be conducted in Q4 with SAIF AP review of the Cross-paradigm immunization project.

20130508 HL7 PLA Meeting