The pharmacy's ZIP code isn't your patient's location.

Most telehealth workflows treat "the address on file" or "where the prescription was routed" as the location check. Neither answers the question a state board or the DEA is actually asking.

Most telehealth providers use one of two proxies for patient location during a session:

• The address on the intake form. What you had at signup — often months old.
• The state the prescription was sent to. Where the pharmacy is, not where the patient was.

Neither is what a state board looks at when a question comes up. State licensure keys to where the patient is physically located at the moment of the encounter. Not where they live. Not where the script is filled.

Three layers, three different checks

State licensure. Your license authorizes you to practice on patients located within that state's borders during the encounter. This is the layer most cross-state telehealth cases turn on. If a patient with a Texas address is joining from a hotel in New Jersey and you're not licensed in NJ (or covered by a compact), the state you're practicing in — for licensure purposes — is New Jersey.

DEA registration. The DEA's proposed telemedicine special-registration rule (90 FR 6541, published January 17, 2025) would require prescribers to register in each state where their patients are located and to document patient location for each encounter. The prescription would need to carry the patient's address. The final rule is expected in late 2026 and hasn't published yet — the proposed framework is the current signal.

Pharmacy corresponding responsibility. When a prescription arrives, the pharmacist independently checks that it's valid and appropriate. This is a pharmacist obligation — it doesn't relieve the prescriber of the licensure or DEA questions above.

Routing the prescription to a pharmacy in the right state satisfies layer three. It says nothing about layer one or layer two.

The failure modes are predictable

Address-on-file and pharmacy-state work fine until they don't:

• The college student home for the summer. Address on file: Boston, MA. Actually in: parents' house in Portland, ME.
• The snowbird. Address on file: Buffalo, NY. Actually in: rental in Naples, FL from November to April.
• The patient traveling for work. In their home state on the intake form, in another state during the session.
• The patient who moved. Six months since they updated the chart. They're two states over.
• Mail-order and central-fill pharmacies. Prescription routes to a fulfillment center that isn't where the patient lives, works, or was during the visit.
• The pharmacy near home, patient joining from elsewhere. Common with regulars — they pick their usual pharmacy, they join the session from wherever they happen to be.

Each one produces a real-time gap between what the chart says and where the patient actually was. In practice, most providers don't notice — and boards don't ask about routine sessions. The distinction only matters when it matters, and by then the record doesn't exist.

What to record

The question a board or reviewer is going to ask, if they ever ask, is: where was the patient at the moment of the encounter? Not: where does the patient live? Not: where was the prescription sent?

TeleVerify captures the patient's real-time location at session start and stores a signed record. When the question comes, the answer already exists.