FHIR Artifacts > Structure Definition: Bundle Profile
Structure Definition: Bundle Profile
Canonical URL:http://ehealthontario.ca/fhir/StructureDefinition/eReferralBundle
Simplifier project page:
Command 'link' could not render: Object reference not set to an instance of an object.
Derived from: Bundle (R4)
Formal Views of Profile Content
Description of Profiles, Differentials, Snapshots and how the different presentations work
Could not find subject. File was not found for tabs
Differential View
Command 'tree' could not render: File was not found for eReferralBundle
Hybrid View
Command 'tree' could not render: File was not found for eReferralBundle
Snapshot View
Command 'tree' could not render: File was not found for eReferralBundle
Table View
Command 'table' could not render: File was not found for eReferralBundle
JSON View
Command 'json' could not render: File was not found for eReferralBundle
Could not find subject. File was not found for script
Usage
A Bundle resource is used to package together a collection of FHIR Resource instances to be sent from one system to another. The Bundle SHALL have an entry for each of the FHIR Resources required to convey information about the business event, starting with the MessageHeader which SHALL always be first.
Notes
The following rules apply to message
type Bundles.
.id
- used to uniquely identify a message instance
- populate this element with a UUID each time a message is sent
- note: a FHIR message contains two identifiers that are unique within the message stream, rules:
- a
Bundle.id
(this element) SHALL be assigned each time the message is sent - a
MessageHeader.id
SHALL be assigned when the message is created
- a
.meta.profile
- used to declare conformance to this profile
- populate with a fixed value:
http://ehealthontario.ca/fhir/StructureDefinition/eReferralBundle|1.0.0
.type
- declares that the Bundle contains a message
- populate with a fixed value:
message
.timestamp
- populate with the instant in time when the Bundle was created
- format: YYYY-MM-DDThh:mm:ss.sss+zz:zz (e.g. 2015-02-07T13:28:17.239+02:00 or 2017-01-01T00:00:00Z).
.entry
- create an
entry
for each of the FHIR Resources required to convey information about the business event - the MessageHeader SHALL be the first entry
.entry.fullUrl
- each entry in the Bundle SHALL have a fullUrl which is the identity of the resource in the entry
- if a persistent identity for the resource is not available to use in the Bundle, a UUID SHOULD be used (urn:uuid:...)
.entry.resource
- SHALL be populated with the resource for this entry
.entry.request
- SHALL NOT be populated
.entry.response
- SHALL NOT be populated