Skip to content
LOGITEXDevelopment LLC

Blueprint · Healthcare

Patient portal

Appointment booking, results and secure messaging for a clinic group, designed against HIPAA technical safeguards from the first schema.

Sector
Healthcare
Indicative timeline
18–24 weeks, including a third-party security review before launch

Reference design produced in-house. Not a delivered client project.

The problem

Booking happens by phone, results are mailed, and staff copy the same data into three systems. Every workaround creates another place patient data sits unencrypted.

Our approach

Minimise where data lives. The portal holds identity, appointments and messages; clinical records stay in the EHR and are read through an integration layer that never caches them. Access is role-based, every read of a record is logged, and the audit log is written to storage the application cannot delete.

Architecture

Clients
Next.js portalStaff console
Edge
Session authStep-up verification
Services
AppointmentsSecure messagingFHIR read-throughAttachment scanner
Data
PostgreSQL (encrypted columns)Write-once audit storeAWS KMS
External
EHR (system of record)Identity provider
  • Next.js portal, session-based auth with step-up verification for results

  • HL7 FHIR integration service, read-through only, no clinical data at rest

  • PostgreSQL with column-level encryption for identifiers and full-disk encryption at rest

  • Append-only audit log shipped to write-once storage outside the application account

  • Secure messaging with attachment scanning and retention rules per state law

What usually goes wrong

Compliance is an architecture decision, not a checklist at the end. The threat model and the data map are written in phase two and reviewed by your counsel before the first endpoint exists.

Have a system like this in mind?

Send us the shape of the problem. You get a written scope and a fixed number before anyone writes code.