Search



Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The representation of a medicinal product as it is supplied in a package by a by a single organisation (manufacturer or supplier) in a single jurisdiction under a single name (which may be a trade or brand name) for placement into the supply chain.  It is a subtype of and real world equivalent to the Packaged Clinical Drug (PCD ) class described above.   

Use

...

Cases

The following use cases are supported by the Real Packaged Clinical Drug concept class:

  • Describing medication process activities: prescribing, dispensing, administration and medication statements; of these, dispensing and administration will use this concept when it is available to clearly state which actual packaged product (or content from it) was used/supplied to the patient (with batch/lot and expiry information if required, either manually or by automatic identification and data capture (AIDC) - for example scanning the bar code on the package)
  • Compliance monitoring, using pack size information to calculate whether a patient is following the dosage instructions correctly (how quickly a repeat supply of a package of medication is required)
  • Anti-counterfeiting: in support of initiatives such as the Falsified Medicines Directive (see amended Directive 2001/83/EC) using AIDC and which requires scanning of medicines at the point of supply (to the patient)
  • Reimbursement: national or local systems may set pricing or eligibility against actual packaged products
  • Pharmacovigilance – especially for product defects and labelling issues
  • The association between the clinical representation of medicinal products and their representation in the supply chain for supply chain management

...

National extensions that require real packaged clinical drug concepts can are advised to define their RPCD real packaged clinical drug concepts using real clinical drug concepts from their national extension or, if only real packaged clinical drug concepts are authored without RCDs, using clinical drugs from the international edition or national extension.  However, if real packaged clinical drug concepts are authored without RCDs, there is little opportunity for grouping of concepts on the right-hand/real side of the model; although real packaged clinical drug concepts with the same product name and supplier would have the required attributes to group them together, there is no parent grouper concept to place them under, so the grouping would be hard to show.  If real packaged clinical drug concepts without RCDs and without PCDs, then the stated and inferred views will be equivalent, there will be no grouping concepts for the real packaged clinical drug concepts to be associated with..  This allows grouping of package concepts with their associated real clinical drug using the "contains clinical drug" value and information from that (for example, excipient information) can be transferred through that composition relationship if required.  

Existing national terminology equivalents:

...

Attribute: 

Semantic tag

(real packaged clinical drug)
Definition status


Scg expression
900000000000073002 |Sufficiently defined concept definition status (core metadata concept)

Note: This can only be the case if extensions author concepts to represent real clinical drugs and/or product names and manufacturer / supplier organisations

Attribute: 


Scg expression
1142143009 |Count of clinical drug type|


Range

  • INT (integer)

Cardinality

  • 1..1

Note

  • This attribute provides the number (count) of distinct clinical drug (concepts) present in the package.  For all non-combination packages, this value should be "one"
Scg expression
774158006 |Has product name|

(to be used if xxx is valued with a clinical drug concept rather than a real clinical drug concept)

Range

Scg expression
< 774167006 |Product name (product name)|
  • Extensions must author product name concepts within their extension using the root of 
    Concept
    t774167006 |Product name (product name)|
     from the Qualifier hierarchy

Cardinality

  • 1..1

Notes

The attribute value should represent the (authorised) product name; this may (or may not) be a trademarked name, and is often referred to as the "brand name
  • "
(see section below)

Attribute: 

Scg expression
774159003 |Has supplier|

(to be used if xxx is valued with a clinical drug concept rather than a real clinical drug concept)

Range
Scg expression
< 774164004 |Supplier (supplier)|
  • Extensions must author concepts to value supplier organisation information within their extension using the root of 
    Concept
    t774164004 |Supplier (supplier)|
     from the Qualifier hierarchy

Cardinality

  • 1..1

Notes

  • The attribute value should represent the holder of the marketing authorisation or authorisation for supply; this may or may not be the organisation responsible for the actual manufacture of the product (see section below)

Role Group 
[1..*]

(although for all packages other than combination products it is 1..1)

Attribute:


Scg expression
774160008 |Contains clinical drug|


Range


  • Scg expression
    < 763158003 |Medicinal product (product)|


Cardinality

  • 1..1

Note

  • This attribute value represents the real clinical drug that is contained in the packaged product
    It is currently not possible to explicitly specify an expression to describe the range of clinical drugs - either from the international edition or of real clinical drugs from a national extension - to populate this attribute, since (for example) a range cannot currently recognise a set of concepts with a particular semantic tag - in this case "(clinical drug)" or "(real clinical drug)".  This may be possible in the future; alternatively the range expression might be expressed as: "all products with a dose form, precise ingredient substance and basis of strength substance". For the interim, the range is specified as the descendants of the root medicinal product concept: 763158003 |Medicinal product (product)|. 

Attribute: 


Scg expression
1142142004 |Has pack size|


Range

  • INT (integer)

Cardinality

  • 1..1

Note

  • This attribute represents the amount or quantity of clinical drug present in the package; for presentation strength it is the number of countable units of presentation in the package; for concentration strength it is the mass or volume of the continuous dose form in the package

Attribute: 


Scg expression
774163005 |Has pack size unit|


Range


  • Scg expression
    <  767524001 |Unit of measure (qualifier value)|


Cardinality

  • 1..1

Note

  • This attribute value represents the unit of measure of the pack size;  for presentation strength it is the unit of presentation in the package; for concentration strength it is the unit of mass (e.g. gram) or volume (e.g. millilitre) of the continuous dose form in the package. 
    More specific range expressions such as "One of EITHER 732935002 | Unit of presentation (unit of presentation) - descendants only OR 258680008 | Unit of mass (qualifier value) - descendants only OR 258769000 | Unit of volume (qualifier value) - descendants only" are currently not supported, nor are rules based on the strength patterns that (for example) assert "if the clinical drug has a unit of presentation of 'tablet' then the Has_pack_size_unit will be valued as 'tablet").

...

Gliffy Diagram
macroId837f09bd-23cf-4695-a860-decb2b9cc508
displayNameRPCD Template Gliffy
nameRPCD Template Gliffy
pagePin12

Figure 34: Template for a simple real packaged clinical drug

Example: simple real packaged clinical drug

...

: stated view followed by the inferred view

Figure 35: Example of a real packaged clinical drug described using a real clinical drug - stated view

...

Figure 36: Example of a real packaged clinical drug described using a real clinical drug - inferred view

Example: simple real packaged clinical drug described using clinical drug: stated view followed by the inferred view

xxx

Figure 37: Example of a real packaged clinical drug described using a clinical drug - stated view

xxxx

Figure 38: Example of a real packaged clinical drug described using a clinical drug - inferred view

Optional Additional Information

The following information may be additionally used to describe the Real Packaged Clinical Drug concept in a national extension. With the exception of container information, the attribute concepts and values to populate these, if this data is to be held in a structured form, would need to be authored into the extension using reference sets.

Optional Additional Information 

As with the real clinical drugs, national extensions may require additional information to be associated with real packaged clinical drugs. This may include characteristics of the packaged product that can be described within the SNOMED CT structure using attributes and values, managed alongside the SNOMED CT structure (e.g. in a reference set) and/or relationships between identification systems should be managed in cross maps.

  • Packaged product characteristics may include package/container types Package/container type (e.g. bottle, box, jar, tube ); some use cases may also require information about sterile wrapping of some medicinal product packaging
  • License information - for those jurisdictions that license at a package level rather than at the real clinical drug level
    • License identification ("authorisation number")
    • Licensing class and/or legal status of supply
  • Usage information (prescribability within a particular jurisdictional context) including legal status 
  • Reimbursement information
  • Administration - to support various use cases including robotic dispensing) and administration device supplied in the package (e.g. medicine spoon, vaginal applicator, applicator brush for cutaneous liquid products)
  • Knowledge about the product may include usage information such as availability within the supply chain, licensing/authorization category and/or legal status of supply, and prescribability information including reimbursement categories.  
  • Other identification systems for a real packaged clinical drug may include licensing/authorization number, if this is provided for individual packages or Global Trade Identification Number

In jurisdictions where repackaging and/or "parallel importing" are authorised, a national extension may wish to consider having a relationship between the repackaged or parallel imported real packaged clinical drug and the real clinical drug supplied by the original manufacturer, if that is present within the jurisdiction.

IDMP Compatibility

This concept as defined is equivalent to the Packaged Medicinal Product of ISO 11615, which in that standard is identified by a PCID. As the representation of the "real world product" authorised for sale and/or supply that exists for all jurisdictions and which is marketed into the supply chain for use, it is the concept that should form the 1:1 join between representation in the regulatory domain (IDMP) and representation in the clinical domain (SNOMED CT and national medicinal product terminologies), even if some national medicinal product terminologies choose not to represent it, but only an abstraction of it (i.e. the Real Clinical Drug class of concepts).