Integration technical brief

Office Ally Integration: How MedReception AI Connects to Practice Mate, EHR, and Service Center

Office Ally is the EHR and clearinghouse of choice for tens of thousands of small US practices because of one simple reason: it is free or near free. The trade off has always been weak third party integration. This page is the full technical breakdown of how MedReception AI bridges that gap with a hybrid REST plus session keeper architecture that has been live in production since June 2026.

Live Production Integration · Verified at preferred-gynecology

Production Since

Jun 2026

Live for preferred-gynecology with read and write workflows

Addressable Market

30K+

US practices on Office Ally EHR and Practice Mate

Office Ally Cost

Practice Mate and EHR 24/7 base subscription

Stack Total Per Month

$400

Office Ally plus MedReception AI vs $4,800 for a human FTE

The Office Ally product family

What "Office Ally" Actually Refers To Inside Your Practice

Office Ally is not one product. It is a stack of four interlocking services and any AI integration that does not know which surface to talk to will silently miss data. Here is the full family and where MedReception AI hooks into each one.

Practice Mate (PM)

Free practice management system. Owns the appointment schedule, patient demographics, insurance on file, and the daily provider view that staff actually work out of.

• Daily View page is the canonical schedule surface
• ManagePatients.aspx hosts the patient search and update workflows
• Drives every appointment write MedReception AI performs

EHR 24/7

The clinical record. Charts, encounters, problem lists, medication and allergy data, vitals, lab review. The MedReception AI agent does not write clinical content here; it only reads enough context to answer scheduling and intake questions safely.

• Read only access for chart context
• Never writes orders, prescriptions, or clinical notes
• Provider preferences inform call routing decisions

Service Center

Office Ally clearinghouse for claims, eligibility, and remittance. MedReception AI uses Service Center to confirm insurance is in network and to surface claim status when a caller asks about a bill.

• Real time eligibility checks before booking
• Claim status lookups for billing inquiries
• ERA visibility for posted payment questions

Reminder Mate

Office Ally native appointment reminder tool. MedReception AI coordinates with Reminder Mate so confirmations and cancellations the agent processes flow back to the schedule and do not collide with the reminder cadence.

• De duplicates reminder SMS when AI already confirmed
• Honors patient opt outs captured by either system
• Cancellations propagate to the reminder queue

Integration architecture

A Hybrid REST Plus Session Keeper Design

Office Ally does not publish a complete REST API. The pieces it does expose move slowly, and the workflows clinicians and front desk staff use every day live behind authenticated web pages. MedReception AI uses every documented endpoint where it exists and falls back to a hardened session keeper for everything else.

Layer 1: REST first

• Eligibility 270 and 271 transactions
• Claim status 276 and 277 transactions
• Patient demographic lookups where exposed
• Always preferred when the same data is available

Layer 2: Session keeper

• Long lived Playwright session inside a hardened EC2 instance
• Keeps Office Ally logged in across calls so the agent never waits on auth
• Holds one authenticated tab per tenant, isolated from production data of other clinics
• Auto relogin on expiry, with strict retry caps

Layer 3: Daily View scrape

• HTML parse of #tblDailyApp.tblAppts every minute
• PDF schedule export lags 45+ minutes and is not used for live data
• Backstop for any provider or location the REST surface does not cover

Why we built it this way

A pure scraper is brittle. A pure API integration leaves half the booking flow on the floor. The hybrid stack means the agent always uses the most reliable surface available, falls back gracefully when Office Ally pushes a UI change, and is observable end to end through our alert manager so the operations team is paged before a clinician notices.

What we read

Data MedReception AI Pulls From Office Ally on Every Call

Before the agent quotes an open time slot, confirms insurance, or describes a balance owed, it pulls live data straight from Office Ally. Nothing is precomputed and nothing relies on a stale cache.

Provider schedule (live)

• Daily View HTML scrape from #tblDailyApp.tblAppts
• Refresh interval tuned to call volume per tenant
• Honors per provider block reasons and color codes
• Detects same minute double bookings before quoting a slot

Patient demographics

• ManagePatients.aspx?Tab=C canonical search surface
• Phone formatted XXX-XXX-XXXX before lookup
• Multi tier search ladder for partial matches
• Returned record never persists outside the call

Insurance on file

• Payer and member id from patient record
• Real time 270 eligibility transaction against payer
• In network status confirmed before booking is offered
• Captures secondary coverage if present

Claim and balance status

• Service Center claim status lookup by date of service
• Patient responsibility surfaced if the caller asks about a bill
• Routes complex billing questions to the practice biller
• Never quotes a balance the clearinghouse has not confirmed

What we write

Changes MedReception AI Posts Back Into Office Ally

Reads are easy. The hard part of any EHR integration is writing the right thing into the right field without breaking the workflow your staff already trusts. Every write the agent performs has been validated against the live preferred-gynecology install.

Appointment booking

• Books straight into Practice Mate via ManagePatients.aspx flow
• Uses the same form your front desk uses, with the same validation
• Visit reason, location, provider, and duration all driven by the caller intent
• Confirms the slot is still open immediately before submit

Demographics updates

• Phone, address, email, emergency contact
• Spelled back to the caller before commit
• Audit log captures who changed what and when
• Never overwrites a verified field with a less specific value

Insurance capture

• New payer, member id, group, subscriber relationship
• Secondary coverage added without disturbing primary
• Card images uploaded through the MedReception intake link
• Eligibility re run after save so staff see a clean record

Cancellations and reschedules

• Removes the appointment from the canonical schedule
• Notifies Reminder Mate so the SMS confirmation queue is updated
• Offers the freed slot to the waitlist when the practice has one
• Logs cancellation reason for the front desk dashboard

Session keeper detail

Inside the Session Keeper EC2 Instance

The session keeper is the most operationally sensitive piece of the integration. It is a dedicated EC2 instance, isolated per tenant, that holds an authenticated Office Ally session so the agent never has to log in mid call. The design is paranoid by intent because a misbehaving login flow can lock the practice out of Office Ally for 24 hours.

Host

• EC2 instance 32.192.53.51, us-east-1
• Headed browser inside Xvfb, observable via noVNC
• Per tenant container, no cross tenant browser context
• Restart only with explicit human approval

Auth policy

• Strict 2 attempt cap on any login retry
• 24 hour cooldown after consecutive failures
• Credentials retrieved from AWS Secrets Manager at boot
• No headless logins, ever

Observability

• Centralized alert manager fires on session loss
• #qa-critical and #qa-review Slack channels with 24h dedupe
• CloudWatch alarms on relogin attempts and request latency
• Heartbeat record in DynamoDB, never stale longer than 5 minutes

Production reliability

What "Live Since June 2026" Actually Means

Pilot tenant: preferred-gynecology

Single specialty clinic on Office Ally Practice Mate plus EHR 24/7. End to end booking, search, demographics update, and reschedule flows in live use.

Session keeper auto relogin

Live relogin proven on June 1, 2026 with the 2 attempt cap and 24 hour cooldown wired all the way through. Front desk has not been locked out once since.

Centralized alerting

Every Office Ally error flows through the mr-ehr2 alert manager so the operations team sees broken to healthy transitions in Slack within seconds.

Honest limitations

What This Integration Will Not Do

A good integration page is an honest one. There are real limits to what any Office Ally integration can promise. Here are ours, in plain language.

No PHI cached locally

• Every patient lookup round trips through Office Ally
• No local copy of the chart, ever
• Trade off: slightly slower lookups, much smaller security surface
• HIPAA posture stays simple because the data does not leave Office Ally

Office Ally outages are our outages

• If Office Ally is down the agent cannot quote a schedule
• Graceful degradation: agent collects callback details and pages the practice
• Reminder Mate cancellations queue until the system returns
• Status surfaced live to the practice through the QA dashboard

UI changes can pause a workflow

• When Office Ally renames a form field the scraper will detect mismatch
• Affected workflow is auto disabled and alerted before bad writes occur
• Mean time to patch on the last UI change: under 4 hours
• Other workflows continue uninterrupted during the patch

No clinical writes

• The agent never writes orders, prescriptions, or chart notes
• Reads from EHR 24/7 are strictly to inform scheduling and intake
• Clinical decisions remain the clinician's, by design
• This is a policy choice, not a technical limit

For Office Ally practices

See the Office Ally specific hub

Pricing, ROI, sample call recordings, and the practice facing overview of the Office Ally AI receptionist live on the product hub. This page is the engineering perspective; the hub is for practice owners.

Office Ally Hub

Ready to see it on your data

Book a live Office Ally demo

We will spin up a sandbox session keeper against a copy of your Office Ally tenant and walk you through booking, search, demographics update, and a reschedule in real time.

Schedule the demo