Clinic check-in handoff

Check-in can begin in the clinic and continue on the patient's phone.

A check-in can begin at the front desk, at a kiosk, or in a provider app. The patient opens the request on their phone, reviews it in their wallet, chooses what to share, and the check-in flow updates when the response is ready.

Overview Try kiosk creator Try phone check-in

What staff and patients see

The clinic starts the visit, but the patient reviews and shares from their phone. That keeps private health information off a shared clinic screen while still letting staff see when check-in information has arrived.

The important idea: the clinic starts the request; the patient's phone handles wallet review and approval; the completed response returns to the waiting check-in session.

This is the same patient-approved wallet sharing flow used when a patient checks in directly from their phone. The clinic handoff lets the patient complete the private sharing step on their phone while the check-in flow waits for the result.

Patient checks in from phone

The patient opens the check-in page on their phone, reviews the wallet request, shares approved information, and sees the result on the same phone.

Check-in continues on the patient's phone

The visit can begin at the front desk, at a kiosk, or in a provider app. The patient opens the wallet request on their phone and shares approved information back to the waiting check-in session.

Step by step

  1. The clinic starts check-in. The check-in flow creates a request for this visit and gives the patient a way to open it on their phone.
  2. The patient opens it on their phone. The handoff connects the patient's phone to the same check-in visit, without asking the patient to type private information into a shared clinic screen.
  3. The patient reviews the request. The phone shows what the clinic is asking for, such as insurance, demographics, medications, or an intake form.
  4. The patient approves sharing in their wallet. The wallet shows what will be shared. The patient can approve, decline, or share only some items.
  5. The check-in screen updates. The approved response returns to the waiting session. The clinic system checks it against the original request and displays the result for staff.

What the handoff needs to do

The handoff only needs to connect the waiting kiosk session with the patient's phone. Once connected, the phone runs the normal wallet sharing flow and returns the approved SMART Health Check-in response to that session.

1. Start The clinic creates a visit-scoped check-in session.
2. Join Patient opens the session on their phone.
3. Share Patient reviews and shares from their wallet.
4. Return Kiosk receives and checks the response.
What the handoff shows: the phone and kiosk are working on the same check-in visit, and the returned response matches the original request.
Technical note for implementers: identity, clinical provenance, patient matching, EHR write-back, and payment or claims handling are still site policy and integration decisions.

The connection can vary

A clinic can choose the handoff that fits its setting: a kiosk prompt, a front-desk prompt, a provider app notification, or another authenticated way to connect the visit and the patient's phone. The user experience can vary while the wallet sharing step stays the same.

Technical note for implementers: SMART Health Check-in defines the request, the wallet sharing step, and the returned response. The handoff mechanism and completion screen are implementation choices unless a specific deployment profile defines them.

Across those choices, the clinic starts the visit, the patient's phone handles private wallet sharing, and the check-in flow checks the returned response against the original request.