Guidance for populating and consuming the Bundle profile
Introduction
The headings below list the elements of the Bundle profile and describe how to populate and consume them.
Important: Any element not specifically listed below SHOULD NOT be populated or consumed.
Tip: You’ll find it helpful to read it in conjunction with: the underlying Bundle population illustration diagram and the Bundle profile definition.
Bundle elements
The logical identifier of the Bundle profile.
meta.profile
Data type: uri |
Optionality: Mandatory | Cardinality: 1..* |
The Bundle profile URL.
Fixed value https://fhir.nhs.uk/STU3/StructureDefinition/GPConnect-StructuredRecord-Bundle-1
type
Data type: type |
Optionality: Mandatory | Cardinality: 1..1 |
The type of the Bundle.
Fixed value of collection.
id
Data type: id |
Optionality: Mandatory | Cardinality: 1..1 |
A logical id for the bundle. This MUST be set to the same value as the Ssp-TraceID header in the request.
entry
Data type: BackboneElement |
Optionality: Required | Cardinality: 0..* |
Items that make up the Bundle.
See below for subelements of this BackboneElement.
entry.resource
Data type: Resource |
Optionality: Mandatory | Cardinality: 0..1 |
A resource carried within the Bundle. This can any type of resource, for example Patient, Organization, AllergyIntolerance.
Bundle elements not in use
The following elements SHALL NOT be populated:
meta.versionId
Data type: Id |
meta.lastUpdated
Data type: Instant |
entry.fullUrl
Data type: uri |