ManufacturedItemDefinition FHIR Resource Proposal

MedicinalProductDefinition

Draft resource in build:

Owning work group name

BR&R

Committee Approval Date:

6th May 2019 (earlier approval as "RegulatedManufacturedItem" 13th September 2017)

Contributing or Reviewing Work Groups

• Pharmacy
• Orders and Observations

FHIR Resource Development Project Insight ID

1367

Scope of coverage

ManufacturedItemDefinition is to be used when you need to describe an actual physical medication item such as a tablet or capsule. This is typically for regulatory or manufacturing use cases.

This is the only resource that treats the "tablet" (or whatever it may be) as a physical object. It is still definitional however - it describes all instances of this tablet.

The definition needs to be a resource, rather than just a shared concept such as a data type, because the same physical item can appear in many different package types (which may come along after the item has been defined). (Gforge tracker item 23924 specifically requests this use case: "How to express multiple package configurations of the same manufactured item?")

This resource excludes devices and other items found in medication packaging such as scissors, bottle stoppers, applicators and so on (which would use DeviceDefinition).

This detail would very rarely be needed when prescribing – for which the correct resource is Medication. If you need to know what size, shape or colour the tablet is, or which packaging variations it can appear in, this resource has that level of detail.

The manufactured item describes the physical characteristics of the item, as opposed to its pharmaceutical aspects (which may only apply after mixing with other items), or its packaging, or legal aspects (which apply only to the whole group of packing and manufactured items).

Note that there can be several types of manufactured item in one package (e.g. a combination pill product, or a cream and a tablet).

There are typically multiple instances of the item in the packaging and this is indicated by the quantity within the package (e.g. a package of 12 tablets), referencing a single copy of the manufactured item.

In scope:

Drug form and unit of presentation (e.g. solid, tablet, film-coated tablet).

Manufacturer and ingredients.

Physical characteristics, e.g. size, shape, color, image, imprints (logo/text)

Not in scope:

For day to day prescribing, the resource to use is Medication. This covers basic drug information – code, form, strength, batch number.

Devices - this does not cover devices, unless they have a pharmaceutical aspect, such as an impregnated bandage.

(Note that the lines between devices, biologicals and medicinal products are unclear in the real world, and this resource does not attempt to solve that issue by being prescriptive.)

Pricing and contextual or local formulary information - for that see MedicationKnowledge.

Closely related scope:

Some other closely related information is in scope of other proposed resources, but not in scope of this resource:

Detailed packaging information (PackagedProductDefinition) - this resource "contains" ManufacturedItemDefinitions

Pharmaceutical aspects of the product (AdminstrableProductDefinition) - can be created from one or more ManufacturedItemDefinitions (possibly mixed together)

Regulatory authorizations (RegulatedAuthorization) - legal aspects of the product as a whole (of which the manufactured item is a key component).

Details of ingredients of the manufactured item (Ingredient) and their substances (SubstanceDefinition).

RIM scope

Similar in scope to the product parts of CPM. Entity: Material (EntityClass="MAT") determinerCode=KIND

Resource appropriateness

There is an outstanding requirement to support the standardised exchange of detailed "Product" data, for regulatory and other use cases.

This resource does not intend to clash with the existing Medication resource, but complements it with an extra level of detail. It is definitional rather than about an instance of a medication. (Also note however that when prescribing there is a duality of instance vs definition even in the Medication resource.)

This resource has been designed in close consultation with Pharmacy WG, and in conjunction with the MedicationKnowledge resource

Drug manufacturers currently submit this data electronically to regulators, when products are registered or altered, or marketing situations change.

Expected implementations

EMA and European drug manufacturers, who have a requirement to submit to EMA (and already do so in a proprietary format). They are required to move to IDMP, and this is a good opportunity to use a standards-based FHIR solution.

FDA for drug submission (currently using SPL, which is not likely to change in the near term, but have expressed an interest in FHIR).

Norwegian SAFEST project implementation https://github.com/HL7Norway/SAFEST (TODO more information)

Content sources

A large amount of actual data of this kind exists in the EMA EU XEVMPD data base (and XEVPRM XML messages). Example FHIR data for several full product data sheets exists based on draft resources.

Also, information gained from early stage implementation of these resources at EMA (2018, 2019), and from many many received to EMA about the draft API specification from the European medicines regulatory network (https://www.ema.europa.eu/en/about-us/how-we-work/european-medicines-regulatory-network).

Also from FDA requirements (for PQ/CMC) and other workgroup review (BR&R, Pharmacy) and their comments. Current active work on this project, with this resource.

This content is supported by the HL7 V3 SPL (Structured Product Labeling) standard.

Example Scenarios

Pharma companies submit details of new products to regulators. These include full product details down to the actual tablet level (also with packaging and other physical aspects).

Tablets or other physical representations can be stored and linked to multiple package variations, that may be created at later times.

Specific use cases include:

Submission of products from drug companies and NCAs (National Competent Authorities - the national regulators) to regional regulators. This is already implemented in Europe (by EMA and EU-wide stakeholders) with an earlier non-HL7 format (XEVPRM/XEVMPD). That scenario is currently being re-implemented, using this resource, as part of the EU wide SPOR project.

Resource Relationships

For the relationship to other resources, see the diagram below.

High level relationships of the main prescribing resources and the regulatory strata below:

Also refer to the logical model which was used to clarify the resource relationships, at the request of FMG, in the preparation of this proposal (linked to the approved MedicationKnowledge proposal page): MedicationKnowledge_FHIR_Resource_Proposal

The manufactured item is always physically within some packaging, so the PackagedProductDefinition resource has a reference to this item.

One or more manufactured items eventually forms the product that is directly administered to the patient, so the AdministrableProductDefinition also has a reference to this resource.

Some notable resource references:

Reference to Organization, for the manufacturer.

Reference to Ingredient for the ingredients of this manufactured item.

So:

   MPD – as licenced 
     / \
   /    \____PPD1  or  PPD2 – as supplied
 /           /  \
APD   <--  MID1+MID2 (mixed)
 \
  as administered to the patient

MPD Medicinal Product (definition)

MID Manufactured Item (definition)

PPD PackagedProduct (definition)

APD Administrable Product (definition)

Timelines

Draft content is modelled in the FHIR build ManufacturedItemDefinition, with outline supporting documentation. Completion planned Q4 2019.

gForge Users

riksmithies

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org