Logical model of the HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026. Built only from the element IDs, conformance, cardinality and datatypes published in the draft. Coded values are not specified by HIQA. This is a consultation draft and will change. Not endorsed by HIQA.

Section 1. Patient Details (grouping heading; no HIQA conformance)

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.

1.1 Name Details (grouping heading; no HIQA conformance)

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.

HIQA EP 1.1.1 Name title. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 25.

HIQA EP 1.1.2 Forename. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 25.

HIQA EP 1.1.3 Surname. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 25.

HIQA EP 1.1.4 Name suffix. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 26.

1.2 Address (grouping heading; no HIQA conformance)

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.

HIQA EP 1.2.1 Postcode. Conformance: Required. Cardinality: 0..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 26.

HIQA EP 1.2.2 Address line(s). Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 26.

HIQA EP 1.2.3 Suburb/ Town/ Townland/ Locality. Conformance: Required. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 27.

HIQA EP 1.2.4 District/ County. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded Value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 27.

HIQA EP 1.2.5 Country. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 27.

HIQA EP 1.2.6 Address type. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 27.

HIQA EP 1.2.7 Address use. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 27.

1.3 Identifiers Used in Health and Social Care (grouping heading; no HIQA conformance)

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.

HIQA EP 1.3.1 Individual Health Identifier (IHI). Conformance: Required. Cardinality: 0..1. HIQA datatype: Numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 28.

HIQA EP 1.3.2 Personal Public Service Number. Conformance: Required. Cardinality: 0..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 28.

HIQA EP 1.3.3 Other identifiers used in health and social care details (cluster). Conformance: Required. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 28.

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.

HIQA EP 1.3.3.1 Other identifier used in health and social care – Type. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 29.

HIQA EP 1.3.3.2 Other identifier used in health and social care-Value. Conformance: Required. Cardinality: 0..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 29.

HIQA EP 1.3.3.3 Other identifier used in health and social care - Time period. Conformance: Required. Cardinality: 0..1. HIQA datatype: Period. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 29.

HIQA EP 1.3.3.4 Organisation who issued the other identifier used in health and social care. Conformance: Required. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 29.

1.4 Additional Demographic Details (grouping heading; no HIQA conformance)

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.

HIQA EP 1.4.1 Date of birth. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Date. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 30.

HIQA EP 1.4.2 Age (cluster). Conformance: Required. Cardinality: 0..1. HIQA datatype: (none given). Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 30.

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.

HIQA EP 1.4.2.1 Age if less than 12 years – value. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Numeric. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 31.

HIQA EP 1.4.2.2 Age if less than 12 years - type. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 31.

HIQA EP 1.4.3 Sex. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 31.

HIQA EP 1.4.4 Gender (cluster). Conformance: Required. Cardinality: 0..1. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 31.

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.

HIQA EP 1.4.4.1 Gender. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 31.

HIQA EP 1.4.4.2 Other gender identity. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 32.

1.5 Communication Details (grouping heading; no HIQA conformance)

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.

HIQA EP 1.5.1 Mobile phone number. Conformance: Required. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 32.

HIQA EP 1.5.2 Email address. Conformance: Required. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 33.

HIQA EP 1.5.3 Other Communication details (cluster). Conformance: Optional. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 33.

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.

HIQA EP 1.5.3.1 Communication details – Type. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 33.

HIQA EP 1.5.3.2 Communication Details – Value. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 33.

1.6 Clinical Information (grouping heading; no HIQA conformance)

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.

HIQA EP 1.6.1 Reason for not recording allergies and intolerances. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 35.

HIQA EP 1.6.2 Allergies and intolerances (record entry). Conformance: Required. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 35.

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.

HIQA EP 1.6.2.1 Allergies or intolerances. Conformance: Required. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 35.

HIQA EP 1.6.2.2 Causative agent or allergen. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 35.

HIQA EP 1.6.2.3 Additional information. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 35.

HIQA EP 1.6.2.4 Record entry provenance data for allergies and intolerances (cluster). Conformance: Required. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 36.

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.

HIQA EP 1.6.2.4.1 Record entry identifier. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 36.

HIQA EP 1.6.2.4.2 Record entry author. Conformance: Mandatory. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 36.

HIQA EP 1.6.2.4.3 Record entry date. Conformance: Mandatory. Cardinality: 0..1. HIQA datatype: Datetime. Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 36.

HIQA EP 1.6.2.4.4 Record entry source. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 37.

HIQA EP 1.6.2.4.5 Record entry language. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription record. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 37.

HIQA EP 1.6.3 Weight (record entry). Conformance: Optional. Cardinality: 0..1. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 37.

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.

HIQA EP 1.6.3.1 Weight value. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Decimal. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

HIQA EP 1.6.3.2 Weight type. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

HIQA EP 1.6.3.3 Record entry provenance data for weight (cluster). Conformance: Optional. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

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.

HIQA EP 1.6.3.3.1 Record entry identifier. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

HIQA EP 1.6.3.3.2 Record entry author. Conformance: Mandatory. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

HIQA EP 1.6.3.3.3 Record entry date. Conformance: Mandatory. Cardinality: 0..1. HIQA datatype: Datetime. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 38.

HIQA EP 1.6.3.3.4 Record entry source. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 39.

HIQA EP 1.6.3.3.5 Record entry language. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 39.

HIQA EP 1.6.4 Height (record entry). Conformance: Optional. Cardinality: 0..1. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 39.

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.

HIQA EP 1.6.4.1 Height value. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Decimal. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 40.

HIQA EP 1.6.4.2 Height type. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 40.

HIQA EP 1.6.4.3 Record entry provenance data for height (cluster). Conformance: Optional. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 40.

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.

HIQA EP 1.6.4.3.1 Record entry identifier. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 40.

HIQA EP 1.6.4.3.2 Record entry author. Conformance: Mandatory. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 40.

HIQA EP 1.6.4.3.3 Record entry date. Conformance: Mandatory. Cardinality: 0..1. HIQA datatype: Datetime. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 41.

HIQA EP 1.6.4.3.4 Record entry source. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 41.

HIQA EP 1.6.4.3.5 Record entry language. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Expected to be auto-populated from another system. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 41.

HIQA EP 1.6.5 Additional notes. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 41.

Section 2. Health Practitioner Details (grouping heading; no HIQA conformance)

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.

HIQA EP 2.1 Name title. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 45.

HIQA EP 2.2 Forename. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 45.

HIQA EP 2.3 Surname. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 45.

HIQA EP 2.4 Name suffix. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 46.

HIQA EP 2.5 Health practitioner role and speciality (cluster). Conformance: Required. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 46.

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.

HIQA EP 2.5.1 Health practitioner role. Conformance: Required. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 46.

HIQA EP 2.5.2 Health practitioner specialty. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 47.

HIQA EP 2.6 Health practitioner registration (cluster). Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 47.

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.

HIQA EP 2.6.1 Health Professional body registration – type. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 47.

HIQA EP 2.6.2 Health Professional body registration – value. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 48.

HIQA EP 2.7 Healthcare facility name. Conformance: Required. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 48.

HIQA EP 2.8 Healthcare facility identifier. Conformance: Required. Cardinality: 0..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 49.

HIQA EP 2.9 Healthcare facility address (cluster). Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 49.

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.

HIQA EP 2.9.1 Postcode. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 49.

HIQA EP 2.9.2 Address line(s). Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 50.

HIQA EP 2.9.3 Suburb/Town/ Townland/Locality. Conformance: Required. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 50.

HIQA EP 2.9.4 District/ County. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded Value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 50.

HIQA EP 2.9.5 Country. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 50.

HIQA EP 2.10 Communication details (cluster). Conformance: Mandatory. Cardinality: 1..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 51.

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.

HIQA EP 2.10.1 Telephone Number. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 51.

HIQA EP 2.10.2 Email address. Conformance: Required. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 52.

HIQA EP 2.10.3 Other Communication details (cluster). Conformance: Optional. Cardinality: 0..*. HIQA datatype: (none given). Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 52.

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.

HIQA EP 2.10.3.1 Communication details – Type. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Coded value. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 53.

HIQA EP 2.10.3.2 Communication Details – Value. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Alpha-numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 53.

HIQA EP 2.11 Location ID (GLN). Conformance: Required. Cardinality: 0..1. HIQA datatype: Numeric. Applies to: prescription and dispensation records. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 53.

HIQA EP 2.12 GMS Panel ID. Conformance: Optional. Cardinality: 0..1. HIQA datatype: Numeric. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 53.

HIQA EP 2.13 Signature. Conformance: Required. Cardinality: 0..1. HIQA datatype: Multi-media. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 54.

Section 3. Medication Prescription (grouping heading; no HIQA conformance)

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.

HIQA EP 3.1 Electronic prescription identifier (cluster). Conformance: Mandatory. Cardinality: 1..*. HIQA datatype: Alpha-numeric Alpha-numeric. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 57.

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.

HIQA EP 3.1.1 Electronic prescription identifier – type. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 57.

HIQA EP 3.1.2 Electronic prescription identifier – value. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Alpha-numeric. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 57.

HIQA EP 3.2 Date and time of issuing the prescription. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: DateTime. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 58.

HIQA EP 3.3 Prescription Status (cluster). Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: (none given). Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 58.

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.

HIQA EP 3.3.1 Status. Conformance: Mandatory. Cardinality: 1..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 58.

HIQA EP 3.3.2 Status reason. Conformance: Required. Cardinality: 0..1. HIQA datatype: Coded value. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 59.

HIQA EP 3.3.3 Status reason (free text). Conformance: Optional. Cardinality: 0..1. HIQA datatype: Free text. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 59.

HIQA EP 3.4 Presented form. Conformance: Optional. Cardinality: 0..*. HIQA datatype: Attachment. Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 59.

HIQA EP 3.5 Prescription item (cluster). Conformance: Mandatory. Cardinality: 1..*. HIQA datatype: (none given). Applies to: prescription record. Source: HIQA Draft National Standard for Electronic Prescriptions and Electronic Dispensations, v1.1 draft for public consultation, September 2026, p. 60.

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.