You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

  1. Discussion of cross-organizational scheduling, i.e. the ability of the initiator to directly schedule an appointment at the receipient's organization. A current specificaiton for doing that is the Argonaut Scheduling Implmentation Guide, which already haas some implementations.
    From the overall 360X workflow, we need to consider the following:
    1. As part of the referral initiation process, the initiator org schedules the patient at the recipient org, and then the referral request is sent to the recipient. The initiator's system needs to reflect the information about the scheduled visit.
    2. It is expected that in most cases the recipient will send an accept, and any changes to the appoinment after that will be handled via the Argo Scheduling mechanism to be conveyed back to the initiator (need to verify that), and the patient needs to be contacted (which is always the case, including with the existing 360X scheduling option.
    3. In rare cases where the recipient needs to decline, they need to cancel the already made appointment, and make sure the patient is contacted and made aware of that a new referral is needed.
    4. Discussion:
      1. We need to make sure it is clear that the ability to do cross-organizatiional scheduling usually implies a close business relationship, and thus scheduled apponitments for referrals are not expected to end up as declined referrals due to the recipient not being the appropriate provider for that patient.
      2. It is likely that Argo Scheduling needs any pre-auth to be done in order to justify allowing the appointment to be made. If that is the case, sending the pre-auth number may be required. We need to see if the Argonaut project have considered this, and whether 360X should make the insurance information option (and the a pre-authorization number) as required when cross-organizational scheduling is used.
      3. It is a good idea to create a companion diagram to visualize cross-organizational scheduling.
      4. Note: in the SNF case, CMS/Insurance is also very important, low income patients may be discharged to shelter.
  2. Review of topics from the June 7th call
    1. Insurance infomation option - still work needs to be done
    2. eCQM measure 50 - Brett provided the value sets, Next step is to confirm with eCQM experts on what to include in Event Code List (if still necessary).
    3. Sending prior authorization information from initiator to recipient - reviewed the options, and an e-mail will be sent to request review and opiniions on the topic.
  3. Review of initial scenario for ONC Interoperability Forum demo.
  • No labels