Difference between revisions of "FHIR Ballot Prep"
| Line 7: | Line 7: | ||
** DSTU 2 patch published | ** DSTU 2 patch published | ||
** Substantive changes for non-frozen resources and non-substantive changes for all resources can be committed (wait for announcement on committer's list) | ** Substantive changes for non-frozen resources and non-substantive changes for all resources can be committed (wait for announcement on committer's list) | ||
| − | * Oct 30th | + | * Oct 30th |
** All work groups should have active PSSs for 2.1 (and ideally 3.0) FHIR development work | ** All work groups should have active PSSs for 2.1 (and ideally 3.0) FHIR development work | ||
* Nov 30th | * Nov 30th | ||
| Line 15: | Line 15: | ||
* Jan 9, 2016 | * Jan 9, 2016 | ||
** Resource and profile proposals approved by the FMG | ** Resource and profile proposals approved by the FMG | ||
| − | |||
** Connectathon | ** Connectathon | ||
* Mar 18 | * Mar 18 | ||
** Final content freeze | ** Final content freeze | ||
** Start of QA process | ** Start of QA process | ||
| − | * Mar | + | * Mar 25 |
** QA complete | ** QA complete | ||
** Apply QA changes | ** Apply QA changes | ||
| Line 27: | Line 26: | ||
* May 2 | * May 2 | ||
** DSTU 2.1 Ballot closes | ** DSTU 2.1 Ballot closes | ||
| − | * May 7 | + | * May 7 |
** Ballot triage complete | ** Ballot triage complete | ||
| Line 38: | Line 37: | ||
* July 31 | * July 31 | ||
** Publication QA complete | ** Publication QA complete | ||
| − | * 1st week of August | + | * 1st week of August 2016 |
** DSTU 2.1 published, SVN opened for 3.0 commits | ** DSTU 2.1 published, SVN opened for 3.0 commits | ||
We'll worry about FHIR "release 3" timelines once 2.1 is published and there's a good idea of scope. | We'll worry about FHIR "release 3" timelines once 2.1 is published and there's a good idea of scope. | ||
Revision as of 16:55, 14 October 2015
This page lists the tasks to be completed by work groups in preparation for the DSTU 2.1 interim 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:
- Oct 17th, 2015
- DSTU 2 patch published
- Substantive changes for non-frozen resources and non-substantive changes for all resources can be committed (wait for announcement on committer's list)
- Oct 30th
- All work groups should have active PSSs for 2.1 (and ideally 3.0) FHIR development work
- Nov 30th
- Proposals for new resources and profiles for inclusion in DSTU 2 are submitted to the FMG
- All substantive changes applied for connectathon release
- Connectathon release published
- Jan 9, 2016
- Resource and profile proposals approved by the FMG
- Connectathon
- Mar 18
- Final content freeze
- Start of QA process
- Mar 25
- QA complete
- Apply QA changes
- April 1
- DSTU 2.1 ballot opens
- May 2
- DSTU 2.1 Ballot closes
- May 7
- Ballot triage complete
Note: The following timelines are dependent on the volume of in-scope ballot requirements
- June 30
- Reconciliation complete
- July 17
- All changes applied
- WGs have voted for content to progress from draft to FMM 1 and from FMM 3 to FMM 4
- July 31
- Publication QA complete
- 1st week of August 2016
- DSTU 2.1 published, SVN opened for 3.0 commits
We'll worry about FHIR "release 3" timelines once 2.1 is published and there's a good idea of scope.
