Process for Publishing a FHIR IG

Publishing a FHIR IG

This process is followed by anyone when publishing a FHIR IG to http://hl7.org/fhir/

Pre-conditions

To follow this process, you must have:

• permission from the FHIR Product Director to publish FHIR IGs (including write access to the google sheet)
• permission from FMG+TSC to publish the particular FHIR IGs
• an FTP acccount with access to the source for http://hl7.org/fhir

Record Keeping

All publication runs must be recorded in the google spreadsheet at https://docs.google.com/spreadsheets/d/1SRxxwA5GSJNx93oXUNTSPqbL19yeBYrNCCQAZ0sp0CI/edit#gid=0

When you being processing the publication request, create a new row in the sheet, and add the following columns:

• Operator : Your name
• IG Name : The formal name for the ballot or publication request
• IG Source : The github repository URL where the source is located - Check that the repository URL is HL7 (or an other wise approved Organization - consult CTO for approved list)
• Primary Editor : the name of the editor who will handle any QA issues
• IG approval: The URL of the wiki page that FMG Approved for the proposal of the IG (if there isn't one, consult the FHIR product director)
• new IG : "yes" if this is the first time that any version is being published for this IG (whatever version - draft or ballot)

Checks

The following checks must be run:

• TSC Approval: check that TSC has signed off on the publication, and record "yes" in the spreadsheet
• Realm: add the realm code identified in the IG approval page. Check that this is consistent with the stated scope of the ballot and in the TSC approval
• Code: add the code as identified in the IG Approval page (note that the name of the github repository does not need to be the same)
• fill out the canonical (http://hl7.org/fhir/{realm}/{code}) and packageId (hl7.fhir.{realm}.{code}) values.
  • If this is is a new IG: Look up the URL {canonical}/package-list.json and check that it doesn't exist
  • if this is not a new IG: Look up the URL {canonical}/package-list.json and check that the canonical url and packageId and the name of the IG in the package list agree with the details for the IG (canonical and packageId must be identical, name can vary a little).
• Find the IG (based on it's github URL org and name) in https://hl7-fhir.github.io/auto-ig-builder/builds.html, and check that the IG was built in the last 24 hours. If not, rebuild it. Wait for it to rebuild (refresh the page, or watch https://chat.fhir.org/#narrow/stream/179297-committers.2Fnotification)
• now check the qa page (rightmost link on the IG Builds page).
  • check that the packageId and canonical URL in the first line are correct against the spreadsheet, and check that the stated path starts with {canonical}
  • Review any errors in the page, paying particular attention the publication QA checks at the top
  • If there are any errors, refer to the FHIR product Director for approval
  • Once ok, record "yes (N)" in Build QA column, where N is the number of errors
• in the version column, record the version as stated in the first line (after the {packageId#} part
  • if this is a new IG: the version should be 0.1.0, or as approved by the FHIR Product Director
  • if this is a not a new IG: check that the FHIR Product Director has approved the version
• in the subdir column, record the subfolder stated in the publication path
  • If it does not conform to the pattern YYYYMMM (with the date correct) or STU{X}, check with the FHIR product director
• Now review the actual guide (left most link in the IG build page)
• Check that the header conforms to the FHIR Implementation Guide Publishing Requirements:
  • check that the header shows the name of the IG and the ballot status correctly.
  • check that the header shows the correct HL7 logo
  • check that the header includes the yellow publish box that displays correctly (don't worry about what it actually says)
  • if all checks out, "yes" in the header column
• Check that the footer conforms to the FHIR Implementation Guide Publishing Requirements:
  • check that the following items are shown in the footer: packageId, version, FHIR version, publishing committee, history link, propose changes link, Copyright (© 20YY+), generated date
  • if all checks out, "yes" in the footer column