R6 Ballot (1st Draft)

This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions

1.13 R6 Ballot Roadmap

FHIR Infrastructure icon Work GroupMaturity Level: N/AStandards Status: Informative

Welcome to the FHIR Release 6 (R6) ballot.

This ballot is the first ballot of R6. This is only a draft ballot seeking review on the following items:

The intention is that there will be minimal changes to artifacts within the scope of the ballot between now and the final normative ballot, and what changes do occur will be carefully tracked and declared to balloters, which should minimize review time for these resources and pages in the final normative/STU ballot.

Comments are able to be made outside these specific areas as part of this ballot, but they'll be considered out of scope, and the underlying Jira issues handled just like any other Jira issue.

1.13.1 The FHIR R6 Ballot Process

This is the first of a series of draft ballots on R6, where different candidate resources for normative status in the final R6 version undergo focused review in order to try and reduce the overall ballot load of the final R6 ballot.

Balloter's attention is drawn to two useful links at the bottom of every page: . These are very useful when preparing ballot comments.

This ballot is using HL7's Jira balloting process icon. As such, ballot comments will need to be submitted in Jira and, in general, balloting spreadsheets will not be used. Some organizational and affiliate balloters may continue to use spreadsheets but will be responsible for importing them into Jira themselves and may have slightly different processes for consolidating ballots to take that into account. The ballot desktop will be used for voter registration but will not be available for vote submission. Voters are encouraged to view the recorded tutorial icon on Jira balloting in addition to reading through the instructions on submitting Jira feedback icon and using Jira balloting icon. A webinar will be held part-way through the ballot cycle to provide an opportunity to ask questions about the process. Questions can also be raised on the Jira/Confluence stream icon on http://chat.fhir.org.

Because this is only a draft ballot, committees are not required to response to comment, but will endeavour to do so.

When submitting your ballot feedback, if you have a general comment on something that you see occurring multiple times, please include at least a couple of specific locations where you see the issue. As much as possible, capture each separate concern as a distinct tracker item icon; it makes our job of reconciling much easier. Also, don't forget to fill in the section numbers (gray numbers to the left of each heading) and URLs. Only one URL should be placed in the "url" element or column. If you want to reference additional URLs, include them in the text of your ballot comment.

If you have questions that are interfering with the ability to review the specification or submit ballot comments, please contact one of the co-chairs of the FHIR Management Group: Lloyd McKenzie or David Hay.

Thanks for taking the time to review the FHIR specification. We appreciate any feedback you can provide.

The difference analysis in this ballot for resources is still between Release 3 and Release 4. This will be updated when Release 5 is prior to publication of the final specification. In the meantime, balloters are welcome to comment on suggested improvements to the mappings and difference statements, but these cannot be the basis for negative votes. Contributions may also be made directly (join the conversation at chat.fhir.org icon).