Patient-owned data, clinic-aware workflows.
The production design separates patient-owned Personal Health Record data from clinic/provider workflow records, with explicit access, sharing, export and deletion controls.
Patient • Family • Provider • Clinic
One application shell, different role-aware workspaces. Patients see only their own authorized record and relationships.
Login, roles, consent
Authenticated accounts, multi-factor authentication direction, role-based access, patient sharing grants and revocation.
Patient-centric services
Accounts, care team, medications, appointments, labs, documents, learning, requests, follow-up and notifications behind a stable API.
PostgreSQL + secure files
Structured records in PostgreSQL, encrypted document/object storage, immutable-style audit events, source provenance and consent history.
FHIR, labs, devices
FHIR APIs, approved provider/lab integrations, phone/wearable sources and secure notification providers. Availability differs by organization.
Optional, replaceable AI
1min.AI, OpenAI, Gemini or other providers sit behind an adapter. Sensitive patient data is not sent until privacy, contracts and controls are approved.
Deletion must be precise
Patient-owned Personal Health Record data should have clear export and deletion controls. If a clinic/provider is legally required to retain its own clinical/business record, ForMyMedical must identify that separately rather than claiming the clinic’s regulated record has been erased.