This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Ballot Prep"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
*Sun. Mar. 13 | *Sun. Mar. 13 | ||
**QA period closes | **QA period closes | ||
| − | *Sun. Mar. | + | *Sun. Mar. 19 |
**All QA applied | **All QA applied | ||
The "following week" STU 3 is published! | The "following week" STU 3 is published! | ||
Revision as of 21:19, 7 March 2017
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 current schedule for this release is as follows:
- Sun. Feb. 5
- Ballot reconciliation deadline - All ballot comments must be reconciled, tracker issue report must be clean
- Sun. Feb. 19
- Publication substantive resource freeze
- Sun. Feb 26
- Publication total freeze
- Mon. Feb 27
- QA period opens
- Tue. Feb 28
- FMM QA spreadsheet updated for all WG resources
- Sun. Mar. 13
- QA period closes
- Sun. Mar. 19
- All QA applied
The "following week" STU 3 is published!
