Gravitate Health FHIR Implementation Guide (FHIR R4), published by . This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/gravitate-health-ips/ and changes regularly. See the Directory of published versions
All ePI documents are based on the same FHIR structure. The only exception is that each ePI document has unique section and sub-section headings. For example, the SmPC and PIL have the same FHIR document structure and have the same metadata but have different section headings and different narrative content.
The common ePI structure is as described below.
Figure 1: The common structure for all ePI documents
The Bundle is a container that gathers together a collection of resources into a single instance. The contained resources in the Bundle can be interpreted in two ways:
As a logical document: the bundle of contained resources is a single instance and can only be interpreted, changed or viewed as a whole. For example, the Bundle represents version 3 of a Patient Information Leaflet or version 2 of a SmPC.
As individual resources: Certain resources exist independently outside the Bundle and outside of the logical document. For example, the Medicinal Product Definition resource lives both as part of the logical document and as an independent resource.
The list resource references other resources. In this context, the List contains:
Although some use cases involve pulling metadata, sections or narrative content from the Composition, the List resource is not published independently from the Bundle.
The Composition defines the basic structure and the human readable narrative content for the ePI document. For example, encoded section headings; narrative text (paragraphs, sentences); tables; and bulleted lists. The Composition tags the language of the narrative content
All narrative content is in XHTML fragment with HTML 4.0 standard formatting (Refer to section 2.4 Narrative of the FHIR specification for HTML 4.0 exceptions and exclusions).
Althought some use cases involve pulling metadata, sections or narrative content from the Composition, the Composition resource is not published independently from the Bundle.
The Binary resource is used to handle images as Base64.
Summary of Product Characteristics (SmPC) is a document describing the properties and the officially approved conditions of use of a medicinal product. The SmPC is used by healthcare professionals, such as doctors, nurses and pharmacists, and explains how to use and prescribe a medicine safely and effectively.
The SmPC document template is made up of the following section and sub-section headings (Refer to the corresponding Terminology section of this IG for section codes):
Patient Information Leaflet (PIL):is included in the pack with a medicine. The PIL is written as a patient-friendly version of the SmPC.
The PIL document template is made up of the following section and sub-section headings (Refer to the Terminology section of this IG for the corresponding section codes]):
Section 1. What is your medicine and what it is used for
Section 2. Before you take or use your medicine
Section 3. How to take or use your medicine
Section 4. Possible side effects
Section 5. How to store your medicine
Section 6. Further Information
The Organization resource is used to describes contact and other information about the Market Authorization Holder (MAH) for the medicine the ePI documents are about. The MAH is also the author of the ePI documents.
The Organization resource can live independently from the document Bundle.
The Medicinal Product Definition resource provides uniquely identifiable detail about the ePI's medicinal product(s). It describes the overall medicinal product as a whole unit (similar to a Stop Keeping Unit or SKU) as authorized by the national competent regulatory authority.
The Medicinal Product Definition resource can live independently from the document Bundle.