Patient visitor or caregiver
Approved window, department or reception point, responsible coordinator, current status, and departure.
Coordinate patient visitors, caregivers, vendors, contractors, candidates, and service partners without turning the visitor workflow into a clinical record.
The operational job is to prepare the visit window, confirm the responsible department, manage reception and destination handoff, respond to restrictions or delays, and close the visit.
The visitor workflow should hold only the operational context needed by reception and the responsible department.
Approved window, department or reception point, responsible coordinator, current status, and departure.
Appointment, department host, purpose, evidence, destination, equipment context, and closeout.
Work purpose, facilities host, approved area, documents, escort, schedule, and exit.
Administrative appointment, host, location, arrival instruction, handoff, and completion.
Separate visitor operations from care documentation, patient identity, and clinical decisions.
Capture visitor type, purpose, visit window, destination, responsible department, host, and required check.
Reception sees approved arrivals.Approve, return, or reject the visit according to the current department and site policy.
Decision and reason remain visible.Find the visit, record arrival and check result, issue the pass if appropriate, and start waiting time.
The visit becomes current.Record the receiving department or host and current destination.
Reception can answer who owns the visit.Assign visit-window conflict, restriction, host delay, destination change, or late checkout.
One coordinator owns response and closeout.Record departure, pass return, unresolved follow-up, and history.
The current visitor list is reconciled.Keep clinical care, identity checks, and visitor coordination in the systems designed for each job.
The need is configurable requests, visit windows, department ownership, reception workflow, exceptions, dashboards, and frequent operating changes.
The record belongs to care delivery, patient identity, clinical documentation, or health information governance.
Native ID verification, watchlists, access credentials, readers, emergency response, or security adjudication defines the job.
No. It describes visitor coordination: visit window, reception, department or host, destination, current status, exceptions, and checkout. Clinical data and patient records stay in the hospital’s clinical systems.
Yes. Configure destination, visit type, window, approval, check, role view, and exception path by department or site while keeping a consistent visit record.
Yes, with separate branches for work purpose, facilities host, evidence, approved area, escort, equipment, schedule, and closeout.
Jodoo can record a check result and workflow decision. Native identity verification, scanning, watchlists, and physical access require specialist systems or integrations.
Collect only the operational visitor data required for the defined purpose, restrict role access, set retention, and keep clinical information out of the visitor workflow.
Test a patient visitor, vendor, contractor, window conflict, unavailable department, destination change, and overdue checkout without moving clinical data into the visitor record.