Skip to content
INTERACTIVE PATIENT JOURNEY

Everyday Dental

Independent build of a dental practice website with an interactive patient journey, consent and access-denial states. No real patient records.

Everyday Dental independent website build, home page
CURRENT SCOPE

Independent build · source published on GitHub

WHO IT'S FOR

Independent build

An independent build of a dental practice website, not a real practice. The patient journey stores no real patient records, payments or clinical data.

THE ENGINEERING

An independent build of a dental practice website, not a client project and not a real practice, with an interactive patient journey, consent examples, access-denial states and a FHIR-shaped export. State lives in browser memory and no real patient records are stored. Real intake, clinical authentication, payments, messaging and the historical clinical endpoints are disabled. It shows interface behavior and engineering boundaries; it is not an operating clinical portal. Source and documentation were published on GitHub with all 255 file hashes matching.

Responsive UIBilingualPrivacy flows

BEFORE → AFTER

Real problems from this build, what I changed and the verified result.

  1. CASE 01
    Before

    The historical clinical version had real security gaps, including unauthenticated notification and breach handlers.

    After

    The public site runs only in a mode that accepts no real patient data.

    How I fixed it

    Disabled all 11 historical Edge Function endpoints behind a deployed guard, with owner approval, and kept the defects documented rather than relabelled as repaired.

  2. CASE 02
    Before

    Reviewers need to see privacy and consent behavior without handing over real health data.

    After

    15 of 15 regression tests covering access decisions, consent, erasure and the runtime boundary.

    How I fixed it

    Built a fixed patient journey with consent, access-denial, erasure and export flows in browser memory, with no real patient records.

  3. CASE 03
    Before

    Applying historical migrations to an unknown live database could destroy existing records.

    After

    The corrected release passed all 138 file hashes.

    How I fixed it

    Preserved every record: no migrations or database mutations were run, and upgrades require inventory, comparison and a tested rollback plan first.

Evidence reviewed: Portfolio release and GitHub publication, September 24, 2026