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

Event Notification Request Details: make text more clear.

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Applied (View Workflow)
    • Priority: Highest
    • Resolution: Persuasive
    • Specification:
      FHIRCast (FHIR)
    • Raised in Version:
      0.1
    • Work Group:
      Imaging Integration
    • Related Page(s):
      (NA)
    • Related Section(s):
      Event Notification
    • Grouping:
    • Resolution Description:
      Hide

      Agreed. Will adopt Bas' suggested rewrite for clarity.

      Show
      Agreed. Will adopt Bas' suggested rewrite for clarity.
    • Resolution Vote:
      Isaac Vetter / Bas van der Heuval: 9-0-0
    • Change Category:
      Clarification
    • Change Impact:
      Non-substantive

      Description

      Make text more clear. Suggestion: "Each event in the Event Catalog defines what context is expected in the notification. The context contains zero, one or more FHIR resources. Hubs MAY use the FHIR _elements parameter to limit the size of these resources data being passed by specifying the elements to be included in the in message (e.g. the identifiers of a resource). When they do so they SHALL include all elements indicated in the event definition.
      Subscribers SHALL accept a full FHIR resource or the _elements-limited resource as defined in the Event Catalog."

      Existing Wording:

      Each event in the Event Catalog defines what context is expected in the notification. Hubs MAY use the FHIR _elements parameter to limit the size of the data being passed while also including additional, local identifiers that are likely already in use in production implementations. Subscribers SHALL accept a full FHIR resource or the _elements-limited resource as defined in the Event Catalog.

      Proposed Wording:

      Each event in the Event Catalog defines what context is expected in the notification. The context contains zero, one or more FHIR resources. Hubs MAY use the FHIR _elements parameter to limit the size of these resources data being passed by specifying the elements to be included in the in message (e.g. the identifiers of a resource). When they do so they SHALL include all elements indicated in the event definition.
      Subscribers SHALL accept a full FHIR resource or the _elements-limited resource as defined in the Event Catalog.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Isaac.Vetter Isaac Vetter
              Reporter:
              bvdh Bas van den Heuvel
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: