Anpheros for developers
What developers can build with Anpheros and where to start, by role: patient apps, medical backends, clinic and lab integrations, FHIR, AI features and AI-assisted development.
Anpheros gives developers interoperable medical-data infrastructure: a patient-controlled HL7 FHIR R4 record per person, a REST and FHIR API over it, OAuth-based consent, provenance, an audit visible to the patient, webhooks, a lab connector, an AI context API and SDKs for TypeScript and Dart. You build the product; Anpheros keeps the medical record and the rules around it. This page answers "what can I build with Anpheros, and where do I start?" by role.
What can I build?
- A patient or family health app — symptoms, measurements, medications, documents, a timeline — without designing a medical database.
- The backend of a medical product — remote monitoring, chronic-condition management, medication adherence — with consent and audit built in.
- A clinic or laboratory integration that delivers results into the patient's record with the patient's consent.
- An AI assistant or agent that answers questions about a person's record, with sources, within the patient's consent.
- A third-party app that reaches data a person already keeps in Anpheros, through SMART on FHIR.
Detailed scenarios: Use cases.
Start here, by role
| If you are… | Start with | Then |
|---|---|---|
| a mobile or web developer building a patient app | Build a healthcare app | SDKs, Authentication and OAuth |
| a backend developer | Medical app backend and database | Medical data API, Webhooks |
| an integration engineer at a clinic or lab | Healthcare integrations | Lab connector, Healthcare data interoperability |
| a FHIR developer | FHIR platform | FHIR code systems, API reference |
| building AI features or agents | AI healthcare applications | LLM applications and healthcare data, AI agents and medical data |
| writing code with AI tools | Anpheros for AI developers | llms.txt, OpenAPI |
| a founder or CTO evaluating infrastructure | Healthcare startups | Security, privacy and data residency, Architecture |
Developer resources
| Resource | Where |
|---|---|
| First calls, step by step | Getting started |
| The whole path to production | Build with Anpheros |
| Every endpoint | API reference (OpenAPI) · openapi.json |
| FHIR R4 | FHIR platform · CapabilityStatement |
| OAuth and consent | Authentication and OAuth · Consent and access model |
| Events | Webhooks |
| Client libraries | SDKs: @anpheros/sdk on npm, anpheros_sdk on pub.dev |
| AI | AI healthcare applications |
| Examples | runnable calls in Build a healthcare app, Medical data API and Webhooks |
| Architecture | Healthcare application architecture |
| Errors, limits, versioning | Errors · Limits · Versioning |
The platform in five facts
- Standard data: 26 HL7 FHIR R4 resource types, coded with LOINC, ICD-10, ATC and UCUM.
- Two APIs, one record:
/fhir/R4and/v1read and write the same resources with the same ids. - Consent by the patient: OAuth 2.1 with PKCE and SMART on FHIR; grants of 30–365 days, revocable.
- Traceability: every write has provenance, every version is kept, every read is visible to the patient.
- Safe development: a self-service sandbox, separate from production, where each project has its own 30 synthetic patients.
Anpheros Platform is in private beta. The sandbox is self-service on the dashboard (sign in with Google); production access is by request.