Bundle (6)

#NameSourceVerDescription
1ClaimBundlendhm.in#currentR4The profile is based on a Bundle of type collection, where all the supporting information required for processing claim can be shared. Multiple entries can be added in a bundle to provide information like financial, clinical, provision of health care services with payors and for reporting to regulatory bodies and firms which provide data analytics. The bundle can be generated depending on the nature of the request defined by 'use' element in a claim resource, like preauthorization, predetermination and claim and can be shared over NHCX ecosystem.
2ClaimResponseBundlendhm.in#currentR4The profile is based on a Bundle of type collection, where adjudicated response to a Claim, Predetermination or Preauthorization related information is carried. Multiple entries included in a bundle carries the information and provides application level adjudication results.
3CoverageEligibilityRequestBundlendhm.in#currentR4The profile is based on a Bundle of type collection, where all the information required to process Coverage Eligibility Request can be shared. Depending on the purpose of the request like validation, discovery,auth-requirement and benefit data can be included in the etries of a bundle.
4CoverageEligibilityResponseBundlendhm.in#currentR4The Coverage Eligibility Response Bundle is a Bundle profile with type collection. The bundle profile provides the response and plan details from the processing of an CoverageEligibilityRequest resource.
5DocumentBundlendhm.in#currentR4This profile sets minimum expectations for the DocumentBundle that includes all resources into a single instance with containing context to act as an exchangeable clinical document.
6InsurancePlanBundlendhm.in#currentR4This profile is built upon a Bundle of type collection, providing a description of a health insurance package that consists of a comprehensive list of covered benefits (referred to as the product), associated costs (known as the plan), and supplementary details regarding the offering, such as ownership and administration, coverage area, contact information, and more.
1 2 3 4 5 6
Bundle
Bundle.meta C
Bundle.meta.security
Bundle.meta.versionId C
Bundle.implicitRules
Bundle.language
Bundle.identifier C
Bundle.identifier.assigner
Bundle.identifier.value C
Bundle.identifier.system C
Bundle.type F F F F F F
Bundle.timestamp C
Bundle.total
Bundle.link
Bundle.link.extension
Bundle.link.modifierExtension
Bundle.link.relation
Bundle.link.url
Bundle.entry S C D (2) S C D (2) S C D (2) S C D (2) S C (2)
Bundle.entry.extension
Bundle.entry.modifierExtension
Bundle.entry.link
Bundle.entry.fullUrl
Bundle.entry.resource
Bundle.entry.search
Bundle.entry.search.extension
Bundle.entry.search.modifierExtension
Bundle.entry.search.mode
Bundle.entry.search.score
Bundle.entry.request
Bundle.entry.request.extension
Bundle.entry.request.modifierExtension
Bundle.entry.request.method
Bundle.entry.request.url
Bundle.entry.request.ifNoneMatch
Bundle.entry.request.ifModifiedSince
Bundle.entry.request.ifMatch
Bundle.entry.request.ifNoneExist
Bundle.entry.response
Bundle.entry.response.extension
Bundle.entry.response.modifierExtension
Bundle.entry.response.status
Bundle.entry.response.location
Bundle.entry.response.etag
Bundle.entry.response.lastModified
Bundle.entry.response.outcome
Bundle.signature
Bundle.issues
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023