Link State Transitions to messaging events

XMLWordPrintableJSON

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

      The BSeR Referral state machine will be updated to align with the 360x state machine and more clearly represent the relationship between state transitions and triggered information exchanges.

      Show
      The BSeR Referral state machine will be updated to align with the 360x state machine and more clearly represent the relationship between state transitions and triggered information exchanges.
    • AMS/Mead: 14-0-0
    • Clarification
    • Compatible, substantive

      The Referral Request State Machine, it would be helpful to implementers to know which state transitions trigger FHIR messaging exchange events. For example, from the End State Description, it's clear if the Finish action results in a message back to the Referral requester (or what other "in progress" triggers exist). A column added to the State Transition Trigger Events indicating a message trigger may make things clearer. As well, it would be nice in the scoping section that cancellations and withdrawls are in scope for messaging.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: