Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.




Over the next few months we will be moving to the use of JIRA for capturing all specification feedback.  This will align with the way that FHIR currently captures feedback.

As part of the migration, we will also be moving the capture of STU Comments to JIRA.  We will import all active STU’s and their comments to JIRA, but need your help in identifying any expired STU’s with comments that should be imported into JIRA. We don’t want to migrate all of the expired STU’s with comments unless they are needed. There will be a way to continue to view the expired STU Comments for specifications if needed, but if your Work Group is still working through the comments submitted, we would like to identify those specifications and migrate to JIRA.

Please review the following spreadsheet of expired STU’s (you can sort or filter the spreadsheet by your Work Group) and identify only those specifications to migrate.  Expired STUs with Comments for WG Review.xlsx

If your Work Group is not the sponsor for one of the specifications identified, please send an email to


The HL7 Essentials Page is now live. This page is designed to be a source of truth for all HL7 Leadership (co-chairs) announcements! This is the place to find information about HL7, HL7 processes and other information that is relevant to your work as an Co-Chair, Facilitator, Accelerator or anyone with an interest in gaining a basic understanding of the HL7 organization and it's processes. 


The second UTG session geared towards the HL7 community can be found at the links below:

HL7 Education on Demand (free access):

HL7 YouTube:

July 29, 2020
"File Storage - S3 Connector" pages have been added to each workgroup space. For now these are placeholders as we finalize the process. Please do not request access at this time. When they are finalized they will be opened up and an announcement will be added here. July 15, 2020still draft state

The HL7 Calendars page now has the ability to sort items on the "All HL7 Calendars" tab by going to the top right drop-down arrow on the calendar and selecting your choice of calendars to display. 

June 23, 2020

Co-Chair Meeting Slides found here: Co-Chair Webinars

June 1, 2020
Short Tutorials on Jira Basics including what Jira is, how to work with issues, and how to search can be found here: How To WebinarsMay 15, 1010

Project Proposals

The TSC is implementing a new Project Proposal process which is now available for use.  The goal of this process is to provide early insight for Work Groups into potential projects, to identify Work Groups who want to be involved as a sponsor, a co-sponsor or an interested party, and to identify if there are other projects underway in or outside of HL7 that overlap with the proposed project.  We want to enable project proponents to find a sponsoring Work Groups without the need to go from Work Group to Work Group until a sponsor is identified.

We are asking that newly-introduced potential projects start with a proposal before submitting the Project Scope Statement, but it is not mandatory at this point. At some point in the future, Project Proposals will be required for all new projects at HL7 that are producing Release 1 of an artefact but not for updates to previously published material.  Each proposal is expected to provide:

  • A description of the project with sufficient detail for reviewers to understand its intent and scope as well as the types of artefacts expected to be developed, and how much of the content is already created;
  • Potential sponsoring work group or work groups, if known; and
  • A target ballot cycle, if known.

This information is intended to eventually feed into a draft PSS form once accepted.

When a new proposal is created, Work Group Co-chairs will be notified via an email and an announcement will be made to the Announcements stream on Zulip.  The notification will provide a link to the proposal in JIRA.  Work Groups are asked to review and comment on the project using the following questions as a guide:

  • Does this project fit into my Work Group's Mission and Charter?
  • Is my Work Group willing to sponsor this project?
  • Is there an ongoing project(s) in my Work Group that are similar to this one that may overlap?  If so, provide details in your comment.
  • Is there a project(s) underway in other Groups that are similar to this one that may overlap? If so, provide details in your comment.
  • Are you aware of a project(s) outside of HL7 that may overlap with this project?
  • What other Work Groups should be considered as co-sponsors or interested parties?

Once the project is accepted (i.e. a sponsor is identified and no barriers to the project are foreseen), a Project Scope Statement (PSS) must still be created and approved through the current HL7 PSS processes. It is important to note that this project proposal does not replace the actual Project Scope Statement and is not sufficient for work to begin, but is intended to quickly give early visibility into proposed new work.  When a Work Group accepts being included on a project proposal, they are accepting that they will be a sponsor for the PSS.  Further discussion and agreement with the project proponent are expected to take place to determine the next steps for the actual project.

You can review the How To Documentation and How to Videos for Project Proposals on Confluence:  and view the submitted Project Proposals in JIRA

If you have any feedback about this new process, please add a comment to the Project Proposal Confluence page:

May 8, 2020

Recently there has been a large jump in size of attachments and duplication of such. This causes storage to be unnecessarily large and makes it harder to find the actual content users are looking for. Keep your spaces clean and organized by deleting old attachments/versions that you do not need anymore! Please check out this quick tutorial on managing attachments: 7, 2020