Authorization preparation
Review how requests are prepared, which payer channels are available and where staff approve a submission. Confirm which eligibility, order and documentation fields can be read from your installation.
Explore this workflowFor provider organizations and RCM companies
Plan a QuickIntell workflow for your Centricity environment
Evaluate a focused revenue-cycle workflow against your actual EHR and practice-management setup. Begin with the product, version and access your organization has, then confirm what QuickIntell can support before agreeing to an implementation.
30 minutes with QuickIntell. Share non-sensitive workflow context; no patient records are needed to book.
Identify the exact Centricity product first
A legacy product name is not enough to establish compatibility. athenahealth renamed Centricity Business to athenaIDX. Its separate developer portal documents API resources for athenaPractice and athenaFlow. Those sources describe vendor capabilities; they do not establish that a particular QuickIntell connector, writeback operation or customer tenant is ready.
Bring the product name, version, hosting arrangement and the workflow you want to change. If your clinical and billing systems are separate, include both. A connection that can read a clinical resource may not be authorized to update a billing record. We will make that distinction part of the scoping discussion.
Choose one workflow to evaluate
The following are evaluation paths, not a promise that every module is connected to every Centricity installation. A useful demonstration shows the input, proposed action, staff review and exception path for the task your team actually performs.
Documentation and coding
Walk through a non-sensitive example from source documentation to a coding recommendation. Establish the reviewer, approved writeback route and handling for missing or conflicting documentation.
Explore this workflowPayment posting
Check the actual EOB or ERA input format, validation rules and reconciliation process. Agree how an exception reaches the billing team before a payment is posted.
Explore this workflowDenial and AR follow-up
Start with one work queue. Identify the claim-status source, required payer access, staff handoff and the information that should return to the practice-management system.
Explore this workflowRequirements to confirm before a pilot
- Access: which APIs, interfaces or approved exports are enabled, who authorizes access and whether the intended operation is read-only or includes writeback.
- Environment: the exact product version, hosting model, test environment and any vendor or interface-engine dependencies.
- Data mapping: required fields, identifiers, status codes and the handling of missing, delayed or duplicate records.
- Human control: which actions need staff approval, how exceptions are assigned and how a failed action is investigated.
- Security review: the proposed data flow, access scope, audit requirements and applicable agreements. Request current security documentation for your review.
- Acceptance criteria: test cases, reconciliation checks, rollback steps and named operational owners before production access.
Implementation timing and fees depend on these findings. Ask for a written scope that identifies dependencies and the work included. No fixed deployment time, denial-reduction percentage or certification status is promised on this page.
For provider teams
Choose a task that currently creates repetitive work for your staff. Identify the current owner, the system of record and the step where a clinician or biller must review the result. The initial assessment should show how the proposed workflow fits your existing responsibilities and escalation process.
Provider workflowsFor RCM and billing companies
Start with one client environment and identify which configuration can be reused. Include client separation, authorized access, operator permissions and reporting in the assessment. Do not assume a successful workflow in one tenant establishes compatibility for every client in your portfolio.
Billing-company onboarding checklistSee whether the workflow fits
Use the demo to review a relevant example, identify access questions and decide whether a technical assessment is worthwhile. Where production evidence is needed, ask for evidence applicable to the same workflow and environment. An illustrative demonstration should be identified as such.
Book a workflow demoReview the Centricity setup stepsContent and vendor naming reviewed September 18, 2026. Vendor documentation is not a QuickIntell partnership or endorsement claim.