Use cases
What can be built on Anpheros: patient and family health apps, medical-data backends for startups, clinic and laboratory integrations, AI health assistants and consented third-party apps.
What can be built on Anpheros Platform, and which parts of the platform each case uses. The first case is how Anpheros itself uses the platform; the others describe what the implemented API supports — they are not customer references.
A patient or family health record app
Anpheros Daily, the Anpheros patient app, is built this way: it writes symptoms, vital signs, weight, medications, lab results, documents, appointments and daily summaries from Apple Health and Health Connect into the platform, for the account holder and for family members, and reads vital signs and medications back from it. It uses the same public API as any other application.
Uses: REST API · FHIR resources · documents · consent
A healthcare startup that needs a medical-data backend
A team building a new medical product — a chronic-condition tracker, a remote-monitoring service, a pregnancy or medication app — can keep its records in Anpheros instead of designing a medical database: patients, observations with LOINC codes, conditions with ICD-10, medications with ATC, documents with immutable originals, provenance and audit. It starts in the sandbox with synthetic patients and moves to production keys after verification.
Uses: Build a healthcare app · sandbox · SDKs
A clinic or laboratory delivering results to the patient
A laboratory sends a whole report (CSV, HL7 v2 ORU^R01 or JSON) and every result becomes a laboratory Observation in the patient's record, with provenance naming the source system; re-sending the same report is safe. A clinic writes on behalf of its organisation and names the practitioner, so the patient sees who recorded what. With the patient's consent the organisation reads the whole record but can change only what it wrote. This flow — consent, lab Observation, notification in the patient's app within seconds — has been exercised end-to-end with a test clinic project.
Uses: Lab connector · Consent and access model · Webhooks
An AI health assistant or agent
An assistant that answers questions about a person's health asks for consent, requests a budgeted context for each question, sends it to the model of its choice and can write its own notes back as AI-authored. The patient sees every read in the access log.
Uses: AI agents and medical data · Authentication and OAuth
A third-party app reaching an existing record
A fitness, nutrition or specialist app that wants data a person already keeps in Anpheros asks for exactly the scopes it needs (for example laboratory observations only), for a limited time, through SMART on FHIR standalone launch. It receives its own identifier for the person and loses access the moment the person revokes it.
Uses: Authentication and OAuth · FHIR R4 API
Sharing a standard summary
An application or a person who needs to hand a summary to a doctor elsewhere can generate an International Patient Summary (Patient/$summary), a FHIR document format designed for cross-border care.
Uses: FHIR platform