20140122 HL7 PLA Meeting

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: Room TBD

Date: 2014-01-22
Time: 1:45 PM Central (Q3)
Facilitator Ken Note taker(s) Lynn
Attendee Name


Calvin Beebe
Woody Beeler
x Lorraine Constable
Bo Dagnall
Jean Duteau,
x Rick Haddorff
Tony Julian
regrets Paul Knapp
regrets Austin Kreisler,
x Lynn Laakso
x Ken McCaslin
Brian Pech
x Ron Parker
x Dmytro Rud, Roche
x John Quinn
no quorum definition

Agenda

Agenda review

  • Notes of 20131211 PLA call review
  • Map our existing products into 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


Minutes

Agenda review - Ken had discussed with Austin that we need to review everything under standards on the website and categorize them into preliminary concepts of product families and lines in order to figure out how to move forward.

  • Map our existing products into notional division of products into product families and lines, to provide examples for peer review.
    • Is certification a product? Is it something that is an artifact that allows you to achieve interoperability.
    • Outward facing collection of items for consumability is product line. Coherent collection from a consumability perspective is product line.
    • FHIR architecture is a product family - Production perspective.


Product Family

  • FHIR
  • V2
  • V3
  • vMR-CDS
  • EHR-S FM
  • Arden Syntax
  • CCOW
  • GELLO
  • DAM? Are they a product family? With the ArB definition should share common method of production. Analytical viewpoint from where requirements are derived. Most DAMs also have use cases in them. What do we call them - "Analysis Artifacts"? Methodology and structure for how they are produced is coherent. It is at a higher level on the ECCF than other products.
  • Templates? are structures in V2 considered a template? V3 has templates mechanism being defined, CDA also has structured data templates. It is intended to feed into reuse, constraint or extensibility.
  • Conformance and certification - conformance assertions skillset and methodology should be consistent across paradigms. Ron notes that some WGs may have to reframe thinking the application of methodology.
    • Certification is individual conformance to HL7's established standards of performance notes Ken. Ron agrees that certification is adherence to standards of conformance. John suggests you might regard it as managing optionality.
  • Education
    • Is Help Desk part of education - uses a different methodology and manner of production. It's its own category.
  • WGMs or just meetings. Specialization of any meeting i.e. teleconferences - anywhere we have applied health metrics where consistent methodology and approach is used. Harmonization is another.

Ken would like to send out the product master grid and ask the group to tag product families on each of them, sort them out and see who product lines emerge. Ron notes we have a gap analysis as we identify those product lines whose methodology and manner of production are fully defined and those that are not.

  • We should also identify who "owns" certain product family
  • Need to identify quality metrics in each family.
  • Columns will only include the standards name and description; not even include the existing WG stewards. Remaining columns are all product families which can be selected. If they fit into multiple product families, do we identify primary and secondary? Those that do fit into multiple will probably include the analysis artifacts.
    • One benefit of this product family assessment will be to be able to give to the marketing committee to assess. Discussion ensued on what really needs to be considered an advertising function or product line management - Ron likes the term product directorate. He adds that the BAM now describes the notion of a product catalog, which would take a form similar to the matrix we've been discussing but is managed by someone organizationally. You start treading into marketing and sales, value to customers and organizational value in membership, etc. Market segmentation in the BAM as an ongoing process.
    • FHIR for example is market segment for developers who want to build rapidly. Not the same as clinical IG for CDA. Market segment intended for EHR is very different than lab to lab interaction for example. What segments of the market will value those attributes, is an after-the-fact activity.

ACTION ITEM : Lynn will have this to Ken by Friday and then the group will have two weeks to review
Ken will check with Austin to ensure he's handed this off appropriately. Plan to restart in three weeks and meet every two weeks following. Lynn will also look into getting a listserv for this started but in the meantime will distribute to both TSC and ArB lists.


Product Family
Product Line FHIR V3 V2 Analysis Artifacts CDA EHR-S FM vMR-CDS Templates Conformance Education Certification Arden Syntax CCOW GELLO
? RIM C-CDA
e.g. C-CDA C-CDA
Lab LRI IG
LOI IG
eDOS IG
LAB DAM C-CDA
S&I/MU
US Realm
LRI IG
LOI IG
eDOS IG
C-CDA


    • 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


Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items
  • TBD

© 2014 Health Level Seven® International. All rights reserved