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

FHIR Infrastructure Minutes CC 20170501

From HL7Wiki
Revision as of 20:01, 1 May 2017 by Ron Shapiro (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


FHIR Infrastructure Conference Call 3:00PM Eastern Time (Date above)

Return to FHIR Infrastructure Minutes

Agenda

Attendees

  • Lloyd McKenzie (chair)
  • Brian pech
  • Bryn Rhodes
  • Chris Johnson
  • Craig Gabron
  • Durwin Day
  • Eric Haas
  • James Agnew
  • Lenel James
  • Rob Hausam
  • Ron Shapiro
  • Brett Marquard
  • Linda Michaelsen
  • Ewout Kramer

Versioning discussion

Chris Johnson presented the storyboard sent out.

Lloyd explained the current approach in FHIR for supporting different versions. End goal is to maintain full backward compatability once FHIR has gone Normative, at which point, the version should not matter. Until then, Conformance or CapabilityStatement is used to interrogate to see what version of a resource is supported.

Lenel further described the storyboard sent out and the need in the payor community to exchange data with a wide variety of FHIR servers in various stages of FHIR implementation. To ensure that clinically relevant data is not overlooked, it is important to know exactly which FHIR version the endpoint currently supports.

Proposed Saturday Q3 breakout discussion during FHIR Connectathon in Madrid.

Madrid agenda

FHIR-I will have 2 sessions on Monday Q3/Q4 and will then be joint with other work groups the rest of the week.

Discussion about adding a time at WGM to discuss Hot Topics. No known Hot Topics for now, but some may come up at FHIR Connectathon.

Ewout will triage tracker list to identify items appropriate for face to face WGM discussion.

Tracker items

Discussion about the possibility of technical corrections that are approved being published in a 3.2 version of FHIR versus waiting until FHIR 4. Given the current publication process, this is unlikely. However, if the implementer community identifies critical errors in FHIR 3, then we should probably consider how these corrections can be published. Review Grahame's Wiki page describing the publication process to see if there are some suggestions for streamlining that process.

Adjournment

Next FHIR-I call will be in 3 weeks.

Retrieved from "https://wiki.hl7.org/w/index.php?title=FHIR_Infrastructure_Minutes_CC_20170501&oldid=138382"