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 R4 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.)
+
A calendar has not yet been established for the FHIR R5 cycle.  General ballot timelines for implementation guides can be found on the [[https://confluence.hl7.org/display/HL7/HL7+Calendars HL7 confluence page]]
 +
 
 +
<!--This page lists the tasks to be completed by work groups in preparation for the R4 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.)
  
 
[http://wiki.hl7.org/index.php?title=Category:FHIR_IG_Proposal Here] is a link for Implementation Guide proposals
 
[http://wiki.hl7.org/index.php?title=Category:FHIR_IG_Proposal Here] is a link for Implementation Guide proposals
Line 7: Line 9:
 
* R4 is also the first time we're expecting to have multiple "ballots" for FHIR core content.  This means that there will be '''one''' FHIR specification hosted on the web.  However, each page in the specification will identify both what level it's being balloted at (not balloted, draft, STU or normative) as well as which ballot it's part of.  Multiple ballots are necessary to allow content to proceeed by different paths - balloting at different levels requires separate ballots and if there's a need to allow some content to be demoted to a lower level while other content remains on the normative path, that content needs to be packaged separately.
 
* R4 is also the first time we're expecting to have multiple "ballots" for FHIR core content.  This means that there will be '''one''' FHIR specification hosted on the web.  However, each page in the specification will identify both what level it's being balloted at (not balloted, draft, STU or normative) as well as which ballot it's part of.  Multiple ballots are necessary to allow content to proceeed by different paths - balloting at different levels requires separate ballots and if there's a need to allow some content to be demoted to a lower level while other content remains on the normative path, that content needs to be packaged separately.
  
<!--==Priorities==
+
==Priorities==
 
For this WGM:
 
For this WGM:
 
* Discuss the candidate normative artifacts and evaluate whether your WG/organization would like to see the list changed.  The current candidate list is:
 
* Discuss the candidate normative artifacts and evaluate whether your WG/organization would like to see the list changed.  The current candidate list is:
Line 88: Line 90:
 
*2018-08-24: Ballot opens
 
*2018-08-24: Ballot opens
 
*2018-09-24: Ballot closes and initial triage occurs.  Note: No substantive changes allowed for normative candidates unless they drop to STU.
 
*2018-09-24: Ballot closes and initial triage occurs.  Note: No substantive changes allowed for normative candidates unless they drop to STU.
-->
+
 
 
===R4 Publication===
 
===R4 Publication===
 
These are the publication deadlines leading to the publication of the FHIR R4 core specification and any IGs that plan to *publish* on the same cycle.
 
These are the publication deadlines leading to the publication of the FHIR R4 core specification and any IGs that plan to *publish* on the same cycle.
Line 134: Line 136:
 
*2018-12-02 - Final freeze.  If there are QA errors at this point, you don't publish.  No slippage for any reason
 
*2018-12-02 - Final freeze.  If there are QA errors at this point, you don't publish.  No slippage for any reason
 
*2018-12-07 - Ballot opens
 
*2018-12-07 - Ballot opens
 +
-->

Latest revision as of 21:16, 24 April 2019

A calendar has not yet been established for the FHIR R5 cycle. General ballot timelines for implementation guides can be found on the [HL7 confluence page]