Demonstration environment. Fictional organization, fictional people, synthetic data throughout. No patient data. Changes you make stay in this browser only.
ParvinCorpPractice Reporting

Ridgeline Health Partners. Multi-specialty physician group, 6 sites, 14 providers. This reporting pilot covers two primary care sites on athenaOne, Main Campus and Stonebridge, and their 4 providers.

Signed in as

Rowan Bexley, Practice Administrator. Owns the monthly numbers for the practice. Starts runs, enters athena’s figures, explains variances, and is the only role that can publish a run.

Data sourcesMenu
OverviewThis month’s numbersRunsReconcile and publishAudit trailWho did what, and whenMetric definitionsFormulas and versionsOrganizationEntities, regions, sitesData sourcesWhere numbers come fromGuided tourDrive it yourself
Appearance

Practice Reporting. Prepared for Rowan Bexley on Oct 6, 2026. Whole organization.

Where the numbers come from

Data sources

Every number is worked out from athenaOne data. Visit and claim records are read into memory, cut down to the few details each number needs, added up, and thrown away. Only totals and counts are ever stored.

Where the data comes from

Demo data

This demonstration uses made-up data shaped exactly like athena’s: weekday clinics, no-shows, denials that differ by payer, payments that arrive late, patient balances and write-offs. The same month always produces the same numbers, so a published figure never moves.

What is stored

Totals, counts and the checks that prove nothing was missed: how many records were read, the money they add up to, and the dates they cover. No visit, claim or patient record is ever stored, and there is nowhere in the database to put one.

What is read, and what never is

Anything not named here is dropped before anything else sees it.

From each claim

  • Date of the visit
  • Date the claim was created
  • Provider who saw the patient (an id, no name)
  • Insurance company billed (an id)
  • Amount charged
  • Date the payer first decided on the claim
  • Whether that first decision was paid or denied
  • Kind of each money movement (payment or adjustment)
  • Amount of each money movement
  • Date each money movement was posted

From each appointment

  • Date of the appointment
  • Provider booked (an id, no name)
  • Department, which says the site
  • Whether it was kept, cancelled or still booked
  • Whether a cancellation was a no-show

Never read or kept

  • Patient id
  • Patient name
  • Date of birth
  • Address
  • Medical record number
  • Phone number
  • Claim number
  • Appointment number
For your IT team

The exact athena field names read, from the code’s allowlist, and the two athena reports it calls.

  • Claims: servicedate, claimcreateddate, renderingproviderid, primaryinsurancepayerid, billedamount, firstadjudicationdate, firstadjudicationstatus, transactions[].transactiontype, transactions[].amount, transactions[].postdate from /v1/{practiceid}/claims
  • Appointments: date, providerid, departmentid, appointmentstatus, cancelreasonnoshow from /v1/{practiceid}/appointments/booked
  • Never read: patientid, patient name, birth date, address, MRN, phone, claimid, appointmentid
No real patient data here
Everything in this demonstration is made up. A screenshot of an athena report attached as evidence must show totals only; the person attaching it confirms that every time.