Start a referralFind a hospitalPatientsDentistsHospitals

For your reviewer

What eReferral is, what it stores, and who handles it

One page for a privacy, security or legal reviewer. Everything here is what the running service does today.

Who we are

eReferral is published by Continuum Health Systems LLC. Contact: send a request.

What pays for it

It is free. There is no money from any party, and eReferral never picks the dentist. Nobody pays to be listed or to be sent a referral.

What it does

It records the status of a dental evaluation request: sent, received, scheduled, seen, report back, closed. It does not carry the report and does not notify anyone about a referral. There are no accounts and no cookies. A private link is the key to a referral.

What is stored, field by field

A referral has no free text field. Every value in a referral is a choice from a list, a date picked from a calendar, or a code the server makes. The separate request page (claim, correction, help, contact) has an optional note box, listed in its own row below. No names, birth dates, contact details or notes are asked for. This table is checked by a test against the keys the service really writes.

Hospital
The hospital picked from the public CMS list: its slug, CMS number, name, city, state and the main phone number CMS lists. Nothing typed. The phone is shown to the dentist link only.
Who can read it: Requester link and dentist link; track page (hospital and track code): name, city and state only, no phone. Kept: Until the referral is deleted.
Request id
A random 16 character id. It is part of both links.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Link keys
Only a SHA-256 hash of each link key is stored, never the key. Nobody can rebuild a link from storage.
Who can read it: Neither page shows it. Kept: Until the referral is deleted.
Who started it
One of: patient, family or caregiver, care team, dentist office, physician office. Not verified.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
What is being sent
Dental or medical, picked by the sender. A referral made before this choice existed has none and reads as dental.
Who can read it: Requester link and dentist link; track page (hospital and track code): yes. Kept: Until the referral is deleted.
Who it is going to
One of: dental office, medical office, hospital or care team. Optional. Names no office.
Who can read it: Requester link and dentist link; track page (hospital and track code): yes. Kept: Until the referral is deleted.
What is needed
One fixed choice from a list that depends on what is sent and who it goes to (six for dental, five for medical, plus two older dental choices kept for existing callers).
Who can read it: Requester link and dentist link; track page (hospital and track code): yes. Kept: Until the referral is deleted.
How the report gets back
One of four fixed choices. The report itself never passes through eReferral.
Who can read it: Requester link and dentist link; track page (hospital and track code): yes. Kept: Until the referral is deleted.
Reference code
The random eight character code for the written order, kept encrypted under the requester link key, and the stored name of the code pointer item that opens the request (a keyed hash, not the code). It opens the dentist page only. It does not open the track page.
Who can read it: Requester link only. Kept: Until the referral is deleted, or until the requester makes a new code.
Track code
A second random eight character code, for a chart note, kept encrypted under the requester link key, and the stored name of its pointer item (a keyed hash, not the code). It only lets a reader look.
Who can read it: Requester link only; track page (hospital and track code): the code the visitor typed. Kept: Until the referral is deleted, or until the requester makes a new reference code, which replaces it.
Track code pointer (a separate stored item)
Named by a keyed hash of the hospital and the track code. Holds only the request id and a time. It holds no link key, so it opens nothing writable.
Who can read it: Neither page shows it. Kept: Until the referral is deleted, or the track code is replaced.
Server reference
A random 16 character reference the server assigns for a connecting system. Nobody chooses it.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Dates entered
Optional, picked from a calendar: needed by, first asked for, the dentist visit date, the date treatment finished.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Time of each stop
The server time each stop was marked, the time the referral was made and last changed, and a change counter.
Who can read it: Requester link and dentist link; track page (hospital and track code): sent, received, scheduled, seen, report back, closed and the start time; not the treatment stops, the change time or the counter. Kept: Until the referral is deleted.
First time each side opened what the other sent
A server time. No other viewing is recorded.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Dentist finding
One of three fixed choices. Not a clearance. (result is the older name of the same field.)
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Decline
The time the dentist office declined and one of seven fixed reasons.
Who can read it: Requester link and dentist link; track page (hospital and track code): the time, not the reason. Kept: Until the referral is deleted.
No longer needed or canceled
The time and one of four fixed reasons, or the time of a cancel.
Who can read it: Requester link and dentist link; track page (hospital and track code): the time, not the reason. Kept: Until the referral is deleted.
Reschedule count
How many times the dentist changed the visit date.
Who can read it: Requester link and dentist link; track page (hospital and track code): the count. Kept: Until the referral is deleted.
Reopen count
How many times the requester reopened a declined request.
Who can read it: Neither page shows it. Kept: Until the referral is deleted.
Care team desk
The time a care team desk took the referral on, and the id of that desk. Pages show the time and whether a desk holds it, not the desk id.
Who can read it: Time: requester link and dentist link. Desk id: neither page. Kept: Until the referral is deleted.
Questions and answers
Up to eight pairs. Each question is one of nine fixed choices and each answer one of four, stored as a code, with who asked and when. No words typed by a person are stored.
Who can read it: Requester link and dentist link. Kept: Until the referral is deleted.
Code pointer (a separate stored item)
Named by a keyed hash of the hospital and the code. Holds the request id, the dentist link key encrypted under the code and a server secret, and a time. It opens only with the hospital and the code.
Who can read it: Neither page shows it. Kept: Until the referral is deleted, or the code is replaced.
Desk (a separate stored item)
The time it was made, a hash of the desk link key, and its list of referrals with the time each was added. Each referral key on the list is encrypted under the desk link.
Who can read it: Desk link: the list of its referrals and their status links. Kept: Deleted after 400 days with no change.
Deletion heartbeat (a separate stored item)
The time the daily deletion job last ran and how many items it looked at, deleted, cleaned, how many old-form or out-of-date code pointers it removed, how many requests remain, how many owner alerts it resent, whether alerts remain stuck, and the retry progress and continuation cursor. No record content.
Who can read it: Neither page shows it. Kept: Replaced at each run.
Request from the request page (a separate stored item, not part of a referral)
Only when someone sends a claim, listing, correction, help or contact request. The kind of request, the hospital or practice named and the public listing it matched, the sender role, work email, optional phone number and optional note, and the time. The form refuses some patterns that look like patient details, such as birth dates and record numbers, but it cannot catch every name, so do not write about a patient in it. No IP address is stored.
Who can read it: Us and Vercel as the host. No page shows it. Kept: 180 days, or sooner when the sender asks us to delete it.
Owed owner alert (a separate stored item)
A marker that exists only while the alert telling us about a request has not gone out. It holds the request reference and a time and is removed when the alert is delivered. While one exists the health check reports a failure.
Who can read it: Neither page shows it. Kept: Until the alert is delivered.

Read this before your team puts a code in a chart

A referral holds no name. It does hold the time of each step, the visit date and the dentist's one-line finding. If your team pastes the track code or track link into a patient's chart, or writes the reference code on an order, your organization can link the record to that patient. Ask your privacy officer whether that use is allowed under your policy before you do it. We do not offer a business associate agreement for the free tracker.

Anyone with access to the storage account, which means us and Vercel as the host, can read the stored values above. Link keys are stored only as hashes, and reference codes and desk entries are stored encrypted under a value the store does not hold.

Profile store (separate from referrals)

A practice or hospital team can make a profile of business contact details. It is a different stored item from a referral, in a different place in storage, and a referral never points to it or holds a copy of it. A profile holds no patient information of any kind: no field exists for one, and the server refuses a request that carries a key outside the list below. There are no accounts. One private link is the only key, and we cannot recover a lost one.

Profile id and kind
A random 16 character id, and whether it is a dental office or a hospital team.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Link key
Only a SHA-256 hash of the profile link key is stored, never the key. Nobody can rebuild a link from storage, so a lost link cannot be recovered.
Who can read it: Nobody: no page shows it. Kept: Until the profile is deleted.
Public identifiers
The practice NPI (public, checked for format only, not looked up) or the hospital CMS number from the public list.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Listing status
Always the words "pending license check". The holder cannot change it.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Business details
Office or team name, public business phone, business email, address lines, city, state, ZIP, and the hours as one pick from a short list. Business details only. The server refuses dates, long numbers and patient words.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Availability, as the office told us
Dental office profiles only. Four picks (yes, some or no) for seeing a patient within the week, same-day emergencies, a 72 hour window and after hours; whether there is a biller or admin (biller, admin, both or none) with a first name or role, a title and a business phone or email; and the day it was last given. These are the office's own answers on that day, not a promise.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Who receives evaluation requests
A reference to one of the contacts below. Nothing is typed here.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Points of contact (up to 5)
For each: a random id, a first name or a role (letters only), a business phone and or business email, and which of four request types it receives, picked from a list.
Who can read it: Only the holder of the profile link. Kept: Until the contact or the profile is deleted.
How to be told, and pause
Text, email or both, and an optional pause date up to 30 days ahead.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Times and change counter
The server time the profile was made and last changed, and a change counter.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Confirmation and what the holder opened
The time the holder confirmed the details are right, and for five page events (opened, celebration shown, forms opened, form printed, office rows viewed) plus the first hospital pick the first time and how many times. For a link we made after a call, the public-registry name it was made for. No page text, no address of the visitor.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Hospitals that send them patients
Up to three hospitals the holder picked from the public CMS list.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.
Office list for a hospital team
Up to 40 dental offices near the hospital, each with office name, type, address, business phone and a status of "Listed, from public record" or "Confirmed". It is built from the public NPI registry by us, held in the profile, and released to the page only after the holder confirms the profile.
Who can read it: Only the holder of the profile link. Kept: Until the profile is deleted.

Anyone with access to the storage account, which means us and Vercel as the host, can read the stored values above. No page shows another holder's profile. Nothing is sent to anyone from a profile today.

Limits on guessing a reference code

A reference code or track code is eight letters and numbers (about 1.1 trillion combinations) and works only with the hospital it was made for. Opening a request by reference code and looking one up by track code share one budget: after 40 tries that miss, in an hour, from one connection (an IPv6 visitor counts as its /64), the page asks the visitor to wait. A track page that is refreshing a code that already worked is counted separately, at 60 an hour for that hospital and code, unless the refresh misses. That count is kept per server instance, and the hosting can run more than one, so it slows guessing and does not put a hard cap on it. The requester can make a new reference code at any time from the status page, and the old code stops working.

Two codes

Each referral has two eight character codes. The reference code goes on the written order and opens the dentist's page. The track code goes in a chart note and only lets a reader look. They are made separately and each has its own stored pointer. The reference code does not open the track page, and the track code does not open anything on the dentist's page or the requester's.

The track page, by hospital and track code

At ereferral.org/track anyone who has the hospital and the track code can see where a referral stands. It is read only: it writes nothing, does not stamp an open time and returns no link key. It returns the hospital name, city and state (not its phone number), what is needed, how the report should get back, the track code the visitor typed, the date it was started, the time of five stops (sent, received, scheduled, seen, report back) and of closing, whether it was declined, canceled, ended or has passed its date, and how many times the visit date moved. It never returns the treatment stops, the dentist's finding, the questions and answers, who started it, a referral id or a link key. The code alone is not enough, because the hospital is part of the lookup. A deleted referral, a replaced track code and a wrong code give the same plain answer.

Retention

A daily job deletes a referral 180 days after its last activity. The person who started it can delete it at any time, and that removes the record and its printed code at once. A desk is deleted after 400 days with no change. A profile is deleted after a year with no change, or at once when its holder deletes it.

Subprocessors

  • Vercel. Hosts the site and the API, and holds referrals in a private Vercel Blob store. Vercel keeps standard server logs, which include IP addresses, for a short period.
  • Telegram. Carries our own staff alert when someone sends a request from the request page. It receives the request reference, its kind and the public listing name it matched, never an email, phone or note. Nothing about a referral is sent to it.
  • Twilio. Carries text updates only for people who sign up at ereferral.org/text. It receives the mobile number and the message, which holds links and codes only. Not used by the referral tracker itself.

Other companies that see a visitor's IP address

  • Google Fonts. The page fonts load from Google. Google can see the visitor's IP address. Nothing typed on this site is sent to it.
  • unpkg. The page icons load from unpkg. It can see the visitor's IP address. Nothing typed on this site is sent to it.

Our own application log lines carry a short hash of the referral and the action taken, never a link key, a reference code or a question.

What we do not offer

We do not offer a BAA (business associate agreement). Do not use eReferral for anything that must stay inside the chart. We make no claim that it meets any hospital policy, and whether your policy asks for a review is your call.

Questions

Send a request on the request page. See also the privacy page and the terms.