The world's leading automated proofreading software

Calculate Your ROI with TVT  |  Help Centre   |   Contact Sales

FHIR: Transforming Product Labeling

Published By:

Mike Baird
6 minutes read
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Table of Contents

The shift from paper-based to digital processes has opened enormous opportunities in the healthcare sector in terms of data sharing and content management. But data can only be shared efficiently and add value if systems can “talk” to each other. The term we use for how compatibly systems work together is “interoperability.” Traditionally, the healthcare sector has suffered from a high lack of interoperability. [1]

What is interoperability?

When we talk about interoperability in the healthcare sector, it is useful to break it down into several different types:

  • Technical interoperability:
    Applications and infrastructure linking systems, including Application Programming Interfaces (APIs), which allow disparate systems to exchange information and functionality [2]
  • Syntactic and semantic interoperability:
    How data is structured and formatted across systems (syntactic), and the consistent context and meaning of data, such as terminologies, nomenclatures and ontologies (semantic).
  • Organizational interoperability:
    Business processes must be organizationally compatible with each other, otherwise interoperability will collapse into chaos (at worst) or lack efficiency and cohesion (at best). In almost everything we do in business; we require organizational interoperability. [3]

Areas in which interoperability offer the most potential include; electronic health records (EHR; e.g. referrals, doctor visits), electronic medical records (EMR; e.g. diagnoses, medications), and Structured Product Labeling (SPL), along with other data for clinical and administrative purposes in healthcare.

What is FHIR?

FHIR (pronounced “fire”) stands for Fast Healthcare Interoperability Resources and has its origins in Melbourne, Australia, when around 2011 the scientist Graham Grieve [4] set out to overcome shortfalls he saw in existing approaches. 

FHIR Fast Healthcare Interoperability Resources

Working with a team and community, he developed an early version of the FHIR framework. He and the teams did this through the existing health standards framework HL7 (Health Level Seven), from Health Level Seven International, a non-profit organization dedicated to developing standards for the interoperability of health data [5]

A shortfall often levelled at HL7 in its traditional versions has been data sharing limitations. This became all the more challenging with the growing use of smartphones, wearables and the constantly expanding range of healthcare apps. These presented technical challenges for the traditional HL7 framework standard. A significant problem that Grieves also saw with traditional HL7 was how vendors implemented it, resulting in inconsistencies.

It was the perfect moment for an innovative and advanced solution – one based on technical standards widely used in contemporary technology, and sufficiently future-proof to take into account the latest developments in digital healthcare applications. [6]

Moving to FHIR and APIs

Traditional HL7 interface engines, built on protocols like Transmission Control Protocol (TCP)/Internet Protocol (IP), generally lack the flexibility, scalability, and compatibility needed to integrate with modern web-based systems. An API based system – essentially, a set of rules that allows different systems to interact and communicate – offers more interoperability and flexibility in this regard. [7]

FHIR also offers the opportunity to move to a more patient-centric approach, because it allows patients and healthcare professionals to access data easily via apps, across different healthcare providers and geographies. As result, patient data is more transparent, more available.

When combined with the platform SMART (Substitutable Medical Applications, Reusable Technologies) – generally called “SMART on FHIR” – developers have been able to create a strong range of healthcare applications that are interoperable across many different health IT systems.

For example, SMART on FHIR opens the way for patients to have a personal health record (PHR) via an app on their smartphone, along with an electronic health record and electronic medical record that contains all information from different health providers (i.e. visits, treatments from different specialists, etc.). Changes to the EHR and EMR might be synchronized with the app, in some cases allowing the patient to view the EHR/EMR. Apple’s Health app is a form of this and uses SMART on FHIR APIs. [8]

This also involves obvious organizational and legal questions of interoperability, especially in regards to data privacy. Policies and processes must therefore ethically keep pace with the technical, syntactic and semantic aspects.

Next level interoperability

FHIR is gaining widespread attention both among regulatory bodies and – as the growth of healthcare apps shows – in the medical and patient community itself. Significantly, it plays a key role in the US 21st Century Cures Act as FHIR and SMART on FHIR are the minimum conformance standards under the act. Furthermore, as well as stipulating how user authorization is performed and how apps launch, it forbids information blocking by EHR and FHIR providers. [9]

This is causing a shake-up in the healthcare ecosystem. Acceptance of the Act by some EHR vendors and hospital systems has apparently been lukewarm at best. “Intense lobbying against the rule, preceding its release, by EHR vendors and hospital systems signals that control over data and revenue are both at stake. The rule not only enables patient and provider access to medical record data in computable formats but also shifts how they interact with the health care system, which entities control those interactions, and the underlying business models that could either threaten or accelerate interoperability’s potential to improve care delivery.” [10]

Interoperability is therefore raising some very significant commercial questions.

FHIR from a regulatory perspective

Through its CBER-CDER Data Standards Program action plan, the FDA is engaging strongly with FHIR on several levels. [11] The CBER-CDER strategy is all about having comprehensive data standards in place that facilitate the pre- and post-market regulatory review process. Significantly, as part of its project in the area of Identification of Medicinal Product (IDMP) standards – a set of five ISO standards to identify and describe medicinal products [12, 13] – FHIR is foreseen as the standard for global information exchange. It is working together with the European Medicines Agency (EMA) on this project.

Across the Atlantic, EMA also outlines its clear commitment to FHIR when it reiterates that EMA, the FDA and the European medicines regulatory network are “working with Health Level Seven (HL7) to incorporate the ISO IDMP standards into the FHIR specification.” [14]

This is integral to EMA’s Substance and Product Data Management Services (SPOR) programme for managing centralized master data in compliance with ISO IDMP standards. [15, 16, 17] SPOR has four domains. In its Product Management Services (PMS) domain, HL7 FHIR “replaces the current data submission format, the eXtended EudraVigilance Product Report Message (XEVPRM).” [18]

How FHIR is transforming product labeling

Structured Product Labeling (SPL) is one of the most important areas in which FHIR is set to have an impact (see Part II of our series on structured content here]. This XML format (HL7 version 3 SPL) for the exchange of information is the current standard for a range of key FDA drug filings. While FHIR has not yet been introduced, “FDA is working towards replacing Structured Product Labeling (SPL) with HL7 FHIR.  The FDA has created a proof-of-concept system that can receive labeling information using either SPL or FHIR standard (Dual Submission) in addition to a draft Implementation Guide (IG).” [19]

The SPL specification has enormous strengths in terms of semantic and syntactic interoperability, but the strength of FHIR is its technical interoperability across devices and systems. This is crucial when using different devices in the age of electronic labeling (e-labeling), as well as for being able to automate workflows. SPL and its Canadian counterpart, the Structured Product Monograph (SPM), have created windows of opportunity for automation, and FHIR builds on these.

We can see this as the next level in the exchange of information, which began with the nervous exchange of duplicate hardcopy filings and time-consuming manual review by the FDA in a pre-electronic age, then advanced to the age of electronic submission in SPL format, and now has reached the age of FHIR. In brief, the benefits we are already seeing are:

  • Cost and time efficiencies through the better exchange of information
  • Greater potential for scalability
  • Risk mitigation through automation of workflows and processes (information must not be transposed, rewritten or otherwise manually replicated)
  • Empowerment and ownership for patients, physicians and other stakeholders through the availability of information
  • Information exchange across different devices and media

 In Europe, FHIR in regulatory action can already be seen in EMA’s pilot project on electronic product information (ePI), which began in July 2023. This FHIR-based pilot covers “authorised, statutory product information for medicines (including the summary of product characteristics, package leaflet and labeling) adapted for handling in electronic format and dissemination via the web, e-platforms and in print.” [20] The results of the project can already be accessed on its ePI portal. [21]

FHIR represents a significant step in how we manage, and exchange information and it has rapidly gained acceptance. While regulatory bodies are exercising caution and the required due diligence in implementing FHIR, it features in many different aspects of their planning. HL7 International is working closely on supporting the FDA on future implementation of HL7 Structured Product Labeling (SPL) standard using FHIR. [22] Similarly, in Europe we are seeing its implementation in key regulatory areas of healthcare, including e-labeling. In the commercial arena, it is already changing the face of healthcare.

Read Part I and Part II in our series on structured content.

  1. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6702215/
  2. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9030107/
  3. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6702215/
  4. HIStalk Interviews Grahame Grieve, FHIR Architect and Interoperability Consultant – HIStalk (histalk2.com)
  5. http://www.hl7.org/about/index.cfm?ref=nav
  6. https://fire.ly/blog/what-is-fhir/
  1. https://www.linkedin.com/pulse/evolution-healthcare-data-exchange-embracing-api-systems-jed-horning-6xhue/
  2. https://www.apple.com/healthcare/health-records/
  3. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7762678/
  4. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7762678/
  5. https://www.fda.gov/media/176436/download
  6. https://www.fda.gov/media/176436/download
  7. https://www.fda.gov/industry/fda-data-standards-advisory-board/identification-medicinal-products-idmp
  8. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview
  9. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview
  10. https://spor.ema.europa.eu/sporwi/
  11. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview/substance-product-organisation-referential-spor-master-data/substance-product-data-management-services#data-standard-for-information-exchange-12041
  12. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview/substance-product-organisation-referential-spor-master-data/substance-product-data-management-services#data-standard-for-information-exchange-12041
  13. https://www.fda.gov/media/176436/download
  14. https://www.ema.europa.eu/en/human-regulatory-overview/marketing-authorisation/product-information-requirements/electronic-product-information-epi#eu-epi-common-standard-14451
  15. https://plm-portal.ema.europa.eu/ePIAll
  16. https://build.fhir.org/ig/HL7/fhir-spl/branches/main/index.html

 

 

 

Do you want to find out more about how your proofreading life can be easier? Get in touch and we’ll tell you all about it.

Share this article

Mike Baird profile picture

Mike Baird

Director of Product Management, Schlafender Hase

Mike is the Director of Product Management for Schlafender Hase.

Learn More

Follow Us

Subscribe to our blog

The shift from paper-based to digital processes has opened enormous opportunities in the healthcare sector in terms of data sharing and content management. But data can only be shared efficiently and add value if systems can “talk” to each other. The term we use for how compatibly systems work together is “interoperability.” Traditionally, the healthcare sector has suffered from a high lack of interoperability. [1]

What is interoperability?

When we talk about interoperability in the healthcare sector, it is useful to break it down into several different types:

  • Technical interoperability:
    Applications and infrastructure linking systems, including Application Programming Interfaces (APIs), which allow disparate systems to exchange information and functionality [2]
  • Syntactic and semantic interoperability:
    How data is structured and formatted across systems (syntactic), and the consistent context and meaning of data, such as terminologies, nomenclatures and ontologies (semantic).
  • Organizational interoperability:
    Business processes must be organizationally compatible with each other, otherwise interoperability will collapse into chaos (at worst) or lack efficiency and cohesion (at best). In almost everything we do in business; we require organizational interoperability. [3]

Areas in which interoperability offer the most potential include; electronic health records (EHR; e.g. referrals, doctor visits), electronic medical records (EMR; e.g. diagnoses, medications), and Structured Product Labeling (SPL), along with other data for clinical and administrative purposes in healthcare.

What is FHIR?

FHIR (pronounced “fire”) stands for Fast Healthcare Interoperability Resources and has its origins in Melbourne, Australia, when around 2011 the scientist Graham Grieve [4] set out to overcome shortfalls he saw in existing approaches. 

FHIR Fast Healthcare Interoperability Resources

Working with a team and community, he developed an early version of the FHIR framework. He and the teams did this through the existing health standards framework HL7 (Health Level Seven), from Health Level Seven International, a non-profit organization dedicated to developing standards for the interoperability of health data [5]

A shortfall often levelled at HL7 in its traditional versions has been data sharing limitations. This became all the more challenging with the growing use of smartphones, wearables and the constantly expanding range of healthcare apps. These presented technical challenges for the traditional HL7 framework standard. A significant problem that Grieves also saw with traditional HL7 was how vendors implemented it, resulting in inconsistencies.

It was the perfect moment for an innovative and advanced solution – one based on technical standards widely used in contemporary technology, and sufficiently future-proof to take into account the latest developments in digital healthcare applications. [6]

Moving to FHIR and APIs

Traditional HL7 interface engines, built on protocols like Transmission Control Protocol (TCP)/Internet Protocol (IP), generally lack the flexibility, scalability, and compatibility needed to integrate with modern web-based systems. An API based system – essentially, a set of rules that allows different systems to interact and communicate – offers more interoperability and flexibility in this regard. [7]

FHIR also offers the opportunity to move to a more patient-centric approach, because it allows patients and healthcare professionals to access data easily via apps, across different healthcare providers and geographies. As result, patient data is more transparent, more available.

When combined with the platform SMART (Substitutable Medical Applications, Reusable Technologies) – generally called “SMART on FHIR” – developers have been able to create a strong range of healthcare applications that are interoperable across many different health IT systems.

For example, SMART on FHIR opens the way for patients to have a personal health record (PHR) via an app on their smartphone, along with an electronic health record and electronic medical record that contains all information from different health providers (i.e. visits, treatments from different specialists, etc.). Changes to the EHR and EMR might be synchronized with the app, in some cases allowing the patient to view the EHR/EMR. Apple’s Health app is a form of this and uses SMART on FHIR APIs. [8]

This also involves obvious organizational and legal questions of interoperability, especially in regards to data privacy. Policies and processes must therefore ethically keep pace with the technical, syntactic and semantic aspects.

Next level interoperability

FHIR is gaining widespread attention both among regulatory bodies and – as the growth of healthcare apps shows – in the medical and patient community itself. Significantly, it plays a key role in the US 21st Century Cures Act as FHIR and SMART on FHIR are the minimum conformance standards under the act. Furthermore, as well as stipulating how user authorization is performed and how apps launch, it forbids information blocking by EHR and FHIR providers. [9]

This is causing a shake-up in the healthcare ecosystem. Acceptance of the Act by some EHR vendors and hospital systems has apparently been lukewarm at best. “Intense lobbying against the rule, preceding its release, by EHR vendors and hospital systems signals that control over data and revenue are both at stake. The rule not only enables patient and provider access to medical record data in computable formats but also shifts how they interact with the health care system, which entities control those interactions, and the underlying business models that could either threaten or accelerate interoperability’s potential to improve care delivery.” [10]

Interoperability is therefore raising some very significant commercial questions.

FHIR from a regulatory perspective

Through its CBER-CDER Data Standards Program action plan, the FDA is engaging strongly with FHIR on several levels. [11] The CBER-CDER strategy is all about having comprehensive data standards in place that facilitate the pre- and post-market regulatory review process. Significantly, as part of its project in the area of Identification of Medicinal Product (IDMP) standards – a set of five ISO standards to identify and describe medicinal products [12, 13] – FHIR is foreseen as the standard for global information exchange. It is working together with the European Medicines Agency (EMA) on this project.

Across the Atlantic, EMA also outlines its clear commitment to FHIR when it reiterates that EMA, the FDA and the European medicines regulatory network are “working with Health Level Seven (HL7) to incorporate the ISO IDMP standards into the FHIR specification.” [14]

This is integral to EMA’s Substance and Product Data Management Services (SPOR) programme for managing centralized master data in compliance with ISO IDMP standards. [15, 16, 17] SPOR has four domains. In its Product Management Services (PMS) domain, HL7 FHIR “replaces the current data submission format, the eXtended EudraVigilance Product Report Message (XEVPRM).” [18]

How FHIR is transforming product labeling

Structured Product Labeling (SPL) is one of the most important areas in which FHIR is set to have an impact (see Part II of our series on structured content here]. This XML format (HL7 version 3 SPL) for the exchange of information is the current standard for a range of key FDA drug filings. While FHIR has not yet been introduced, “FDA is working towards replacing Structured Product Labeling (SPL) with HL7 FHIR.  The FDA has created a proof-of-concept system that can receive labeling information using either SPL or FHIR standard (Dual Submission) in addition to a draft Implementation Guide (IG).” [19]

The SPL specification has enormous strengths in terms of semantic and syntactic interoperability, but the strength of FHIR is its technical interoperability across devices and systems. This is crucial when using different devices in the age of electronic labeling (e-labeling), as well as for being able to automate workflows. SPL and its Canadian counterpart, the Structured Product Monograph (SPM), have created windows of opportunity for automation, and FHIR builds on these.

We can see this as the next level in the exchange of information, which began with the nervous exchange of duplicate hardcopy filings and time-consuming manual review by the FDA in a pre-electronic age, then advanced to the age of electronic submission in SPL format, and now has reached the age of FHIR. In brief, the benefits we are already seeing are:

  • Cost and time efficiencies through the better exchange of information
  • Greater potential for scalability
  • Risk mitigation through automation of workflows and processes (information must not be transposed, rewritten or otherwise manually replicated)
  • Empowerment and ownership for patients, physicians and other stakeholders through the availability of information
  • Information exchange across different devices and media

 In Europe, FHIR in regulatory action can already be seen in EMA’s pilot project on electronic product information (ePI), which began in July 2023. This FHIR-based pilot covers “authorised, statutory product information for medicines (including the summary of product characteristics, package leaflet and labeling) adapted for handling in electronic format and dissemination via the web, e-platforms and in print.” [20] The results of the project can already be accessed on its ePI portal. [21]

FHIR represents a significant step in how we manage, and exchange information and it has rapidly gained acceptance. While regulatory bodies are exercising caution and the required due diligence in implementing FHIR, it features in many different aspects of their planning. HL7 International is working closely on supporting the FDA on future implementation of HL7 Structured Product Labeling (SPL) standard using FHIR. [22] Similarly, in Europe we are seeing its implementation in key regulatory areas of healthcare, including e-labeling. In the commercial arena, it is already changing the face of healthcare.

Read Part I and Part II in our series on structured content.

  1. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6702215/
  2. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9030107/
  3. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6702215/
  4. HIStalk Interviews Grahame Grieve, FHIR Architect and Interoperability Consultant – HIStalk (histalk2.com)
  5. http://www.hl7.org/about/index.cfm?ref=nav
  6. https://fire.ly/blog/what-is-fhir/
  1. https://www.linkedin.com/pulse/evolution-healthcare-data-exchange-embracing-api-systems-jed-horning-6xhue/
  2. https://www.apple.com/healthcare/health-records/
  3. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7762678/
  4. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7762678/
  5. https://www.fda.gov/media/176436/download
  6. https://www.fda.gov/media/176436/download
  7. https://www.fda.gov/industry/fda-data-standards-advisory-board/identification-medicinal-products-idmp
  8. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview
  9. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview
  10. https://spor.ema.europa.eu/sporwi/
  11. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview/substance-product-organisation-referential-spor-master-data/substance-product-data-management-services#data-standard-for-information-exchange-12041
  12. https://www.ema.europa.eu/en/human-regulatory-overview/research-development/data-medicines-iso-idmp-standards-overview/substance-product-organisation-referential-spor-master-data/substance-product-data-management-services#data-standard-for-information-exchange-12041
  13. https://www.fda.gov/media/176436/download
  14. https://www.ema.europa.eu/en/human-regulatory-overview/marketing-authorisation/product-information-requirements/electronic-product-information-epi#eu-epi-common-standard-14451
  15. https://plm-portal.ema.europa.eu/ePIAll
  16. https://build.fhir.org/ig/HL7/fhir-spl/branches/main/index.html

 

 

 

Do you want to find out more about how your proofreading life can be easier? Get in touch and we’ll tell you all about it.

Subscribe to our blog

Related Blogs

September 2, 2024

Schlafender Hase Team

Avalis Publishing Case Study – Compliance through Watertight Version Control

3 minutes read

Avalis Publishing Case Study – Compliance through Watertight Version Control

September 2, 2024

Schlafender Hase Team

Soaring Medical Device Scrutiny: How is the Market Adapting?

4 minutes read

Soaring Medical Device Scrutiny: How is the Market Adapting?

August 22, 2024

Schlafender Hase Team

FHIR: Transforming Product Labeling

The shift from paper-based to digital processes has opened enormous opportunities in the healthcare sector in terms of data sharing and content management. But data can only be shared efficiently and add value if systems can "talk" to each other. The term we use for how compatibly systems work together is "interoperability." Traditionally, the healthcare sector has suffered from a high lack of interoperability.

6 minutes read

FHIR: Transforming Product Labeling

The shift from paper-based to digital processes has opened enormous opportunities in the healthcare sector in terms of data sharing and content management. But data can only be shared efficiently and add value if systems can "talk" to each other. The term we use for how compatibly systems work together is "interoperability." Traditionally, the healthcare sector has suffered from a high lack of interoperability.