Page tree
Skip to end of metadata
Go to start of metadata

Print a copy of this for your project

Project Tasks

Project Category
  • Identify work to be undertaken . Work at HL7 can only be advanced when there is a Project. Work with your accelerator to determine what Work Group should sponsor your work and what Work Groups should co-sponsor. Make sure your team has subscribed to the Sponsor and Co-Sponsoring Work Group's main Listserver. Contact your Accelerator for instructions.
  • Identify the name of your project. Check to see if there are other project with similar name to make sure it is clear what your project is about.
  • See the  Project Scope Statement Checklist  for assistance in preparing a Project Scope Statement and the following for additional information:
  • Make sure the person on your team creating the Project Scope Statement has a HL7 Confluence User ID. This can be done on the main HL7 Confluence page .


Create a Project Scope Statement and follow the instructions on the screen.  Instructions

  • Forward the Project Scope id to the Work Group Co-chairs and ask for time on their next conference call.
  • Note: All work developed external to HL7 must be reviewed by the Architectural Review Board (ARB) before the Work Group can advance the work (Governance and Operations Manual (GOM).


  • Make sure members of your team will be available for the call. Be prepared to explain your project in 10 minutes or less. At the end of your presentation make a motion to have the Work Group Sponsor the project.
    • For complicated projects, develop a presentation of 3 to 4 slides that help explain the project.
    • Verify with during the call with the sponsoring Work Group that co-sponsors are appropriate (Do not be afraid to ask why to any request made by the Work Group. They will explain what HL7 process they are following and how it impacts your work).
Preparing for project conversation
  • The Work Group will not advance projects until all co-sponsoring Work Groups have approved their engagement.
    • Email each Co-Sponsor Work Group co-chairs requesting agenda time on their next conference call.
    • Co-Sponsor Work Group will request the ability to sign-off before advancing your project or just notification. Make sure to note the expectations of each Work Group.
    • Now maybe a good time to get on the ARB agenda if your project has been externally developed outside HL7 Work Groups.

Preparing for project conversation

Preparing for the Steering Division (SD). The sponsoring Work Group Co-chairs may ask you to join them on the call with the Steering Division when your project is presented. They will share with you the call in information. Make sure your project is updated with the SD approval.

Preparing for project conversation

Preparing for the Technical Steering Committee (TSC) approval call. It is rare, but sometimes your team maybe asked to join the TSC call when your project is being presented. Make sure your project is updated with the TSC approval.

Preparing for project conversation

Begin your work (4 steps).

1. Committer Preparation

2. Local Build and Content Development

3. FHIR IG Quality Criteria

4. Submission

Project Development or updates for ballot

Notice of Intent to Ballot (NIB) . Follow the checklist. 

Ballot preparation

Ballot Reconciliation. Final Ballot Reconciliation must be reviewed and approved by the Sponsoring Work Group. Work developed outside of HL7 can be reviewed, proposals developed to resolve negative comments, and the artifact can be updated only after the Sponsoring Work Group have approved ballot reconciliation. See the ( Governance and Operations Manual (GOM) for the requirements of ballot reconciliation by ballot type.

  • Comment Only Ballot - GOM Section 13.03
  • Informative Ballot - GOM Section 13.01
  • Standard for Trial Use Ballot - GOM Section 13.02
  • Normative Ballot - GOM Section 15.0

Ballot Reconciliation

Publication Request. This checklist defines the steps to publish the ballot after it has been reconciled. Follow the checklist (9 steps). 


Reaffirmation Ballot . All ANSI approved standards are required to be reaffirmed every 5 years from the date of publication as noted in the ( Governance and Operations Manual (GOM). The Sponsoring Work Group will receive notification about 3 Working Group Meetings prior to expiration of the standard.


Project Tasks

Project Category

  • No labels