Process should be asynchronous to prevent delays or lock up within clinical workflow. - PAS #252

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci PAS (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      The interaction between provider and payer is synchronous (to be performed in <15 seconds).  The provider application may well allow this synchronous process to be handled in the background and for other actions to be taken while waiting for a response.  This specification sets no expectation around EHR user interface; it focuses on how the interaction between provider and payer occurs.

      Show
      The interaction between provider and payer is synchronous (to be performed in <15 seconds).  The provider application may well allow this synchronous process to be handled in the background and for other actions to be taken while waiting for a response.  This specification sets no expectation around EHR user interface; it focuses on how the interaction between provider and payer occurs.
    • Mark Scrimshire / Mary Kay McDaniel: 19-0-0

      Existing Wording: Process should be asynchronous to prevent delays or lock up within clinical workflow.

      Clinician must to be able to complete form subsequently when time permits.

      Need to be able to trigger event before or after encounter.

      Summary:

      Process should be asynchronous to prevent delays or lock up within clinical workflow.

            Assignee:
            Unassigned
            Reporter:
            Peter Muir
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: