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

Clarify event wildcard matching

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.0.0
    • Infrastructure & Messaging
    • Event format
    • 2.3.2
    • Hide

      We will remove the ability to use a wildcard to define one or more events when subscribing. Specifically, this paragraph (and the following table) – 

      When subscribing to FHIRcast events a list of events is added. These events may contain wild cards. Wild cards are expressed as a {} replacing either the FHIRresource or suffix with {} indicates any events that match the resulting definition are requested. The event * means the Subscriber subscribes to any event. The table below shows some typical examples.

       

      Because – we believe that wilcard subscriptions are not currently supported by production hubs, and reasonably would never be.

      Show
      We will remove the ability to use a wildcard to define one or more events when subscribing. Specifically, this paragraph (and the following table) –  When subscribing to FHIRcast events a list of events is added. These events may contain wild cards. Wild cards are expressed as a { } replacing either the  FHIRresource  or  suffix  with { } indicates any events that match the resulting definition are requested. The event  *  means the Subscriber subscribes to any event. The table below shows some typical examples.   Because – we believe that wilcard subscriptions are not currently supported by production hubs, and reasonably would never be.
    • Eric Martin / Alex Z Liu: 7-0-0
    • Clarification
    • Non-compatible

    Description

      Taken together these statements imply that proprietary events only have "focus" components, and no "suffix" (as the event can't be separated at the dash). This leads to the conclusions that (1) * will match all events including propietary events; (2) - will match all non-proprietary events, and (3) that aside from , there is no way to subscribe to a set of proprietary events without enumerating them (something along the lines of foo_ isn't permitted to match foo_blarg and foo_baz). Please update text to clarify whether these conclusions are accurate.

      Existing Wording:

      The fhir-resource indicates the focus of the event; the suffix defines the type of event. … Proprietary events SHALL NOT contain a dash (“-“). … Wild cards are expressed as a * replacing either the fhir-resource or suffix with * indicates any events that match the resulting definition are requested.

      (Comment 4 - imported by: Lloyd McKenzie)

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: