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

Add CRD support during order dispatching

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.0.0 [deprecated]
    • Financial Mgmt
    • Supported Hooks
    • Hide

      We will propose a new Hook type (level 0) called "dispatch-order" with a hook payload of the order id and the Task representing the fulfillment solicitation request - including the proposed performer, if any.  Will will add support for this hook to the CRD specification.

      Show
      We will propose a new Hook type (level 0) called "dispatch-order" with a hook payload of the order id and the Task representing the fulfillment solicitation request - including the proposed performer, if any.  Will will add support for this hook to the CRD specification.
    • Bob Dieterle / Celine Lefebvre: 19-0-3
    • Enhancement
    • Compatible, substantive

    Description

      Sometimes the determination of whether a service is covered or not or whether prior authorization is required can't be determined until the performer of the service has been selected.  As well, payers may be able to provide information about whether a selected performer is considered in or out of network, provide estimated pricing information and other useful decision support guidance as part of the process for selecting where an active order should be performed.  There needs to be an ability to invoke CRD during this dispatch process - which occurs after the order is signed, and is quite often performed by someone other than the ordering provider.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: