Bundle: EMS Report (CZ) - HL7 Czech EMS Implementation Guide v0.0.2

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

Resource Profile: Bundle: EMS Report (CZ)

Official URL: https://hl7.cz/fhir/cz-ems/StructureDefinition/cz-bundle-ems		Version: 0.0.2
Standards status: Draft	Maturity Level: 0	Computable Name: CZ_BundleEms
Copyright/Legal: HL7 CZ

Clinical document used to represent a EMS Report for the scope of this guide.

EMS report bundle is an electronic health record.

Usages:

Examples for this Profile: Bundle/cz-example-bundle

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
Bundle	C	0..*	Bundle	EMS Report Bundle Constraints: bdl-1, bdl-2, bdl-3, bdl-4, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, one-comp
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
identifier	Σ	1..1	Identifier	Business identifier for this Imaging Report
type	Σ	1..1	code	document \| message \| transaction \| transaction-response \| batch \| batch-response \| history \| searchset \| collection Binding: BundleType (required): Indicates the purpose of a bundle - how it is intended to be used. Required Pattern: document
timestamp	Σ	1..1	instant	When the bundle was assembled
Slices for entry	ΣC	3..*	BackboneElement	Entry in the bundle - will have a resource or information Slice: Unordered, Open by type:resource, profile:resource Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
entry:All Slices				Content/Rules for all slices
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource	Σ	1..1	Resource	A resource in the bundle
entry:composition	ΣC	1..1	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_CompositionEms	Emergency medical service report composition
entry:patient	ΣC	1..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_PatientCore, CZ_PatientAnimal	Czech Patient (base)
entry:organization	ΣC	0..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_OrganizationCore	Czech Organization (core)
entry:practitioner	ΣC	0..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_PractitionerCore	Czech Practitioner (core)
entry:encounter	ΣC	1..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_Encounter	An interaction during which services are provided to the patient
entry:procedure	ΣC	0..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_ProcedureEms	An action that is being or was performed on a patient
entry:attachment	ΣC	0..*	BackboneElement	Entry in the bundle - will have a resource or information Constraints: bdl-5, bdl-8 This repeating element order: For bundles of type 'document' and 'message', the first resource is special (must be Composition or MessageHeader respectively). For all bundles, the meaning of the order of entries depends on the bundle type
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
fullUrl	Σ	1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	CZ_Logo, CZ_Attachment	Logo
signature	Σ	0..1	CZ_Signature	Digital Signature of this report
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet / Code	URI
Bundle.type	required	Pattern Value: document `http://hl7.org/fhir/ValueSet/bundle-type\|4.0.1` From the FHIR Standard
Bundle.entry.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:composition.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:patient.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:organization.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:practitioner.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:encounter.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:procedure.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:attachment.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard

Constraints

Id	Grade	Path(s)	Details	Requirements
bdl-1	error	Bundle	total only when a search or history : total.empty() or (type = 'searchset') or (type = 'history')
bdl-2	error	Bundle	entry.search only when a search : entry.search.empty() or (type = 'searchset')
bdl-3	error	Bundle	entry.request mandatory for batch/transaction/history, otherwise prohibited : entry.all(request.exists() = (%resource.type = 'batch' or %resource.type = 'transaction' or %resource.type = 'history'))
bdl-4	error	Bundle	entry.response mandatory for batch-response/transaction-response/history, otherwise prohibited : entry.all(response.exists() = (%resource.type = 'batch-response' or %resource.type = 'transaction-response' or %resource.type = 'history'))
bdl-5	error	Bundle.entry, Bundle.entry:composition, Bundle.entry:patient, Bundle.entry:organization, Bundle.entry:practitioner, Bundle.entry:encounter, Bundle.entry:procedure, Bundle.entry:attachment	must be a resource unless there's a request or response : resource.exists() or request.exists() or response.exists()
bdl-7	error	Bundle	FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) : (type = 'history') or entry.where(fullUrl.exists()).select(fullUrl&resource.meta.versionId).isDistinct()
bdl-8	error	Bundle.entry, Bundle.entry:composition, Bundle.entry:patient, Bundle.entry:organization, Bundle.entry:practitioner, Bundle.entry:encounter, Bundle.entry:procedure, Bundle.entry:attachment	fullUrl cannot be a version specific reference : fullUrl.contains('/_history/').not()
bdl-9	error	Bundle	A document must have an identifier with a system and a value : type = 'document' implies (identifier.system.exists() and identifier.value.exists())
bdl-10	error	Bundle	A document must have a date : type = 'document' implies (timestamp.hasValue())
bdl-11	error	Bundle	A document must have a Composition as the first resource : type = 'document' implies entry.first().resource.is(Composition)
bdl-12	error	Bundle	A message must have a MessageHeader as the first resource : type = 'message' implies entry.first().resource.is(MessageHeader)
ele-1	error	ALL elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	ALL extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
one-comp	error	Bundle	A EMS report bundle SHALL include one and only one Composition : entry.resource.ofType(Composition).count() = 1

This structure is derived from Bundle

Name	Flags	Card.	Type	Description & Constraints Filter: Bindings Constraints Obligations
Bundle	C	0..*	Bundle	EMS Report Bundle Constraints: one-comp
identifier		1..1	Identifier	Business identifier for this Imaging Report
type		1..1	code	document \| message \| transaction \| transaction-response \| batch \| batch-response \| history \| searchset \| collection Required Pattern: document
timestamp		1..1	instant	When the bundle was assembled
total		0..0
link		0..0
Slices for entry		3..*	BackboneElement	Entry in the bundle - will have a resource or information Slice: Unordered, Open by type:resource, profile:resource
entry:All Slices				Content/Rules for all slices
link		0..0
fullUrl		1..1	uri	URI for resource (Absolute URL server address or URI for UUID/OID)
resource		1..1	Resource	A resource in the bundle
search		0..0
request		0..0
response		0..0
entry:composition		1..1	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_CompositionEms	Emergency medical service report composition
entry:patient		1..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_PatientCore, CZ_PatientAnimal	Czech Patient (base)
entry:organization		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_OrganizationCore	Czech Organization (core)
entry:practitioner		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_PractitionerCore	Czech Practitioner (core)
entry:encounter		1..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_Encounter	An interaction during which services are provided to the patient
entry:procedure		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_ProcedureEms	An action that is being or was performed on a patient
entry:attachment		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_Logo, CZ_Attachment	Logo
signature		0..1	CZ_Signature	Digital Signature of this report
Documentation for this format

Constraints

Id	Grade	Path(s)	Details	Requirements
one-comp	error	Bundle	A EMS report bundle SHALL include one and only one Composition : entry.resource.ofType(Composition).count() = 1