This wiki has undergone a migration to Confluence found Here

FHIR Infrastructure Minutes CC 20160201

From HL7Wiki
Jump to navigation Jump to search


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

Return to FHIR Infrastructure Minutes



  • Bryn Rhodes
  • Eric Haas
  • Ewout Kramer (chair)
  • Grhame Grieve
  • James Agnew
  • John Moehrke
  • Josh Mandel
  • Lloyd McKenzie (scribe)
  • Marten Smits
  • Rob Hausam
  • Thomas Lukasik
  • Yunwei Wang


Motion to approve Jan. 25 minutes: Lloyd/Bryn: 11-0-0


Motion to approve HL7 Vocabulary FHIR Specification Updates PSS: Rob/Grahame - unanimous

Motion to approve FluentPath/CQL PSS: Lloyd/Bryn - unanimous

Tracker Items

Block vote:

  • 7704 2015May core #995 - Still references to ValueSet in coding, though history says it was removed (Ioana Singureanu)
  • 8693 Operation $validate form with raw resource needs to be allowed (James Agnew)
  • 8700 validation shouldn't be an allowed interaction code for resources any more (Lloyd McKenzie)
  • 8793 Substantive change wording (Ed Costello)
  • 8818 Rename "Transaction element" to "Request Element" (Simone Heckmann)
  • 8851 Duplicate narrative on what kind of constraints are allowed (Ewout Kramer)
  • 8917 Root ElementDefinition of a complex datatype is incorrectly marked "InSummary" (Ewout Kramer)
  • 8971 Are "sparse" differentials allowed in StructureDefinition? (Ewout Kramer)
  • 8975 How can re-slicing without using a be combined with re-slicing with ? (Ewout Kramer)
  • 9079 Add computable directive for snapshot rules (Chris Grenz)
  • 9120 Glossy PDF is missing (Lloyd McKenzie)
  • 9129 Dual use of name (slicing/nameReference) (Chris Grenz)
  • 9177 child elements should have type BackboneElement, not Element (Brian Postlethwate)
  • 9199 Add support for Profile governed CRUD (Chris Grenz)
  • 9284 Use of elements in extensions (Ewout Kramer)

Motion to approve block vote: James/Grahame 11-0-0

Grahame & Eric depart

  • 8826 Persuasive with mod

Discussed 8883

EK will send out a note to the FHIR list asking about opinions on a) Limiting the valueset for package.resource.purpose to just say: “example”, “dictionary”?, and let this be possible for any kind of (Conformance) resource

b) Actual purposes found by authors for including a (conformance) resource

c) How to naturally extend the IG resource to also include Conformance, and other resources (KnowledgeModule?)