Demographic and insurance updates

How do we take a patient's address, phone, guarantor or new insurance card in the portal or at check-in, verify it, and update the EHR without a registrar retyping it?

Treat the update as a verified instruction from an identified patient. Callvu identifies the patient with the verification the change warrants, prefills the demographics, the guarantor and the coverage on file from the EHR, takes the new details or the card images on a secure screen, reads the card and runs the eligibility check, classifies the consequences (a new guarantor changes the financial responsibility, a new plan changes the referral and authorization rules for booked visits), routes a mismatch or a coverage that fails eligibility to the registration desk in the Decision Desk, and writes the update to the EHR registration record with the change logged.

In scopeSimpleCallvu moves: prefill, chase and verify, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The new insurance card was photocopied at check-in, filed, and the claim went to the old payer.

Today, without Callvu

A patient moves, changes phones, switches jobs and gets a new plan. They mention it at check-in; the registrar photocopies the card and promises to update it later. The claim bills the old payer and denies; the statements go to the old address; the appointment reminders go to a disconnected number. A small update that was never written is a denied claim and a lost patient.

A demographic or insurance update touches the HIPAA rules on verifying who is asking and on the patient's right to confidential communications, the registration data standards the EHR enforces, and the billing consequences of a guarantor or plan change. The card is a document to read, the coverage is a check to run against the payer, and the EHR is the only place the update counts.

An update the patient makes on their phone, verified and written to the EHR, is the one the next claim uses.

How it runs

From the requestto the system of record.

A patient starts an update in the portal, from a check-in text, at the kiosk, or with a registrar on a call. Callvu identifies them and opens the update.

Patient or guarantor: Verifies identity, enters the new details or photographs the card on a secure screen, and confirms.
Registration desk: Decides mismatches and failed eligibility in the Decision Desk.
Callvu: Verifies, prefills, reads the card, checks eligibility, classifies the consequences, routes and writes to the EHR.

Verify and prefill
The patient is identified with the verification the change warrants (a one-time code to the contact on file for an address, a stronger check for a change that moves both the address and the phone), and the demographics, the guarantor, the emergency contact, the communication preferences and the coverage on file are prefilled from the EHR so the patient changes only what changed.
Chase and verify the new details
The new address, phone, email, guarantor or insurance is entered; a new card is photographed front and back and read for the member and group numbers, the plan and the payer; the coverage is checked for active eligibility with the payer and the result is attached; a request for confidential communications (an alternative address or phone) is captured under the patient's HIPAA right; what is unreadable or fails is requested again with the specifics.
Classify the consequences and decide
The change is classified: a contact-only change, a guarantor change that moves financial responsibility and needs the guarantor's acknowledgment, a new plan that changes the referral and authorization requirements for visits already booked (which are flagged for the scheduling and authorization processes), or a card that fails eligibility; a mismatch between the card and the patient, a failed eligibility or a guarantor change without acknowledgment goes to the registration desk in the Decision Desk with the images and the result and only the allowed outcomes.
Write back
The update is written to the EHR registration record (and the billing system where the guarantor or the plan changed) with the effective date, the card images attached, the eligibility response stored, and the change logged with who made it and how they were verified; a confirmation goes to the old and the new contact where the contact changed.

Where it ends: The patient changed only what changed, from their phone or the kiosk, the card was read and the coverage checked before anything was written, and the EHR holds the update with the log the privacy rule expects. The Decision Trace shows the verification level, the classification and any decision; the Audit Trace shows the entries, the eligibility check and the write with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

HIPAA Privacy Rule, verification and confidential communications (45 CFR 164.514(h) and 164.522(b)): A covered entity must verify the identity and authority of a person requesting a change to or disclosure of protected health information before acting, and must accommodate a reasonable request by a patient to receive communications by alternative means or at an alternative location, without asking the reason; the verification step and the confidential communication flag apply these to the update.
Payer eligibility and the HIPAA standard transactions (45 CFR 162, the 270 and 271 eligibility inquiry and response): Coverage is verified with the payer through the standard eligibility transaction, and the response (active or inactive, the plan, the copay and deductible information) is stored with the registration so the visit is billed to the right plan.
Patient identification and registration data standards (the Joint Commission patient identification goal and the provider's registration policy): Two identifiers are matched before a record is changed, and the registration policy sets the fields, the guarantor acknowledgment and the audit log the EHR must hold for every demographic change.

Company policies

The patient changes only what changed; the rest is prefilled from the EHR.
A new card is read and the coverage checked with the payer before the plan is written.
Verification is proportional to the change, and a confidential communications request is honored by rule.
The EHR registration record is the system of record; the billing system follows it.

Controls

Risk-based identity verification.
Prefill from the EHR.
Card reading and eligibility check.
Consequence classification with flags to scheduling and authorization.
Decision Desk for mismatches and failed eligibility.
EHR write with log and dual confirmation.

Clocks and deadlines

Effective date: The date entered, not before the request; a new plan applies to visits from its effective date.
Eligibility check: Run at the update and again before the next visit through the verification process.

Documents and checks

The verification record
The prefilled record and the changes
The card images and the eligibility response
Any decision
The EHR update and the log

In the Decision Trace

The verification level and why.
The classification and the flags raised.
Any decision and the person.

In the Audit Trace

The request with channel and time.
The eligibility check with time.
The write and the confirmations.

The handoff

Between the front doorand the back office.

The front door

The portal, a check-in text, the kiosk or a registrar's link on a call; the patient acts on a secure screen.

The back office

The registration desk sees only mismatches and failed eligibility; the EHR is written by the process.

The Decision Desk

A card that does not match the patient, a failed eligibility or a guarantor change without acknowledgment goes to the registration desk in the Decision Desk with the images and the result, and only accept, request again, or hold.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

23 hospitals in the Ministry of Health network run on Callvu.

Across Callvu customers

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Questions

What buyers ask next,answered plainly.

How is the patient verified?

With a check proportional to the change: a one-time code to the contact on file for an address, more for a change that moves the address and the phone together, as the privacy rule's verification standard requires.

What happens with a new insurance card?

It is photographed on the patient's phone, read for the member and plan details, and checked for active eligibility with the payer before the plan is written to the EHR.

Does a new plan affect booked visits?

Yes. The change flags visits already booked so the scheduling and authorization processes recheck the referral and authorization rules under the new plan.

Related processes

Insurance card and ID capture Insurance eligibility verification New patient registration Guardian and proxy access setup Try it in the sandbox All healthcare processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.