Contents

When the NIB is submitted

Check that realm listed on the NIB agrees with the realm as documented in the [wiki url] and the PSS, or else agrees with a variation that has been approved by FMG

Before Ballot Announcement

These checks must be carried out before the ballot annoucement is made, and you must verify with the ballot coordinator (Lynn)
that you have met these goals. They must be carried out by whoever is nominated as the contact on the NiB

The IG must use the standard HL7 FHIR IG template (or must be exempted by FMG)

The IG must be auto-building successfully on the CI build system with few / no errors (see below)

The agreed version number (see above) must be specified in all the conformance resources, and in the build control file as the version for the IG, and must appear as the specified version in the page header and/or footer

All IG dependencies and core version reference must be literal versions, not the special values 'current' or 'dev'

A set of history notes documenting the significant changes must be prepared. These may be in the IG, or in a separate document for the FHIR Product director to publish

Errors

The IG publisher reports many errors in the file qa.html. This will will be published so that any reviewer of the specification can check the status of the IG.
The FHIR Product Director will review the QA page before publishing, and discuss outstanding issues with the editors before publishing.

Implementation Guides can be (and have been) published with outstanding errors, either due to deficiencies in the tooling, or lack of time or authority on the part of the editors.
The FHIR Product Director works with FMG to set allowable parameters for such errors. If there are too many unresolved errors, FMG may not allow the IG to go to ballot.

Publishing process

This is the process for publishing the final implementation guides as followed by the FHIR Product Director

Create a Google worksheet to track the process of the IGs being published - links below. Start by entering the following:

Realm

Code

GitHub source URL

Final web page destination (version specific)

Package ID

Version of FHIR it is based on

Version of IG itself

dependencies and versions

Editor contacts

Check that all the publication checks in the previous sections have been made

Check that history notes are available

Check that the guide builds ok, and review errors with editor

Do a build, and check for unexpected terminology errors in qa.html

Check that there are no references to build.fhir.org and fix/repeat previous step until there are none

Edit the templates for the IG:

Ensure that the title+ header reflect the ballot/publication status

Add a head status bar using html like below

Ensure that the footer has the right content and links - in particular, history links to the cross version history page ([canonical]/history.html)

Build again, and repeat previous step until all pages are correct

Final build with -publish [url], using the url from above (IG will be the same, but package will be production package, not current)

Copy output into correct location on the local copy of the FHIR website

Update the history.html for the new version

Upload the new content + history.html to the hl7.org server (or fhir.org, if FHIR foundation content)