This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Ballot Prep"
Jump to navigation
Jump to search
| (10 intermediate revisions by 2 users not shown) | |||
| 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 | ||
Notes: | Notes: | ||
| − | * R4 is the first FHIR publication that | + | * R4 is the first FHIR publication that will contain Normative content. For those who aren't familiar with HL7 processes, Normative means that, once the specification passes, we will no longer make breaking changes to the specification from that point forward - ever. The rules for change in FHIR for normative content are described [[http://hl7.org/fhir/versions.html#b-compat here]]. |
* 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== | |
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. | ||
*2018-09-29 - 10-05: October WGM (Baltimore). | *2018-09-29 - 10-05: October WGM (Baltimore). | ||
| − | *2018-10-06: | + | *2018-10-06: Notification of Ballot opens for "final" targeted R4 normative ballots |
*2018-10-12: Final reconciliation packages posted for Normative Sept. ballots | *2018-10-12: Final reconciliation packages posted for Normative Sept. ballots | ||
| + | * Working on R3/R4 conversions (see [[Progress on FHIR R3/R4 conversions]]) | ||
** Changes will be auto-deferred after this date | ** Changes will be auto-deferred after this date | ||
*2018-10-31: Final reconciliation package posted for STU ballot | *2018-10-31: Final reconciliation package posted for STU ballot | ||
| − | *2018-11-01: Substantive content freeze for core R4 publication including all substantive QA changes. Decision based on vote results and withdrawals about which normative packages to drop to STU. | + | *2018-11-01: Substantive content freeze for core R4 publication including all substantive QA changes. Decision based on vote results and withdrawals about which normative packages to drop to STU. Profiles publishing as part of R4 and implementation guides aiming to publish simultaneously with R4 may continue to make substantive changes. |
*2018-11-06: Targeted R4 normative ballot opens | *2018-11-06: Targeted R4 normative ballot opens | ||
*2018-11-11: Final content freeze for R4 publication and start of QA period. No changes permitted for FHIR Core without product director permissions. Implementation Guides may update based on their QA processes | *2018-11-11: Final content freeze for R4 publication and start of QA period. No changes permitted for FHIR Core without product director permissions. Implementation Guides may update based on their QA processes | ||
| Line 112: | Line 115: | ||
The world rejoices, Grahame sleeps | The world rejoices, Grahame sleeps | ||
| − | ===Jan | + | ===IGs published with R4=== |
| + | *2018-11-18: Content is final, work group performs and applies QA | ||
| + | *2018-12-02: IG is locked | ||
| + | ** qa.html contains no errors or warnings (or Grahame has pre-approved all remaining errors/warnings as insignificant | ||
| + | ** WG submits publication request and notifies fmgcontact@hl7.org of their desire to publish with R4 | ||
| + | *2018-12-05: FMG votes on whether to publish the IG after reviewing IG and QA page | ||
| + | *2018-12-10: TSC votes on whether to publish the IG (at the same time they vote on R4) | ||
| + | |||
| + | Sometime before Dec. 31, depending on FHIR Core recirculation requirements, IG is published alongside R4 spec | ||
| + | |||
| + | ===Jan 2019 ballot cycle for FHIR IGs=== | ||
NOTE: There will be no deadline extensions for this cycle. If you miss a deadline, your content will not appear in the January ballot and will have to wait for the May cycle. | NOTE: There will be no deadline extensions for this cycle. If you miss a deadline, your content will not appear in the January ballot and will have to wait for the May cycle. | ||
| Line 120: | Line 133: | ||
** All artifact types, all key behaviors, etc. present. If there are bugs in the publication process, they must be identified by this point and must be resolved to the point that the build at least runs successfully and any tooling-related issues must be agreed to be resolvable | ** All artifact types, all key behaviors, etc. present. If there are bugs in the publication process, they must be identified by this point and must be resolved to the point that the build at least runs successfully and any tooling-related issues must be agreed to be resolvable | ||
*2018-11-18 - Content deadline for QA. All content must be final from the workgroup perspective - no changes other than QA fixes from this point - no new artifacts or content | *2018-11-18 - Content deadline for QA. All content must be final from the workgroup perspective - no changes other than QA fixes from this point - no new artifacts or content | ||
| − | 2018-12-02 - Final freeze. If there are QA errors at this point, you don't publish. No slippage for any reason | + | ** Reconciliation packages posted to ballot desktop for previous ballots (if any) |
| − | 2018-12-07 - Ballot opens | + | *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 | ||
| + | --> | ||
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]
