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

ITS Concall Minutes 20150915

From HL7Wiki
Jump to navigation Jump to search

Return to: ITS Main Page > ITS Meeting Minutes > 2015

Return to ITS Meeting Minutes

ITS Teleconference - September 15, 2015

HL7 ITS Meeting Minutes Date: 2015-09-15
Facilitator: Dale Nelson Note taker(s): Andy Stechishin
Present Name Init Affiliation
× Paul Knapp PK Knapp Consulting
× Dale Nelson DN Lantana
× Andy Stechishin AS CANA Software & Services
× Brian Pech BP Kaiser-Permanente
David Booth DB Hawaii Group
Quorum Requirements Met: Yes


  1. Role call and agenda
  2. Approve Minutes of previous meetings September 1
  3. Announcements
  4. RDF sub-group report
  5. Review WGM Agenda
  6. Approve Minutes of January 2015 WGM
  7. Approve Minutes of May 2015 WGM
  8. ITS R1.1 Publishing update
  9. Review ITS FHIR Tasks
    • For discussion:
  10. Action Items
    • Publish HL7 over HTTP DSTU
      • PK provided reconciliation to JA (2014-12-09)
    • Update ITS R1.1 for publishing
      • PK will work to complete for Feb 17 (2015-02-10)
    • Update RIM Serialization for Publishing
      • Last action: PK will prepare Publication Request for July 22, 2014 teleconference
    • Review of Product Briefs
  11. Next Meeting
  12. Adjourn

Meeting called to order 2:19 PM Eastern

Discussion of

There was a discussion of

At this point AS left the call

Questions from FHIR Infrastructure

  • Comments in xml
    • Review in Atlanta: comments in XML vs JSON
  • Maturity level
    • Motion: DN/BP The XML & JSON FMM level be established at FMM3, unless we have assurance that a higher level would not cause issues with respect to the “reason” below. FMM 4 might be considered with those assurances. (unanimous)
    Maturity level definition is not precise enough to know whether potentially breaking changes can be made at any level. We are concerned with the notion that comments are not considered part of the content model of a resource, and as such, want to visit the topic in Atlanta. In the event that we recommend comments (and other potentially unknown serialization artifacts) are resource content that needs to be faithfully preserved, we feel the guidance on the ability to make potentially breaking changes in a wire format is not detailed enough for a proper decision.

Meeting adjourned at 3:35 pm Eastern