Message/Task Completeness - BSeR #79

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Bidirectional Services eReferrals (BSeR) (FHIR)
    • STU3
    • Public Health
    • MessageHeader [deprecated]
    • (profiles) [deprecated]
    • BSeR Messaging Workf
    • Hide

      The BSeR Messaging Workflow section of the specification will be modified to include instructions for a messaging workflow and a RESTful submit workflow.

      Show
      The BSeR Messaging Workflow section of the specification will be modified to include instructions for a messaging workflow and a RESTful submit workflow.
    • AMS/Mead: 14-0-0
    • Enhancement
    • Non-substantive

      Existing Wording: Adoption of the FHIR messaging framework does not rule out the use of alternative information exchange frameworks such as RESTful APIs.

      Proposed Wording: Adoption of the FHIR messaging framework enables complete information exchange via payload-neutral push transports, such as Direct/360X, or via the messaging RESTful APIs, and it does not rule out the use of the FHIR RESTful API to exchange the same profiled resources.

      Summary:

      Message/Task Completeness

            Assignee:
            Unassigned
            Reporter:
            Daniel Chaput
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: