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

implied open events are experimental, and should be labeled as such

    XMLWordPrintableJSON

Details

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

      The fact of the matter is that this capability is still experimental. Hubs that allow subscribers to subscribe to different sets of context and do not support derived events is a rich source of complex scenarios involving patient safety. 

      We will – 

      1. Mark derived events as experimental
      2. Recommend / SHOULD that Hubs either support derived events or require that subscribers are subscribed to the same context. 
      Show
      The fact of the matter is that this capability is still experimental. Hubs that allow subscribers to subscribe to different sets of context and do not support derived events is a rich source of complex scenarios involving patient safety.  We will –  Mark derived events as experimental Recommend / SHOULD that Hubs either support derived events or require that subscribers are subscribed to the same context. 
    • Bas van den Heuvel / Trent Nolin: 7-0-0
    • Correction
    • Non-substantive

    Description

      We don't have many real-world implementations of a hub deriving open events. We should label this capability as experimental, and continue to solicit implementer input, even after publication of STU3

      Attachments

        Activity

          People

            Unassigned Unassigned
            Isaac.Vetter Isaac Vetter
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: