MyHealth@Eu Vaccination - Local Development build (v10.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

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

Logical Model: MyHealth@EU Vaccination History - Logical Model

Logical model representing the EU Vaccination history as defined by the MyHealth@EU specification.

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
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
author[x]	O	1..*		Author(s) of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor Source SHOULD:handle MyHealth@EU Handler from Document model
status	O	1..1	CodeableConcept	Status of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
attestation	O	0..*	Base	Document attestation details Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Terminology Bindings

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

This structure is derived from MyHealthEuDocument

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
author[x]	O	1..*		Author(s) of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor Source SHOULD:handle MyHealth@EU Handler from Document model
status	O	1..1	CodeableConcept	Status of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
attestation	O	0..*	Base	Document attestation details Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Terminology Bindings

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

This structure is derived from MyHealthEuDocument

Summary

Mandatory: 0 element(1 nested mandatory element)

Key Elements View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
author[x]	O	1..*		Author(s) of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor Source SHOULD:handle MyHealth@EU Handler from Document model
status	O	1..1	CodeableConcept	Status of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
attestation	O	0..*	Base	Document attestation details Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Terminology Bindings

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

Differential View

This structure is derived from MyHealthEuDocument

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuVaccinationHistory		0..*	MyHealthEuDocument	MyHealth@EU Vaccination History - Logical Model Elements defined in Ancestors:header, header, presentedForm, presentedForm
header		1..1	Base	Document header
subject	O	1..1	MyHealthEuPatient	Patient/subject information Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
identifier	O	1..*	Identifier	Unique identifier of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
author[x]	O	1..*		Author(s) of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
authorMyHealthEuHealthProfessional			MyHealthEuHealthProfessional
authorMyHealthEuOrganisation			MyHealthEuOrganisation
authorMyHealthEuDevice			MyHealthEuDevice
date	O	1..1	dateTime	Date of finalising/issuing the document Obligations Actor Source SHOULD:handle MyHealth@EU Handler from Document model
status	O	1..1	CodeableConcept	Status of the document Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
documentType	O	1..1	CodeableConcept	Type of document at hand, e.g. 60591-5 Patient summary document. Binding Description: (preferred): LOINC Obligations Actor Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
attestation	O	0..*	Base	Document attestation details Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
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 Source SHALL:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
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 Source SHOULD:handle MyHealth@EU Handler from Document model
presentedForm	O	0..*	EHDSAttachment	A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document Obligations Actor Source MAY:able-to-populate MyHealth@EU Handler from Document model
immunisations		1..1	Base	Section: Immunisations
generatedNarrative		0..1	string	Narrative, potentially formatted, content of the whole section.
immunisation		0..*	MyHealthEuVaccination	Immunisations given to the patient and their status at the point of care.
note		0..1	string	Free text notes by the health professional
Documentation for this format

Terminology Bindings

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

This structure is derived from MyHealthEuDocument

Summary

Mandatory: 0 element(1 nested mandatory element)

Other representations of profile: CSV, Excel