Referral analytics

Who this page is for: the practice manager or owner who wants the operational numbers behind their referral base - and needs them to stay firmly on the administrative side of the line.

Refera is not a reporting tool bolted onto a clinical record. The current connected Practice analytics surface derives a bounded tenant-owned summary from the authenticated arrival queue and verifies every event ledger before publishing a number. It exposes arrival volumes, channel mix, administrative process state, closure rate and timing, top identified referrers and queue integrity. Practices can choose 30 days, 90 days, 12 months or all time; month boundaries use the practice timezone stored in Workspace settings. Never referral text, patient identity or clinical meaning.

Relationship segments, never-referred gaps, the geographic map and the standalone closure ledger shown in the design recording are not part of the current connected artifact.

Design recording with fictional details and no patient information. Relationship, geography and closure-ledger routes do not ship in the connected console.

Connected analytics today

Referral volumes and arrival stats. Every connected referral is counted on the way in, by channel and over time. The console’s Today tiles and Practice analytics monthly count are read from arrivals at the door, not from what was later typed in. Order is always arrival order, never a ranking of anyone’s urgency. Invalid or future arrival timestamps are verified and reported as data-quality exceptions, but excluded from every operational total.

Administrative timing and closure. The connected aggregate reports median and 90th percentile arrival-to-closure timing, open-age buckets and the share entered or declined. It fails closed rather than publishing a number when a referral event ledger does not verify.

Top identified referrers. The connected aggregate shows bounded business labels, latest arrival and counts for referrers already represented in the tenant queue.

Aggregate CSV. The selected view can be downloaded as a spreadsheet-safe CSV containing only aggregate counts, administrative timing and business referrer labels. It does not export patient identity, referral text, documents, stated urgency or clinical content.

The connected page remains locked until the workspace is live, the connector proof is current and the workspace reports ready. It fails closed without requesting the aggregate while those conditions are incomplete.

Extended views are not included

The loyal/lapsed/never-referred segmentation, Show the gap, geographic catchment and standalone closure-ledger routes remain design-only features. They will not enter the licensed artifact until they use tenant-owned, non-clinical projections and pass their named privacy and connected-browser gates. Authenticated Inbox and account exports remain the current specimen-level paths; the aggregate CSV is the machine-readable analytics path.

The boundary that never moves

Everything on this page is process analytics about the practice, never clinical analysis of a patient. The views aggregate referral arrivals, closure state, referrer identity, channel and administrative timestamps. They never expose geography in the connected console, read into the referral’s clinical content, rank patients or compute acuity. Refera tracks referral admin only. It does not triage patients.

Related

• Growth intelligence - the relationship and geography design exploration.
• Closure ledger design - the evaluated specimen-level design, not a current connected route.
• Why the front door - why counting at the door beats EMR-derived reporting.
• What Refera does not do - the clinical line, stated plainly.