This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FHIR Ballot Prep"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
  
This page lists the tasks to be completed by work groups in preparation for the DSTU 3 release of the FHIR core specification.  The timelines for implementation guide publication and balloting may differ.  Implementation Guides may choose to either publish in sync with the core specification (and actively manage dependencies as underlying resources and profiles are updated) or may choose to ballot later, once the FHIR specification is finalized.  (The disadvantage of the latter approach is that changes to the core specification identified as part of implementation guide revision won't be able to be applied until a subsequent release)
+
This page lists the tasks to be completed by work groups in preparation for the STU 3 release of the FHIR core specification.  The timelines for implementation guide publication and balloting may differ.  Implementation Guides may choose to either publish in sync with the core specification (and actively manage dependencies as underlying resources and profiles are updated) or may choose to ballot later, once the FHIR specification is finalized.  (The disadvantage of the latter approach is that changes to the core specification identified as part of implementation guide revision won't be able to be applied until a subsequent release)
  
 
The tentative schedule for this release is as follows:
 
The tentative schedule for this release is as follows:

Revision as of 04:28, 29 June 2016

This page lists the tasks to be completed by work groups in preparation for the STU 3 release of the FHIR core specification. The timelines for implementation guide publication and balloting may differ. Implementation Guides may choose to either publish in sync with the core specification (and actively manage dependencies as underlying resources and profiles are updated) or may choose to ballot later, once the FHIR specification is finalized. (The disadvantage of the latter approach is that changes to the core specification identified as part of implementation guide revision won't be able to be applied until a subsequent release)

The tentative schedule for this release is as follows:

  • July 17th, 2016
    • Content freeze for "substantive" changes to resources. This means any changes to data element names, cardinalities, bindings, etc. - anything that might impact profiles and implementation guides based on a resource.
  • July 24th, 2016
    • Total freeze - at midnight Eastern on July 24th we'll work to get a clean build and then send out content for QA review
  • Wednesday August 10th, 2016
    • All QA changes applied. No further changes permitted without approval of product line coordinator
  • Friday August 12, 2016
    • Ballot opens
  • Monday September 12, 2016
    • FHIR ballot closes
  • Friday September 16, 2016
    • FHIR triage complete and ballot content loaded to gForge (or alternative)
  • Sept. 17-23
    • Baltimore WGM
  • Sun. Dec. 11
    • Target for reconciliation complete, substantive changes applied
  • Dec 31
    • Publish?