Website and patient-access guidance, without internal admin content.

Hospital Website Entry Points

• Main website explains specialties, clinicians, service lines, and contact points.
• Book Appointment should route directly into the booking journey with minimal friction.
• Patient portal should be presented as a record-access destination, not an admin surface.
• Support links must show the current front-desk contact path and escalation hours.
• Training videos on the website should explain only public, patient-safe workflows.

Patient Booking Flow

1. Patient selects Book Appointment or a department-specific call to action.
2. Booking captures patient name, phone, visit type, provider, and preferred schedule.
3. Front desk validates duplicates, insurance requirements, and pre-visit instructions.
4. Confirmation is sent with visit details and any required documents.
5. Visit-day staff continue the workflow from Appointments or Front Office.

Patient Portal, Invoices, and Reports

• Portal login uses Organization ID, MRN or Patient ID, date of birth, and phone number.
• Visible data includes appointments, prescriptions, verified reports, and invoice-ready billing documents where enabled.
• Reports can be printed or saved as PDF from the verified reports section.
• Invoices and receipts should be shared only through approved patient-facing workflows.
• Session expiry should direct patients to sign in again rather than escalate unnecessary support calls.

Website Governance

• Tenant admin or website owner keeps specialties, clinician listings, and patient instructions current.
• Front desk lead owns booking-response expectations and contact details.
• Billing lead approves how invoices, receipts, and reports are described publicly.
• Patient-facing training must never mention preview modules, tenant controls, or platform-admin operations.