TEMPLATE CAEHR_C_Zwischenanamnese_Akute_Symptomatik (CAEHR_C_Zwischenanamnese_Akute_Symptomatik)

TEMPLATE IDCAEHR_C_Zwischenanamnese_Akute_Symptomatik
ConceptCAEHR_C_Zwischenanamnese_Akute_Symptomatik
DescriptionDokumentation von zwischen Anamnese und akuter Symptomatik
PurposeDokumentation von zwischen Anamnese und akuter Symptomatik
References
Authorsname: Severin Kohler; organisation: Berlin Institute of Health; email: severin.kohler@charite.de
Other Details Languagename: Severin Kohler; organisation: Berlin Institute of Health; email: severin.kohler@charite.de
Other Details (Language Independent)
  • Notes: Generated automatically by Adl Designer
  • MetaDataSet:Sample Set: Template metadata sample set
  • MD5-CAM-1.0.1: 4e81ca97eefe46fa8f610002647f3b0e
  • PARENT:MD5-CAM-1.0.1: 005501C1FA493A4838F5F1121F2870EC
  • Sem Ver: 215.0.0
  • Build Uid: 63025009-40ce-4fd8-868a-5f0ea6f656b7
  • Original Language: ISO_639-1::de
Language useden
Citeable Identifier1246.169.3529
Root archetype idopenEHR-EHR-COMPOSITION.report.v1
ReportReport: Document to communicate information to others, commonly in response to a request from another party.
other_context
Other Context
Case identificationCase identification: To record case identification details for public health purposes.
Case identifierCase identifier: The identifier of this case.
Care journey metadataCare journey metadata: Tp capture Care plan metadata
Care plan nameCare plan name: The name , preferably coded of the Care plan with which this journey is associated, and against which the composition was updated.
Care plan identifierCare plan identifier: The identifier , preferably coded, of the Care plan with which this journey is associated, and against which the composition was updated.
Patient journey identifierPatient journey identifier: A patient-journey specific identifier i.e unique to a patient's journey along a specific care pathway.
Zwischenzeitliche EreignisseZwischenzeitliche Ereignisse: A generic section header which should be renamed in a template to suit a specific clinical context.
Kardialer EingriffKardialer Eingriff: A clinical activity carried out for screening, investigative, diagnostic, curative, therapeutic, evaluative or palliative purposes.
Description
Procedure nameProcedure name: Identification of the procedure by name.
Coding of the specific procedure with a terminology is preferred, where possible.
DescriptionDescription: Narrative description about the procedure, as appropriate for the pathway step.
For example: description about the performance and findings from the the procedure, the aborted attempt or the cancellation of the procedure.
Terminology: http://snomed.info/sct
  • Procedure on heart (procedure) 
Kardiale ZwischendiagnoseKardiale Zwischendiagnose: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Clinical descriptionClinical description: Narrative description about the problem or diagnosis.
Use to provide background and context, including evolution, episodes or exacerbations, progress and any other relevant details, about the problem or diagnosis.
Terminology: http://snomed.info/sct
  • Cardiac finding (finding) 
Ausschluss kardiale EingriffeAusschluss kardiale Eingriffe: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
EingriffEingriff: The Procedure to which the 'Exclusion statement' applies. For example: 'Heart surgery' or 'Appendectomy' or 'Hip replacement'.
  • Zwischenzeitliche kardiale Eingriffe
Ausschluss kardiale DiagnosenAusschluss kardiale Diagnosen: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
  • Zwischenzeitliche kardiale Diagnosen
Zwischenzeitliche Ereignisse nicht erhobenZwischenzeitliche Ereignisse nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
  • Zwischenzeitliche Diagnose/Eingriffe
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
BelastungsdyspnoeBelastungsdyspnoe: A generic section header which should be renamed in a template to suit a specific clinical context.
BelastungsdyspnoeBelastungsdyspnoe: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Dyspnea on exertion (finding) 
Ausschluss BelastungsdyspnoeAusschluss Belastungsdyspnoe: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Dyspnea on exertion (finding) 
Belastungsdyspnoe nicht erhobenBelastungsdyspnoe nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • Dyspnea on exertion (finding) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
RuhedyspnoeRuhedyspnoe: A generic section header which should be renamed in a template to suit a specific clinical context.
RuhedyspnoeRuhedyspnoe: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Dyspnea at rest (finding) 
Ausschluss RuhedyspnoeAusschluss Ruhedyspnoe: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Dyspnea at rest (finding) 
Ruhedyspnoe nicht erhobenRuhedyspnoe nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • Dyspnea at rest (finding) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
Periphere ÖdemePeriphere Ödeme: A generic section header which should be renamed in a template to suit a specific clinical context.
Periphere ÖdemePeriphere Ödeme: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Peripheral edema (disorder) 
Ausschluss periphere ÖdemeAusschluss periphere Ödeme: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Peripheral edema (disorder) 
Periphere Ödeme nicht erhobenPeriphere Ödeme nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • Peripheral edema (disorder) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
HalsvenenstauungHalsvenenstauung: A generic section header which should be renamed in a template to suit a specific clinical context.
HalsvenenstauungHalsvenenstauung: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Jugular venous engorgement (finding) 
Ausschluss HalsvenenstauungAusschluss Halsvenenstauung: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Jugular venous engorgement (finding) 
Halsvenenstauung nicht erhobenHalsvenenstauung nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • Jugular venous engorgement (finding) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
Pulmonale RasselgeräuschePulmonale Rasselgeräusche: A generic section header which should be renamed in a template to suit a specific clinical context.
Pulmonale RasselgeräuschePulmonale Rasselgeräusche: Details about a single identified health condition, injury, disability or any other issue which impacts on the physical, mental and/or social well-being of an individual.
Clear delineation between the scope of a problem versus a diagnosis is not easy to achieve in practice. For the purposes of clinical documentation with this archetype, problem and diagnosis are regarded as a continuum, with increasing levels of detail and supportive evidence usually providing weight towards the label of 'diagnosis'.
Data
Problem/Diagnosis nameProblem/Diagnosis name: Identification of the problem or diagnosis, by name.
Coding of the name of the problem or diagnosis with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Respiratory crackles (finding) 
Ausschluss pulmonale RasselgeräuscheAusschluss pulmonale Rasselgeräusche: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Respiratory crackles (finding) 
Pulmonale Rasselgeräusche nicht erhobenPulmonale Rasselgeräusche nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • Respiratory crackles (finding) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
BelastbarkeitBelastbarkeit: A generic section header which should be renamed in a template to suit a specific clinical context.
BelastbarkeitBelastbarkeit: Findings observed during the physical examination of a subject of care.
Data
Any eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Belastbarkeit bei z.B. TreppensteigenBelastbarkeit bei z.B. Treppensteigen: Narrative description of the overall findings observed during a physical examination of a patient.
May be used to record a narrative summary of the complete clinical examination or key aspects of clinical examination findings, which will be supported by structured data. Details of specific structured findings can be included using CLUSTER archetypes in the 'Examination Detail' slot. This data element may be used to capture legacy data that is not available in a structured format.
Terminology: http://snomed.info/sct
  • Physical fitness behavior (observable entity) 
BelastbarkeitBelastbarkeit: Findings observed during the physical examination of a body system or anatomical structure.
System or structure examinedSystem or structure examined: Identification of the examined body system or anatomical structure.
Coding of the system or structure examined with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Impairment (finding) 
Clinical interpretationClinical interpretation: Single word, phrase or brief description that represents the clinical meaning and significance of the physical examination findings.
For example: 'No abnormality detected' or 'Moderate inflammation present'. Coding of the 'Clinical interpretation' with a terminology is preferred, where possible.
Terminology: http://snomed.info/sct
  • Mild (qualifier value) 
  • Moderate (severity modifier) (qualifier value) 
  • Severe (severity modifier) (qualifier value) 
Ausschluss BelastbarkeitAusschluss Belastbarkeit: A statement of exclusion of a specific Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item that is either not currently present, or have not been present in the past.
Data
Exclusion statementExclusion statement: A qualifying statement about the exclusion of a Problem/diagnosis, Family history, Medication, Procedure, Adverse reaction or other clinical item.
This statement is to be used in conjunction with the 'Excluded concept' data element. For example: this data element can support recording general statements such as "No known history of ..." where the 'Excluded concept' identifies the specific problem, diagnosis, substance, procedure or medication. If the 'Excluded concept' data element is used to record a precoordinated term such as 'No family history of diabetes', this element is redundant.
Terminology: http://snomed.info/sct
  • Definitely NOT present (qualifier value) 
Problem/DiagnoseProblem/Diagnose: The problem or diagnosis to which the 'Exclusion statement' applies. For example: 'Diabetes', 'COPD' or 'Asthma'.
Terminology: http://snomed.info/sct
  • Impairment (finding) 
NYHANYHA: A generic section header which should be renamed in a template to suit a specific clinical context.
New York Heart Association functional classificationNew York Heart Association functional classification: A simple method of classifying the extent of heart failure, as defined by the New York Heart Association.
Data
Any eventAny event: Default, unspecified point in time or interval event which may be explicitly defined in a template or at run-time.
Data
Functional capacityFunctional capacity: Assessment of heart failure based on how a patient with cardiac disease feels during physical activity.
Class III and the Class III subtypes, IIIa and IIIb, are intended to be mutually exclusive but are included in this internal code set for completeness. Within a template either the Class III alone or both of the subtypes, IIIa and IIIb, should be set to inactive.
Terminology: http://snomed.info/sct
  • Class I 
  • Class II 
  • Class III 
  • Class IIIa 
  • Class IIIb 
  • Class IV 
  • New York Heart Association Classification - Class I (finding) 
  • New York Heart Association Classification - Class II (finding) 
  • New York Heart Association Classification - Class III (finding) 
  • New York Heart Association Classification - Class IV (finding) 
NYHA nicht erhobenNYHA nicht erhoben: Statement that specified health information is not available for inclusion in the health record or extract at the time of recording.
Data
Absence statementAbsence statement: Positive statement that no information is available.
For example: "No information available about adverse reactions"; No information available about problems or diagnoses"; "No information available about previous procedures performed"; or "No information available about medications used".
Terminology: http://snomed.info/sct
  • New York Heart Association Classification (assessment scale) 
Reason for absenceReason for absence: Description of the reason why there is no information available.
For example: patient is unconscious or refuses to provide information. Coding the reason with a terminology is desirable, if possible.
Terminology: http://snomed.info/sct
  • Not recorded (qualifier value) 
MenstruationMenstruation: A generic section header which should be renamed in a template to suit a specific clinical context.
Menstruation summaryMenstruation summary: Summary or persistent information about an individual's menstruation history.
Data
Menstrual statusMenstrual status: Statement about the current menstrual activity.
If this data element is updated, the 'Date last updated' in Protocol should also be amended.
Terminology: http://snomed.info/sct
  • Premenarchal 
  • Premenopausal 
  • Perimenopausal 
  • Postmenopausal 
  • Postmenopausal state (finding) 
  • Premenopausal state (finding) 
  • Perimenopausal state (finding) 
Per episodePer episode: Details about a typical pattern of menstruation during a specified interval of time.
If the pattern of menstruation changes significantly, or other factors significantly interrupt (for example, a full term pregnancy) or influence (for example, changing contraception methods) the menstrual cycle, then it may be useful to record as a new episode .
Tag Beginn der letzten RegelblutungTag Beginn der letzten Regelblutung: Date when this episode commenced.
Can be a partial date, for example, only a year.
Alter in den WechseljahrenAlter in den Wechseljahren: Cessation of all menstrual cycles.
This data element allows 2 occurrences in a template, if required. Use the DV_DATE data type to represent a partial date, such as year only, of menopause and the DV_DURATION data type to represent the age at menopause.
>=P0M
Units:
  • Year
  • Month
Other contributorsThomas Haese,; Alexander Bartschke