Versions Compared


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

This page will be used to post CTO and project team updates related to the implementation of Confluence and Jira Collaboration software at HL7.

March 2020 CTO Tooling Update

A lot has happened since our last update, and the world is changing before our eyes in the face of a pandemic.  I have sent out some recent emails and posted a general tooling update on The Standard that summarizes recent developments with introducing Zoom, merging our chat streams, and other activities to continue our simplification initiative throughout HL7.  This blog post also discusses our plans to implement UTG this spring and expand rollout of JIRA for all issue tracking and eventually to support balloting.  While our transition to Confluence is now complete, we're still working to relocate a few more Wikis, and new pages have been created to support tooling activities (like use of Zoom) as well as to collect useful information relevant to HL7's response to the COVID-19 crisis. Confluence continues to be our source of truth, with new reference sites like the FHIR Accelerator Reference Page and new Co-Chair Handbook.  

We'll continue to be providing additional tools, tips sheets and training materials to help you make the most of your precious time with HL7.

November 2019 CTO Tooling Update

JIRA Updates:

As promised, we have now scheduled the migration of FHIR tracker items from GForge to JIRA for this coming weekend, November 15-17. We expect to be using JIRA exclusively for FHIR tracking tickets by Monday, Nov. 18.  

To ensure that we migrate all Tracker items to JIRA, FHIR GForge Tracker will be locked to read-only at precisely 8pm EST on Friday, November 15 - no one will be able to enter or update FHIR tracker items in GForge after that time so we can ensure all content is migrated to JIRA.  

For those of you who are new to JIRA, a set of brief webinars on the basics of using JIRA have been posted at .  We believe you’ll find JIRA to be intuitive and natural, but we’ll be adding additional documentation and tips over time to this page to help improve your experience.  

In the future, all HL7 work groups and projects will be expected to use JIRA as our standard issue tracking tool. We will not be supporting use of GitHub tracking, so any projects using that are advised to begin transitioning to JIRA.  Once the FHIR migration is completed, we’ll be getting in touch with other WGs to complete migration of any remaining GForge Tracker items.  

So this is an exciting milestone in our quest for improved tooling at HL7.  I’d like to especially thank Lloyd McKenzie and the JIRACon team (Lorraine Constable, Jean and Marc Duteau, Josh Procious, David Johnson and Patrick Lloyd  in particular) for making this migration possible.  And thanks to those of you who cleared up your remaining Tracker items in time to allow this to proceed as planned.

September 2019 CTO Tooling Update


  • A Working Group Meeting Information page is now available for the Atlanta WGM and will be updated for all future WGMs.  This includes links to individual WG agendas as well as other general information (such as eb Seaid to first-timers).  This page is consistent with the EventMobi app.
  • The Confluence and JIRA apps are being migrated to Amazon Web Services cloud hosting, which will improve availability and scalability.
  • Testing of JIRA to replace Tracker has been successfully completed.  The TSC will soon release plans for migrating issue tracking from Tracker to JIRA later this year.
  • Additional spaces have been recently defined for several new Accelerator projects and other initiatives. 
  • Remember to check for other news updates.

June 2019 CTO Tooling Update