FHIR R5 EU ePI QRD Versioning Audit Trail

Turn SmPCs and Package Leaflets into submission-ready EU ePI.

Convert existing Product Information into structured FHIR ePI, validate it against EMA ePI and QRD requirements and manage every version across your portfolio.

ePIverity gives Regulatory and Labeling teams a controlled workflow from today's Product Information to electronic Product Information.

Book an ePI readiness call See how ePIverity works
Portfolio · ePI readiness
01 Import.
02 Structure.
03 Validate.
04 Review.
05 Export.
01 Import.
02 Structure.
03 Validate.
04 Review.
05 Export.
FHIR · validated
EMA PLM Portal

Then import the validated FHIR directly into the EMA PLM Portal for the official regulatory process.

Package Leaflets & SmPCs
5 of 247
ProductMarketLangDocumentVer.Status
Medicine ADEdePackage Leafletv16Ready for export
Medicine AFRfrSmPCv9Awaiting review
Medicine BITitPackage Leafletv43 validation issues
Medicine CESesLabellingv2Not yet converted
Medicine DNLnlPackage Leafletv7Regulator-published
Validate · Medicine B · IT
Mandatory section missing§4.8
XHTML integrity§2.1
QRD structure§3

ePI changes Product Information from a document into structured regulatory data.

For decades, Product Information has primarily lived in documents.

Word files. PDFs. Document-management systems. Different versions for different countries and languages.

European electronic Product Information introduces a structured, machine-readable format for authorised Product Information.

That creates a new operational challenge for pharmaceutical companies:

How do you turn today's Product Information into valid ePI across an entire portfolio?

ePIverity is built for that transition.

From SmPC and Word documents to PLM-ready FHIR ePI.

01

Bring in your existing Product Information.

Start with:

Word documents
existing FHIR
structured Product Information

ePIverity preserves the original source and keeps every transformation traceable.

02

ePIverity maps the document into the relevant ePI and QRD structure.

Sections, headings, paragraphs, tables and metadata are transformed into structured Product Information.

AI can assist with mapping.

It never silently rewrites your approved medicinal content.

03

Run technical validation before the ePI reaches the regulatory submission process.

ePIverity checks:

FHIR structure
EU ePI profiles
QRD structure
mandatory sections
document type
language
metadata
XML/XHTML integrity

Problems are shown directly where they occur.

Instead of receiving a technical validator output, Regulatory teams get actionable review tasks.

04

Compare the source document and generated ePI side by side.

See exactly where every piece of content came from.

Correct mappings.
Resolve validation issues.
Approve sections.
Maintain a complete audit trail.
05

Once the ePI passes your internal review and technical validation:

Download the FHIR package for import into the EMA PLM Portal.

The regulatory submission and approval process remains with the relevant authority.

ePIverity prepares the ePI for that process.

Medicine A · Package Leaflet
DE · de · v16
scroll ↓
01 / 05 · Import

Built for portfolio-scale ePI operations.

One medicine is manageable.

Hundreds of products across markets, languages and continuous regulatory changes are an operational challenge.

ePIverity gives teams a portfolio view of ePI readiness.

Filter by:

productmarketlanguagedocumentePI versionvalidation statusregulatory status

Know exactly where your ePI transition stands.

Example:
247products
183 ready
31 awaiting review
14 with validation issues
19 not yet converted
52 regulator-published

Every transformation is traceable.

Regulated content should not disappear into an AI black box.

For every structured ePI element, ePIverity keeps the relationship to its original source.

Regulatory reviewers can inspect that relationship before approving the output.

Source
Paragraph 187 in the approved Product Information
ePI
Package Leaflet
Section 3
FHIR Composition
QRD section

ePI validation: FHIR, QRD and metadata checks.

A technically valid XML file is not enough.

ePIverity evaluates the document against the structures expected for electronic Product Information.

FHIR validation

Validate resources against the applicable profiles.

QRD validation

Identify missing, duplicated or incorrectly structured sections.

Metadata validation

Check relevant Product Information metadata.

Structural validation

Detect malformed XML, XHTML and document relationships.

Human review stays in charge.

Technical validation never replaces Regulatory approval. Every version is signed off by an independent reviewer before export.

Regulatory Diff

See changes in regulatory context.

Generic document comparison tells you which words changed.

ePIverity shows where the Product Information changed.

Understand changes by document and QRD section instead of reviewing an undifferentiated text diff.

Package Leaflet v15 → v16
Section 2 — Warnings and precautions
New paragraph added.
+ added
Section 3 — How to take the medicine
Dosage paragraph modified.
~ modified
Section 4 — Possible side effects
No change.
= unchanged

Keep every ePI version under control.

Approved internal versions are immutable.

New Product Information creates a new version instead of silently changing the old one.

Each version has its own: v16
sourceLeaflet_DE.docx
FHIR outputBundle.json
validation reportpassed
review statusapproved
audit trail42 events
submission reference—
regulatory statussubmitted

The regulatory authority remains the source of approval.

ePIverity does not replace the EMA PLM Portal or the regulator.

It is designed around the European ePI standard and FHIR architecture, and is version-aware as that standard evolves. The workflow is deliberately clear:

01

Pharmaceutical company

creates and reviews Product Information

02

ePIverity

structures and technically validates ePI

03

EMA PLM Portal

official regulatory submission workflow

04

Regulatory authority

reviews and publishes authorised ePI

This separation keeps the roles clear.

After publication, close the loop.

Creating the ePI should not be the end of its lifecycle.

Once an authority publishes the authorised ePI, ePIverity can synchronise the published version back into your controlled environment.

That enables teams to compare:

v16 · internal

What we prepared

with
v16 · published

What the authority published

and keep a verified record of the current authorised version.

Keep your existing Regulatory stack.

ePIverity is not another RIM replacement project.

Continue using your existing:

RIMdocument-management systemlabeling platformstructured-content systemWord-based workflows

ePIverity adds the ePI transformation and lifecycle layer.

1Existing systems
2ePIverity
3PLM / authority
Published ePI

Start with an ePI Readiness Pilot.

You do not need to migrate an entire portfolio before proving the workflow.

5

representative products are enough to prove the workflow.

At the end of the pilot, you know:

What is already ePI-ready.
Where the gaps are.
What can be automated.
What requires Regulatory review.
What portfolio-scale migration will involve.

Start small. Scale with your portfolio.

Prove the workflow on a handful of products first. The platform subscription follows once you know what portfolio-scale migration involves.

Start here

ePI Readiness Pilot

from€9,900
one-off · excl. VAT
  • Up to 5 products, one language
  • Word or FHIR input
  • Automated QRD structuring
  • FHIR ePI generation
  • EMA profile validation
  • Manual Regulatory review
  • Validation report
  • PLM-ready export
  • Portfolio readiness report
Book a pilot call
Platform

ePIverity Core

Annual subscription
scales with product × language
  • Conversion workflow
  • Technical validation
  • Versioning and diff
  • Audit trail
  • PLM export
  • Authority sync
Talk to sales
Large portfolios

Enterprise

Custom
agreement + implementation
  • Everything in Core
  • SSO
  • RIM / Veeva integration
  • API access
  • SLA
  • Dedicated environment
Talk to sales
Add-on

Verified Search

Annual add-on
for Core and Enterprise
  • Natural-language search
  • Authority-published content only
  • Verbatim-only output
  • API and web component
  • Multiple languages
Talk to sales
Pricing model

Base platform fee plus portfolio volume, measured in product × language configurations.

Initial migration

Existing documents are converted once, quoted per product and language, with volume pricing.

No usage surprises

No per-seat, per-API-call or AI-token pricing.

EU ePI: frequently asked questions

Is ePI already mandatory for every medicine in Europe?

No.

The EU is transitioning towards ePI and implementation is being rolled out progressively.

EMA has stated that ePI will become mandatory for newly authorised medicines once the revised EU pharmaceutical legislation becomes applicable.

ePIverity is designed to help organisations prepare their processes and portfolios for that transition.

Does ePIverity submit our ePI to EMA?

Not in the initial product.

ePIverity prepares and technically validates the ePI.

Your authorised Regulatory user imports the FHIR into the EMA PLM Portal and manages the official regulatory submission process.

This keeps ePIverity separate from the role of the regulator.

Why do we need ePIverity if the PLM Portal has an editor?

The PLM Portal is the official regulatory environment.

ePIverity addresses the operational work that happens around it:

converting existing Product Information;
automating QRD mapping;
pre-validating ePI;
managing large portfolios;
keeping source traceability;
comparing versions;
maintaining a review workflow;
synchronising published versions.

The goal is not to replace PLM.

The goal is to arrive at PLM with a controlled, validated ePI.

What does “submission-ready” mean?

It means the ePI has passed the configured technical validation and internal review workflow for export into the official submission process.

It does not mean that EMA or another authority has approved the Product Information.

Regulatory approval remains with the relevant authority.

Does ePIverity replace our RIM or labeling system?

No.

ePIverity is designed to integrate with the systems you already use.

It acts as an ePI transformation, validation and lifecycle layer.

Can ePIverity convert Word documents?

Yes.

ePIverity is designed to ingest existing Product Information and map it to the appropriate structured ePI representation.

Automated mapping remains reviewable before the output is approved internally.

Does ePIverity support PDF?

PDF support can be provided for legacy content, although structured source formats such as Word provide better information for reliable automated conversion.

Does ePIverity use AI?

Yes, selectively.

AI can support structure recognition, section mapping and information retrieval.

Deterministic validation and human approval remain separate from AI-based suggestions.

What happens after the regulator publishes the ePI?

ePIverity can retrieve and store the authority-published version where supported by the relevant regulatory interface.

This creates a controlled record of the current authorised Product Information and enables downstream delivery.

Is Verified Search part of the regulatory submission?

No.

Verified Search is an optional downstream capability.

It uses structured, authority-published Product Information to make specific passages easier to find.

Does Verified Search generate medical answers?

No.

Its purpose is to locate and return the relevant original passage from authorised Product Information.

Prepare your Product Information
for ePI.

The standard exists. The regulatory infrastructure is being deployed. The transition is beginning.

Build a repeatable ePI process before it becomes a portfolio-scale problem.

Book an ePI readiness call

Talk to the ePIverity team.

Book a 15-minute ePI readiness call or send us a message. We usually reply within one business day.

Book a readiness call

Pick a time. We'll look at your portfolio, your source formats and whether a pilot makes sense.

15 min · online
ePI readiness call

The booking calendar is provided by Cal.com and only loads after you click. See our privacy policy. Open in a new tab.

Send a message