The /Mailbox endpoint is no longer needed, given FHIR's "operations" framework

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • STU
    • Messaging
    • Hide

      remove mailbox from document paradigm. IHE can define something if they want for the XDR use case

      define new operation $process-message specifically for the task of processing messages synchronously using the existing documentation.

      Rename existing operations batch -> batch-validate, Renam $closure?

      Show
      remove mailbox from document paradigm. IHE can define something if they want for the XDR use case define new operation $process-message specifically for the task of processing messages synchronously using the existing documentation. Rename existing operations batch -> batch-validate, Renam $closure?
    • Josh Mandel / John Moehrke: 4-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      When the "Mailbox" endpoint was defined in DSTU1 (http://hl7-fhir.github.io/messaging), it was designed as a catch-all pattern to handle a variety of not-strictly-RESTful use cases in a consistent way. Today, FHIR's "operations" framework can handle these use cases and more. I'd recommend simply removing the "Mailbox" endpoint from the specificaiton. (If needed, a new "$mailbox" operation could be defined to replace it – but I'm not sure I see value in defining such a generic operation, rather than defining individual use-case-specific operations as needed,)

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: