rootQ integration setup

Request Athena API access and authorize DRootDx

Effective 2026-09-20 · Version 2026-09-20.2

For clinic-led Athena API access, each clinic must request or confirm production API access for its own Practice ID and separately authorize DRootDx/rootQ as its integration vendor. API access approval and vendor authorization are two separate requirements. Follow the process athenahealth confirms for your clinic and integration program.

  1. Confirm the clinic identity. The clinic’s authorized Athena administrator gathers its legal name, production Practice ID (context or clinic ID), relevant department IDs, and authorized signer’s contact information. A department ID does not replace the Practice ID.
  2. Have the clinic request API access. The clinic administrator contacts athenahealth support or the clinic’s account representative to apply for production API access, or confirm that existing access covers the planned rootQ integration. Ask which application, agreements, fees, and approvals are required for this clinic. Complete Athena’s requested steps before proceeding.
  3. Identify DRootDx/rootQ as the vendor. Obtain the exact vendor/application identity and technical contact details from DRootDx. Ask athenahealth how the clinic should designate DRootDx/rootQ as its authorized third-party integration vendor for the approved Practice ID. Do not use another clinic’s access or assume a Marketplace listing is required or available.
  4. Authorize the requested access. The clinic’s authorized signer completes the vendor assignment, authorization/consent, or other access-approval steps specified by athenahealth. Request only the functions needed for the purchased integration, such as patient and appointment lookup and document upload. Complete the DRootDx agreement and applicable Business Associate Agreement. Purchasing Athena integration carries a 12-month minimum subscription commitment.
  5. Confirm both approvals. Obtain confirmation that production API access is enabled for the clinic and that DRootDx/rootQ is authorized for that Practice ID and the approved functions. Share the confirmation, Practice ID, and department IDs with DRootDx through the agreed onboarding channel. A Practice ID alone does not grant access. Do not email passwords, client secrets, or patient records; use the approved secure credential-provisioning process if Athena requires credentials to be provided.
  6. Configure and validate the connection. After Athena confirms access, DRootDx configures the approved application credentials, clinic and department mapping, and document types. Validate an authorized patient lookup and document-upload workflow, including the destination clinic, patient, and chart category, before enabling routine use.

If athenahealth instead directs your clinic to a Marketplace partner connection, follow that program’s vendor-specific instructions. These are different onboarding paths. Athena must confirm the applicable path, approval requirements, and exact vendor-assignment steps; this guide does not establish universal requirements for every Athena product. DRootDx authorization for one clinic does not authorize access to another clinic.

Suggested request to athenahealth

We would like production API access for our athenaOne practice, Practice ID [Practice ID], and authorization for DRootDx/rootQ to act as our third-party integration vendor. Please confirm the application process, required agreements and fees, vendor-assignment steps, approved functions, and secure credential-provisioning method for our clinic. Our clinic administrator is [name and business contact]. DRootDx will supply its exact vendor/application identity and technical contact.

Contact DRootDx about billing, account closure, or Athena setup. Do not include patient information.

Reference: athenahealth API and integration resources. Confirm clinic-specific onboarding with athenahealth.

rootQ and VisitRoom are temporary workspaces. The clinic’s EHR remains the official medical-record repository.