HL7 Czech EMS Implementation Guide
0.0.2 - ci-build Czechia flag

HL7 Czech EMS Implementation Guide, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.0.2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/cz-ems/ and changes regularly. See the Directory of published versions

Logical Model: LogEnDiagnosticSummary - Detailed Descriptions

Draft as of 2025-09-05

Definitions for the LogDiagnosticSummary logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. LogDiagnosticSummary
Definition

Emergency Medical Service Report – Diagnostic Summary – A.2.8 EN

ShortA.2.8 - Diagnostic Summary (en)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. LogDiagnosticSummary.diagnosticSummary
Definition

All problems/diagnoses that affect care during hospitalization or that are important to record in order to ensure continuity of care. A distinction is made between treated and untreated problems, as well as between conditions present at admission, acquired during hospitalization, and unclassifiable. The description should be structured, well specified, and codable.

ShortA.2.8.1 - Diagnostic Summary
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
4. LogDiagnosticSummary.diagnosticSummary.id
Definition

unique id for the element within a resource (for internal references)


Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Shortxml:id (or equivalent in JSON)Unique id for inter-element referencing
Control0..1
Typestring
Is Modifierfalse
XML FormatIn the XML format, this property is represented as an attribute.
Summaryfalse
6. LogDiagnosticSummary.diagnosticSummary.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.


May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

ShortAdditional content defined by implementations
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Control0..*
TypeExtension
Is Modifierfalse
Summaryfalse
Alternate Namesextensions, user content
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
8. LogDiagnosticSummary.diagnosticSummary.value
Definition

The actual value

ShortPrimitive value for string
Control0..1
Typestring
Is Modifierfalse
XML FormatIn the XML format, this property is represented as an attribute.
Summaryfalse
Max Length:1048576
10. LogDiagnosticSummary.diagnosticSummary.problemDescription
Definition

Textual description of the problem.

ShortA.2.8.1.1 - Problem Description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. LogDiagnosticSummary.diagnosticSummary.detail
Definition

Formalized representation of the health problem by a code (classification).

ShortA.2.8.1.2 - Code
Control0..1
TypeCodeableConcept
14. LogDiagnosticSummary.diagnosticSummary.onsetDate
Definition

Date of onset of the condition. Exact or approximate date.

ShortA.2.8.1.3 - Onset Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
16. LogDiagnosticSummary.diagnosticSummary.resolutionOrRemissionDate
Definition

Date when the problem was resolved or entered remission.

ShortA.2.8.1.4 - Resolution/Remission Date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
18. LogDiagnosticSummary.diagnosticSummary.problemCategory
Definition
  • POA – Condition was present on admission
ShortA.2.8.1.5 - Problem Category
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. LogDiagnosticSummary
Definition

Emergency Medical Service Report – Diagnostic Summary – A.2.8 EN

ShortA.2.8 - Diagnostic Summary (en)
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. LogDiagnosticSummary.diagnosticSummary
Definition

All problems/diagnoses that affect care during hospitalization or that are important to record in order to ensure continuity of care. A distinction is made between treated and untreated problems, as well as between conditions present at admission, acquired during hospitalization, and unclassifiable. The description should be structured, well specified, and codable.

ShortA.2.8.1 - Diagnostic Summary
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
4. LogDiagnosticSummary.diagnosticSummary.problemDescription
Definition

Textual description of the problem.

ShortA.2.8.1.1 - Problem Description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. LogDiagnosticSummary.diagnosticSummary.detail
Definition

Formalized representation of the health problem by a code (classification).

ShortA.2.8.1.2 - Code
Control0..1
TypeCodeableConcept
8. LogDiagnosticSummary.diagnosticSummary.onsetDate
Definition

Date of onset of the condition. Exact or approximate date.

ShortA.2.8.1.3 - Onset Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. LogDiagnosticSummary.diagnosticSummary.resolutionOrRemissionDate
Definition

Date when the problem was resolved or entered remission.

ShortA.2.8.1.4 - Resolution/Remission Date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. LogDiagnosticSummary.diagnosticSummary.problemCategory
Definition
  • POA – Condition was present on admission
ShortA.2.8.1.5 - Problem Category
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. LogDiagnosticSummary
Definition

Emergency Medical Service Report – Diagnostic Summary – A.2.8 EN

ShortA.2.8 - Diagnostic Summary (en)
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. LogDiagnosticSummary.diagnosticSummary
Definition

All problems/diagnoses that affect care during hospitalization or that are important to record in order to ensure continuity of care. A distinction is made between treated and untreated problems, as well as between conditions present at admission, acquired during hospitalization, and unclassifiable. The description should be structured, well specified, and codable.

ShortA.2.8.1 - Diagnostic Summary
Control1..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
4. LogDiagnosticSummary.diagnosticSummary.id
Definition

unique id for the element within a resource (for internal references)

Shortxml:id (or equivalent in JSON)
Control0..1
Typestring
Is Modifierfalse
XML FormatIn the XML format, this property is represented as an attribute.
Summaryfalse
6. LogDiagnosticSummary.diagnosticSummary.extension
Definition

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

ShortAdditional content defined by implementations
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Control0..*
TypeExtension
Is Modifierfalse
Summaryfalse
Alternate Namesextensions, user content
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
8. LogDiagnosticSummary.diagnosticSummary.value
Definition

The actual value

ShortPrimitive value for string
Control0..1
Typestring
Is Modifierfalse
XML FormatIn the XML format, this property is represented as an attribute.
Summaryfalse
Max Length:1048576
10. LogDiagnosticSummary.diagnosticSummary.problemDescription
Definition

Textual description of the problem.

ShortA.2.8.1.1 - Problem Description
Control1..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. LogDiagnosticSummary.diagnosticSummary.detail
Definition

Formalized representation of the health problem by a code (classification).

ShortA.2.8.1.2 - Code
Control0..1
TypeCodeableConcept
14. LogDiagnosticSummary.diagnosticSummary.onsetDate
Definition

Date of onset of the condition. Exact or approximate date.

ShortA.2.8.1.3 - Onset Date
Control1..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
16. LogDiagnosticSummary.diagnosticSummary.resolutionOrRemissionDate
Definition

Date when the problem was resolved or entered remission.

ShortA.2.8.1.4 - Resolution/Remission Date
Control0..1
TypedateTime
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
18. LogDiagnosticSummary.diagnosticSummary.problemCategory
Definition
  • POA – Condition was present on admission
ShortA.2.8.1.5 - Problem Category
Control1..1
Typecode
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension