Short Description

This track is Phase 6 of an ongoing series, spanning multiple Connectathons, to test the creation, exchange and display of electronic Product information (ePI) and the International Patient Summary (IPS) as FHIR Documents, as well as potential UNICOM scenario’s for IDMP implementation. 

Each phase will include increased numbers of product information and increasingly complex healthcare/life scenarios. 

Track Objective is to test and gather feedback on the following: 

  1. Applying comment changes to IG
  2. Creating and validating ePI
  3. Searching ePI and IPS documents
  4. Linking of terminologies and clinical to regulatory terminology
  5. End to end ePI Processing
    1. Semantic Annotation
    2. Persona Dimensions as FHIR artifacts
    3. IPS data addition
    4. Lenses engines and examples
  6. Deep dive on interactions and substances
  7. Alignment with IDMP

The track is supported by the EU IMI Project Gravitate Health, the EU funded project UNICOM and supports the ePI pilot project at the European Medicines Agency. 

Long Description

Problem Statements 

  1. Existing ePI formats are not meeting the needs of patients, professionals and developers. 
  2. Expressing rules for G-lens and Persona characteristics in HL7 FHIR to tailor the presentation of ePI highlighting reported interactions.
  3. Due to variety in identification of medicinal products it is difficult to match the right information to the right products. This causes confusion and may introduce risks for the patient.  IDMP-standards provide globally consistent identification of medicinal products regarding their substance(s), strength and dose form.
  4. The lack of harmonization is leading to fragmented approaches where multiple differing standards are developing internationally e.g., eLabeling in HL7 SPL in North America, ePI in HL7 FHIR in the European Union; and custom XML standards in Asia. 


The vision of the Gravitate Health ePI /Vulcan accelerator ePI/ eLabeling project is to define a common structure for medicinal product information, including consistent identification by IDMP standards, that improves the patient experience and supports interoperability across the international healthcare clinical and regulatory environment.  

ePI Track Phase 5 builds towards this vision by incorporating lessons learned from the previous 5 connectathons 28-29-30-31-32. Also, by testing more complex real-world scenarios; additional FHIR resources; and more advanced product label data we expect the IG to be more mature and effective in covering a wider range of products. 


A medicine’s product information is a pivotal source of regulated and scientifically validated information that assists healthcare professionals in prescribing and dispensing the medicine and informs consumers about its safe use. 

ePI includes two primary forms of Information adapted for healthcare professionals and patients/consumers. Frequently apart from the core ePI, there are additional risk minimization measures like a patient card, videos, pictures, etc. that can act in support of the ePI to support patient understanding and safe use. IDMP-standards are crucial to ensure that any medicinal product can be accurately identified anywhere in the world to improve patient safety.

These documents are currently mostly based on PDF and they are section-formatted, but basically unstructured electronic paper content. As a result, they are difficult to search, difficult to find, and the content does not always meet patient needs as it lacks e.g., large fonts, accessibility support, multimedia, multiple languages, UpToDate (not including latest information). 

Only a few regions/countries have XML ePI’s, but the number and interest is growing. For example, US FDA uses HL7’s SPL with an ongoing SPLtoFHIR project; Japan’s PMDA uses custom XML; EU’s EMA is developing a FHIR XML ePI and authoring tool. Without harmonization, alignment and exchange of ideas, there is a high risk of divergence. This divergence won’t allow us to reap the benefits of the digital transformation.

Hence the need to transition to a dynamic structured format that can be used as an international standard, i.e., FHIR documents with the added benefit of tailoring to individual patient/consumer needs. 


Testing IG/Brainstorming:

  • Test IG
  • Brainstorm on ePI Validator, creators and lenses
  • Design and test workflows

Related Tracks?

None in specific,  in general is connected with IPS track and various accelerator tracks

Call for participants

Gravitate Health members; HL7 Vulcan Members; FDA; EMA; Project UNICOM; adopters; implementers; ePI and IPS data consumers, HELIOS and Gravity accelerators, CDSS implementers, EHR vendors, pharma and regulatory information providers and consumers

Track Prerequisites


Track Lead(s)

Catherine Chronaki, Craig Anderson, Giorgio Cangioli, João Almeida

Track Lead Email(s)

Gravitate Health Team Patricia Arbil, Cecilia Vera, Alvaro Belmar, Joao Almeida, Giorgio Cangioli, Erol Hoffman, Evinn Drusys, Adam Kover, Bente Jansen, Alejandro M. Medrano  

Specification Information

Vulcan/Gravitate Health Core ePI IG 

Github Repository with sample instances (in FSH)  

FHIR ePI spec


EMA ePI Specification 

Draft SPLtoFHIR specification.

Zulip stream


System Roles

 ePI Creator: any system able to generate HL7 FHIR ePI. It might be a tool converting existing ePI into a HL7 FHIR ePI

IPS Repository: a system storing HL7 FHIR IPS 

ePI Repository: a system storing HL7 FHIR ePI, allowing to search and retrieving them

ePI/IPS Consumer: any system designed to search, retrieve and present HL7 FHIR ePI and /or IPS

MPD: a system maintaining data about medicinal products. 

Testing Scenario:

Servers (ePI/IPS Repository)

 ePI Creator:

Sample data for use with the testing scenarios noted below 

  1. IPS samples: Here
  2. ePI samples: Here and here
  3. Focusing Mechanisms: Here

Electronic Product Information (ePI) 

  1. EU/EMA Sample ePI 
  2. US/FDA Sample ePI 
  3. Japan/PMDA Sample ePI 

International Patient Summary (IPS) 

  1. Helen 
  2. Maria 
  3. Pedro (new Spanish persona with HIV)

ePI Profiles 

  1. International Core
  2. National/European extensions 
  3. Formulation of Glens rules for drug-to-drug interactions.

Test Scenarios 

  1. Drug-to-drug interactions in a person’s medication list in the IPS
  2. Considering taking a new drug given the medication list in the IPS
  3. Textual analysis of ePI sections and formulation of rules for drug classes and annotations

Other Testing Scenarios to be considered as we move closer to FCAT33

  1. Core ePI Implementation Guide 
  2. Core ePI Profile vs Regional/national profile(s)
  3. G-Lens business rules and Gravitate Health Federated Open-Source Platform and Services (FOSPS)