Search and review patient records
The patient area includes responsive list and table views, search controls, filters, pagination, and patient summary patterns.
Keep the patient record connected to the work around it
Move from a permission-aware patient directory into profile, care-team, appointment, documentation, messaging, billing, form, and portal context without rebuilding the story in every tool.
Find and orient
Start with a directory that supports real operational work
Open the right patient context
Patient detail routes organize profile and related workflow information around a stable patient record rather than loose contact entries.
Continue into the task at hand
From the patient context, staff can reach appointment, chat, billing, insurance, form, and documentation workflows that exist in the current application.
Access boundaries
Patient visibility follows organization, role, and permission context
A healthcare record should not appear merely because a route exists. The current architecture layers route, UI, API, and data-access checks.
Active organization context
The staff application resolves the active organization before organization-scoped workflows and supports switching only among available memberships.
Role and permission gates
Patient access distinguishes broader patient-management permissions from own-patient, location, company, and chart-related flags.
Server-side access contracts
Service and database layers contain explicit organization and patient-access checks; production tenant isolation still requires independent environment evidence.
Patient relationship
Keep staff workflow and patient self-service related but distinct
Patient portal access
Invitation and patient-context routes connect an approved patient identity to a separate portal shell.
Explore patient self-serviceMessaging in context
Staff and patient messaging routes support conversation access without exposing the full staff workspace to patients.
Forms and requested actions
Patient form routes create a focused place for assigned actions while staff retain the broader administrative view.
Continue exploring
Evaluate one patient journey from both sides
Choose a task such as scheduling, forms, messaging, or billing and see how staff and patient views remain connected without becoming the same interface.