MyHealth@EU Core
1.0.0 - trial-use 150

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

## Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Requirements: Actor Definitions

The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.

MyHealth@EU Handler | A system that handles MyHealth@EU FHIR resources, responsible for correctly processing and displaying the data elements marked with obligations in this Implementation Guide.

### Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Address model | MyHealth@EU refined base model for Address structure
Allergy intolerance model | MyHealth@EU refined model for allergy or intolerance
Body structure model | MyHealth@EU refined base model for body structure
Condition model | MyHealth@EU refined model for a clinical condition, problem, diagnosis, or other event, situation, or issue
Device model | MyHealth@EU refined model for device information
Document model | MyHealth@EU refined model for document
Health professional model | MyHealth@EU refined base model for Health professional (HP)
Human name model | MyHealth@EU refined base model for Human name
Immunisation model | MyHealth@EU refined model for immunisation
Location model | MyHealth@EU refined model for location
Medication model | MyHealth@EU refined model for prescribed/dispensed medication. The model is shared by statements, requests, dispensations, and treatment lines
Medication statement model | MyHealth@EU refined model for medication use statement
Organisation model | MyHealth@EU refined base model for Health provider or any other type of organisation
Patient model | MyHealth@EU refined model for patient (subject of care) information in the context of imaging
Procedure model | MyHealth@EU refined model for procedure
Related person model | MyHealth@EU refined model for information about a guardian or other person related to the subject of care
Telecom model | MyHealth@EU refined base model for Telecommunication contact information structure

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Allergy Intolerance (Core) | This profile sets minimum expectations for the AllergyIntolerance resource common to most of the use cases.
BodyStructure (Core) | This profile specifies how the HL7 FHIR BodyStructure resource should be used for conveying commonly used concepts in the European context.
Composition (Core) | This profile sets minimum expectations for the Composition resource for commonly used EHDS documents.
Condition (Core) | This profile sets minimum expectations for the Condition resource common to most of the use cases.
DiagnosticReport (Core) | This profile sets minimum expectations for the DiagnosticReport resource for commonly used EHDS documents.
Flag (Core) | This profile defines the core constraints and extensions for a Flag resource when used in European systems for communicating warnings, alerts, or reminders about important health information.
Immunization (Core) | This profile sets minimum expectations for the Immunization resource common to most of the use cases.
Location (Core) | This profile sets minimum expectations for the Location resource to be used for the purpose of this guide.
Medication (Core) | This profile sets minimum expectations for the Medication resource common to most of the use cases. This profile is adapted from the MPD work.
MedicationRequest (Core) | This profile sets minimum expectations for the MedicationRequest resource common to most of the use cases. This profile is adapted from the MPD work.
MedicationStatement (Core) | This profile sets minimum expectations for the MedicationStatement resource common to most of the use cases. This profile is adapted from the MPD work.
Observation: Medical Test Result (Core) | This profile introduces essential constraints and extensions for the Observation resource for Medical Test Results that apply across multiple use cases.
Organization (Core) | This profile sets minimum expectations for the Organization resource common to most of the use cases.
Patient (Core) | This profile sets minimum expectations for the Patient resource common to most of the use cases. When the ips-pat-1 invariant is satisfied (Patient.name.given, Patient.name.family or Patient.name.text SHALL be present) then this profile complies with the IPS patient profile.
Practitioner (Core) | This profile sets minimum expectations for the Practitioner resource common to most of the use cases.
PractitionerRole (Core) | This profile sets minimum expectations for the PractitionerRole resource common to most of the use cases.
Procedure (Core) | This profile represents the constraints applied to the Procedure resource by this guide.

### Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Address (MyHealth@EU) | This profile sets minimum expectations for the Address dataType common to most of the use cases.
Quantity (MyHealth@EU) | This profile of the Quantity data type constraints the Quantity (MyHealth@EU) profile defining a core value set for UCUM. The Quantity (MyHealth@EU) imposes the usage of the UCUM as the code system for units and allows expressing uncertainty of measurement.
Ratio (MyHealth@EU) | This profile of the Ratio data type constraints the Ratio (MyHealth@EU) profile defining a core value set for UCUM. The Ratio (MyHealth@EU) imposes the usage of the UCUM as the code system for units and allows expressing uncertainty of measurement.
Simple Quantity (MyHealth@EU) | This profile inherits from Quantity (MyHealth@EU) but behaves like a SimpleQuantity by forbidding the comparator element.

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

eHDSI Admission Reason With Exceptions | The Value Set is used for coding reason or reasons for admission, e.g. problem, procedure or finding. It is defined as the union of: (a) eHDSIIllnessesAndDisorder (b) eHDSIRareDisease (c) eHDSIProcedure (d) eHDSIExceptionalValue
eHDSI Agent or Allergen Substance With Exceptions | The Value Set is used for coding s specific allergen or other agent/substance (drug, food, chemical agent, etc.) to which the patient has an adverse reaction propensity. It is defined as the union of: (a) eHDSIAllergenNoDrug (b) eHDSISubstance (c) eHDSIExceptionalValue
eHDSI Agent or Allergen With Exceptions | The Value Set is used for coding s specific allergen or other agent/substance (drug, food, chemical agent, etc.) to which the patient has an adverse reaction propensity. It is defined as the union of: (a) eHDSIAllergenNoDrug (b) eHDSISubstance (c) eHDSIActiveIngredient (d) eHDSIExceptionalValue
eHDSI Allergy Reaction With Exceptions | The Value Set is used for coding clinical manifestation of the allergic reaction. It is defined as the union of: (a) eHDSIIllnessandDisorder (b) eHDSIReactionAllergy (c) eHDSIExceptionalValue
eHDSI Animal Species With Exceptions | The Value Set is used to code the animal species of specimen subject (animal of the patient). It also includes exceptional values.
eHDSI Body Site With Exceptions | The Value Set is used for the details about the anatomical location of a specimen in the Laboratory Result Report or the target body location of a procedure in the Patient Summary. It includes also exceptional values.
eHDSI Body Structure Location Qualifier with exceptions | This Value Set is used for the body structure location qualifier. Concepts modifying the anatomic location. It also includes exceptional values.
eHDSI Clinical Location Role Type With Exceptions | The Value Set is used to encode a role of a place that further classifies the clinical setting in which care is delivered during an encounter. It also includes exceptional values.
eHDSI Condition Finding With Exceptional Values | The Value Set is used to code clinical condition findings relevant for the medical imaging interpretation. It is defined as the union of: (a) EHDSIIllnessesAndDisorder (b) EHDSIRareDisease (c) EHDSIOncologyDisease (d) EHDSIAbsentOrUnknownProblem (e) EHDSIImagingFinding (f) EHDSIExceptionalValue
eHDSI Condition Stage Type With Exceptions | The Value Set is used for coding the kind of staging, such as pathological or clinical staging. It also includes exceptional values.
eHDSI Condition Stage With Exceptions | The Value Set is used for coding stage such as 'Stage 3' or 'Early Onset'. The determination of the stage is disease-specific, such as cancer, retinopathy of prematurity, kidney diseases, Alzheimer's, or Parkinson disease. It also includes exceptional values.
eHDSI Diagnostic Report Code With Exceptions | The Value Set is used for the diagnostic report type codes. It also includes exceptional values.
eHDSI Discharge Disposition With Exceptions | The Value Set is used for encoding category or kind of location after discharge. It also includes exceptional values.
eHDSI Document Types | Document Types
eHDSI Event Timing Combination | This Value Set is used for coding event timing of dosage regimen. It is defined as the union of: (a) eHDSITimingEvent (b) eHDSIEventTiming
eHDSI Illness and Disorder With Exceptions | The Value Set is used to code illness and disorders. It also includes exceptional values.
eHDSI Imaging Code With Exceptions | The Value Set is used for the standard imaging codes. It also includes exceptional values.
eHDSI Imaging Observation Method With Exceptions | The Value Set is used for coding imaging observation method to obtain the result. It also includes exceptional values.
eHDSI Imaging Procedure With Exceptions | The Value Set is used to encode the imaging procedures. It also includes exceptional values.
eHDSI Laboratory Codes With Exceptions | This Value Set is used for the standard laboratory codes. It also includes exceptional values.
eHDSI Laboratory Specimen Type With Exceptions | This Value Set is used for the kind of material that forms the specimen. It also includes exceptional values
eHDSI Laboratory Study Types With Exceptions | eHDSI Laboratory Study Types. Notes: Note 1: 26436-6 (Laboratory studies) enables issuing a report putting together observations from multiple specialties (disciplines) in the same text block, allowing delivery of a global interpretation comment at the end of the text block that will be rendered at the end of the report. Note 2: Mycology and parasitology, as well as bacteriology, are part of the 18725-2 (Microbiology studies (set)) studies. Note 3: Virology MAY be included in 18725-2 (MICROBIOLOGY STUDIES) or 18727-8 (SEROLOGY STUDIES) or split between both study types, depending upon the Content Creator Actor’s choice. It includes also exceptional values.
eHDSI Laboratory Technique With Exceptions | This Value Set is used to encode laboratory technique for the result measurement. It also includes exceptional values.
eHDSI Medical Device With Exceptions | eHDSI Medical Device. The Value Set contains exceptional values.
eHDSI Medication Reason With Exceptions | The Value Set is used for coding reason or reasons for medication. It is defined as the union of: (a) eHDSIIllnessandDisorder (b) eHDSIReactionAllergy (c) eHDSIRareDisease (c) eHDSIExceptionalValue
eHDSI Medication Status Reason With Exceptions | The Value Set is used for coding reasons for the current state of the medication used. It also includes exceptional values.
eHDSI Modalities | The Value Set is used to identify the type of equipment, or function or technique of that equipment, that created the data used to create an instance.
eHDSI Morphologic Abnormality With Exceptions | The Value Set is used to code the morphological abnormalities of the anatomical location where the material is taken. It also includes exceptional values.
eHDSI Observation Code With Exceptions | The Value Set is used for the observation type codes. It also includes exceptional values.
eHDSI Observation Interpretation With Exceptions | This Value Set is used for a rough qualitative interpretation of the Laboratory Observation Results. It also includes exceptional values.
eHDSI Observation Method With Exceptions | The Value Set is used for coding observation method to obtain the result. It also includes exceptional values.
eHDSI Observation Results Coded Value With Exceptions | The Value Set is used to code the value of observation result. It is defined as the union of: (a) eHDSIBloodGroupLab (b) eHDSIPresenceAbsence (c) eHDSIMicroorganism (d) eHDSIImagingFinding (e) eHDSIExceptionalValue
eHDSI Order Reason With Exceptions | The Value Set is used to code clinical conditions relevant for the laboratory results interpretation. It is defined as the union of: (a) EHDSIIllnessandDisorder (b) EHDSIRareDisease (c) EHDSIReactionAllergy (d) EHDSIExceptionalValue
eHDSI Problems and Diagnoses With Exceptions | The Value Set is used for coding the patient's relevant problems or diagnoses. It is defined as the union of: (a) eHDSIIllnessandDisorder (b) eHDSIRareDisease (c) eHDSIOncologyDisease (d) eHDSIAbsentOrUnknownProblem (e) eHDSIExceptionalValue
eHDSI Procedure With Exceptions | The Value Set is used to code procedures. It also includes exceptional values.
eHDSI Reaction allergy With Exceptions | The Value Set is used to allergy reaction manifestation. It also includes exceptional values.
eHDSI Reference Range Applies To With Exceptions | This value set defines a set of codes that can be used to indicate the particular target population the reference range applies to. It also includes exceptional values.
eHDSI Reference Range Meaning With Exceptions | This value set defines a set of codes for a reference range qualifier. It also includes exceptional values.
eHDSI Results Coded Value Imaging With Exceptions | The Value Set is used to code the value of imaging observation result. It is defined as the union of: (a) eHDSIImagingFinding (b) eHDSIPresenceAbsence (c) eHDSIExceptionalValue
eHDSI Results Coded Value Laboratory With Exceptions | The Value Set is used to code the value of laboratory observation result. It is defined as the union of: (a) eHDSIBloodGroupLab (b) eHDSIPresenceAbsence (c) eHDSIMicroorganism (d) eHDSIExceptionalValue
eHDSI Specimen Collection Method With Exceptions | The Value Set is used for coding specimen collection procedures. It also includes exceptional values
eHDSI Substance With Exceptions | The Value Set is used for coding substances. It also includes exceptional values.
eHDSI Vaccine With Exceptions | The Value Set is used to identify the patient's vaccinations. It also contains exceptional values.
eHDSI Vital Signs and Anthropometric Observation Codes With Exceptions | The Value set is used for the standard vital sign and anthropometric observation codes. It is defined as the union of: (a) eHDSIVitalSignCode (b) eHDSIAnthropometricCode (c) eHDSIExceptionalValue

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

AllergyIntolerance: example | HL7 FHIR AllergyIntolerance example for MyHealth@EU Core.
BodyStructure: example | HL7 FHIR BodyStructure example for MyHealth@EU Core.
Composition: example | HL7 FHIR Composition example for MyHealth@EU Core.
Condition: example | HL7 FHIR Condition example for MyHealth@EU Core.
DiagnosticReport: example | HL7 FHIR DiagnosticReport example for MyHealth@EU Core.
Flag: example | HL7 FHIR Flag example for MyHealth@EU Core.
Immunization: example | HL7 FHIR Immunization example for MyHealth@EU Core.
Location: example | HL7 FHIR Location example for MyHealth@EU Core.
Medication: example | HL7 FHIR Medication example for MyHealth@EU Core.
MedicationRequest: example | HL7 FHIR MedicationRequest example for MyHealth@EU Core.
MedicationStatement: example | HL7 FHIR MedicationStatement example for MyHealth@EU Core.
Observation: Medical Test Result example | HL7 FHIR Observation (Medical Test Result) example for MyHealth@EU Core.
Organization: example | HL7 FHIR Organization example for MyHealth@EU Laboratory Result Report (LRR).
Patient | HL7 FHIR Patient example for MyHealth@EU Core project.
Practitioner: example | HL7 FHIR Practitioner example for MyHealth@EU Laboratory Result Report (LRR).
PractitionerRole: example | HL7 FHIR PractionerRole example for MyHealth@EU Laboratory Result Report (LRR).
Procedure: example | HL7 FHIR Procedure example for MyHealth@EU Core.