# What is Anpheros?

> Anpheros is infrastructure for interoperable medical data: a patient-controlled HL7 FHIR R4 record and an API for building healthcare applications, software and AI services on it.

Source: https://developers.anpheros.com/guides/what-is-anpheros

**Anpheros is infrastructure for interoperable medical data and for integrating that data into healthcare applications, software and AI services.** For a patient it is a digital medical record they control; for a developer it is an API over that record, stored as standard HL7 FHIR R4 data.

Anpheros has two parts that share one record per patient:

- **Anpheros Daily** — the patient app (Android, macOS, web) where people and families record symptoms, vital signs, medications, lab results, documents and appointments.
- **Anpheros Platform** — the API and data store behind it. Applications, clinics, laboratories and AI agents read and write the same record through it, and each of them reaches a patient only with that patient's consent.

Anpheros Daily is itself a client of the public API: what the app records is available to other authorised applications in exactly the same form. The platform is in private beta; data is hosted in the European Union.

## The problem it addresses

A healthcare application usually has to solve the same things before it can do anything useful: a data model for medical records, storage, identity, consent, an audit trail, integration with labs and clinics, and a way to hand the right part of a record to an AI model. Most of that work is not specific to the application.

Anpheros provides that layer once, on open standards, so that an application can concentrate on its own experience while the record stays portable between applications and under the patient's control.

## What the platform provides

| Capability | What it is | Where it is documented |
|---|---|---|
| FHIR R4 store | One record per patient made of standard FHIR resources — 26 resource types, search, version history, transactions, `Patient/$everything` | [FHIR platform](https://developers.anpheros.com/guides/fhir) |
| REST API | `/v1`: patients, observations, conditions, medications, documents, timeline, provenance — the same data and ids as the FHIR API | [Getting started](https://developers.anpheros.com/guides/getting-started) |
| Patient consent | OAuth 2.1 with PKCE, SMART on FHIR standalone launch, scopes per resource type and category, revocation that takes effect on the next request | [Authentication and OAuth](https://developers.anpheros.com/guides/authentication), [Consent and access model](https://developers.anpheros.com/guides/consent) |
| Provenance and audit | Every write records who wrote it, for whom and from which system; every read is logged and visible to the patient | [Security, privacy and data residency](https://developers.anpheros.com/guides/security) |
| AI context API | `POST /v1/context` assembles the relevant part of a record for an AI model, within a token budget, with every item labelled by source | [AI agents and medical data](https://developers.anpheros.com/guides/ai-agents-medical-data) |
| International Patient Summary | `Patient/$summary` returns an IPS document, validated with the official HL7 validator | [FHIR platform](https://developers.anpheros.com/guides/fhir) |
| Webhooks | Signed, retried events for writes, consent changes and documents | [Webhooks](https://developers.anpheros.com/guides/webhooks) |
| Lab connector | A whole lab report (CSV, HL7 v2 ORU^R01, JSON) becomes FHIR Observations in one call | [Lab connector](https://developers.anpheros.com/guides/lab-connector) |
| SDKs | Dart / Flutter (`anpheros_sdk` on pub.dev) and TypeScript (`@anpheros/sdk` on npm) | [SDKs](https://developers.anpheros.com/guides/sdks) |
| Sandbox | Self-service; a separate database where each project has its own 30 synthetic patients; `sk_test_` keys cannot reach real data | [Getting started](https://developers.anpheros.com/guides/getting-started) |

## Who it is for

- **Developers and startups** building a healthcare or medical application that needs to store patient data without designing a medical data model, consent system and audit trail from scratch.
- **Clinics and laboratories** that want to deliver results and documents into a patient's record with the patient's consent.
- **Teams building AI assistants and agents** that need a patient's structured medical context, with consent and an audit of what the AI read.
- **Patients and families**, through Anpheros Daily, who want one record they control and can share.

## What Anpheros is not

- It is not a hospital EHR or a practice-management system; it holds the patient's own record and connects applications to it.
- It does not ship integrations with specific AI vendors. The context API returns JSON or text that your code passes to whichever model you use.
- It does not provide a Model Context Protocol (MCP) server today.
- It is not generally available yet: the platform is in private beta, single-zone, without a contractual SLA. Production keys are issued to verified organisations with a signed data processing agreement.

## Frequently asked questions

### Is Anpheros a FHIR server?
Yes, among other things. `/fhir/R4` is a FHIR R4 (4.0.1) interface with a CapabilityStatement at `/fhir/R4/metadata`. It also adds what a plain FHIR server does not: per-project isolation, patient consent, provenance on every write, an audit visible to the patient, a simpler REST API over the same data and an AI context API.

### Can I use Anpheros as the backend of my healthcare app?
That is its purpose. Your app stores and reads patient data through the REST or FHIR API; your patients' records stay portable and can be shared with other applications when the patient consents. Start with [Build a healthcare app](https://developers.anpheros.com/guides/build-a-healthcare-app).

### Can I use Anpheros as the database of my AI healthcare application?
For the patient medical data, yes: Anpheros is a managed healthcare database built on HL7 FHIR R4, with an API, patient consent and an AI context API — a FHIR backend your application calls instead of designing its own medical tables. It is not a general-purpose SQL database and it does not run AI models; your application keeps its own users and non-medical data and calls the model of your choice. See [AI healthcare applications](https://developers.anpheros.com/guides/ai-healthcare).

### Can an AI model read patient data through Anpheros?
Only through your application and only within a patient's consent (or the patients your project created). The context API prepares the data for a model and records what was used. See [AI agents and medical data](https://developers.anpheros.com/guides/ai-agents-medical-data).

### Where is the data stored?
In the European Union. Documents are kept in an EU storage bucket encrypted with a customer-managed key. See [Security, privacy and data residency](https://developers.anpheros.com/guides/security).

### How do I get access?
The sandbox is self-service: sign in with Google on the dashboard (`https://platform.anpheros.com/dashboard/`) and get a key in one click. Production access is by request during the private beta (`contact@anpheros.com`): production keys are issued to verified organisations with a signed data processing agreement.

### Is Anpheros free?
The sandbox is free: each sandbox project gets its own 30 synthetic patients and up to 10 000 writes a day. Production starts at €49 a month for 2,500 patients, with the first month free; production access is for verified organisations with a signed data processing agreement. See [Pricing](https://developers.anpheros.com/guides/pricing).

## Related

- [Medical data infrastructure](https://developers.anpheros.com/guides/medical-data-infrastructure)
- [Anpheros for developers](https://developers.anpheros.com/guides/developers)
- [Healthcare application architecture](https://developers.anpheros.com/guides/architecture)
- [AI healthcare applications](https://developers.anpheros.com/guides/ai-healthcare)