20151005 FMG WGM

From HL7Wiki
Jump to: navigation, search
HL7 TSC FMG Meeting Minutes

Location:
Atlanta 5

Date: 2015-10-04
Time: 12:30 PM U.S. Eastern
Chair: Note taker(s): Anne W.
Quorum = chair + 4 yes/no
Co chairs x David Hay x Lloyd McKenzie
ex-officio Woody Beeler,
Dave Shaver
FGB Co-chairs
. John Quinn, CTO
Members Members Members Observers/Guests
x Hans Buitendijk x Brian Postlethwaite x Paul Knapp x Anne W., scribe
x Josh Mandel x John Moehrke x Brian Pech
.

Agenda

  • Roll Call
  • Agenda Check
  • Minutes from 20150930_FMG_concall
  • Administrative
  • Action items
    • Lloyd to review DSTU QA page for completeness against the QA spreadsheet
  • Discussion Topics:
    • Hot topics
    • Criteria for inclusion in 2.1
    • What warnings should be errors?
    • WG liaison objectives
    • Source control management for 2.1 vs. 3.0 changes
    • Role of FMG in reviewing or approving FHIR-related PSSs
    • Expectations for reconciliation using gForge (what should have a vote)?
    • Transitioning profile editing to Forge
    • FMM levels
    • Finalizing timeline for 2.1
  • Reports
  • Process management
  • AOB (Any Other Business)

Minutes

  • Agenda and Minutes approved
  • Criteria for 2.1 scope:
    • A frozen (no substantive changes) candidate list has been prepared by Grahame; list displayed to group
    • Lloyd notes that infrastructure resources aren’t well represented, like value set and structure definition. All non-draft should be part of the freeze list.
    • Other items to freeze - all conformance resources that are non-draft, parameters, datatypes, immunization, all of the infrastructure web pages
    • Remove from freeze list: questionnaire and questionnaire response
      • MOTION by Paul to accept Grahame’s list with the additions and subtractions noted above, with the addition that substantive change can be made on a case by case basis if allowed by FMG. Second by Hans.
      • VOTE: All in favor
  • WG liaison objectives:
    • Reviewed Lloyd’s email to co-chairs regarding this issue.
  • Source control management for 2.1 vs. 3
    • Anything that is substantive that is not permitted in the 2.1 release gets deferred to being committed until after 2.1 is published.
      • Josh – so I can’t share anything new and different until after next May? Lloyd – essentially yes. We’ll run reports against the SVN against the directories which are subject to freeze. Paul expresses concerns that it’s an odd build process. New stuff should go into a continuous build and then be pulled off for integration. We’re going to have to fork these things off as we have more versions. Lloyd: you can’t hive off it if you make substantive change. Source materials are not as easy to merge. Concerns about things like typos and smaller changes that need to be corrected before the next release. Couldn’t we use the major.minor.increment approach? Lloyd: challenge is that every time we need to fix a single comma, it’s 12 hours of Grahame’s time to put up the new release. Ewout states he is not against updating in batches.Lloyd: the other challenge is from a QA perspective and a governance perspective; reviewing content that is checked in as being non-substantive and getting the approval to put it out is not a small amount of work. What are the changes that are important enough to justify going through that amount of effort? Paul: the issue is how do we make it so that we’re presenting complete and current information to the implementer community? Lloyd: the changes go with tooling changes. Ewout: I just want to make textual changes, not complicated changes. Brian Pech: if the process is so onerous, we need to look at the project. Discussion over material changing in 3.0 that also has to be changed in 2.1 and implementing forking. Lloyd: we don’t want to do forking unless we absolutely have to. Paul states that this is not the best policy for implementers.

Next Steps

Actions (Include Owner, Action Item, and due date)
Next Meeting/Preliminary Agenda Items

20151014 FMG concall


Back to FHIR_Management_Group

© 2015 Health Level Seven® International

Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.