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

2012-06-28 Tooling Call

From HL7Wiki
Revision as of 15:00, 28 June 2012 by Llaakso (talk | contribs)
Jump to navigation Jump to search

Tooling Meeting

Meeting Information

HL7 Tooling Meeting Agenda/Minutes

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

Date: 2012-06-28
Time: 10:00 am EDT
Facilitator: Jane Curry Note taker(s): Lynn Laakso
Attendee Name, Affiliation
x Woody Beeler, Beeler Consulting
x Wilfred Bonney, HL7 HQ
Joshua Carmody, HL7 HQ Tooling Administrator
x Jane Curry, Co-Chair
Tim Ireland, Co-chair
x Lynn Laakso, HL7 HQ Tooling Support
x Abdul-Malik Shakir, AMS Consulting
x John Ritter, EHR
regrets Andy Stechishin, Co-chair
Quorum Requirements Met (co-chair plus 3 counting staff): yes

Agenda

Agenda Topics


Supporting Documents
See links

Minutes

Minutes/Conclusions Reached:
Call to order 10:05 AM EDT

  • Roll Call & Agenda Review - no changes identified
  • Approval of previous minutes from 2012-06-21 Tooling Call Lynn moves and John seconds approval. Approved 3/0/1. Woody joins. AMS comments on the criteria - they are more applicable to developers, not project managers or BA or testers. Only a subset apply if other roles are needed. Multiple proposals may also be considered with different subsets of activity.
  • Review action items -
  • No update on validator tool (1998)
  • Joshua working on piloting
  • Lynn waiting for word back on university
  • Review projects:
    Tooling-sponsored Projects
    • PI# 904 HL7/OHT Health Ingenuity Exchange Alpha Program Participation
      Next step: Presentation on how to use HingX at Tooling telecom
      • Jane only has partial presentation. She will have the full presentation next week.
      • PSS has been approved by Steering Division. It is on the TSC agenda on Monday July 2nd.
    • PI# 831 EHR-S FM Profiling Tool
      • Jane has the RFP for this as well as MAX but need to align them together. Word from Karen is that we'll use reply to contract email and need to include a reference to a contract template. She discussed briefly with John Quinn and Karen for process after the RFP is released. Two weeks after the RFP is put out, an open Q&A can be held and answers provided to the contracts listserv.
    • PI# 803 Tooling_Dashboard
    • PI# 802 Tooling Communication Plan and Execution
      • Postpone tooling communication plan RFP until after tooling strategy is done, so after the Baltimore WGM.
    • PI# 801 Tooling Strategy and Process Revision
      • First strategy iteration due 2nd week in July so Jane will be working on that. Draft strategy needs to be produced in time for Board Retreat at end of July. Board input will be used for revision to be presented in Baltimore. She will present to Tooling WG before giving to John to take to the Board retreat.
    • PI# 742 Model Automated Exchange (MAX) for UML Models
      • AMS had a MAX phone call where a couple of potential participants expressed interest in the RFP.
    Tooling co-sponsored projects
    • PI# 905 V2 Publishing Database Upgrade (Publishing sponsor) - this has been approved by Templates but needs to go to T3SD.
    • PI# 829 HL7 Templates Registry Business Process Requirements Analysis (Templates sponsor) - going to an informative ballot. Dates need to be updated.
    • PI# 806 Development of policies and procedures of an HL7 terminology authority (Vocabulary sponsor) part of agreement with authority is to try automating potential revisions to IHTSDO. Project in vocab to use NLM for that submission process. IHTSDO workbench project is also anticipated.
    • PI# 752 Publish CDA IGs from Tooling (Structured Docs sponsor) - should be on hold. Remove from review list until further notice from SDWG. Their focus is on Templates ITS for exchange of template design. They're content with publishing in PDF and not entering the V3 publishing stream at this time.
    • PI# 611 Template Registry Pilot (Tooling co-sponsor) -checked with Keith, closed in Project Insight
  • Other/New Business
    • Would any of the projects like to use HingX as a trial for the development of their work. This is the incarnation of the Shared Artifact Repository. It is not a replacement for GForge as a repository. HingX is a registry - it can point to an HL7 repository but it can also host the artifacts/resources. It also has social networking capability. She will have a presentation next week. She'll be using HingX in the development of the Tooling Strategy. Jane is working out how we create our user groups and organize them. Please explore www.hingx.org and send any questions to Jane. Feel free to sign up as a user and create a user group for the organization you represent.

Adjourned 10:33 AM EDT

Meeting Outcomes

Actions
  • Please explore www.hingx.org and send any questions to Jane.
Next Meeting/Preliminary Agenda Items
  • HingX introduction next week.
  • Woody may not be on the call next week. Jane may repeat a presentation for Publishing at noon next Friday.
  • 2012-07-05 Tooling Call


Return to Tooling


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