Clear answers before anyone gets access.

Only individual patients should request patient portal access. The portal is for appointments, queue updates, records, invoices, receipts, and notifications, but the hospital must verify the official patient record before clinical use.

No. Patients may request access and submit correction requests, but identity details, date of birth, medical identifiers, allergies, diagnoses, prescriptions, and clinical records should be verified or managed by authorised healthcare staff.

No. Hospitals, clinics, GP practices, care homes, and other healthcare organisations should use Request demo. After review and approval, the organisation contact receives a secure setup email and becomes the organisation admin.

Staff should not self-register as patients. They should be invited by the organisation admin or platform owner through the staff workflow, so their account receives the correct role and branch access.

Introducers are created by the platform owner. They receive a reusable referral link by email and may later access an introducer dashboard for referral and commission tracking only.

The platform owner manages MediFlow-wide setup, demo requests, and introducers. Organisation admins manage their own healthcare organisation. Staff use role-specific operational tools. Introducers track referrals only. Patients use the patient portal only.

MediFlow is being built for hospitals, clinics, GP practices, care homes, and other healthcare providers that want one secure operating platform for patient journeys, staff workflows, appointments, records, billing, insurance, communications, and analytics.

Not yet. The current release is a private preview for evaluation, demonstrations, workflow validation, and early customer discovery. It should not be used for live patient care until production security, compliance, testing, contracts, and operational onboarding are complete.

A healthcare organisation can review the product direction, test onboarding, explore core workflows, request additions, assess suitability, and discuss implementation requirements before becoming a paying customer.

A real work email, contact name, role, organisation name, phone number, organisation type, and a meaningful explanation of what they want to evaluate. This keeps the preview professional and helps filter fake or casual submissions.

A healthcare organisation requests a demo, the platform owner reviews the request, and approved contacts receive a secure Supabase Auth invite or password setup email. They then complete onboarding as the organisation admin.

No. Introducers have a separate referral view only. They can track referral links, referred organisations, status, and commission history, but cannot access patient records, clinical notes, billing, insurance claims, staff dashboards, or operational data.

The platform is designed around role-based access control, Supabase Row Level Security, audit-friendly workflows, service-role isolation for trusted server actions, and a strict separation between public preview, introducer, organisation, clinical, and admin areas.

No. AI features are intended to support operational insight, queue forecasting, triage suggestions, alerts, anomaly detection, and reviewable recommendations. Clinical decisions remain with authorised healthcare professionals.

Introducers are trusted contacts such as doctor friends, healthcare contacts, family friends, or professional contacts who can introduce MediFlow to hospitals, clinics, care homes, GP practices, and other healthcare providers.

Each introducer receives a unique referral link or code. When a healthcare organisation requests a demo through that link and later becomes a paying customer, the introducer may qualify for the agreed one-off referral reward.

The current proposal is a 5% one-off referral reward, payable after a referred organisation becomes a paying customer and the payment is confirmed. This can be adjusted later as the commercial model matures.

Introducers can see their referral link, referred organisations, onboarding status, and commission/payment history. They cannot see private healthcare operations or any patient-level information.

MediFlow uses managed cloud infrastructure with secure authentication, controlled data access, encrypted connections, and monitored deployment workflows. Technical providers and infrastructure details are reviewed internally and may evolve as the platform moves toward production.

The expected model includes subscriptions for hospitals or branches, setup/configuration, training, support, integrations, and premium modules. Final pricing should be confirmed after customer discovery and pilot feedback.

The public Vercel link allows people to request a demo, but full organisation access is controlled. The platform owner reviews requests before granting access, and production customer use should be governed by subscription terms.

The approved organisation contact receives a secure setup email, completes account setup, and can then continue through organisation onboarding. The platform owner can track the request and referral status.