SPRY

Claims leave SPRY through a Claim.MD clearinghouse connection, with ERA files posted back automatically. Orders from ModMed arrive in SPRY and charges return to ModMed over HL7 once care is done, and Zocdoc bookings sync straight into the schedule. A Zapier connection reaches more than 5,000 other apps. Payments run through Stripe, Square, Paya, FortisPay and GoCardConnect, texting and reminders through Twilio and Emitrr, faxes through eFax, home exercise programs through Wibbi, and CRM through Mailchimp, Keap and the Zoho products.

Sourcespryhealth.ai/integrationsread 2026-10-09

An authorization runs as a chain of steps. The eligibility check flags whether the plan needs prior authorization, the agent reads the therapist's note for diagnosis, goals, treatment plan, visit count and medical necessity, then completes and submits the payer workflow and tracks approved, used and remaining visits against the expiration date.

Anything it cannot finish goes to staff with the payer details, reference IDs, documentation and request history attached. One patient record carries the work across the scribe, scheduling, claim and denial steps, so a signed note feeds both the authorization and the claim.

Sourcespryhealth.ai/prior-authorizationread 2026-10-09

The agents draw on the clinic's own record at each step. Before a visit the scribe brings forward prior notes, goals, baselines, range of motion history and plan of care context, and the authorization agent pulls what each payer asks for out of the therapist's note. Payer and clinic rules are applied to eligibility, authorization and claim scrubbing, and payer submissions run on workflows trained payer by payer. The agents work from the EMR record itself, rather than a separate index or knowledge base built over the clinic's documents, so their context moves with every signed note.

Sourcespryhealth.ai/agentic-scriberead 2026-10-09

The Scheduling Agent books nothing until staff approve. It generates appointment sets from the plan of care, staff review the options and pick one, and that approval locks the plan before visits are created and confirmations go out. Clinics set the booking rules, provider availability, active hours and blocked time it works within, and can override its matches.

Clinicians review, edit and sign every scribe note, with flags for body part mismatches, conflicting measurements and missing details before sign off. On trained payer workflows the authorization agent submits supported requests itself, and anything outside them goes to staff with the case history attached.

Sourcespryhealth.ai/schedulerread 2026-10-09

Access inside SPRY is role based, with clinical, billing and operational permissions kept separate, and data is encrypted at rest and in transit with audit logging. BAAs are available for covered entities. API and agent access is approved per partner, scoped per tenant and held to role based permissions and read and write boundaries. The EHR is ONC certified health IT with a CHPL listing. Alongside that, SPRY's security rests on HIPAA alignment rather than a SOC 2, HITRUST or ISO 27001 attestation, and there is no single sign on or SCIM provisioning for clinic users.

Sourcespryhealth.ai/trust-and-complianceread 2026-10-09

Authorization reporting follows approval status, payer turnaround, denials, expirations and follow up needs across locations. Each case that reaches staff carries its request history, payer reference IDs and documentation, so a biller picking up an exception sees what was already tried. Audit logging is part of the platform's security controls, though clinics work from these reports and case histories rather than a searchable log of every agent action.

Sourcespryhealth.ai/prior-authorizationread 2026-10-09

The scribe learns how each clinician documents and applies those repeated preferences to future notes, and approved corrections, prior actions and outcomes make the next case easier. That learning is kept per clinician, with no set lifetime and no screen where a clinic can review or clear it. The patient history the scribe loads before each visit comes from the EMR's own notes and measures, so it is the clinical record rather than a separate memory.

Sourcespryhealth.ai/agentic-scriberead 2026-10-09

SPRY runs as a hosted service on its own infrastructure, with no region choice, single tenant or customer cloud option and no on premises install. When a clinic leaves, billing stops without penalties or lock in fees, and one designated user keeps seven years of read only access to its records at no cost.

Sourcespryhealth.ai/trust-and-complianceread 2026-10-09

SPRY ships named agents for separate jobs: Agentic Scribe for documentation, the Prior Authorization Agent, the Scheduling Agent for plan of care booking and cancellation backfill, and AI Fax for reading and filing incoming documents, with Claim, AR and Compliance Intelligence on the billing side. Each does its own work on the shared record, and the Scheduling Agent also runs in connected scheduling workflows outside the full platform. AI Scribe comes with the Plus plan.

Sourcespryhealth.ai/spry-airead 2026-10-09

Work starts from events in the clinic day. Running eligibility routes a patient into the authorization workflow when the plan requires it, and benefits are checked daily so the front desk sees every scheduled patient's coverage each morning. A logged cancellation sends the open slot to eligible waitlist patients, who can accept after hours. Incoming faxes are read, classified and filed to the right chart and workflow. Outbound, webhooks tell connected systems when patient, appointment, case and SOAP note activity happens.

Sourcespryhealth.ai/schedulerread 2026-10-09

The models behind the scribe and the agents are undisclosed, and clinics have no choice of model. SPRY puts the weight on context instead: patient history, payer rules and the schedule each agent draws on when it acts.

Sourcespryhealth.ai/spry-airead 2026-10-09

A public developer site documents a REST API, v1 current and v2 in beta, across scheduling (clinics, providers, availability, appointments, cancellation reasons, waitlists), patient and clinical records (patients, cases, documents, insurance, referring providers, SOAP notes) and revenue operations (eligibility, prior authorization, staff, tasks).

Webhooks report patient, appointment, case and SOAP note activity, and a quickstart walks through creating an appointment. Credentials and a sandbox go to approved customers and partners on request. SPRY MCP sits over these APIs as a governed layer for outside agents, with no public endpoint or tool list.

Sourceapi-docs.spryhealth.careread 2026-10-09

Approved corrections, prior actions and outcomes feed back into the agents, and the scribe checks each draft for inconsistencies before sign off. There is no evaluation harness or test suite a clinic can use to measure agent accuracy before or after a change, and the sandbox SPRY offers is for partners testing API integrations.

Sourcespryhealth.ai/spry-airead 2026-10-09

For supported payers the authorization agent completes the payer's form, attaches the documentation and submits the request itself, on trained workflows for Carelon and BCBS, UnitedHealthcare and Humana, with more payer portals on the way. A supported request takes about 90 seconds against twenty minutes by hand. Whether that runs through a browser session on the payer portal or a direct payer connection is unclear.

Sourcespryhealth.ai/prior-authorizationread 2026-10-09