3.84.6 StructureDefinition: Interaction Message Header 901 - Message disposition notification - Detailed Descriptions
Definitions for the interaction-messageheader-901 Profile.
1. MessageHeader | |
Definition | The header for a message exchange that is either requesting or responding to an action. The reference(s) that are the subject of the action as well as other information related to the action are typically transmitted in a bundle in which the MessageHeader resource instance is the first resource in the bundle. |
Control | 0..* |
Must Support | true |
Max Length | 0 |
2. MessageHeader.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Control | 1..1 |
Type | id |
Must Support | true |
Comments | Usage Note: This value is assigned by the system that creates a bundle and is unique to the specific message instance of the bundle and the uniqueness of this value will be validated by the PrescribeIT® service. This value is sometimes referenced in error messages. |
Max Length | 0 |
3. MessageHeader.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Control | 1..1 |
Type | Meta |
Must Support | true |
Comments | See children |
Max Length | 0 |
4. MessageHeader.meta.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Max Length | 0 |
5. MessageHeader.meta.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
6. MessageHeader.meta.versionId | |
Definition | The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted. |
Control | 0..1 |
Type | id |
Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. |
Max Length | 0 |
7. MessageHeader.meta.lastUpdated | |
Definition | When the resource last changed - e.g. when the version changed. |
Control | 0..1 |
Type | instant |
Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. |
Max Length | 0 |
8. MessageHeader.meta.profile | |
Definition | A list of profiles StructureDefinitions that this resource claims to conform to. The URL is a reference to StructureDefinition.url. |
Control | 1..1 |
Type | uri |
Must Support | true |
Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. |
Max Length | 0 |
Slicing | This element introduces a set of slices on MessageHeader.meta.profile. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
9. MessageHeader.meta.profile:profile | |
SliceName | profile |
Definition | A list of profiles StructureDefinitions that this resource claims to conform to. The URL is a reference to StructureDefinition.url. |
Control | 1..1 |
Type | uri |
Must Support | true |
Comments | Fixed value: http://sharedhealth.exchange/fhir/StructureDefinition/interaction-messageheader-901 |
Max Length | 0 |
Fixed Value | http://sharedhealth.exchange/fhir/StructureDefinition/interaction-messageheader-901 |
10. MessageHeader.meta.security | |
Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. |
Control | 0..* |
Binding | The codes SHALL be taken from All Security Labels; other codes may be used where these codes are not suitable Security Labels from the Healthcare Privacy and Security Classification System. |
Type | Coding |
Comments | The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. |
Max Length | 0 |
11. MessageHeader.meta.tag | |
Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. |
Control | 0..* |
Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones" |
Type | Coding |
Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. |
Max Length | 0 |
12. MessageHeader.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible. |
Max Length | 0 |
13. MessageHeader.language | |
Definition | The base language in which the resource is written. |
Control | 0..1 |
Binding | The codes SHALL be taken from http://tools.ietf.org/html/bcp47 A human language. |
Type | code |
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). |
Max Length | 0 |
14. MessageHeader.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. |
Control | 0..1 This element is affected by the following invariants: dom-1 |
Type | Narrative |
Alternate Names | narrative, html, xhtml, display |
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. |
Max Length | 0 |
15. MessageHeader.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Control | 0..* |
Type | Resource |
Alternate Names | inline resources, anonymous resources, contained resources |
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. |
Max Length | 0 |
16. MessageHeader.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
17. MessageHeader.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
18. MessageHeader.timestamp | |
Definition | Time and date the transaction was created |
Control | 1..1 |
Type | instant |
Must Support | true |
Requirements | Allows limited detection of out-of-order and delayed transmission. Also supports audit. |
Comments | Conformance Rule: Must be a full date and time with timezone (i.e. yyyy-mm-ddTHH:mm:ss.SSS-ZZZZZ). |
Max Length | 0 |
19. MessageHeader.event | |
Definition | Code that identifies the event this message represents and connects it with its definition. |
Control | 1..1 |
Binding | The codes SHOULD be taken from SharedMessageEvents (20220810) |
Type | Coding |
Is Modifier | true |
Must Support | true |
Requirements | Drives the behavior associated with this message. |
Max Length | 0 |
20. MessageHeader.event.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Max Length | 0 |
21. MessageHeader.event.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
22. MessageHeader.event.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Control | 1..1 |
Type | uri |
Must Support | true |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | Fixed value: https://fhir.infoway-inforoute.ca/CodeSystem/sharedmessageevents |
Max Length | 0 |
Fixed Value | https://fhir.infoway-inforoute.ca/CodeSystem/sharedmessageevents |
23. MessageHeader.event.version | |
Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. |
Note | This is a business versionId, not a resource version id (see discussion) |
Control | 0..1 |
Type | string |
Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. |
Max Length | 0 |
24. MessageHeader.event.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Control | 1..1 |
Type | code |
Must Support | true |
Requirements | Need to refer to a particular code in the system. |
Comments | Fixed value: 901 |
Max Length | 0 |
Fixed Value | 901 |
25. MessageHeader.event.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Control | 0..1 |
Type | string |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Max Length | 0 |
26. MessageHeader.event.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). |
Control | 0..1 |
Type | boolean |
Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. |
Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. |
Max Length | 0 |
27. MessageHeader.response | |
Definition | Information about the message that this message is a response to. Only present if this message is a response. |
Control | 1..1 |
Type | BackboneElement |
Is Modifier | true |
Must Support | true |
Max Length | 0 |
28. MessageHeader.response.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Max Length | 0 |
29. MessageHeader.response.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
30. MessageHeader.response.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
31. MessageHeader.response.identifier | |
Definition | The id of the message that this message is a response to. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 1..1 |
Type | id |
Must Support | true |
Requirements | Allows receiver to know what message is being responded to. |
Comments | Conformance Rule: This is to be populated with the MessageHeader.id of the original message that is being responded to. |
Max Length | 0 |
32. MessageHeader.response.code | |
Definition | Code that identifies the type of response to the message - whether it was successful or not, and whether it should be resent or not. |
Control | 1..1 |
Binding | The codes SHALL be taken from ResponseType The kind of response to a message |
Type | code |
Is Modifier | true |
Must Support | true |
Requirements | Allows the sender of the acknowledge message to know if the request was successful or if action is needed. |
Comments | Fixed value: ok |
Max Length | 0 |
Fixed Value | ok |
33. MessageHeader.response.details | |
Definition | A reference from one resource to another. |
Control | 1..1 |
Type | Reference(Shared Health Reference)(Shared Health Operation Outcome) |
Must Support | true |
Requirements | Allows the sender of the message to determine what the specific issues are. |
Comments | - |
Max Length | 0 |
34. MessageHeader.source | |
Definition | The source application from which this message originated. |
Control | 1..1 |
Type | BackboneElement |
Must Support | true |
Requirements | Allows replies, supports audit. |
Max Length | 0 |
35. MessageHeader.source.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Max Length | 0 |
36. MessageHeader.source.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Max Length | 0 |
Slicing | This element introduces a set of slices on MessageHeader.source.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
37. MessageHeader.source.extension:applicationId | |
SliceName | applicationId |
Definition | Unique identifier for the application responsible for sending a message. |
Control | 1..1 |
Type | Extension(Message Header Application Id) (Extension Type: uri) |
Must Support | true |
Comments | Vendors will be assigned this identifier upon registration by PrescribeIT® technical support. |
Max Length | 0 |
38. MessageHeader.source.extension:conformanceVersion | |
SliceName | conformanceVersion |
Definition | String identifying the version of the sending software application that was most recently subjected to conformance testing |
Control | 1..1 |
Type | Extension(Message Header Source Conformance Version) (Extension Type: string) |
Must Support | true |
Comments | This is the version number of the software that underwent conformance testing. It may be earlier than the source.version in cases where the application has since undergone changes that do not affect the communication interface. Usage Note: This version must be registered with the Shared Services Hub and will be validated by the Hub at runtime. |
Max Length | 0 |
39. MessageHeader.source.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
40. MessageHeader.source.name | |
Definition | Human-readable name for the source system. |
Control | 0..1 |
Type | string |
Must Support | true |
Requirements | May be used to support audit. |
Comments | Usage Note: The name of the Vendor. Usage Note: Max Length = 100 characters. If greater than this limit, an error will be returned |
Max Length | 0 |
41. MessageHeader.source.software | |
Definition | May include configuration or other information useful in debugging. |
Control | 1..1 |
Type | string |
Must Support | true |
Requirements | Supports audit and possibly interface engine behavior. |
Comments | Usage Note: The name of the Vendor's software creating the message. Conformance Rule: This must be a known value that is registered on Shared Services Hub. This will be validated at run time. |
Max Length | 0 |
42. MessageHeader.source.version | |
Definition | Can convey versions of multiple systems in situations where a message passes through multiple hands. |
Note | This is a business versionId, not a resource version id (see discussion) |
Control | 1..1 |
Type | string |
Must Support | true |
Requirements | Supports audit and possibly interface engine behavior. |
Comments | Conformance Rule: This must convey the build version of the vendor application. This is the version of the application that created the message. Usage Note: This version number is issued by the software vendor and will be used primarily for audit and troubleshooting purposes. This may or may not be the same as the conformance version. |
Max Length | 0 |
43. MessageHeader.source.contact | |
Definition | An e-mail, phone, website or other contact point to use to resolve issues with message communications. |
Control | 0..1 |
Type | ContactPoint |
Requirements | Allows escalation of technical issues. |
Max Length | 0 |
44. MessageHeader.source.endpoint | |
Definition | Identifies the routing target to send acknowledgements to. |
Control | 1..1 |
Type | uri |
Must Support | true |
Requirements | Identifies where to send responses, may influence security permissions. |
Comments | Conformance Rule: This must be populated with the full URL for the Organization Identifier (CPRID) that was issued by PrescribeIT®. The URL's must be completely configurable within the EMR or PMS as they will vary by environment. Format: https://{environmentSpecificHost}/{environmentAndContextSpecificPath}/Organization/{CPRID} Vendors will be given the actual values for {environmentSpecificHost}/{environmentAndContextSpecificPath} in the API document at time of onboarding. |
Max Length | 0 |
45. MessageHeader.destination | |
Definition | The destination application which the message is intended for. |
Control | 1..1 |
Type | BackboneElement |
Must Support | true |
Requirements | Indicates where message is to be sent for routing purposes. Allows verification of "am I the intended recipient". |
Comments | Usage Note: This is used to specify the destination system. |
Max Length | 0 |
46. MessageHeader.destination.id | |
Definition | unique id for the element within a resource (for internal references). |
Control | 0..1 |
Type | id |
Max Length | 0 |
47. MessageHeader.destination.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
48. MessageHeader.destination.modifierExtension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. |
Max Length | 0 |
49. MessageHeader.destination.name | |
Definition | Human-readable name for the target system. |
Control | 0..1 |
Type | string |
Requirements | May be used for routing of response and/or to support audit. |
Max Length | 0 |
50. MessageHeader.destination.target | |
Definition | Identifies the target end system in situations where the initial message transmission is to an intermediary system. |
Control | 0..1 |
Type | Reference(Device) |
Requirements | Supports multi-hop routing. |
Max Length | 0 |
51. MessageHeader.destination.endpoint | |
Definition | Indicates where the message should be routed to. |
Control | 1..1 |
Type | uri |
Must Support | true |
Requirements | Identifies where to route the message. |
Comments | Format: https://{environmentSpecificHost}/{environmentAndContextSpecificPath}/Organization/{CPRID}. The URL's must be completely configurable within the EMR or PMS as they will vary by environment. Vendors will be given the actual values for {environmentSpecificHost}/{environmentAndContextSpecificPath} in the API document at time of onboarding. Conformance Rule: This must be populated with the full URL for the Organization Identifier (CPRID) that was issued by PrescribeIT®. Conformance Rule: In the context of Task e180-m - Deferred RX Fill Request, this will be the PrescribeIT® Switch URI (https://{environmentSpecificHost}/{environmentAndContextSpecificPath}/Organization/111111111). |
Max Length | 0 |
52. MessageHeader.enterer | |
Definition | The person or device that performed the data entry leading to this message. Where there is more than one candidate, pick the most proximal to the message. Can provide other enterers in extensions. |
Control | 0..1 |
Type | Reference(Practitioner) |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request, but can be used in a response. |
Max Length | 0 |
53. MessageHeader.author | |
Definition | The logical author of the message - the person or device that decided the described event should happen. Where there is more than one candidate, pick the most proximal to the MessageHeader. Can provide other authors in extensions. |
Control | 0..1 |
Type | Reference(Practitioner) |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request, but can be used in a response. |
Max Length | 0 |
54. MessageHeader.receiver | |
Definition | Allows data conveyed by a message to be addressed to a particular person or department when routing to a specific application isn't sufficient. |
Control | 0..1 |
Type | Reference(Practitioner | Organization) |
Requirements | Allows routing beyond just the application level. |
Max Length | 0 |
55. MessageHeader.responsible | |
Definition | The person or organization that accepts overall responsibility for the contents of the message. The implication is that the message event happened under the policies of the responsible party. |
Control | 0..1 |
Type | Reference(Practitioner | Organization) |
Requirements | Need to know for audit/traceback requirements and possibly for authorization. |
Comments | Usually only for the request, but can be used in a response. |
Max Length | 0 |
56. MessageHeader.reason | |
Definition | Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this message. |
Control | 0..1 |
Binding | For example codes, see Example Message Reason Codes Reason for event occurrence |
Type | CodeableConcept |
Requirements | Need to be able to track why resources are being changed and report in the audit log/history of the resource. May affect authorization. |
Max Length | 0 |
57. MessageHeader.data | |
Definition | A reference from one resource to another. |
Control | 1..1 |
Type | Reference(Shared Health Reference)(Shared Health Media Fax) |
Must Support | true |
Requirements | Every message event is about actual data, a single resource, that is identified in the definition of the event, and perhaps some or all linked resources. |
Comments | The data is defined where the transaction type is defined. The transaction data is always included in the bundle that is the full message. Only the root resource is specified. The resources it references should be contained in the bundle but are not also listed here. Multiple repetitions are allowed to cater for merges and other situations with multiple focal targets. |
Max Length | 0 |