Supportable navigation logo

FAQs

  • A. We stand by the Supportable Path to Success Plan.

    Project Kickoff:
    Introductions, Role Establishment, Onboarding Portal access, Meeting Cadence established.
    2-4
    Weeks     		Phase 1 - Configuration:
    • Discovery of Sub-entities/Divisions and their required data (services, billing info (NPI, Tax ID, etc), payers).
    • Assess requirements for individual services data (stages, checklists, rejection reasons).
    • Setup of programs and services.
    • QA testing.
    1-2
    Weeks     		Phase 2 - User Acceptance Testing (UAT):
    • Admin User Training (train the trainer).
    • Admin User(s) test setup to approve setup configuration.
    • Establish Go-Live Date.
    1-2
    Weeks     		Phase 3 - End User Training:
    • Training with specific staff departments (front-end team, billing, marketing, etc.).
      *Admin User(s) present for training.
    • Import legacy data (if applicable to Project Plan).
    • Ensure integrations are active as applicable.
    Go-Live Date:
    Referral Form(s) live on your website, social media, etc.
    As
    Needed     		Phase 4 - Post-Launch Support
    • Establish post-launch meeting cadence.
    • Schedule 3-month check-in.
    This is our general expected time-frame. The process varies based on the complexity of your setup and the availability of your team.

    Basically, if you're ready and available, we can get you going ASAP.

  • YES!

    We love integration. If you have a platform that you love, we're interested in hearing about it.

    Integrations, however, can be complex. So no guarantees. If your situation and/or use case is viable to our our product roadmap, we start with a discussion. At the end of the day, that system needs to be integration friendly.

  • YES! We already integrate with a number of EHRs.

    If your EHR is integration friendly, our priority is always to build a direct API integration. It provides the best user experience and ideally, depending on that EHR’s available endpoints, offers 2-way transfer of data. The approach here is always to work in tandem with their product team. We’ve come across several of them ready and willing to build integrations with us.

    If that is not an option, we have an integration solution via Chrome extension. All we need from any new EHR is a temporary user account for one of our developers to access the system, map the fields, and build the configuration. This is an efficient and repeatable process, as we’ve already done the heavy lifting of building the engine that drives the extension.

    • You can refer to our Pricing page for subscription details. We charge a Setup Fee for onboarding, which is based on the complexity of your setup.
    • We charge a Setup Fee for onboarding. This is based on the complexity of your setup and the degree of customization you'd like our Chrome Browser Extension to have with your EHR, should you opt to.
    • We offer custom reporting for a fee. This fee will come in the form of an estimate based on a Statement of Work (SOW). This SOW is determined by your requirements for the custom report.

  • ACH