Common elements for all EHDS document exchange.

Unique identifier of the data object

Patient/subject information

Country of the data exchange initiator.

ISO 3166

Patient/subject guardian and related person information

Some roles for the related person are essential for data access control. For example, the role of the guardian is essential for the data access control of a minor 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Identification and description of the contact person for that patient. This includes relatives, guardians, caring persons etc.

The nature of the relationship between the patient and the related person.

HL7 RoleCode

Some roles for the related person are essential for data access control. For example, the role of the guardian is essential for the data access control of a minor patient.

Document/resource authoring details

Author by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Date and time of the last update to the document/information

Status of the information

Business version of the data object.

Language in which the information is written. Language is expressed by the IETF language tag.

BCP 47

The presentation of the data, e.g. a PDF document, a video, a text file, etc. In case of unstructured data, this is the actual content.

Author by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Identifies the type of document at hand, e.g. Hospital discharge report.

LOINC

Categorization of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement betwen data sharing parties. This meta-data element serves primarily for searching and filtering purpuses.

LOINC, SNOMED CT, dicom-cid-33-Modality

Document title, such as Hospital Discharge Report, Laboratory Result Report, etc.

The status of the Hospital discharge report. E.g., preliminary, final.

hl7:CompositionStatus

Time of service that is being documented

Date and time of the report creation.

Document attestation details

Attester who validated the document. Mulitple attesters could be provided.

Date and time of the approval of the document by Attester.

Document legal authentication

The person taking responsibility for the medical content of the document

Date and time when the document was authorized.

Additional details about where the content was created (e.g. clinical specialty)

SNOMED CT

Organisation that is in charge of maintaining the document/report.

An identifier of the document constraints, encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType.

HL7 Document Format Codes

Related documents and information sources

...

Common elements for all EHDS document exchange.

Identifies the type of document at hand, e.g. Hospital discharge report.

LOINC

Categorization of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement betwen data sharing parties. This meta-data element serves primarily for searching and filtering purpuses.

LOINC, SNOMED CT, dicom-cid-33-Modality

Document title, such as Hospital Discharge Report, Laboratory Result Report, etc.

The status of the Hospital discharge report. E.g., preliminary, final.

hl7:CompositionStatus

Time of service that is being documented

Date and time of the report creation.

Document attestation details

Attester who validated the document. Mulitple attesters could be provided.

Date and time of the approval of the document by Attester.

Document legal authentication

The person taking responsibility for the medical content of the document

Date and time when the document was authorized.

Additional details about where the content was created (e.g. clinical specialty)

SNOMED CT

Organisation that is in charge of maintaining the document/report.

An identifier of the document constraints, encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType.

HL7 Document Format Codes

Related documents and information sources

...

Common elements for all EHDS document exchange.

Unique identifier of the data object

Patient/subject information

Country of the data exchange initiator.

ISO 3166

Patient/subject guardian and related person information

Some roles for the related person are essential for data access control. For example, the role of the guardian is essential for the data access control of a minor 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Identification and description of the contact person for that patient. This includes relatives, guardians, caring persons etc.

The nature of the relationship between the patient and the related person.

HL7 RoleCode

Some roles for the related person are essential for data access control. For example, the role of the guardian is essential for the data access control of a minor patient.

Document/resource authoring details

Author by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Date and time of the last update to the document/information

Status of the information

Business version of the data object.

Language in which the information is written. Language is expressed by the IETF language tag.

BCP 47

The presentation of the data, e.g. a PDF document, a video, a text file, etc. In case of unstructured data, this is the actual content.

Author by whom the resource was/were authored. Multiple authors could be provided.

Date and time of the issuing the document/resource by its author.

Identifies the type of document at hand, e.g. Hospital discharge report.

LOINC

Categorization of the event covered by the document (e.g. laboratory study types, imaging study types including modality, etc.). Selection of such tags or labels depends on the use case and agreement betwen data sharing parties. This meta-data element serves primarily for searching and filtering purpuses.

LOINC, SNOMED CT, dicom-cid-33-Modality

Document title, such as Hospital Discharge Report, Laboratory Result Report, etc.

The status of the Hospital discharge report. E.g., preliminary, final.

hl7:CompositionStatus

Time of service that is being documented

Date and time of the report creation.

Document attestation details

Attester who validated the document. Mulitple attesters could be provided.

Date and time of the approval of the document by Attester.

Document legal authentication

The person taking responsibility for the medical content of the document

Date and time when the document was authorized.

Additional details about where the content was created (e.g. clinical specialty)

SNOMED CT

Organisation that is in charge of maintaining the document/report.

An identifier of the document constraints, encoding, structure, and template that the document conforms to beyond the base format indicated in the mimeType.

HL7 Document Format Codes

Related documents and information sources

...