...
- permission from the FHIR Product Director to publish FHIR IGs (including write access to the [FHIR IG Publication Record])
- permission from FMG+TSC to publish the particular FHIR IGs
- an FTP acccount with access to the source for http://hl7.org/fhir
- permission to push changes to https://github.com/FHIR/ig-registry
- A local clone of the FHIR IG registry github repository https://github.com/FHIR/ig-registry to {registry}
- A local clone of the FHIR History Template github repository https://github.com/HL7/fhir-ig-history-template to {history}
- A local clone of the HL7 FHIR website Template GitHub repository: https://github.com/HL7/fhir-web-templates to {templates}
You must also know how to run the IGPublisher locally
...
- Zip up the folder {clone} as it is to a file named {packageId}#{version}.zip and ftp to ftp://hl7.org/fhir/ig-build-zips
You are now good to publish the IG
Publishing the IG
Note: This describes doing this as part of a batch, since this is a common case, but you can do the entire sequence for a single IG:
Do once for the batch:
...
Publish one IG at a time - finish the process for each IG before starting the next one.
- check that {registry}, {history} and {
...
- templates} are up to date (git PULL)
...
when all these are synchronised, do once for each IG:
...
- the title should match the approved title for ballot or the approved name in the IG Proposal
- the introduction should be copied in from the short description in the IG Proposal
- the category should be filled in, and generally matches one of those already in use at http://fhir.org/guides/registry/
create the destination folder in {root}
...
...
- run publisher.jar -go-publish -source {clone} -
...
- web http://hl7.org/fhir -registry {registry}\fhir-ig-list.json -history {history}
...
- -templates {templates} (If this process fails
...
- then consult the FHIR Product Director
...
Finishing the Publication Process
...
- )
- At the end of the run, the IG publisher will provide a directory. Use FTP to copy all the files from that directory to /implement/standards/FHIR on hl7.org, overwriting any that already exist.
- The IG publisher might give you a list of files to delete on the server too - these must be deleted
- mark "yes" in the
...
- Published column
...
- If this is a milestone publication, let Lynn know that it's time to mark applied tasks as published, and considered for future use tasks as open (see Administering Specification Feedback Projects#Publishingissues)
- check the changes to {registry}/fhir-ig-list.json (use git diff) and fill out any missing information (look for ?? in the changes)
...
- - may need to talk to FHIR product director to decide what to put
- commit and push the changes to the FHIR IG registry to github to a new branch, let Grahame know, & mark "yes" in the Register IG column
- If this is a milestone publication (not for ballots) make an announcement on the https://chat.fhir.org/#narrow/stream/179240-Announcements/topic/FHIR.20Publication.20Announcement topic in Zulip using the following template:
new Publication: [publication name] of the [IG Name] implementation guide: {canonical}/{subdir}FTP additional files:- {root}/package-feed.xml to ftp://hl7.org/fhir/package-feed.xml
- {root}/publication-feed.xml to ftp://hl7.org/fhir/publication-feed.xml us
e.g. New Publication: STU Update 3.2 of the QI-Core implementation guide: http://hl7.org/fhir/us/qicore/STU32/
Final steps. Note that if you are publishing more than one IG, do once for the batch:
- index.html
- uv/index.html
- check the changes to {registry}/fhir-ig-list.json (use git diff) and fill out any missing information (look for ?? in the changes) - may need to talk to FHIR product director to decide what to put
- commit and push the changes to the FHIR IG registry to github to a new branch, let Grahame know, & mark "yes" in the Register IG column