This wiki has undergone a migration to Confluence found Here
FHIR IG QA process
Revision as of 04:15, 21 August 2018 by GrahameGrieve (talk | contribs) (Created page with "Check list for publishing an IG: this is the checklist for publishing an implementation guide for ballot by HL7. You must know, at all times, 3 things: * the [wiki url] fo...")
Check list for publishing an IG:
this is the checklist for publishing an implementation guide for ballot by HL7.
You must know, at all times, 3 things:
- the [wiki url] for the wiki page the documents the IG approval
- [realm] - the realm code that is assigned to the IG e.g. uv or us - as documented on the wiki page
- [code] - the code that is assigned to the eg. core or adv-thing - as documented on the wiki page
When the NIB is submitted
- the IG must be approved by FMG
- check that realm on the NIB agrees with the realm as documented in the [wiki url], or FMG has approved a variation
Before Ballot Announcement
These check must be carried out before the ballot annoucement is made, and you must report to 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 be auto-building on the CI build system (see IG Publisher Documentation)
- The IG must have a canonical URL of http://hl7.org/fhir/[realm]/[code]
- the IG must have a package name of hl7.fhir.[realm].[code]
- you must have decided what the version number will be, following the normal version numbering policy, and have agreed this with the FHIR product director
Reasons for varying this exist, but must be approved by the FHIR product director on a case per case basis (noted on the IG approval page)