Bundle - Laboratory Result Report - HL7 CZ Laboratory IG v0.5.0

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

Resource Profile: Bundle - Laboratory Result Report

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

This profile represents the constraints applied to the Bundle resource by the Czech national laboratory report FHIR Implementation Guide.

Laboratory result report bundle is an electronic health record extract containing results of laboratory testing of specimens from a subject of care, comprising at least the required elements of the lab dataset.

Usages:

Derived from this Profile: Bundle: Obligations
Examples for this Profile: Bundle/CZ-LabReport-Bundle-Example-Complex, Bundle/CZ-LabReport-Bundle-Example-ObsTypes and Bundle/CZ-LabReport-Bundle-Example

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	Laboratory Result Report Bundle This profile also imposes the profile Bundle: Laboratory Report Constraints: bdl-1, bdl-2, bdl-3, bdl-4, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, one-comp, one-dr, dr-comp-identifier, dr-comp-type, dr-comp-category, dr-comp-subj, dr-comp-enc
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
identifier	Σ	1..1	Identifier	Business identifier for this Laboratory 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 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_CompositionLabReport	Laboratory Report composition
entry:diagnosticReport	Σ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_DiagnosticReportLab	Laboratory Report DiagnosticReport
entry:patient	Σ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_PatientCore, CZ_PatientAnimal	Czech Patient (base)
entry:observation	Σ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_ObservationResultLaboratory	Laboratory result for a simple test or for a panel/study
entry:specimen	Σ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_SpecimenLab	Czech Specimen
entry:serviceRequest	Σ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_ServiceRequestLab	Laboratory Order
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:practitionerRole	Σ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_PractitionerRoleCore	Czech Practitioner Role (core)
entry:bodyStructure	Σ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	BodyStructureCz	Czech Body Structure
entry:encounter	Σ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_Encounter	An interaction during which services are provided to the patient
entry:location	Σ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_LocationCore	Czech location
entry:provenance	Σ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_Provenance	Who, What, When for a set of resources
entry:coverage	Σ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_Coverage	Czech coverage
entry:device	Σ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_DeviceObserver	Czech device
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_Attachment	Lab Report attachment
signature	Σ	0..1	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:diagnosticReport.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:observation.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:specimen.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:serviceRequest.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:practitionerRole.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:bodyStructure.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:location.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:provenance.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:coverage.request.method	required	HTTPVerb `http://hl7.org/fhir/ValueSet/http-verb\|4.0.1` From the FHIR Standard
Bundle.entry:device.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:diagnosticReport, Bundle.entry:patient, Bundle.entry:observation, Bundle.entry:specimen, Bundle.entry:serviceRequest, Bundle.entry:organization, Bundle.entry:practitioner, Bundle.entry:practitionerRole, Bundle.entry:bodyStructure, Bundle.entry:encounter, Bundle.entry:location, Bundle.entry:provenance, Bundle.entry:coverage, Bundle.entry:device, 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:diagnosticReport, Bundle.entry:patient, Bundle.entry:observation, Bundle.entry:specimen, Bundle.entry:serviceRequest, Bundle.entry:organization, Bundle.entry:practitioner, Bundle.entry:practitionerRole, Bundle.entry:bodyStructure, Bundle.entry:encounter, Bundle.entry:location, Bundle.entry:provenance, Bundle.entry:coverage, Bundle.entry:device, 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)
dr-comp-category	error	Bundle	At least one DiagnosticReport.category.coding and Composition.category.coding SHALL be equal : (entry.resource.ofType(Composition).category.exists() or entry.resource.ofType(DiagnosticReport).category.exists()) implies entry.resource.ofType(Composition).category.coding.intersect(entry.resource.ofType(DiagnosticReport).category.coding).exists()
dr-comp-enc	error	Bundle	DiagnosticReport and Composition SHALL have the same encounter : ( (entry.resource.ofType(Composition).encounter.empty() and entry.resource.ofType(DiagnosticReport).encounter.empty() ) or entry.resource.ofType(Composition).encounter = entry.resource.ofType(DiagnosticReport).encounter )
dr-comp-identifier	error	Bundle	If one or more DiagnosticReport.identifiers are given, at least one of them SHALL be equal to the Composition.identifier : (entry.resource.ofType(Composition).identifier.exists() or entry.resource.ofType(DiagnosticReport).identifier.exists()) implies entry.resource.ofType(Composition).identifier.intersect(entry.resource.ofType(DiagnosticReport).identifier).exists()
dr-comp-subj	error	Bundle	DiagnosticReport and Composition SHALL have the same subject : ( (entry.resource.ofType(Composition).subject.empty() and entry.resource.ofType(DiagnosticReport).subject.empty() ) or entry.resource.ofType(Composition).subject = entry.resource.ofType(DiagnosticReport).subject )
dr-comp-type	error	Bundle	At least one DiagnosticReport.code.coding and Composition.type.coding SHALL be equal : entry.resource.ofType(Composition).type.coding.intersect(entry.resource.ofType(DiagnosticReport).code.coding).exists()
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 laboratory report bundle SHALL include one and only one Composition : entry.resource.ofType(Composition).count() = 1
one-dr	error	Bundle	A laboratory report SHALL include one and only one DiagnosticReport : entry.resource.ofType(DiagnosticReport).count() = 1

This structure is derived from Bundle

Name	Flags	Card.	Type	Description & Constraints Filter: Bindings Constraints Obligations
Bundle	C	0..*	Bundle	Laboratory Result Report Bundle This profile also imposes the profile Bundle: Laboratory Report Constraints: one-comp, one-dr, dr-comp-identifier, dr-comp-type, dr-comp-category, dr-comp-subj, dr-comp-enc
identifier		1..1	Identifier	Business identifier for this Laboratory 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
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_CompositionLabReport	Laboratory Report composition
entry:diagnosticReport		1..1	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_DiagnosticReportLab	Laboratory Report DiagnosticReport
entry:patient		1..1	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_PatientCore, CZ_PatientAnimal	Czech Patient (base)
entry:observation		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_ObservationResultLaboratory	Laboratory result for a simple test or for a panel/study
entry:specimen		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_SpecimenLab	Czech Specimen
entry:serviceRequest		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_ServiceRequestLab	Laboratory Order
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:practitionerRole		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_PractitionerRoleCore	Czech Practitioner Role (core)
entry:bodyStructure		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	BodyStructureCz	Czech Body Structure
entry:encounter		0..*	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:location		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_LocationCore	Czech location
entry:provenance		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_Provenance	Who, What, When for a set of resources
entry:coverage		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_Coverage	Czech coverage
entry:device		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_DeviceObserver	Czech device
entry:attachment		0..*	BackboneElement	Entry in the bundle - will have a resource or information
resource		1..1	CZ_Attachment	Lab Report attachment
signature		0..1	Signature	Digital Signature of this report
Documentation for this format

Constraints

Id	Grade	Path(s)	Details	Requirements
dr-comp-category	error	Bundle	At least one DiagnosticReport.category.coding and Composition.category.coding SHALL be equal : (entry.resource.ofType(Composition).category.exists() or entry.resource.ofType(DiagnosticReport).category.exists()) implies entry.resource.ofType(Composition).category.coding.intersect(entry.resource.ofType(DiagnosticReport).category.coding).exists()
dr-comp-enc	error	Bundle	DiagnosticReport and Composition SHALL have the same encounter : ( (entry.resource.ofType(Composition).encounter.empty() and entry.resource.ofType(DiagnosticReport).encounter.empty() ) or entry.resource.ofType(Composition).encounter = entry.resource.ofType(DiagnosticReport).encounter )
dr-comp-identifier	error	Bundle	If one or more DiagnosticReport.identifiers are given, at least one of them SHALL be equal to the Composition.identifier : (entry.resource.ofType(Composition).identifier.exists() or entry.resource.ofType(DiagnosticReport).identifier.exists()) implies entry.resource.ofType(Composition).identifier.intersect(entry.resource.ofType(DiagnosticReport).identifier).exists()
dr-comp-subj	error	Bundle	DiagnosticReport and Composition SHALL have the same subject : ( (entry.resource.ofType(Composition).subject.empty() and entry.resource.ofType(DiagnosticReport).subject.empty() ) or entry.resource.ofType(Composition).subject = entry.resource.ofType(DiagnosticReport).subject )
dr-comp-type	error	Bundle	At least one DiagnosticReport.code.coding and Composition.type.coding SHALL be equal : entry.resource.ofType(Composition).type.coding.intersect(entry.resource.ofType(DiagnosticReport).code.coding).exists()
one-comp	error	Bundle	A laboratory report bundle SHALL include one and only one Composition : entry.resource.ofType(Composition).count() = 1
one-dr	error	Bundle	A laboratory report SHALL include one and only one DiagnosticReport : entry.resource.ofType(DiagnosticReport).count() = 1

Description & Constraints Filter: Filters

Bundle

0..*

Bundle

Laboratory Result Report Bundle
This profile also imposes the profile Bundle: Laboratory Report
Constraints: bdl-1, bdl-2, bdl-3, bdl-4, bdl-7, bdl-9, bdl-10, bdl-11, bdl-12, one-comp, one-dr, dr-comp-identifier, dr-comp-type, dr-comp-category, dr-comp-subj, dr-comp-enc

0..1

Logical id of this artifact

Terminology Bindings

Path Conformance ValueSet / Code URI

Bundle.language

preferred

CommonLanguages

http://hl7.org/fhir/ValueSet/languages|4.0.1

From the FHIR Standard

Additional Bindings

Purpose

AllLanguages

Max Binding

Bundle.type