Loading...

XML

Word

Printable

JSON

Specification:

FHIR R5 Subscriptions Backport (FHIR)
Raised in Version:

1.2.0-ballot
Work Group:

FHIR Infrastructure
Related URL:
https://hl7.org/fhir/uv/subscriptions-backport/2024Jan/channels.html#fhir-messaging-1
Related Page(s):

Channels
Grouping:
- block-vote-3
Resolution Description:

Hide

Messaging does create an envelope around the history bundle. However, the actual contents of the notification are still conveyed in a history bundle.

Propose clarifying this further in the Messaging section and adding a note specifically that the specification refers to the history bundles due to this.

Messaging implementations are not common enough to justify adding the note on every mention of the bundle, which will add confusion to the majority of implementers.

Show
Messaging does create an envelope around the history bundle. However, the actual contents of the notification are still conveyed in a history bundle. Propose clarifying this further in the Messaging section and adding a note specifically that the specification refers to the history bundles due to this. Messaging implementations are not common enough to justify adding the note on every mention of the bundle, which will add confusion to the majority of implementers.
Change Category:
Clarification
Change Impact:
Non-substantive

The FHIR messaging channel implies that the bundle being sent will have a type of "message". This is a "soft" conflict with language elsewhere in the spec (e.g., https://hl7.org/fhir/uv/subscriptions-backport/2024Jan/components.html#subscription-notifications).

I think we may just want to update places in the spec that reference history Bundles to note an exception when using the messaging channel type.