This wiki has undergone a migration to Confluence found Here

2012-11-29 Tooling Strategy Call

From HL7Wiki
Jump to navigation Jump to search

Tooling Meeting

Meeting Information

HL7 Tooling Strategy Project Meeting Agenda/Minutes

Location: Phone: +1 770-657-9270;
Participant PassCode:586935#
GoToMeeting URL:
https://www1.gotomeeting.com/join/699884034

Date: 2012-11-29
Time: 10:00 am EDT
Facilitator: Jane Curry Note taker(s): Lynn Laakso
Attendee Name, Affiliation
Wilfred Bonney, HQ
x Woody Beeler, Beeler Consulting
Joshua Carmody, HQ
x Dennis Cheung, eHealth Ontario
regrets Jane Curry, Co-Chair
x Lynn Laakso, HL7 HQ Tooling Support
Andy Stechishin, Co-chair
Michael van der Zel, Co-chair
Quorum Requirements Met (co-chair plus 3 counting staff): (no)

Agenda

Agenda Topics

  • Roll Call & Agenda Review
    • Review Tooling_Strategy_and_Process_Revision action items
      • Continue taking the various sources of draft content and transforming into goal, objectives, action plans and performance measures to fit the format of Tooling Strategy draft from 20121121
      • Address Rene's comments on definition of HL7 Tooling
      • Jane will tackle requirements configuration and release mgmt document for tooling governance and management and methodology to classify sections for this week's feedback
      • Andy will make a draft of Candidate metrics
    • UpdateTooling Strategy Policy Implications


Minutes

Minutes/Conclusions Reached:
'

  • Roll Call & Agenda Review
    • Review Tooling_Strategy_and_Process_Revision action items
      • Continue taking the various sources of draft content and transforming into goal, objectives, action plans and performance measures to fit the format of Tooling Strategy draft from 20121121
      • Address Rene's comments on definition of HL7 Tooling
      • Discussion ensued on definition offered: once defined, what is the mission of the tooling strategy to influence the broad spectrum? Will our demo events become trade shows? Will it turn the WGM into trade shows? We can't do that with the 8 people that come to our calls in Tooling. The Tooling WG will become something very different that what is has been. Education for each tool, such as Dave Shaver's, or Siemens' tools from their trade shows, are not something we want to tackle. Many of our members have software development activities that will want to have balanced coverage and equal promotion.
      • Woody may not be on the strategy call next week.
      • Tooling web page would link to other third party tools and their documentation but not to author them.
      • Tooling sessions at HIMSS - that's what our customers are there at HIMSS to do. FHIR connectathon running from the back of the booth at HIMSS might be an option. Given that this encompasses the bus plan of a large % of our members and greater than what Tooling WG can oversee, a constrained defn for the Tooling WG Strategic Plan focuses on development documentation and distribution of the standards. Facilitates others creating implementations not implementing the standard. For example, developing tooling for taking an IG prompting the user to enter the data to create a CDA record - members would object. Tooling that facilitates implementation, not building implementations. CDA in Eclipse core classes as Java classes, demonstration of EMF by Eclipse, you can go to some other application and make it functional. Woody created an editing tool for SPL in Eclipse while on vacation last year. Need to bridge the entry into HL7 - schemas and MIF files they can take advantage of. Need to adapt the definition of HL7 tooling with what HL7's role is in fostering HL7 tooling to be the subset.
      • Modified definition: HL7 Tooling = any software tool that has the capability to support any of the stages in the lifecycle of HL7 standards definition or usage, irrespective of whether that tool is developed, owned, or managed by HL7 or any other party, and irrespective of whether it is a commercial tool or a open source toolkit.
      • Jane's statement is "enable" standards adoption as well as specifications design and publishing - "enable" might be the intent of the board direction on implementation. We may wish to emphasize "facilitate" standards adoption. Explicitly, HL7 Tooling is inclusive of tools developed by third parties. MDHT and Everest have to be in-scope of HL7's tooling efforts. Its efforts when it comes to such pre-existing tools are different than when it comes to HL7-developed/owned tools
      • development of implementation tools is not feasible - for treading on the space held by our members.


Adjourned 10:50 AM


Meeting Outcomes

Actions
  • Lynn will update definition and insert into draft strategy for discussion this afternoon.
Next Meeting/Preliminary Agenda Items



Return to Tooling


Return to Tooling_Strategy_and_Process_Revision

© 2012 Health Level Seven® International. All rights reserved.