Generated Narrative: StructureDefinition emaWriteApiMedicinalProductDefinition Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> MedicinalProductDefinition EmaWriteApiMedicinalProductDefinitionRestrictions extension 1..* EmaCoding Authorised Dose Form URL: http://ema.europa.eu/fhir/extension/authorisedDoseForm Binding: Authorised Dose Form (required) Slices for identifier 0..3 Identifier Business identifier for this product. Could be an MPID Slice: Unordered, Closed by value:system identifier:All Slices Content/Rules for all slices extension 0..0 use 0..0 type 0..0 period 0..0 assigner 0..0 identifier:eurdId 0..1 EmaEurdIdentifier Business identifier for this product. Could be an MPID system 1..1 uri The namespace for the identifier value Required Pattern: http://ema.europa.eu/fhir/eurdId identifier:mpId 0..1 EmaMpIdentifier Business identifier for this product. Could be an MPID system 1..1 uri The namespace for the identifier value Required Pattern: http://ema.europa.eu/fhir/mpId identifier:apiv2Id 0..1 EmaApiV2Identifier Business identifier for this product. Could be an MPID system 1..1 uri The namespace for the identifier value Required Pattern: http://spor.azure-api.net/pms/api/v2 type 0..1 EmaRefTermCodeableConcept Regulatory type, e.g. Investigational or Authorized Binding: Medicinal Product Type (required) domain 1..1 EmaRefTermCodeableConcept If this medicine applies to human or veterinary uses Binding: Domain (required) status 1..1 EmaRefTermCodeableConcept The status within the lifecycle of this product record Binding: Record Status (required) combinedPharmaceuticalDoseForm 0..1 EmaRefTermCodeableConcept The dose form for a single part product, or combined form of a multiple part product Binding: Combined Pharmaceutical Dose Form (required) indication 1..1 markdown Description of indication(s) for this product, used when structured indications are not required extension 1..1 EmaCoding Language URL: http://ema.europa.eu/fhir/extension/language Binding: Language (required) legalStatusOfSupply 1..1 EmaRefTermCodeableConcept The legal status of supply of the medicinal product as classified by the regulator Binding: Legal Status of Supply (required) additionalMonitoringIndicator 1..1 EmaRefTermCodeableConcept Whether the Medicinal Product is subject to additional monitoring for regulatory reasons Binding: Additional Monitoring Indicator (required) pediatricUseIndicator 1..1 EmaRefTermCodeableConcept If authorised for use in children Binding: Paediatric Use Indicator (required) Slices for classification 1..* CodeableConcept Allows the product to be classified by various systems Slice: Unordered, Closed by value:coding.system classification:xevmpd 0..1 EmaXevmpdProductCodeableConcept Allows the product to be classified by various systems coding system 1..1 uri Identity of the terminology system Required Pattern: http://spor.ema.europa.eu/v1/lists/200000000324 classification:legalBasis 0..1 EmaLegalBasisCodeableConcept Allows the product to be classified by various systems coding system 1..1 uri Identity of the terminology system Required Pattern: http://spor.ema.europa.eu/v1/lists/100000116045 classification:lightAtc 1..* EmaLightAtcCodeableConcept Allows the product to be classified by various systems coding system 1..1 uri Identity of the terminology system Required Pattern: http://spor.ema.europa.eu/v1/lists/100000093533 classification:productCategory 0..* EmaProductCategoryCodeableConcept Allows the product to be classified by various systems coding system 1..1 uri Identity of the terminology system Required Pattern: http://spor.ema.europa.eu/v1/lists/100000155526 masterFile 1..1 Reference(DocumentReference) A master file for the medicinal product (e.g. Pharmacovigilance System Master File) Slices for contact 2..2 BackboneElement A product specific contact, person (in a role), or an organization Slice: Unordered, Closed by value:type.coding.code contact:pharmacovigilanceQualifiedPersonContact 1..1 BackboneElement A product specific contact, person (in a role), or an organization type 0..1 EmaPharmacovigilanceQualifiedPersonTypeCodeableConcept Allows the contact to be classified, for example QPPV, Pharmacovigilance Enquiry Information contact 1..1 Reference(PractitionerRole) A product specific contact, person (in a role), or an organization contact:pharmacovigilanceEnquiryContact 1..1 BackboneElement A product specific contact, person (in a role), or an organization type 0..1 EmaPharmacovigilanceEnquiryContactCodeableConcept Allows the contact to be classified, for example QPPV, Pharmacovigilance Enquiry Information contact 1..1 Reference(Organization) A product specific contact, person (in a role), or an organization name 1..1 BackboneElement The product's name, including full name and possibly coded parts type 0..1 EmaRefTermCodeableConcept Type of product name, such as rINN, BAN, Proprietary, Non-Proprietary Binding: Medicinal Product Name Part Type (required) Slices for part 1..* BackboneElement Coding words or phrases of the name Slice: Unordered, Open by value:type part:All Slices Content/Rules for all slices type coding 0..* EmaNamePartTypeCoding Code defined by a terminology system Binding: Medicinal Product Name Part Type (required) part:inventedName 0..1 BackboneElement Coding words or phrases of the name type 1..1 CodeableConcept Identifying type for this part of the name (e.g. strength part) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://spor.ema.europa.eu/v1/lists/220000000000 code 1..1 code Symbol in syntax defined by the system Fixed Value: 220000000002 part:fullName 0..1 BackboneElement Coding words or phrases of the name type 1..1 CodeableConcept Identifying type for this part of the name (e.g. strength part) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://spor.ema.europa.eu/v1/lists/220000000000 code 1..1 code Symbol in syntax defined by the system Fixed Value: 220000000001 part:pharmaceuticalDoseForm 0..1 BackboneElement Coding words or phrases of the name type 1..1 CodeableConcept Identifying type for this part of the name (e.g. strength part) Required Pattern: At least the following coding 1..* Coding Code defined by a terminology system Fixed Value: (complex) system 1..1 uri Identity of the terminology system Fixed Value: http://spor.ema.europa.eu/v1/lists/220000000000 code 1..1 code Symbol in syntax defined by the system Fixed Value: 220000000005 usage 1..1 BackboneElement Country and jurisdiction where the name applies country 1..1 EmaRefTermCodeableConcept Country code for where this name applies Binding: Country (required) language 1..1 CodeableConcept Language code for this name Binding: Language (required) crossReference 0..1 BackboneElement Reference to another product, e.g. for linking authorised to investigational product product reference identifier 1..1 Identifier Logical reference, when literal reference is not known system 0..1 uri The namespace for the identifier value Required Pattern: http://ema.europa.eu/fhir/crossReference type 1..1 EmaRefTermCodeableConcept The type of relationship, for instance branded to generic or virtual to actual product Binding: Product Cross Reference Type (required) operation type 0..1 CodeableReference(EMA Write API ActivityDefinition) The type of manufacturing operation e.g. manufacturing itself, re-packaging confidentialityIndicator 1..1 EmaRefTermCodeableConcept Specifies whether this process is considered proprietary or confidential Binding: Data Classification (required) characteristic 1..1 BackboneElement Key product features such as "sugar free", "modified release" type 1..1 EmaGmoCodeableConcept A code expressing the type of characteristic <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
EMA Write API MedicinalProductDefinition
Defines the rules a MedicinalProductDefinition resource instance must conform to when belonging to a FHIR bundle representing a Human Variation Application
Detailed definition of a medicinal product
A medicinal product, being a substance or combination of substances that is intended to treat, prevent or diagnose a disease, or to restore, correct or modify physiological functions by exerting a pharmacological, immunological or metabolic action. This resource is intended to define and detail such products and their properties, for uses other than direct patient care (e.g. regulatory use, or drug catalogs).
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Entity, Role, or Act,ManufacturedProduct[classCode='MANU'].manufacturedProduct[classCode='MMAT']
Medicinal Product and Investigational Medicinal Product
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Slice defining three different types of identifiers (closed)
Business identifier for this product. Could be an MPID
Business identifier for this product. Could be an MPID. When in development or being regulated, products are typically referenced by official identifiers, assigned by a manufacturer or regulator, and unique to a product (which, when compared to a product instance being prescribed, is actually a product type). See also MedicinalProductDefinition.code.
Medicinal Product.MPID, Investigational Medicinal Product.IMPID
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [http://hl7.org/fhir/StructureDefinition/rendered-value](http://hl7.org/fhir/extensions/StructureDefinition-rendered-value.html)). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Regulatory type, e.g. Investigational or Authorized
Regulatory type, e.g. Investigational or Authorized.
(indicates if this is Medicinal Product or an Investigational Medicinal Product)
If this medicine applies to human or veterinary uses
If this medicine applies to human or veterinary uses.
A business identifier relating to a specific version of the product
A business identifier relating to a specific version of the product, this is commonly used to support revisions to an existing product.
The status within the lifecycle of this product record
The status within the lifecycle of this product record. A high-level status, this is not intended to duplicate details carried elsewhere such as legal status, or authorization status.
This element is labelled as a modifier because it is a status element that can indicate that a record should not be treated as valid
The date at which the given status became applicable
The date at which the given status became applicable.
The dose form for a single part product, or combined form of a multiple part product
The dose form for a single part product, or combined form of a multiple part product. This is one concept that describes all the components. It does not represent the form with components physically mixed, if that might be necessary, for which see (AdministrableProductDefinition.administrableDoseForm).
Medicinal Product.Combined Pharmaceutical Dose Form
The path by which the product is taken into or makes contact with the body
The path by which the product is taken into or makes contact with the body. In some regions this is referred to as the licenced or approved route. See also AdministrableProductDefinition resource. MedicinalProductDefinition.route is the same concept as AdministrableProductDefinition.routeOfAdministration.code, and they cannot be used together.
A code specifying the route or physiological path of administration of a therapeutic agent into or onto a patient's body.
Pharmaceutical Product.Route of Administration
Description of indication(s) for this product, used when structured indications are not required
Description of indication(s) for this product, used when structured indications are not required. In cases where structured indications are required, they are captured using the ClinicalUseDefinition resource. An indication is a medical situation for which using the product is appropriate.
(roll up of all text in Therapeutic Indication.Indication Text, for common case where information is not granular)
unique id for the element within a resource (for internal references)
The legal status of supply of the medicinal product as classified by the regulator
The legal status of supply of the medicinal product as classified by the regulator.
Marketing Authorisation.Legal Status of Supply (moved here for practicality)
Whether the Medicinal Product is subject to additional monitoring for regulatory reasons
Whether the Medicinal Product is subject to additional monitoring for regulatory reasons, such as heightened reporting requirements.
Medicinal Product.Additional Monitoring Indicator
Whether the Medicinal Product is subject to special measures for regulatory reasons
Whether the Medicinal Product is subject to special measures for regulatory reasons, such as a requirement to conduct post-authorization studies.
Extra measures defined for a Medicinal Product, such as a requirement to conduct post-authorization studies.
If authorised for use in children, or infants, neonates etc.
Medicinal Product.Pediatric Use Indicator
Slice defining 4 different types of classifications
Allows the product to be classified by various systems
Allows the product to be classified by various systems, commonly WHO ATC.
This value set includes codes from the Anatomical Therapeutic Chemical Classification System - provided as an exemplar value set.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).
The string must be either 'true' or 'false'.
Name of the coding system the 'coding' element belongs to
Marketing status of the medicinal product, in contrast to marketing authorization
Marketing status of the medicinal product, in contrast to marketing authorization. This refers to the product being actually 'on the market' as opposed to being allowed to be on the market (which is an authorization).
Package type for the product. See also the PackagedProductDefinition resource.
Types of medicinal manufactured items and/or devices that this product consists of, such as tablets, capsule, or syringes
Types of medicinal manufactured items and/or devices that this product consists of, such as tablets, capsule, or syringes. Used as a direct link when the item's packaging is not being recorded (see also PackagedProductDefinition.package.containedItem.item).
The ingredients of this medicinal product - when not detailed in other resources
The ingredients of this medicinal product - when not detailed in other resources. This is only needed if the ingredients are not specified by incoming references from the Ingredient resource, or indirectly via incoming AdministrableProductDefinition, PackagedProductDefinition or ManufacturedItemDefinition references. In cases where those levels of detail are not used, the ingredients may be specified directly here as codes.
This value set includes all substance codes from SNOMED CT - provided as an exemplar value set.
Medicinal Product.Ingredient (see also FHIR Ingredient resource)
Any component of the drug product which is not the chemical entity defined as the drug substance, or an excipient in the drug product
Any component of the drug product which is not the chemical entity defined as the drug substance, or an excipient in the drug product. This includes process-related impurities and contaminants, product-related impurities including degradation products.
Additional documentation about the medicinal product
Additional information or supporting documentation about the medicinal product.
A master file for the medicinal product (e.g. Pharmacovigilance System Master File)
A master file for the medicinal product (e.g. Pharmacovigilance System Master File). Drug master files (DMFs) are documents submitted to regulatory agencies to provide confidential detailed information about facilities, processes or articles used in the manufacturing, processing, packaging and storing of drug products.
Slice defining two different types of contacts (closed)
A product specific contact, person (in a role), or an organization
A product specific contact, person (in a role), or an organization.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Allows the contact to be classified, for example QPPV, Pharmacovigilance Enquiry Information
Allows the contact to be classified, for example QPPV, Pharmacovigilance Enquiry Information.
Extra measures defined for a Medicinal Product, such as heightened reporting requirements.
Clinical trials or studies that this product is involved in
Clinical trials or studies that this product is involved in.
Investigational Medicinal Product.Clinical Trial Status
A code that this product is known by, within some formal terminology
A code that this product is known by, usually within some formal terminology, perhaps assigned by a third party (i.e. not the manufacturer or regulator). Products (types of medications) tend to be known by identifiers during development and within regulatory process. However when they are prescribed they tend to be identified by codes. The same product may be have multiple codes, applied to it by multiple organizations.
A coded concept that defines the type of a medication.
The product's name, including full name and possibly coded parts
The product's name, including full name and possibly coded parts.
Type of product name, such as rINN, BAN, Proprietary, Non-Proprietary
Type of product name, such as rINN, BAN, Proprietary, Non-Proprietary.
Slice based on the part.type.coding.code
(any and all of the name parts e.g. Medicinal Product Name.Formulation Part)
(text of any of the name parts e.g. Medicinal Product Name.Formulation Part)
Identifying type for this part of the name (e.g. strength part)
Identifying type for this part of the name (e.g. strength part).
Type of part of a name for a Medicinal Product.
(which of the name parts this is e.g. Formulation Part)
Country and jurisdiction where the name applies
Country and jurisdiction where the name applies, and associated language.
Country code for where this name applies
Country code for where this name applies.
Jurisdiction code for where this name applies
Jurisdiction code for where this name applies. A jurisdiction may be a sub- or supra-national entity (e.g. a state or a geographic region).
Reference to another product, e.g. for linking authorised to investigational product
Reference to another product, e.g. for linking authorised to investigational product, or a virtual product.
Reference to another product, e.g. for linking authorised to investigational product.
A reference to a concept - e.g. the information is identified by its general class to the degree of precision found in the terminology.
A reference to a resource the provides exact details about the information being referenced.
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient") - must be a resource in resources
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the [http://hl7.org/fhir/StructureDefinition/additionalIdentifier](http://hl7.org/fhir/extensions/StructureDefinition-additionalIdentifier.html) extension.
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
The type of relationship, for instance branded to generic or virtual to actual product
The type of relationship, for instance branded to generic, virtual to actual product, product to development product (investigational), parallel import version.
A manufacturing or administrative process for the medicinal product
A manufacturing or administrative process or step associated with (or performed on) the medicinal product.
The type of manufacturing operation e.g. manufacturing itself, re-packaging
The type of manufacturing operation e.g. manufacturing itself, re-packaging. For the authorization of this, a RegulatedAuthorization would point to the same plan or activity referenced here.
Manufacturing / Business Operation.Operation Type
Manufacturing / Business Operation.Effective Date
The organization responsible for the particular process, e.g. the manufacturer or importer
The organization or establishment responsible for (or associated with) the particular process or step, examples include the manufacturer, importer, agent.
Manufacturer / Establishment (Organisation)
Specifies whether this process is considered proprietary or confidential
Specifies whether this particular business or manufacturing process is considered proprietary or confidential.
Manufacturing / Business Operation.Confidentiality Indicator
Key product features such as "sugar free", "modified release"
Allows the key product features to be recorded, such as "sugar free", "modified release", "parallel import".
Package Item (Container).Physical Characteristics
A code expressing the type of characteristic
A code expressing the type of characteristic.
This value set includes all observable entity codes from SNOMED CT - provided as an exemplar value set.
Physical Characteristics, all attributes
Text, as markdown, is intended to be used only when the item cannot ever reasonably be coded. Otherwise, for cases where a code is not available, but is feasible, use CodeableConcept.text.
Physical Characteristics, attribute's value