This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Ballot Prep"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user 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 | ||
| 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== | |
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 114: | Line 116: | ||
===IGs published with R4=== | ===IGs published with R4=== | ||
| − | 2018-11-18: Content is final, work group performs and applies QA | + | *2018-11-18: Content is final, work group performs and applies QA |
| − | 2018-12-02: IG is locked | + | *2018-12-02: IG is locked |
| − | * qa.html contains no errors or warnings (or Grahame has pre-approved all remaining errors/warnings as insignificant | + | ** 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 | + | ** 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-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) | + | *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 | Sometime before Dec. 31, depending on FHIR Core recirculation requirements, IG is published alongside R4 spec | ||
| Line 127: | Line 129: | ||
*2018-10-17 - [[:Category:FHIR_IG_Proposal|IG proposals]] due to the FHIR Management Group. (Earlier is better) | *2018-10-17 - [[:Category:FHIR_IG_Proposal|IG proposals]] due to the FHIR Management Group. (Earlier is better) | ||
| − | |||
*2018-10-28 - NIBs due, IG must be publishing on the CI build and "functionally complete" | *2018-10-28 - NIBs due, IG must be publishing on the CI build and "functionally complete" | ||
** FMG will be evaluating "need to ballot" - each ballot must be necessary | ** FMG will be evaluating "need to ballot" - each ballot must be necessary | ||
** 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 | ||
| + | ** Reconciliation packages posted to ballot desktop for previous ballots (if any) | ||
*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]
