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

Allow Parameters to be used in Messaging

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: High High
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • Parameters
    • Hide

      Update langauge on http://build.fhir.org/parameters.html#2.46 to read:

      This resource is a non-persisted resource primarily used to pass information into and back from an operation. There is no RESTful endpoint associated with it.

      Show
      Update langauge on http://build.fhir.org/parameters.html#2.46 to read: This resource is a non-persisted resource primarily used to pass information into and back from an operation. There is no RESTful endpoint associated with it.
    • Rick Geimer / Grahame Grieve: 10-0-1
    • Clarification
    • Non-substantive
    • R5

    Description

      Parameters says:

      > This resource is a non-persisted resource used to pass information into and back from an operation. It has no other use, and there is no RESTful endpoint associated with it.

      ... which seems to preclude this resource from being used in the context of a Messaging bundle (as MessageHeader.focus). There doesn't appear to be any other good way to provide named parameters in a Messaging notification, and http://build.fhir.org/messaging even includes examples showing Parameters. So we should remove the prohibitory language from the Parameters intro.

      Proposal:

      This resource is a non-persisted resource primarily used to pass information into and back from an operation. There is no RESTful endpoint associated with it.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jmandel Josh Mandel
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: