This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

MedicinalProduct FHIR Resource Proposal

From HL7Wiki
Revision as of 23:10, 11 December 2017 by Riksmithies (talk | contribs)
Jump to navigation Jump to search


Owning work group name


Committee Approval Date:

13th September 2017

Contributing or Reviewing Work Groups

  • Pharmacy
  • O&O

FHIR Resource Development Project Insight ID

TBC (PSS has been created and submitted)

Scope of coverage

To support the content of the ISO 11615 IDMP Medicinal Product standard and its ISO/TS 20443 Technical Specification, and other domain areas with similar requirements. 11615 covers detailed definition of products, their submissions to regulators, authorization activities, ingredients, packaging, accompanying devices, clinical particulars etc). Not all of those are expected to be covered in this single resource.

RIM scope

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

Resource appropriateness

There is an upcoming requirement to support the standardised exchange of detailed Product data, as covered by the ISO 11615 specification.

This resource does not intend to clash with the existing Medication FHIR resource, but complements with an extra level of detail. It is seen as a sibling rather than a parent or a superclass to be profiled.

It is intended to add an extra level of product specification detail, such as is typically used by regulators, and only indirectly used during normal medication related work flows (e.g. for lookups of unfamiliar products).

Manufacturers submit this data 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 (currently using SPL, which is not likely to change in the near term, but have expressed an interest in researching what can be done with FHIR).

Content sources

The basis for the resource is the information in ISO 11615 Substances standard. A large amount of actual data exists in the EMA XEVMPD data base and XEVPRM XML messages. Example FHIR data of several full product data sheets exists based on prototyped resources.

Draft resources covering some of IDMP are here: MedicinalProduct

Example Scenarios

Pharma companies submit details of new products to regulators. Updates are made when necessary e.g. Clinical particulars change (a new contra-indication), a new marketing authorization exists etc.

Pharmacies and prescribers can view and download this information for reference and integration with their systems.

Resource Relationships

See diagram below and also associated proposal: SubstanceSpecification_FHIR_Resource_Proposal

Reference to Organization, for the manufacturer, regulator and other establishments. Reference to DocumentReference, for the regulatory submission documentation. Reference to (proposed) SubstanceSpecification to describe ingredients in detail. Reference to directly supporting (proposed) resources such as MedicinalProductAuthorization, MedicinalProductPackaged

MedicinalProduct and Medication

This resource is intended to complement the Medication resource, which is focused on what is commonly needed for medical/clinical use cases. MedicinalProduct adds information needed for regulatory use cases, of which there is little overlap, and also may be appropriate for drug database use.

Most aspects of MedicinalProduct are not present in Medication at all, and are not current candidates for inclusion in the prescribe/dispense/administer workflow.

Clinical particulars - indications, contra-indications etc Authorisations and Marketing - key area for regulators, of little interest to prescribers. Dates, statuses, territories etc. Product packaging - details of packages, including contents, sizes etc Ingredients - Typically at a prescribing level these are inherent in the medication code. The Medication resource does allow specifying ingredients of a medicine but this is typical for extemporaneous mixtures, and not the manufacturing of products.

MedicinalProduct and Device

IDMP does include descriptions of devices that are included with medicinal products. These include physical properties and characteristics that apply at the model level rather than the "instance" or usage level, that the Device resource is primarily concerned with.

Relationship to other resources


Early draft by December 2017 comment-only ballot.

gForge Users

riksmithies (already has commit permission)

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to

FMG Notes