# 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.

Source: https://developers.anpheros.com/guides/developers

**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](https://developers.anpheros.com/guides/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](https://developers.anpheros.com/guides/build-a-healthcare-app) | [SDKs](https://developers.anpheros.com/guides/sdks), [Authentication and OAuth](https://developers.anpheros.com/guides/authentication) |
| a backend developer | [Medical app backend and database](https://developers.anpheros.com/guides/medical-app-backend) | [Medical data API](https://developers.anpheros.com/guides/medical-data-api), [Webhooks](https://developers.anpheros.com/guides/webhooks) |
| an integration engineer at a clinic or lab | [Healthcare integrations](https://developers.anpheros.com/guides/healthcare-integrations) | [Lab connector](https://developers.anpheros.com/guides/lab-connector), [Healthcare data interoperability](https://developers.anpheros.com/guides/interoperability) |
| a FHIR developer | [FHIR platform](https://developers.anpheros.com/guides/fhir) | [FHIR code systems](https://developers.anpheros.com/guides/fhir-code-systems), [API reference](https://developers.anpheros.com/docs) |
| building AI features or agents | [AI healthcare applications](https://developers.anpheros.com/guides/ai-healthcare) | [LLM applications and healthcare data](https://developers.anpheros.com/guides/llm-healthcare-data), [AI agents and medical data](https://developers.anpheros.com/guides/ai-agents-medical-data) |
| writing code with AI tools | [Anpheros for AI developers](https://developers.anpheros.com/guides/ai-developers) | [llms.txt](https://developers.anpheros.com/llms.txt), [OpenAPI](https://developers.anpheros.com/openapi.json) |
| a founder or CTO evaluating infrastructure | [Healthcare startups](https://developers.anpheros.com/guides/healthcare-startups) | [Security, privacy and data residency](https://developers.anpheros.com/guides/security), [Architecture](https://developers.anpheros.com/guides/architecture) |

## Developer resources

| Resource | Where |
|---|---|
| First calls, step by step | [Getting started](https://developers.anpheros.com/guides/getting-started) |
| The whole path to production | [Build with Anpheros](https://developers.anpheros.com/guides/build-with-anpheros) |
| Every endpoint | [API reference (OpenAPI)](https://developers.anpheros.com/docs) · [openapi.json](https://developers.anpheros.com/openapi.json) |
| FHIR R4 | [FHIR platform](https://developers.anpheros.com/guides/fhir) · [CapabilityStatement](https://platform.anpheros.com/fhir/R4/metadata) |
| OAuth and consent | [Authentication and OAuth](https://developers.anpheros.com/guides/authentication) · [Consent and access model](https://developers.anpheros.com/guides/consent) |
| Events | [Webhooks](https://developers.anpheros.com/guides/webhooks) |
| Client libraries | [SDKs](https://developers.anpheros.com/guides/sdks): `@anpheros/sdk` on npm, `anpheros_sdk` on pub.dev |
| AI | [AI healthcare applications](https://developers.anpheros.com/guides/ai-healthcare) |
| Examples | runnable calls in [Build a healthcare app](https://developers.anpheros.com/guides/build-a-healthcare-app), [Medical data API](https://developers.anpheros.com/guides/medical-data-api) and [Webhooks](https://developers.anpheros.com/guides/webhooks) |
| Architecture | [Healthcare application architecture](https://developers.anpheros.com/guides/architecture) |
| Errors, limits, versioning | [Errors](https://developers.anpheros.com/guides/errors) · [Limits](https://developers.anpheros.com/guides/limits) · [Versioning](https://developers.anpheros.com/guides/versioning) |

## The platform in five facts

1. **Standard data:** 26 HL7 FHIR R4 resource types, coded with LOINC, ICD-10, ATC and UCUM.
2. **Two APIs, one record:** `/fhir/R4` and `/v1` read and write the same resources with the same ids.
3. **Consent by the patient:** OAuth 2.1 with PKCE and SMART on FHIR; grants of 30–365 days, revocable.
4. **Traceability:** every write has provenance, every version is kept, every read is visible to the patient.
5. **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](https://platform.anpheros.com/dashboard/) (sign in with Google); production access is by request.

## Related

- [What is Anpheros?](https://developers.anpheros.com/guides/what-is-anpheros)
- [Medical data infrastructure](https://developers.anpheros.com/guides/medical-data-infrastructure)
- [Build with Anpheros](https://developers.anpheros.com/guides/build-with-anpheros)