The Standard

Déjà Vu All Over Again

My last tooling update was titled Focus on Finishing. Thus, in homage to the inimitable Yogi Berra, it would be hypocrisy to change focus now. Focus on Finishing is still the principal theme for the year, building on essentialism, my other guiding light, as expressed in the axiom “Do less, better.”

Toward that end, we continue to move ahead with our transition to our core collaboration tool stack and processes based on workflow-driven online forms. As of this writing, we’re completing final improvements to make the online PSS available to all later this spring. We’ll be working to finish automating most other key form-driven processes after that.

In addition, we hope to finish our transition to a new JIRA-based balloting system, which is also being piloted as of this writing. This, together with the recent transition from GForge Tracker and the STU Feedback web page to JIRA, puts all of our specification feedback in one repository moving forward.

While finishing our transition for balloting is critically important, we also have to update and replace some peripheral systems supporting the balloting process for members, as well as our core business systems for managing membership, events and operations. While we don’t expect to complete this transition to a new Association Management System before the end of 2021, we’ll be focused on finishing this as rapidly as possible since it’s an essential foundation to further systems improvements for the HL7 organization.

Doing Less, but Better

Imagine you’re struggling in a long race – maybe an ultra-marathon over a winding, hilly course. You’ve been running for many hours, and you’re tired, sore and hungry. You’re running up a hill, hoping the end will soon be in sight. But when you get to the top, you only see a turn, not a finish. And after that turn – oh, no! – another hill. We’ve had that feeling during the long pandemic, and, for some of us, we’ve had that feeling even longer with respect to tooling at HL7. We’ve covered a lot of ground, and climbed a lot of hills, and we can feel the end should be in sight very soon. But we’re still running.

Fortunately, we have a team of supporters handing out Gatorade, clapping and cheering us on, and we’ve got our fellow runners pulling us along. And so it is with the HL7 community. We ask a lot of you to help us move forward, with support and understanding; sometimes contributing your valuable time to help us with development or testing, or to struggle patiently with change and the unexpected discoveries of new technology rollouts. While we don’t see that finish line yet, we see plenty of blue skies and greener fields beyond. We won’t always make it on the podium, and sometimes we stumble along the way. But the important thing is to keep moving forward and getting better.

The View from Above

We may not always seem to be progressing very fast, but we’ve really come a long way in the last few years thanks to the important contributions of many of you as well as the ongoing generous support of the US Office of the National Coordinator for Health IT (ONC), which has funded many of our retooling efforts. To list a few prominent examples:

Doing Less, but Better

For many of us, this desperate pandemic year has led to plenty of introspection.  This has also been true for the HL7 Board, which has been contemplating the future of the HL7 organization after emerging from the current crisis. Among a set of core principles adopted by the Board are agility and focus. To be agile, we need to simplify and refine the organization and core processes as well as provide support with continued improvements to our tooling. This also requires getting our global community to better understand and use the processes more consistently and effectively, so we can better focus on our core work of developing and implementing interoperability standards.  This a perfect segue back toward my long-held core belief in essentialism.

Back to Basics

I first espoused the concept of essentialism to an enthusiastic Board and Technical Steering Committee back in 2016. While we’ve only made small incremental progress in the four years since, it has been guiding our process improvement and tooling initiatives. Essentialism was a driving force behind our adoption of Confluence and JIRA as well as efforts to simplify our product portfolio. Of course, we operate in a complex field, and there were many confounding forces acting at the same time. The HL7 community is more adept at introducing new processes, tools and content than at retiring or eliminating the old stuff. Thus, our commitment to essentialism faded over time, tempered by inertia and continuing demands, not the least of which has been the black swan events of 2020.

Perhaps it’s time to once again review the key elements of essentialism and discuss how it fits with our ongoing tooling strategy and plans.

Keeping Us Together While Apart

During this time of global crisis, it’s worth remembering the critical importance of what we at HL7 are doing to improve global health by making health information more available and useful. While so many are struggling with social distancing, we already have a culture that long ago learned to work together remotely on our common goals. But now with fewer opportunities to meet together in person, we need to move ahead to finish much of the work we’ve been doing over the past few years – so we’re better prepared to work together even more effectively, while knowing we must be further apart geographically.

Join Our Webinar on May 22, 2019 at 12 pm Central!

API 101: An Introduction to APIs and How They Are Transforming Health IT

Webinar speakers and blog authors:

Wayne Kubick, HL7 CTO
John Orosco, CTO, Sansoro Health
Dave Levin, CMO, Sansoro Health

Application program interface (API) technology has transformed the digital economy and is now poised to do the same in health IT. The combination of the an increasingly robust HL7 Fast Healthcare Interoperability Resources (FHIR®) standard API and the rules proposed by ONC on interoperability will accelerate this trend. What should you know before diving in? Tune in to our live webinar on Wednesday May 22 at 12pm CT.

 APIs allow software applications to connect, communicate and collaborate through a combination of web services. This harnesses the power of internet “backbone” communication protocols to provide a secure channel for connecting two applications and standards like JSON and XML that provide data-interchange formats or “objects.”

APIs also allow businesses to collaborate more seamlessly. For example, businesses that ship packages via UPS can leverage the UPS API to easily track shipping status. This API hides the complexity of the UPS database and business logic. It’s an open API that is exposed to the world so almost anyone can use it. Simply register, learn how the API works and connect and your system can interrogate the UPS API, instantly retrieve the current status, and display it to your customers on your website or app.

Our ongoing tooling journey at HL7 continues, neither as a sprint nor a marathon.  For us, it’s really more like an odyssey – an ongoing journey where there is always something more to be done, another path to explore, and a final destination (retirement, for example) seems far out of reach.  In the case of HL7 tooling, a fair number of tooling retirements are well overdue.   

Despite the wait, it’s gratifying to see when tangible progress is actually achieved. On the Confluence front, we’re in the home stretch of phase 1 of the rollout, though there’s a whole new course to pursue just around the bend.  We now have all work groups on Confluence (!) and have also migrated many more projects, committees and collaborations. New functions and help features in Confluence (including a major facelift for confluence.hl7.org) are being added regularly, and you can keep up with these by checking the CTO Tooling Update page. This enabling platform is already unleashing many new opportunities within the HL7 community. Our next target is to work toward optimizing our processes with online forms and workflow. The online project scope statement (PSS) pilot is now available and will give us an opportunity to speed up reviews and approvals as well as make new projects more visible to the community in the hope we can avoid last minute catchups. 

Every good story has a beginning, middle and end. First, we get hooked on the opening, which drives us ultimately towards a conclusion, but the real time and effort comes along the way.  While the middle is where most things happen, we can sometimes feel like we’re in a holding pattern there – until something tangible finally happens that directly affects what we do. 

This rings true with HL7’s transition to our new collaboration tooling environment built on Confluence and JIRA. The good thing is that we’re making steady progress on multiple fronts, with many more work groups in Confluence and the killer apps of JIRA Ballot and Unified Terminology Governance (UTG) becoming more palpable. On the other hand, we’re clearly still en route, perhaps able to imagine but not yet actually taste the promised rewards. This is understandable, since the mission of HL7 is the creation of standards, not the creation of tooling to help us achieve that. However, it’s tooling that directly affects us in the ways we develop HL7 standards.

You may have noticed that the HL7 website has a new look and feel. 

The newly launched public homepage is one component of a broader website redesign project with an overall focus to enhance the most widely used and frequently visited sections of the HL7.org.

We hope this redesign will:

• Better highlight the value and benefits offered by HL7 to the healthcare community
•  Increase the visibility of education and membership opportunities
• Support HL7 mission, vision, strategic goals and initiatives
• Provide new users with an appealing, responsive and mobile-friendly experience

 
Achieving healthcare interoperability at any level, by definition, requires at least two parties working together. Achieving it on a global scale requires a shared dedication of the many to the common good.  Consider the vision statements of two organizations:

• HL7 International: “A world in which everyone can securely access and use the right health data when and where they need it.”
• IHE International: “Enable seamless and secure access to health information that is usable whenever and wherever needed.”

The journey to an improved collaboration tooling infrastructure continues. My last update focused on the goal to make the Atlassian Confluence Wiki and Jira Issue Tracking tools available for use by HL7 work groups. These tools are now available for pilot use and are a sample of the myriad of benefits these tools may offer our global community.