List of active profiles

This page contains a list with the name and a short description for all the active profiles, that are defined in this IG.

A

• Attachment - IEHR
  This profile represents the constraints applied to the Attachment resource when it is used in a DocumentReference-MedicalDocument resource.
  
• AuditEvent - IEHR
  This profile is based on the AuditEvent StructureDefinition and makes the agent performing the audit and the time it was perfomed mandatory.

B

• BioSignal - IEHR
  This profile is based on the Observation StructureDefinition and represents a BioSignal. Since a BioSignal may contain more than one value, the actual values of the BioSignal are included as components (Observation.component).
• Bundle - IEHR
  This profile is based on the Bundle StructureDefinition and adds a constraint, that makes the Signature mandatory, if the bundle has the type document.

C

• Condition - IEHR
  This profile is based on the Condition resource and constraints the code to be an ICD-10 code.
• Composition - IEHR
  This profile is based on the ClinicalDocument StructureDefinition and constrains extensions that allow to add a signature to the Composition and its own confidentiality code to each section.
• Composition - IPS - IEHR
  This profile is based on the Composition-IPS StructureDefinition and further constrains the result-section to avoid a potential error when referencing Observation-results.
• Consent - IEHR
  This profile is based on the Consent resource and defines multiple mandatory attributes to ensure the accountability of a Patient's agreement to an attached structured Consent document.
• Consent - IEHR
  This profile is based on the Provenance resource and constrains the Provenance's agent to be of type author, the target to reference a Consent-IEHR and the mandatory signature to be of type ConsentSignature-IEHR.

D

• DiagnosticConclusion - IEHR
  This profile is based in the Condition StructureDefinition and further constrains the code and note attributes to allow the addition of unstructured data to a CarePlan (TreatmentPlan-IEHR) in the form of free text.
• DiagnosticReport BioSignalReport - IEHR
  This profile represents the constraints applied to the DiagnosticReport when it represents findings of Instrumental Examination in the context of the CBDE. It can be used to represent a BioSignal as well as single images, e.g EKG readouts, or complete ImagingStudies.
• DiagnosticReport - IEHR
  This profile represents the constraints applied to a general DiagnosticReport in the context of the CBDE. The different types of reports in the CBDE context are derived from it.
• DiagnosticReport Imaging - IEHR
  This profile represents the constraints applied to the DiagnosticReport when it represents radiology findings in the context of the CBDE. It is used to document the diagnostics generated from the results of imaging observations and the informations surrounding them. It can be used to either represent single images, e.g EKG readouts, or complete ImagingStudies.
• DiagnosticReport LaboratoryResult - IEHR
  This profile represents the constraints applied to the DiagnosticReport when it represents laboratory findings in the context of the CBDE. It is used to document the diagnostics generated from the results of laboratory observations and the informations surrounding them.
• DiagnosticReport VitalSignReport - IEHR
  This profile represents the constraints applied to the DiagnosticReport when it represents vital signs in the context of CBDE. It is used to document diagnoses generated from results of vital sign surveys and the information accompanying them.
• DocumentManifest-IEHR
  This profile represents the constraints applied to the DocumentManifest resource when it is used in the context of the CBDE. It is used to represent a collection of unstructured documents, that can then be exchanged.
• DocumentReference - IEHR
  This profile represents the constraints applied to the DocumentReference resource when it represents medicaldocuments in the context of the CBDE. It is used to represent unstructered documents as structured resources, that can then be exchanged.

E

• Encounter - IEHR
  This profile represents the constraints applied to the Encounter resource, when it represents a visit in the context of the CBDE.

F
G

H

• HospitalDischargeReport - IEHR
  This profile is based on the Composition-IEHR StructureDefinition and defines the relevant sections to represent a DischargeReport. The sections contained are based on the table in the IEHR-Profiles-requirements mapping document and are not necessarily final.

I

• >Immunization - IEHR
  This profile is based on the Immunization-IPS StructuredDefinition and changes the preferred vaccineCode to an ATC code.

J
K
L
M

• Media - IEHR
  This profile is based on the Media StructureDefinition and adds a mandatory signature.
• MedicalVisit - IEHR
  This profile is based on the Composition-IEHR StructureDefinition and defines the relevant sections to represent a VisitReport. The sections contained are based on the table in the IEHR-Profiles-requirements mapping document and are not necessarily final.
• Medication - IEHR
  This profile is based on the MedicationIPS profile and constraints the Medication.code to be an ATC code.
• MedicationRequest-Prescription - IEHR
  This profile represents the constraints applied to the MedicationRequest in the context of the CBDE. It is used to document the prescription of different medications in clinical contexts, e.g. CarePlans or hospital visits.
• MedicationStatement - IEHR
  This profile is based on the MedicationStatementIPS profile and constraints the MedicationStatement.medication to reference a Medication-IEHR.

N

O

• Observation - IEHR
  This profile constraints the codes used in Observation.code to be LOINC codes.

P

• Patient - IEHR
  This profile represents the constraints applied to the Patient StructureDefinition in the context of the CBDE.
• Period - IEHR
  This profile represents the constraints applied to the Period Datatype in the context of the CBDE. It is used to ensure the documentation of a start time.
• Provenance - IEHR
  This profile represents the constraints applied to the Provenance StructureDefinition in the contextof the CBDE. This includes the mandatory agents Author and Provider, as well as a mandatory signature. A Provenance may be referenced by the direct children of the Provenance's target.

Q
R

S

• Provenance-Signature - IEHR
  This profile is based on the Signature StructureDefinition and defines the constraints applied to the resource when it is used in the context of the CBDE.

T

• TreatmentPlan - IEHR
  This profile is based on the CarePlan StructureDefinition and defines a TreatmentPlan, that uses the CarePlan.description attribute to describe the required activities.

U
V
W
X
Y
Z