Getting Started

Requirements

To access and configure the Autorouter, you’ll need:

  • A Google or GitHub account
  • Your Ocean site number
  • Access to the Ocean Admin Portal (to generate OAuth credentials)

Connecting the Autorouter to your Ocean Site

The Autorouter is separate from the Ocean Portal, so you must:

  1. Reach out to Ocean Support via email at support@oceanmd.com to get access to the Autorouter application.

  2. In the Ocean Portal OAuth Settings, create a Client ID and Secret.

    Generating Ocean OAuth Credentials

    Systems must send Ocean a site-specific Client ID and secret in order to receive an OAuth token(s) that can be used to submit referral updates for that Ocean site.

    To generate the Client ID and secret, In Ocean navigate to Admin Settings page, click Manage Credentials > Manage OAuth Credentials > Add New Credentials

  3. In the Autorouter app’s Site Configuration Page, enter:

  • Ocean Site Number
  • Client ID
  • Client Secret
  1. Select the Test Connection to Ocean button.
  • A success message will be displayed if the connection is working
  • If the connection fails, ensure that the “Server” drop down reflects the environment you are connecting to.

Connecting your Ocean Site to the Autorouter

  1. From the Admin view in Ocean, navigate to the Integrations page.
  2. Select "Register an Integration", you can Register an External CDS Hooks or Register an eReferrals integration
  3. Change authentication to OAuth2 Authentication
  4. Enter the information provided on the Autorouter page (there are separate tabs for eReferral and CDS hooks integrations)
  5. Enable Autorouter integration in the Integrations section on the Directory Listing configuration page
  6. In the Autorouter appl, enable integration with third party applications (e.g. Twillio for SMS, SMTP for email, AI model etc.)

This video provides a UI walkthrough of the required steps to connecting the Autorouter and Ocean.

Configuration Options

The Autorouter includes several out-of-the-box integrations to extend functionality and accelerate deployment. These are intended as reference implementations; the platform’s modular, open architecture makes it straightforward to swap in equivalent services or introduce net-new infrastructure from providers such as AWS, Azure, or other vendors

SMS Integration (Twilio)

  • Send outbound text notifications Example: Alert staff when an urgent referral is received

This integration can be easily replaced or supplemented with alternatives such as AWS SNS or Azure Communication Services.

AI Integration (Required)

  • Connect to an AI provider such as OpenAI, Google, Cohere
  • Enables:
    • Referral analysis
    • Summarization
    • Decision support

The AI layer is provider-agnostic, allowing teams to integrate with their preferred models or enterprise AI platforms.

Email Integration (SMTP2GO)

  • Send automated email notifications
  • Example: Summary of accepted referrals sent to clinic inbox

This can be swapped for services such as Amazon SES, Azure Communication Services, or existing enterprise mail infrastructure.

This video provides a walkthrough of the configuration options in the Autorouter.