An Implementation Guide (IG) is the mechanism that describes how FHIR is used to meet a specific Use Case or cases.

When creating an IG that is intended to be published under the HL7 infrastructure, there are a number of steps to go through as detailed here.

The ones where FMG (FHIR Management Group) approval is required are:

  1. Create a Project Scope Statement (PSS)
  2. Create an Implementation Guide Proposal (IG Proposal)
  3. FHIR IG Quality prior to ballot and publication
  4. Create a Publication Request

The details of the steps and the templates to use are described in other sections of this site – this page is intended as a high-level overview – and also points out specific issues you may encounter. It’s written from the perspective of the FHIR Management Group (FMG).

Process Flow

For more information on the process flow of an HL7 Project and a FHIR Implementation Guide, see New Project? Start Here.  For FHIR Implementation Guides, pay special attention to those processes identified as "FHIR Specific"

For more information, watch the "FHIR Implementation Guide Development: Navigating the HL7 Processes" Webinar.

Generic Timeline

The following provides a generic timeline for the tasks associated with the development and balloting of a FHIR IG.  These timelines should be considered as part of the project planning.

  • No labels


  1. where is the IG Proposal in this process? Isn't it required between PSS and Creating Content?

  2. Yes, it the IG Proposal must be approved by the NIB deadline.  If you go to the NIB page it is there.  I was trying to make this diagram more generic with the details in the subsequent pages.  I need to do some updates to the diagram so will take this into consideration when I do.

    1. well, the IG proposal is critical to the creation of the github repository, so it must happen before one can start creation of content, unless you are creating the content in a private space.

  3. Following on to John's comment, the IG proposal and connectathon participation are two key steps that if included on this diagram would be very helpful.

  4. Melva Peters is there a template for the IG Proposal?  Where can I find it?  Thanks!

  5. What is this timeline? I think it's an example of what might occur, but it isn't clear. Some of those dates have fixed relationships, but others are entirely variable. Does the TSC always approve a PSS 10 weeks after submission? What happens if it takes more (or less) than 26 weeks to complete the IG content? Also, it would be helpful to clarify in the page name that this is the HL7 process flow for IG publication; if you're not publishing through HL7, then none of this applies.

  6. Should this page have some mention of the Connectathon requirement?

    1. It does in the IG Maturity Step.

  7. Is it possible to update or remove broken link above:

    "FHIR Implementation Guide Development: Navigating the HL7 Processes" 

    Message: This webinar or its recording was removed. Please contact the organizer for more information.

  8. It would be great to see this timeline go past ballot reconciliation to include the publication request and then any subsequent reaffirmation or extension request.  Could this graphic also include links to the different forms you need to complete for each step?

  9. The "FHIR Implementation Guide Development: Navigating the HL7 Processes" Webinar has been removed. Is it temporary or permanent?

    Thank you for clarifying.

    I also want to acknowledge that instructions on developing a new IG are super helpful!


  10. Webinar recording under the Process Flow section seems to have been moved or removed: link doesn't work

    For more information, watch the "FHIR Implementation Guide Development: Navigating the HL7 Processes" Webinar.

  11. Joshua Procious , is there a new location to access the  "FHIR Implementation Guide Development: Navigating the HL7 Processes" Webinar?  Not sure if it expired or was moved, but when we attempted registering to access, we received a message that it was no longer available.  Thanks!  (cc: Alexandra Goss)