Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-37267

Make Implied Events Part of the Normative Specification

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • Multi-anchor considerations [deprecated]
    • 4.5.1.2
    • Hide

      Already applied, see: https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events

       

      with this text:

      Hub Generated open Events

      If a Hub grants subscriptions to different sets of hub.events to different Subscribers for the same session, the Hub is responsible for generation of implied open events. Close events are typically not generated by the Hub. When distributing a received event, a hub SHALL ensure open events for the referenced resource types of the received event are also sent to subscribers. Hubs SHOULD NOT generate and send duplicative events.

      Show
      Already applied, see: https://build.fhir.org/ig/HL7/fhircast-docs/2-5-EventNotification.html#hub-generated-open-events   with this text: Hub Generated  open  Events If a Hub grants subscriptions to different sets of  hub.events  to different Subscribers for the same session, the Hub is responsible for generation of implied open events. Close events are typically not generated by the Hub. When distributing a received event, a hub SHALL ensure open events for the referenced resource types of the received event are also sent to subscribers. Hubs SHOULD NOT generate and send duplicative events.
    • Jonathan Whitby/Bas van den Heuvel: 6-0-1
    • Enhancement
    • Non-compatible
    • Yes

    Description

      Should we make implied events normative for the Hub?  Rationale, ensure that applications can understand context is in place even if higher level contexts are open.

      Similar to (from 4.5.1.2.1 Implied Events):

      For example, an encounter-open implies a patient-open, because the encounter-open’s context includes not just an encounter resource, but also a patient resource. Similarly, diagnosticreport-open implies patient-open and possibly an imagingstudy-open (if an ImagingStudy is supplied in the diagnosticreport-open event).

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            ericmartinatsiemens Eric Martin
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: