Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

Identification of the patient/subject

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

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

Complete date, following the ISO 8601.

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

Nationality of the patient.

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

Name of country of affiliation

Patient/subject related contact information

Patient address

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the patient has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the patient has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the patient has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the patient has his/her domicile.

The number of the street where the patient has his/her domicile.

The postal code where the patient has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

Health professional role. Multiple roles could be provided.

Health professional organisation

Name of the organization

Address of the organization

Telecom of the organization

Specialty of the organization

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the preferred HP has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the preferred HP has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the preferred HP has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the preferred HP has his/her domicile.

The number of the street where the preferred HP has his/her domicile.

The postal code where the preferred HP has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person/ legal guardian (multiple contacts could be provided)

Role of the contact person: legal guardian, next of kin, other person to contact.

Relationship type with the patient (e.g. father, wife, daughter)

Given name of the contact person/guardian . This field can contain more than one element.

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the contact Person has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the contact Person has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the contact Person has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the contact Person has his/her domicile.

The number of the street where the contact Person has his/her domicile.

The postal code where the contact Person has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person organisation information.

Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

Identification of the patient/subject

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

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

Complete date, following the ISO 8601.

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

Nationality of the patient.

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

Name of country of affiliation

Patient/subject related contact information

Patient address

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

The street where the patient has his/her domicile.

The number of the street where the patient has his/her domicile.

The city where the patient has his/her domicile.

The postal code where the patient has his/her domicile.

The state or province where the patient has his/her domicile.

The country where the patient has his/her domicile (Country of affiliation).

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

Health professional role. Multiple roles could be provided.

Health professional organisation

Name of the organization

Address of the organization

Telecom of the organization

Specialty of the organization

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

The street where the preferred HP has his/her domicile.

The number of the street where the preferred HP has his/her domicile.

The city where the preferred HP has his/her domicile.

The postal code where the preferred HP has his/her domicile.

The state or province where the preferred HP has his/her domicile.

The country where the preferred HP has his/her domicile (Country of affiliation).

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person/ legal guardian (multiple contacts could be provided)

Role of the contact person: legal guardian, next of kin, other person to contact.

Relationship type with the patient (e.g. father, wife, daughter)

Given name of the contact person/guardian . This field can contain more than one element.

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

The street where the contact Person has his/her domicile.

The number of the street where the contact Person has his/her domicile.

The city where the contact Person has his/her domicile.

The postal code where the contact Person has his/her domicile.

The state or province where the contact Person has his/her domicile.

The country where the contact Person has his/her domicile (Country of affiliation).

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person organisation information.

Hospital Discharge Report - Hospital Discharge Report subject data element - A.1.1 and A.1.2 eHN

Identification of the patient/subject

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

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

Complete date, following the ISO 8601.

An identifier of the patient that is unique within a defined scope. Example: National ID (birth number) for a Czech patient. Multiple identifiers could be provided

Nationality of the patient.

This field must contain a recognised valid value for "administrative gender". If different, "physiological gender" should be communicated elsewhere in the relevant clinical information section.

Name of country of affiliation

Patient/subject related contact information

Patient address

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the patient has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the patient has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the patient has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the patient has his/her domicile.

The number of the street where the patient has his/her domicile.

The postal code where the patient has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Preferred health professional (HP) - This section can be repeated and linked to any specific information in the document, for example a link between a rare disease problem and the rare disease specialist responsible for the care of the individual patient (this section).

An identifier of the health professional that is unique within a defined scope. Example: National health professional ID. Multiple identifiers could be provided.

Name of the health professional that has been treating or taking responsibility for the patient.[the structure of the name will be the same as for the patient (given name, family name / surname)]

Health professional role. Multiple roles could be provided.

Health professional organisation

Name of the organization

Address of the organization

Telecom of the organization

Specialty of the organization

Mailing and home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the preferred HP has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the preferred HP has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the preferred HP has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the preferred HP has his/her domicile.

The number of the street where the preferred HP has his/her domicile.

The postal code where the preferred HP has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person/ legal guardian (multiple contacts could be provided)

Role of the contact person: legal guardian, next of kin, other person to contact.

Relationship type with the patient (e.g. father, wife, daughter)

Given name of the contact person/guardian . This field can contain more than one element.

Family name of the contact person. This field can contain more than one element [the structure of the name will be the same as for the patient (given name, family name / surname)]..

Mailing, home or office addresses. The addresses are always sequences of address parts (e.g. street address line, country, postcode, city) even if postal address formats may vary depending on the country. An address may or may not include a specific use code; if this attribute is not present it is assumed to be the default address useful for any purpose.

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

The city where the contact Person has his/her domicile.

The name of the administrative area (county).

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

The state or province where the contact Person has his/her domicile.

A postal code designating a region defined by the postal service.

The country where the contact Person has his/her domicile (Country of affiliation).

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

The street where the contact Person has his/her domicile.

The number of the street where the contact Person has his/her domicile.

The postal code where the contact Person has his/her domicile.

Telecommunication contact information (addresses) associated with a person, such as phone number, email, or messaging service. Multiple telecommunication addresses might be provided.

Contact person organisation information.