Older-Adult Follow-Up Checklist: Visits, Documents & Rides
With consent, check the original follow-up booking, document categories and rides before drafting administrative notes. Try a non-sensitive Yihu sample and review privacy and setup.
Preview privacy before you try
The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.
Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide
US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.
Check the booking, then confirm documents and each ride
With the person’s consent, verify the follow-up booking, date, hospital site and required document categories through hospital-accepted original channels. Confirm each ride and companion role with the actual responsible people. Keep only necessary non-sensitive administrative notes, not patient or family data. Leave missing confirmations open. Clinical matters stay in hospital-required channels; do not wait for this checklist or message receipts in an emergency.
Scope: companion logistics, not clinical handover
This checklist helps family members verify administrative roles when taking turns accompanying someone; it does not replace hospital visit instructions. Accompanying a person does not automatically grant record access, signing rights, document collection rights or decision-making authority. Ask the hospital about the actual procedure and authorization for any representation. Do not put names, identity numbers, booking codes, contacts, medical history, test results or medication into this worksheet or an unapproved device or workbench. Actual documents and medical content remain in the person’s consented, hospital-accepted channels.
With the required model, permissions and compatible workbench, Yihu can organize voice text and recording notes and prepare drafts. It is not a booking, medical-record, family-authorization or transport-dispatch system. It does not contact hospitals, book vehicles or assess fitness for a transport mode. Recording separately requires the person’s permission and compliance with hospital rules; omit it when not permitted. Local recognition does not mean the destination will not store or sync content. Check the device, location, account and access scope before saving.
Twelve checks before handing over companion arrangements
| Check | Where to verify | Minimum conclusion to retain | If uncertain |
|---|---|---|---|
| Current appointment reference | Hospital’s original booking channel | Whether the current arrangement was checked; no booking code | Resolve conflicts with forwarded screenshots or old messages at the original channel |
| Date and hospital site | Current booking and hospital notice | Verified date, site and location scope | Do not infer the visit date from message receipt time or confuse similarly named sites |
| Check-in instructions | Official instructions for that clinic | Which requirement was checked and which needs a question | Family experience is not hospital policy; give no fasting or medication advice |
| Document categories | Hospital’s required-material list | Required categories checked; no contents or identity numbers | Ask the hospital about missing categories; do not interpret test results |
| Document custody | Original channel consented to by the person | Who checks custody within authorization, and whether return steps are clear | “Brought” does not mean returned; do not upload originals as proof |
| Outbound transport | Actual driver’s or provider’s original confirmation channel | Whether ride scope and meeting arrangements are confirmed | Sending is not acceptance; make no transport-safety assessment |
| Return transport | Actual responsible person and original arrangement | Who checks the return ride and whether it remains open | An estimated visit end does not guarantee pickup time |
| Companion roles | Person’s wishes and explicit family feedback | Who checks registration and materials, within authorized roles | No reply means unconfirmed; do not accept tasks or sign for others |
| Assistance request | Person’s wishes and hospital service channel | Whether a request needs clarification or has been confirmed | A wheelchair request is not a reservation; make no mobility assessment |
| Open questions | Original question list consented to by the person | Administrative question categories and who asks the hospital | Clinical questions go to qualified staff; transcription must not invent answers |
| Draft destination | Current account, page and original attempt | Only necessary administrative items, at an authorized destination | Stop on target change or host refusal; do not bypass with attachments |
| Acknowledgement and duplication | Original sending record and explicitly linked feedback | Draft, sending and ride acceptance checked separately | Check the original destination on uncertainty; do not resend to manufacture confirmation |
Use Yihu in this order
- Obtain consent and check the original arrangement. Without access rights, let the person or an authorized representative check in the original channel. Do not borrow accounts or export complete bookings or medical files.
- Keep only administrative scope. Separate verified arrangements, open items and who checks next. Preserve unconfirmed roles rather than turning intentions into commitments.
- Review key terms word by word. Compare dates, hospital site, arrival requirements, outbound and return roles, and negation. “Ride not yet confirmed” must not become “confirmed.” Recording order is not event order.
- Check the target and earlier attempt. Explicit insertion binds to the workbench and page present when the note was opened; stop if the target changes. Not every page supports insertion. A visible draft is neither sent nor registered with the hospital.
- Obtain feedback for each separate scope. The actual responsible person confirms in the original authorized channel. A sending receipt is not driver acceptance; checked document categories do not prove the actual documents are complete. Without feedback, retain the open state.
- Stop on uncertainty and inspect original records. The note’s single handoff reservation covers direct insertion and staging. Do not clear markers, rename notes or switch targets to blindly resend after failure or uncertainty. New operations do not prove old ones; copying can leave duplicates too.
Direct insertion has a 3,000 Swift Character limit; longer notes use the existing Markdown attachment-staging path. Staging, uploading, sending and human acceptance are different stages. Do not use attachments to bypass refusal. There is no offline outbox, automatic notification, automatic retry, cross-target deduplication or recall of every copy added by this page. Restored connectivity does not prove the booking and ride arrangements still apply.
Download the blank manual worksheet
Instructions: /samples/p34-older-adult-follow-up/README.md · 中文:/samples/p34-older-adult-follow-up/checklist.zh.json · English: /samples/p34-older-adult-follow-up/checklist.en.json
The twelve checks are bilingual equivalents. null / unfilled means unfilled, not passed, not applicable or complete. This is not an app import, booking slip, hospital acceptance record or authorization form. The page and files do not receive entries. Before saving a filled copy, check storage and access. Include only minimal non-sensitive references, verified scope and unresolved questions, not patient or family data.
Frequently asked questions
Does sending the checklist to family confirm the appointment?
No. The hospital’s original channel establishes the booking; explicit feedback from the relevant people establishes family roles. A successful send replaces neither.
Can I put medical records, identity documents and booking codes in the download?
No. It checks document categories and administrative custody scope only. Originals and medical content stay in the person’s consented, hospital-accepted channels, not this page or an unapproved workbench.
Should the person stop medication or fast before the follow-up?
This page provides no such advice. Verify the hospital’s and qualified professionals’ instructions for the individual. Do not infer requirements from someone else’s experience or a voice draft.
Does a companion automatically get signing or medical-record access rights?
No. Follow the person’s wishes, the hospital’s actual rules and the relevant authorization process. This worksheet is not authorization or identity-verification evidence.
Will Yihu chase a driver who has not replied or arrange a vehicle?
This page promises neither. No reply remains unconfirmed; check through the original contact method. Ask the relevant service professionals about assistance or safety rather than having this checklist assess it.
The page reloaded after insertion. Can I hand off the note again?
Check the original destination first. Reload, a missing receipt or restored connectivity does not prove the original operation did not happen. Do not bypass the single handoff reservation or use new operations to prove old ones. Use existing reliable channels for urgent matters.
Continue reading and source boundaries
Recording notes · Connectivity troubleshooting · Revised copies · Start · Privacy
Capability evidence: current source README, single handoff and length boundaries. Earlier handoff notes are historical only, not evidence of current Store capabilities. A source merge does not establish installed-version availability; check Store information and the actual version separately. This page is not hospital guidance, clinical advice or legal/compliance certification.
