This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.

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 it's narrative along with other profiles, value sets, etc.

Name of the medicinal product. This is typically the name of a real product as registered. This element should not contain display names of virtual product concepts.

HIQA EP 4.3 Medication product name (brand or trade name), when it differs from code.text.

Medication classification/category. Allows the product to be classified by various systems, e.g ATC, narcotic class, legal status of supply, etc..

HIQA EP 4.2 Classification (Required 0..*): ATC (4.2.1), supply legal status (4.2.2, IEMpdSupplyLegalStatus placeholder), MDA schedule (4.2.3, IEMpdMDASchedule placeholder), other classification group (4.2.4).

Size of a manufactured item or unit of presentation. For example, size of one vial in a package that may contain several vials.

Any characteristic of the medicinal product prescribed or dispensed (for example, price, textual package description, special program information, etc)

HIQA EP 4.9 Characteristics (Optional, dispensation).

Unit of presentation, typically describing the smallest countable package item (e.g tablet, vial, ampoule, etc). Unit of presentation is also often used in describing pack size and the denominator of strength. If the size of presentation unit is relevant, it should be described in sizeOfItem extension.

HIQA EP 4.7.3 Unit of presentation (Optional, dispensation).

This extension applies to Medication and expresses the type of the container for the product (e.g. bottle, unit-dose blister, pre-filled pen).

HIQA EP 4.7.6 Package type (Optional, dispensation); EDQM package terms.

Device, typically an administration device, included in the medicinal product.

HIQA EP 4.8 Device (Optional, dispensation): 4.8.1 device type and 4.8.2 quantity.

An Extension

An Extension

An Extension

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.

An Extension

An Extension

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.

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 for a list).

HIQA EP 3.5.10.1 (Required 0..1, expected auto-populated from the NMPC): whether the medicinal product is on the HPRA List of Interchangeable Medicines. If true, substitution is allowed by default unless the prescriber invokes 'Do Not Substitute' (MedicationRequest.substitution.allowedBoolean = false).

HIQA EP 3.5.10.1 Medicinal product is interchangeable (Required; HPRA List of Interchangeable Medicines).

HIQA EP 4.11 Exempt medication item (Required 0..1, Boolean, expected auto-populated). REQUIRES CLARIFICATION: the draft does not say what the item is exempt from (e.g. an exempt medicinal product without a marketing authorisation). Modelled as a boolean flag so that the dataset element can be carried; see the open issues.

HIQA EP 4.11 Exempt medication item (Required). Meaning Requires Clarification.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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).

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.

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.

A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems.

HIQA EP 4.1 Medication item identifier (Required 0..*) and 4.3 Medication product name (4.3.1 coded, 4.3.2 free text in code.text). NMPC (SNOMED CT Irish Extension) where available; see Terminology Services.

A code to indicate if the medication is in active use.

This status is intended to identify if the medication in a local system is in active use within a drug database or inventory. For example, a pharmacy system may create a new drug file record for a compounded product "ABC Hospital Special Cream" with an active status. At some point in the future, it may be determined that the drug record was created with an error and the status is changed to "entered in error". This status is not intended to specify if a medication is part of a particular formulary. It is possible that the drug record may be referenced by multiple formularies or catalogues and each of those entries would have a separate status.

A coded concept defining if the medication is in active use.

Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product.

HIQA EP 4.4 Manufacturer / marketing authorisation holder (Optional, dispensation).

Describes the form of the item. Powder; tablets; capsule.

HIQA EP 4.5 Dose form (Required, dispensation) and 4.7.1 Medication item dose form (Required). EDQM Standard Terms. For a controlled-drug preparation, the dose form is a legal requirement.

Specific amount of the drug in the packaged product. For example, when specifying a product that has the same strength (For example, Insulin glargine 100 unit per mL solution for injection), this attribute provides additional clarification of the package amount (For example, 3 mL, 10mL, etc.).

HIQA EP 4.7.5 Pack size or amount (Optional).

Identifies a particular constituent of interest in the product.

HIQA EP 4.7.2 Ingredient in medication item (Mandatory 1..*).

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 manageable, 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).

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.

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.

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

HIQA EP 4.7.2.2 Active ingredient/substance (Mandatory 1..1); SNOMED CT substance.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

Indication of whether this ingredient affects the therapeutic action of the drug.

HIQA EP 4.7.2.1 Ingredient is active (Required).

True indicates that the ingredient affects the therapeutic action of the drug (i.e. active). False indicates that the ingredient does not affect the therapeutic action of the drug (i.e. inactive).

Definitional resources should be used for specifying the different types of strengths: presentation; concentration.

HIQA EP 4.7.2.3 Strength (Required; 4.7.2.3.1 Ratio Mandatory within the cluster), UCUM units. A legal requirement on a dispensation record, and on a controlled-drug prescription for a preparation. Basis of strength substance (4.7.2.3.2) via the IHE strengthsubstance extension.

Substance for marking the basis of strength. When the precise active ingredient is a salt, the strength is often provided for the active moiety (basis of strength).

Information that only applies to packages (not products).

HIQA EP 4.10 Batch (Required, dispensation).

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 manageable, 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).

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.

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.

The assigned lot number of a batch of the specified product.

HIQA EP 4.10.1 Batch lot number (Required).

When this specific batch of product will expire.

HIQA EP 4.10.2 Batch expiration date (Required).

HIQA EP 4.3 Medication product name (brand or trade name), when it differs from code.text.

HIQA EP 4.2 Classification (Required 0..*): ATC (4.2.1), supply legal status (4.2.2, IEMpdSupplyLegalStatus placeholder), MDA schedule (4.2.3, IEMpdMDASchedule placeholder), other classification group (4.2.4).

HIQA EP 4.9 Characteristics (Optional, dispensation).

HIQA EP 4.7.3 Unit of presentation (Optional, dispensation).

HIQA EP 4.7.6 Package type (Optional, dispensation); EDQM package terms.

HIQA EP 4.8 Device (Optional, dispensation): 4.8.1 device type and 4.8.2 quantity.

HIQA EP 3.5.10.1 Medicinal product is interchangeable (Required; HPRA List of Interchangeable Medicines).

HIQA EP 4.11 Exempt medication item (Required). Meaning Requires Clarification.

HIQA EP 4.1 Medication item identifier (Required 0..*) and 4.3 Medication product name (4.3.1 coded, 4.3.2 free text in code.text). NMPC (SNOMED CT Irish Extension) where available; see Terminology Services.

HIQA EP 4.4 Manufacturer / marketing authorisation holder (Optional, dispensation).

HIQA EP 4.5 Dose form (Required, dispensation) and 4.7.1 Medication item dose form (Required). EDQM Standard Terms. For a controlled-drug preparation, the dose form is a legal requirement.

HIQA EP 4.7.5 Pack size or amount (Optional).

HIQA EP 4.7.2 Ingredient in medication item (Mandatory 1..*).

HIQA EP 4.7.2.2 Active ingredient/substance (Mandatory 1..1); SNOMED CT substance.

HIQA EP 4.7.2.1 Ingredient is active (Required).

HIQA EP 4.7.2.3 Strength (Required; 4.7.2.3.1 Ratio Mandatory within the cluster), UCUM units. A legal requirement on a dispensation record, and on a controlled-drug prescription for a preparation. Basis of strength substance (4.7.2.3.2) via the IHE strengthsubstance extension.

HIQA EP 4.10 Batch (Required, dispensation).

HIQA EP 4.10.1 Batch lot number (Required).

HIQA EP 4.10.2 Batch expiration date (Required).

This resource is primarily used for the identification and definition of a medication for the purposes of prescribing, dispensing, and administering a medication as well as for making statements about medication use.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

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.

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 it's narrative along with other profiles, value sets, etc.

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).

A human language.

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 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, and nor can they have their own independent transaction scope.

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.

An Extension

Name of the medicinal product. This is typically the name of a real product as registered. This element should not contain display names of virtual product concepts.

HIQA EP 4.3 Medication product name (brand or trade name), when it differs from code.text.

Medication classification/category. Allows the product to be classified by various systems, e.g ATC, narcotic class, legal status of supply, etc..

HIQA EP 4.2 Classification (Required 0..*): ATC (4.2.1), supply legal status (4.2.2, IEMpdSupplyLegalStatus placeholder), MDA schedule (4.2.3, IEMpdMDASchedule placeholder), other classification group (4.2.4).

Size of a manufactured item or unit of presentation. For example, size of one vial in a package that may contain several vials.

Any characteristic of the medicinal product prescribed or dispensed (for example, price, textual package description, special program information, etc)

HIQA EP 4.9 Characteristics (Optional, dispensation).

Unit of presentation, typically describing the smallest countable package item (e.g tablet, vial, ampoule, etc). Unit of presentation is also often used in describing pack size and the denominator of strength. If the size of presentation unit is relevant, it should be described in sizeOfItem extension.

HIQA EP 4.7.3 Unit of presentation (Optional, dispensation).

This extension applies to Medication and expresses the type of the container for the product (e.g. bottle, unit-dose blister, pre-filled pen).

HIQA EP 4.7.6 Package type (Optional, dispensation); EDQM package terms.

Device, typically an administration device, included in the medicinal product.

HIQA EP 4.8 Device (Optional, dispensation): 4.8.1 device type and 4.8.2 quantity.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

An Extension

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

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 for a list).

An Extension

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

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 for a list).

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 for a list).

HIQA EP 3.5.10.1 (Required 0..1, expected auto-populated from the NMPC): whether the medicinal product is on the HPRA List of Interchangeable Medicines. If true, substitution is allowed by default unless the prescriber invokes 'Do Not Substitute' (MedicationRequest.substitution.allowedBoolean = false).

HIQA EP 3.5.10.1 Medicinal product is interchangeable (Required; HPRA List of Interchangeable Medicines).

HIQA EP 4.11 Exempt medication item (Required 0..1, Boolean, expected auto-populated). REQUIRES CLARIFICATION: the draft does not say what the item is exempt from (e.g. an exempt medicinal product without a marketing authorisation). Modelled as a boolean flag so that the dataset element can be carried; see the open issues.

HIQA EP 4.11 Exempt medication item (Required). Meaning Requires Clarification.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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).

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.

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.

Business identifier for this medication.

The serial number could be included as an identifier.

A code (or set of codes) that specify this medication, or a textual description if no code is available. Usage note: This could be a standard medication code such as a code from RxNorm, SNOMED CT, IDMP etc. It could also be a national or local formulary code, optionally with translations to other code systems.

HIQA EP 4.1 Medication item identifier (Required 0..*) and 4.3 Medication product name (4.3.1 coded, 4.3.2 free text in code.text). NMPC (SNOMED CT Irish Extension) where available; see Terminology Services.

A code to indicate if the medication is in active use.

This status is intended to identify if the medication in a local system is in active use within a drug database or inventory. For example, a pharmacy system may create a new drug file record for a compounded product "ABC Hospital Special Cream" with an active status. At some point in the future, it may be determined that the drug record was created with an error and the status is changed to "entered in error". This status is not intended to specify if a medication is part of a particular formulary. It is possible that the drug record may be referenced by multiple formularies or catalogues and each of those entries would have a separate status.

A coded concept defining if the medication is in active use.

Describes the details of the manufacturer of the medication product. This is not intended to represent the distributor of a medication product.

HIQA EP 4.4 Manufacturer / marketing authorisation holder (Optional, dispensation).

Describes the form of the item. Powder; tablets; capsule.

HIQA EP 4.5 Dose form (Required, dispensation) and 4.7.1 Medication item dose form (Required). EDQM Standard Terms. For a controlled-drug preparation, the dose form is a legal requirement.

Specific amount of the drug in the packaged product. For example, when specifying a product that has the same strength (For example, Insulin glargine 100 unit per mL solution for injection), this attribute provides additional clarification of the package amount (For example, 3 mL, 10mL, etc.).

HIQA EP 4.7.5 Pack size or amount (Optional).

Identifies a particular constituent of interest in the product.

HIQA EP 4.7.2 Ingredient in medication item (Mandatory 1..*).

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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 manageable, 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.

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 manageable, 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).

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.

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.

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

HIQA EP 4.7.2.2 Active ingredient/substance (Mandatory 1..1); SNOMED CT substance.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

The actual ingredient - either a substance (simple ingredient) or another medication of a medication.

The ingredient may reference a substance (for example, amoxicillin) or another medication (for example in the case of a compounded product, Glaxal Base).

Indication of whether this ingredient affects the therapeutic action of the drug.

HIQA EP 4.7.2.1 Ingredient is active (Required).

True indicates that the ingredient affects the therapeutic action of the drug (i.e. active). False indicates that the ingredient does not affect the therapeutic action of the drug (i.e. inactive).

Definitional resources should be used for specifying the different types of strengths: presentation; concentration.

HIQA EP 4.7.2.3 Strength (Required; 4.7.2.3.1 Ratio Mandatory within the cluster), UCUM units. A legal requirement on a dispensation record, and on a controlled-drug prescription for a preparation. Basis of strength substance (4.7.2.3.2) via the IHE strengthsubstance extension.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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 manageable, 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.

Substance for marking the basis of strength. When the precise active ingredient is a salt, the strength is often provided for the active moiety (basis of strength).

The value of the numerator.

The value of the denominator.

Information that only applies to packages (not products).

HIQA EP 4.10 Batch (Required, dispensation).

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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 manageable, 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.

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 manageable, 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).

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.

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.

The assigned lot number of a batch of the specified product.

HIQA EP 4.10.1 Batch lot number (Required).

When this specific batch of product will expire.

HIQA EP 4.10.2 Batch expiration date (Required).