Nine years ago, Blue Button started as an idea:
Nine years ago, Blue Button started as an idea:
This week, we published the HL7 Domain Analysis Model: Clinical Genomics after a rigorous ISO/ANSI-compatible balloting process. The document is part of an ongoing effort by the HL7 Clinical Genomics Work Group to identify common workflows and use cases to facilitate scalable and interoperable data standards for the breadth of clinical genomics scenarios. The Domain Analysis Model (DAM) is becoming a widely used reference for clinical genomics, covering a myriad of use cases, including emerging ones such as preimplantation genetic diagnosis, whole exome sequencing, RNA-sequencing and proteomics.
As the global authority for interoperability in health care information technology with affiliates in 35 countries, we're excited to announce the publication of Release 4 of the HL7 Fast Healthcare Interoperability Resources (FHIR®) standard. This new version is the culmination of 18 months of extensive work to finalize the base parts of the specification and incorporates changes and enhancement requests received from implementation partners around the world.
"HL7 FHIR R4 is a beginning," said HL7 CEO Dr. Charles Jaffe. "It is the legacy of eight years of innovation and collaboration among a community of thousands around the world. It is a commitment from HL7 to create a platform from which Interoperability can someday emerge. It is a promise to provide reusable data across the continuum of biomedical research, patient care, and population health."
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.
New to Confluence? We've got you covered.
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:
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 is gearing up for a fall season that is chock full of flexible and convenient FHIR training opportunities for busy people like working professionals and students.
Reflections from an HL7 FHIR Applications Roundtable Presenter
When I was a little girl, I wanted to grow up and do something to make the world a better place for everyone. I thought about becoming a missionary, a doctor or a teacher. Eventually I became a computer programmer because I love solving problems with technology.
To solve big problems, collaboration with many people with varied backgrounds and skill sets is vital for success. This is why I love working with the HL7 FHIR community. HL7 brings together people from all over the planet with a single focus to improve the exchange of electronic health information. Each person brings their experiences and insights into solving real world problems in healthcare. Together we’re learning how to use and expand the HL7 FHIR standards to solve those problems.
The HL7 FHIR Applications Roundtable
I really enjoy the HL7 FHIR Application Roundtable events. These events give developers an opportunity to show us their creations. Seeing what others have built to solve specific problems encourages me about the future of healthcare.
I had an opportunity to showcase our new MyLinks application at a recent HL7 FHIR Applications Roundtable event. For almost two decades, my software company (PatientLink) built products to enable patients to send their information directly into an electronic health record as structured data. This helped doctors understand the patient’s history to provide better care for them. Then cancer changed everything. After experiencing many frustrations in trying to gather my personal records for my care, I decided it was time to build something for patients.
I felt there were three important things I needed.
This was the genesis for MyLinks: Linking patients to their doctors and their data, to each other and to researchers.
HL7 offers certification in its primary standards for health information technology including Version 2 (V2), Version 3 (V3), Clinical Document Architecture (CDA®) and HL7 Fast Healthcare Interoperability Resources (FHIR®). The testing is designed to help professionals achieve industry-recognized levels of proficiency and expertise.