MyHealth@EU Core - Downloaded Version 1.0.0 See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Logical Model: Document model

MyHealth@EU refined model for document

Usages:

• This Logical Model is not used by any profiles in this Implementation Guide

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

• Key Elements Table
• Differential Table
• Snapshot Table
• Statistics/References
• All

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
period		0..1	Period	Time of service that is being documented
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime		1..1	dateTime	Date and time of the approval of the document by Attester
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime		1..1	dateTime	Date and time when the document was authorised
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Binding Description: (preferred): LOINC, SNOMED CT, dicom-cid-33-Modality Obligations Actor SHOULD:handle MyHealth@EU Handler
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuDocument.header.​language	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​documentType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​eventType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDocument

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Obligations Actor SHOULD:handle MyHealth@EU Handler
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
period		0..1	Period	Time of service that is being documented
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime		1..1	dateTime	Date and time of the approval of the document by Attester
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime		1..1	dateTime	Date and time when the document was authorised
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Binding Description: (preferred): LOINC, SNOMED CT, dicom-cid-33-Modality Obligations Actor SHOULD:handle MyHealth@EU Handler
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuDocument.header.​language	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​documentType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​eventType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDocument

Summary

Key Elements View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
period		0..1	Period	Time of service that is being documented
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime		1..1	dateTime	Date and time of the approval of the document by Attester
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime		1..1	dateTime	Date and time when the document was authorised
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Binding Description: (preferred): LOINC, SNOMED CT, dicom-cid-33-Modality Obligations Actor SHOULD:handle MyHealth@EU Handler
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuDocument.header.​language	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​documentType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​eventType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​serviceSpecialty	Base	preferred		Not State	Unknown

Differential View

This structure is derived from EHDSDocument

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Obligations Actor SHOULD:handle MyHealth@EU Handler
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuDocument		0..*	EHDSDocument	Document model Elements defined in Ancestors:header, header, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor SHALL:handle MyHealth@EU Handler
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor SHALL:handle MyHealth@EU Handler
author[x]	O	1..*		Author(s) of the document Obligations Actor SHALL:handle MyHealth@EU Handler
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor SHOULD:handle MyHealth@EU Handler
status	O	1..1	CodeableConcept	Status of the document Obligations Actor SHALL:handle MyHealth@EU Handler
language	O	0..1	CodeableConcept	Language in which the resource is written. Language is expressed by the IETF language tag. Binding Description: (preferred): BCP 47 Obligations Actor SHALL:handle MyHealth@EU Handler
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor SHALL:handle MyHealth@EU Handler
documentTitle	O	1..1	string	Human readable document title that can be displayed in search results, etc. This can be documentType's display name, or it can be assembled from multiple elements. Examples: 'Laboratory Result Report', 'Patient Summary of Jane Green 10.12.2024' Obligations Actor SHALL:handle MyHealth@EU Handler
period		0..1	Period	Time of service that is being documented
version	O	0..1	string	Business version of the document. The exact algorithm for versioning is decided by the producer/custodian Obligations Actor SHOULD:handle MyHealth@EU Handler
attestation	O	0..*	Base	Document attestation details Obligations Actor MAY:able-to-populate MyHealth@EU Handler
attester[x]		1..1		Attester who validated the document
attesterMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
attesterMyHealthEuDevice			MyHealthEuDevice
datetime		1..1	dateTime	Date and time of the approval of the document by Attester
legalAuthentication	O	0..*	Base	Document legal authentication details Obligations Actor SHALL:handle MyHealth@EU Handler
legalAuthenticator[x]		1..1		The person or organisation taking responsibility for the medical content of the document (typically the person who signs it)
legalAuthenticatorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
legalAuthenticatorMyHealthEuOrganisation			MyHealthEuOrganisation
datetime		1..1	dateTime	Date and time when the document was authorised
eventType	O	0..*	CodeableConcept	Categorisation 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 between data sharing parties. This meta-data element serves primarily for searching and filtering purposes. Binding Description: (preferred): LOINC, SNOMED CT, dicom-cid-33-Modality Obligations Actor SHOULD:handle MyHealth@EU Handler
serviceSpecialty		0..*	CodeableConcept	Additional details about where the content was created (e.g. clinical specialty) Binding Description: (preferred): SNOMED CT
custodian	O	0..1	MyHealthEuOrganisation	Organisation that is in charge of maintaining the document/report. Obligations Actor SHOULD:handle MyHealth@EU Handler
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor MAY:able-to-populate MyHealth@EU Handler
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuDocument.header.​language	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​documentType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​eventType	Base	preferred		Not State	Unknown
MyHealthEuDocument.header.​serviceSpecialty	Base	preferred		Not State	Unknown

This structure is derived from EHDSDocument

Summary

Other representations of profile: CSV, Excel