Project gallery
1 / 17 · Carevo Console
The challenge
Patient booking, clinic queues, clinical documentation, and billing need a consistent workflow with clear ownership and access boundaries. Carevo models that journey across patient and staff interfaces, supported by backend safeguards for concurrency and sensitive records.
Outcome
A cohesive healthcare product foundation: interactive patient and clinic experiences, alongside a locally implemented backend with documented booking, queue, clinical, and billing verification.
My contributions
- Designed and built a mobile-first patient experience for discovery, booking, family profiles, visit history, and consent.
- Built an interactive clinic console for appointments, walk-ins, queues, clinical records, prescriptions, billing, and administration.
- Implemented a Go and PostgreSQL backend for tenant-scoped access, atomic booking, rotating sessions, clinical records, and billing.
- Added transactional outbox processing, private upload controls, API documentation, and concurrency-focused backend tests.
Explore the engineering & delivery
Product surfaces, workflows, architecture decisions, and verification details.
The product, end to end
PWA · partial API integration
Carevo Patient App
Clinic and doctor discovery, family-aware booking, appointment history, medical record previews, receipts, privacy, and notifications in a responsive patient interface.
Interactive demo-backed prototype
Carevo Console
Appointments, walk-ins, queue transitions, clinical workspaces, prescription safety, invoices, refunds, multi-clinic management, roles, and audit screens for clinic teams.
Backend implemented locally
Carevo Service
Go services for identity, clinic operations, clinical records, billing, private uploads, and durable jobs, with PostgreSQL transactions and scoped access controls.
Adapters awaiting configuration
External integration boundary
Interfaces for verification delivery, online payments, file scanning, notifications, and clinical ecosystem connections remain explicitly gated until providers and readiness checks are in place.
How the workflow fits together
Discover care and select a visit
The patient interface models clinic and doctor discovery, service selection, family-member selection, and appointment review. Full authenticated journey integration remains in progress.
Reserve a slot consistently
The implemented backend checks patient or guardian ownership, locks booking capacity, and creates the appointment and invoice in a transaction with idempotency protection.
Check in and manage the queue
Walk-in and check-in operations connect appointments with queue state. Backend row locks protect transitions; the Console demonstrates call, serve, and complete interactions using demo data.
Document the visit and settle billing
Clinical services finalize immutable records with addenda and prescription snapshots. Billing covers invoices, offline payments, receipts, and guarded refund/provider flows; external integrations are configuration-dependent.
From product design to delivery
01 / Product & workflow design
Mapped the journey from patient discovery and family booking to clinic check-in, treatment documentation, and billing. Separate patient and staff experiences expose the information and actions appropriate to each role.
02 / Frontend & PWA
Built Next.js and React interfaces with TypeScript, Tailwind CSS, and MapLibre for discovery. The patient app includes an installable manifest and an offline shell; the Console uses shared tables, filters, drawers, and clinical workspaces.
03 / Backend & contracts
Implemented Go modules for identity, clinics, operations, clinical records, billing, and workers. The OpenAPI contract documents the backend operations, while typed client layers provide an integration path for the two frontends.
04 / Database & concurrency
Used PostgreSQL migrations, tenant-scoped queries, row-level booking and queue locks, and transaction-scoped writes. Idempotency prevents duplicate mutations, and a transactional outbox records follow-up work alongside domain changes.
05 / Security & clinical data
Implemented rotating sessions, role and ownership checks, consent, audit trails, private upload validation, and short-lived downloads. Final medical records are immutable with addenda; the service worker excludes sensitive API responses from offline caching.
06 / Verification & pilot preparation
Documented local migrations, backend smoke checks, concurrency tests, API/worker startup, CI definitions, and operational runbooks. Pilot readiness remains dependent on complete frontend integration, configured external services, remote checks, and recovery validation.
Key engineering decisions
Make booking and queue transitions atomic
Database locks and transactions protect the last appointment slot and prevent two operators from advancing the same queue entry concurrently.
Keep the offline experience privacy-aware
Cache the application shell rather than patient, appointment, medical, or profile API data. This offers an installable experience without persisting sensitive responses in the service-worker cache.
Preserve clinical history and gate integrations
Final records are amended through addenda rather than overwritten. External payment and clinical adapters remain inactive until configured, making incomplete integrations explicit.
Testing & operational readiness
- The implementation notes record local race-test and static-analysis passes, migration/seed checks, and API smoke checks; these were not rerun as part of this portfolio update.
- Documented concurrency scenarios include competing requests for the last slot and simultaneous queue calls, with exactly one successful transition.
- Identity verification covers refresh rotation and session-family reuse; billing and worker checks cover transactional behavior and asynchronous processing.
- Pilot usage, production scale, and compliance certification are not claimed. External adapters and broader frontend integration remain delivery work.
Building something similar?
Let’s discuss the users, workflows, and priorities for your product.
Discuss Your Project