Patient or Subject of care. Sections A1.1 and A1.2 of the eHN guideline.

A.1.1.1 National healthcare patient ID - Country ID, unique to the patient in that country. Example: ID for Portuguese patient

A.1.1.2 Family name/surname - The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

A.1.1.3 Given name� - The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.��

A.1.1.4 Date of birth� - The date of birth of the patient [ISO TS 22220]. As age of the patient might be important for correct interpretation of the test result values, complete date of birth should be provided. - Preferred system(s): Complete date, without time, following the ISO 8601�

A.1.1.5 Gender - This field must contain a recognised valid value for ""administrative gender"". If different, ""physiological gender"" should be communicated elsewhere. - Preferred system(s): HL7 Administrative Gender�

A.1.1.5 Country of affiliation - Name of country of affiliation - Preferred system(s): ISO 3166

A.1.2.1 Patient address - Patient address

Address

A.1.2.1.1 Street - Example: Rua dos Campe�es

A.1.2.1.2 House number - Example: 246

A.1.2.1.3 City - Example: Porto

A.1.2.1.4 Post code - Example: 4500

A.1.2.1.5 State or province - Example: Vila Nova de Gaia

A.1.2.1.6 Country - Example: PT - Preferred system(s): ISO 3166

A.1.2.1.7 Telephone no. - Example: +351 20 7025 6161

A.1.2.1.8 Email - Example: jens@bigsmile.eu

A.1.2.2 Preferred HP to contact - This section can be repeated and linked to any specific information in the Patient Summary, for example a link between a rare disease problem (A.2.3.1) and the rare disease specialist responsible for the care of the individual patient (this section).

A.1.2.2.1 Name of the HP - Name of the Health Professional that has been treating or taking responsibility for the patient.

A.1.2.2.2 Role of the HP - Health professional role

A.1.2.2.3 HP Organisation - Health professional organisation

A.1.2.2.4 Telephone no. - Example: +45 20 7025 6161

A.1.2.2.5 Email - Email of the HP/legal organisation

A.1.2.2.6 Network affiliation - The HP organization is affiliated with a European network, for example an ERN.

A.1.2.2.7 Related with - Identify the entry or entries of this Patient Summary for which the health professional is the preferred contact.

A.1.2.3 Contact person/ legal guardian - Role of the contact person: legal guardian, next of kin, other person to contact - Preferred system(s): HL7 RoleClass

A.1.2.3.1 Role of that person - Relationship type with the patient (e.g. father, wife, daughter) HL7 RoleCode

A.1.2.3.2 Relationship level - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.3 Given name - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.4 Family name/surname - This field can contain more than one element. Example: Espa�ol Smith

A.1.2.3.5 Telephone no. - Example: +45 20 7025 6161

A.1.2.3.6 Email - Email of the contact person/legal guardian

Patient or Subject of care. Sections A1.1 and A1.2 of the eHN guideline.

A.1.1.1 National healthcare patient ID - Country ID, unique to the patient in that country. Example: ID for Portuguese patient

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.

A.1.1.2 Family name/surname - The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

A.1.1.3 Given name� - The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.��

A.1.1.4 Date of birth� - The date of birth of the patient [ISO TS 22220]. As age of the patient might be important for correct interpretation of the test result values, complete date of birth should be provided. - Preferred system(s): Complete date, without time, following the ISO 8601�

A.1.1.5 Gender - This field must contain a recognised valid value for ""administrative gender"". If different, ""physiological gender"" should be communicated elsewhere. - Preferred system(s): HL7 Administrative Gender�

A.1.1.5 Country of affiliation - Name of country of affiliation - Preferred system(s): ISO 3166

A.1.2.1 Patient address - Patient address

Address

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.

A.1.2.1.1 Street - Example: Rua dos Campe�es

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.

A.1.2.1.2 House number - Example: 246

A.1.2.1.3 City - Example: Porto

A.1.2.1.4 Post code - Example: 4500

A.1.2.1.5 State or province - Example: Vila Nova de Gaia

A.1.2.1.6 Country - Example: PT - Preferred system(s): ISO 3166

A.1.2.1.7 Telephone no. - Example: +351 20 7025 6161

A.1.2.1.8 Email - Example: jens@bigsmile.eu

A.1.2.2 Preferred HP to contact - This section can be repeated and linked to any specific information in the Patient Summary, for example a link between a rare disease problem (A.2.3.1) and the rare disease specialist responsible for the care of the individual patient (this section).

A.1.2.2.1 Name of the HP - Name of the Health Professional that has been treating or taking responsibility for the patient.

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.

A.1.2.2.2 Role of the HP - Health professional role

A.1.2.2.3 HP Organisation - Health professional organisation

A.1.2.2.4 Telephone no. - Example: +45 20 7025 6161

A.1.2.2.5 Email - Email of the HP/legal organisation

A.1.2.2.6 Network affiliation - The HP organization is affiliated with a European network, for example an ERN.

A.1.2.2.7 Related with - Identify the entry or entries of this Patient Summary for which the health professional is the preferred contact.

A.1.2.3 Contact person/ legal guardian - Role of the contact person: legal guardian, next of kin, other person to contact - Preferred system(s): HL7 RoleClass

A.1.2.3.1 Role of that person - Relationship type with the patient (e.g. father, wife, daughter) HL7 RoleCode

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.

A.1.2.3.2 Relationship level - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.3 Given name - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.4 Family name/surname - This field can contain more than one element. Example: Espa�ol Smith

A.1.2.3.5 Telephone no. - Example: +45 20 7025 6161

A.1.2.3.6 Email - Email of the contact person/legal guardian

Patient or Subject of care. Sections A1.1 and A1.2 of the eHN guideline.

A.1.1.1 National healthcare patient ID - Country ID, unique to the patient in that country. Example: ID for Portuguese patient

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.

A.1.1.2 Family name/surname - The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

A.1.1.3 Given name� - The given name/first name of the patient (also known as forename or first name). This field can contain more than one element.��

A.1.1.4 Date of birth� - The date of birth of the patient [ISO TS 22220]. As age of the patient might be important for correct interpretation of the test result values, complete date of birth should be provided. - Preferred system(s): Complete date, without time, following the ISO 8601�

A.1.1.5 Gender - This field must contain a recognised valid value for ""administrative gender"". If different, ""physiological gender"" should be communicated elsewhere. - Preferred system(s): HL7 Administrative Gender�

A.1.1.5 Country of affiliation - Name of country of affiliation - Preferred system(s): ISO 3166

A.1.2.1 Patient address - Patient address

Address

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.

A.1.2.1.1 Street - Example: Rua dos Campe�es

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.

A.1.2.1.2 House number - Example: 246

A.1.2.1.3 City - Example: Porto

A.1.2.1.4 Post code - Example: 4500

A.1.2.1.5 State or province - Example: Vila Nova de Gaia

A.1.2.1.6 Country - Example: PT - Preferred system(s): ISO 3166

A.1.2.1.7 Telephone no. - Example: +351 20 7025 6161

A.1.2.1.8 Email - Example: jens@bigsmile.eu

A.1.2.2 Preferred HP to contact - This section can be repeated and linked to any specific information in the Patient Summary, for example a link between a rare disease problem (A.2.3.1) and the rare disease specialist responsible for the care of the individual patient (this section).

A.1.2.2.1 Name of the HP - Name of the Health Professional that has been treating or taking responsibility for the patient.

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.

A.1.2.2.2 Role of the HP - Health professional role

A.1.2.2.3 HP Organisation - Health professional organisation

A.1.2.2.4 Telephone no. - Example: +45 20 7025 6161

A.1.2.2.5 Email - Email of the HP/legal organisation

A.1.2.2.6 Network affiliation - The HP organization is affiliated with a European network, for example an ERN.

A.1.2.2.7 Related with - Identify the entry or entries of this Patient Summary for which the health professional is the preferred contact.

A.1.2.3 Contact person/ legal guardian - Role of the contact person: legal guardian, next of kin, other person to contact - Preferred system(s): HL7 RoleClass

A.1.2.3.1 Role of that person - Relationship type with the patient (e.g. father, wife, daughter) HL7 RoleCode

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.

A.1.2.3.2 Relationship level - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.3 Given name - The first name of the contact person/guardian (Example: Peter). This field can contain more than one element.

A.1.2.3.4 Family name/surname - This field can contain more than one element. Example: Espa�ol Smith

A.1.2.3.5 Telephone no. - Example: +45 20 7025 6161

A.1.2.3.6 Email - Email of the contact person/legal guardian