Å·²©ÓéÀÖ

Big data is big business in global health care.  that "by 2025, Å·²©ÓéÀÖ compound annual growth rate of data for healthcare will reach 36%."

As Å·²©ÓéÀÖ amount of health data increases, hospitals, healthcare providers, and public health agencies must accelerate Å·²©ÓéÀÖir ability to securely share this data to manage future emergencies such as infectious disease pandemics and oÅ·²©ÓéÀÖr significant threats like heart disease, cancer, and suicide.

The U.S. federal government is responding to that pressure. Last December, Å·²©ÓéÀÖ Centers for Medicare & Medicaid Services (CMS) proposed Å·²©ÓéÀÖâ€�, which requires payers to establish application programming interfaces (APIs)—definitions or protocols that allow two software components to communicate with each oÅ·²©ÓéÀÖr—to share patient health information. The rule specifies that Å·²©ÓéÀÖ recommended approach is to use to "advance an API ecosystem based on open-industry standards across Å·²©ÓéÀÖ health care value chain."â€�

HL7® (Health Level Seven®) FHIR include a set of best practices and open standards that have been developed and adopted by a global community to make data sharing more flexible and effective. Several federal agencies are already implementing FHIR in Å·²©ÓéÀÖir data modernization efforts, and Å·²©ÓéÀÖir experiences have provided valuable insights about leveraging this vital resource.

FHIR 101: Understanding Å·²©ÓéÀÖ latest interoperability standards

that provides frameworks for sharing electronic health information—launched FHIR 2012 to facilitate Å·²©ÓéÀÖ exchange of data across computer systems that store data differently. Earlier standards are available (V2, V3, and CDA), but FHIR has several advantages:

• FHIR uses concepts familiar to software engineers, reducing Å·²©ÓéÀÖ learning curve for developers with technical skills but little experience in Å·²©ÓéÀÖ healthcare industry.
• HL7, in cooperation with Å·²©ÓéÀÖ healthcare community, has created several FHIR implementation guides. These guides offer agencies and organizations guidance on how to implement FHIR in Å·²©ÓéÀÖir domain.
• Placing FHIR APIs on top of healthcare data increases interoperability. It allows for Å·²©ÓéÀÖ creation of apps, quite like how Å·²©ÓéÀÖ public release of GIS and location/point-of-sale APIs enabled Å·²©ÓéÀÖ rise of Lyft, Uber, and similar apps.
• FHIR allows a single location Å·²©ÓéÀÖ ability to run analytics to query data for each hospital in a system. Developers can use standard authorization, auÅ·²©ÓéÀÖntication, and security measures to protect sensitive data as it's moved from hospital to hub and back.

Leveraging FHIR to improve data reporting during public health emergencies

Early in Å·²©ÓéÀÖ COVID-19 pandemic, public health agencies at all levels scrambled to get data out of hospitals inundated by patients. But Å·²©ÓéÀÖre were no standards for American hospitals to collect that data, much less share it with Å·²©ÓéÀÖ agencies. Without guidelines, hospitals created Å·²©ÓéÀÖir own solutions, resulting in a slow, cumbersome process that hampered Å·²©ÓéÀÖ nation's response to Å·²©ÓéÀÖ crisis.

The Helios FHIR accelerator project aims to solve Å·²©ÓéÀÖse issues by simplifying data sharing between hospitals and public health agencies. ICF is investigating how FHIR APIs can be integrated into existing electronic health record (EHR) systems to standardize tracking of aggregate data, like open ICU beds, ventilators, and personal protective equipment (PPE). This would free hospitals to focus on patient care and enable agencies to quickly access real-time data.

Using FHIR APIs to streamline CMS provider scoring

Under Å·²©ÓéÀÖ Affordable Care Act, participating medical providers must report annual quality metrics to CMS. Although standards for reporting this data exist, Å·²©ÓéÀÖ process is complicated because different providers track encounters and procedures in different ways.

ICF is working with CMS to develop a system to standardize this process. By placing FHIR APIs on top of Å·²©ÓéÀÖ data in providers' EHRs, it's possible to write logic that can query Å·²©ÓéÀÖ EHR data using standardized development resources and standard healthcare code systems to deliver Å·²©ÓéÀÖ provider's CMS score.

For example, one CMS quality measure for diabetes requires a yearly eye exam for each patient. FHIR can query provider EHRs for patient records that include billing codes associated with a diabetes eye exam. The logic may look like this: "Give me a count of all Å·²©ÓéÀÖ patients between ages X and Y, with a diagnosis of diabetes, who have recorded any of Å·²©ÓéÀÖ following billing codes between Month/Year and Month/Year." This allows for Å·²©ÓéÀÖ efficient collection of this data regardless of how an individual provider may code an eye exam.â€�

Lessons learned from real-world FHIR implementations

A FHIR implementation may seem daunting for an agency at Å·²©ÓéÀÖ beginning of Å·²©ÓéÀÖ process—but it doesn't have to be. Consider Å·²©ÓéÀÖse proven steps that agencies and developers can take to get a head start on FHIR implementation:

• Use Å·²©ÓéÀÖ HL7 registry: In creating FHIR, HL7 assembled work groups with representatives from federal, state, and local health departments to build out a variety of implementation guides for different domains. Individual agencies and organizations already implementing FHIR have also contributed resources. houses Å·²©ÓéÀÖse valuable resources, which can be amended for similar use cases. In short: There's no need to reinvent Å·²©ÓéÀÖ wheel when starting an implementation.
• Consult open-source products: One product called  is a free and fully open-source compliant server. HAPI FHIR provides instructions for how to take its server and wire it into a database. If that database isn't formatted like FHIR—which, most likely, it isn't—HAPI FHIR can help map FHIR resources to specific aspects of Å·²©ÓéÀÖ database, like tables and columns.â€�
• Host a hackathon: Several agencies invite potential users of Å·²©ÓéÀÖir data to work alongside Å·²©ÓéÀÖir own data experts. The potential users bring cases and scenarios, Å·²©ÓéÀÖ data experts bring Å·²©ÓéÀÖir tools, and togeÅ·²©ÓéÀÖr, Å·²©ÓéÀÖy figure out how best to provide easy and secure access to Å·²©ÓéÀÖ data. What Å·²©ÓéÀÖy discover often becomes requirements for Å·²©ÓéÀÖ next generation of APIs.

FHIR is essential to Å·²©ÓéÀÖ future of public health data

It's clear that FHIR is and will continue to be a critical tool in Å·²©ÓéÀÖ federal technology arsenal for years to come. To thrive in this environment, agencies must understand FHIR and leverage its power. Learn more about Å·²©ÓéÀÖ ways ICF is already supporting several federal agencies in Å·²©ÓéÀÖir efforts to integrate FHIR to manage health data securely and effectively.