Developer documentation

Anpheros is infrastructure for interoperable medical data and for integrating that data into healthcare applications, software and AI services. Each patient has one HL7 FHIR R4 record that they control; applications, clinics, laboratories and AI agents read and write it through a FHIR R4 or REST API, only with the patient's consent and with provenance on every write. Developers use it as the medical data layer — a managed FHIR backend and healthcare database — of healthcare applications and AI services. Anpheros' own patient app uses the same API. The sandbox is free; production starts at €49 a month with the first month free; the platform is in private beta.

Medical data infrastructure

• Medical data infrastructureWhat medical data infrastructure is and where Anpheros fits: a patient-controlled HL7 FHIR R4 record, an API, consent, provenance and audit as shared building blocks for healthcare applications and AI.
• 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.
• Patient medical recordWhat a patient medical record contains, how it differs from EHRs and EMRs, and how patient, data, applications and consent relate in Anpheros — including families, portability and deletion.
• Digital medical record infrastructureThe infrastructure a digital medical record needs — structure, history, documents, isolation, consent, audit, exchange — and why it is kept separate from the patient-facing application.
• Security, privacy and data residencyHow patient data is protected: EU data residency, project isolation, pairwise ids, credentials, consent, provenance, an audit visible to the patient, and the limits of the private beta.

APIs and interoperability

• Free FHIR database and sandboxA free HL7 FHIR R4 database to build against: the Anpheros sandbox with 30 synthetic patients per project, the production API, OAuth and webhooks, no card, EU-hosted — and how it differs from a self-hosted server.
• Healthcare API with patient consentHow access to a record is granted by the patient through OAuth 2.1 scopes and durations, logged and revocable, what it changes in an application's design, and how pairwise ids keep applications apart.
• SMART on FHIR backendWhat Anpheros implements of SMART on FHIR — discovery, standalone launch, PKCE, SMART v2 scopes, OpenID Connect, hosted consent — a launch in five requests, and what is not offered yet.
• How Anpheros compares with other FHIR serversSelf-hosted FHIR servers, cloud FHIR stores, open-source healthcare platforms and Anpheros side by side: who authorises access, consent, provenance, residency, pricing, and when each is the right choice.
• Healthcare APIWhat a healthcare API is, what to look for in one, and the Anpheros API at a glance: FHIR R4, REST v1, OAuth 2.1, patient-side endpoints, idempotent writes, errors, limits and events.
• Medical data APIWhere each kind of medical data goes in the Anpheros API, how it is coded, and how to write, filter, trace, correct and delete it — with working examples.
• FHIR platformHL7 FHIR R4 explained and how Anpheros implements it as a managed FHIR database: 26 resource types, search, history, transactions, $everything, the International Patient Summary and the simpler REST view of the same data.
• Healthcare data interoperabilityThe technical, syntactic, semantic and organisational levels of interoperability, the standards Anpheros uses (FHIR R4, IPS, SMART on FHIR, HL7 v2) and why provenance makes exchanged data trustworthy.
• Healthcare integrationsIntegration patterns supported today: lab reports in one call, clinics writing on behalf of an organisation, devices, consented third-party apps, webhooks and SDKs — and what is not available.

Build healthcare software

• Healthcare software developmentWhat is different about building medical software and how a healthcare application is layered: your product on top, the Anpheros API, the FHIR record and patient consent underneath.
• Anpheros for developersWhat 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.
• Build with AnpherosThe path from access to production in nine steps — authentication, API, medical data, consent, FHIR, webhooks, SDKs and going live — with the guide for each step.
• Build a healthcare appTutorial: use Anpheros as the medical-data backend of a healthcare app — patients, measurements, conditions, medications, documents, labs, consent, webhooks and SDKs.
• Medical app backend and databaseWhat a medical app backend and its database must handle, which parts Anpheros provides as a managed healthcare database, what stays in your backend, three ways to connect, and how to stay in sync with webhooks.
• Healthcare application architectureDiagrams and data flows: patient to application to Anpheros API to the FHIR record and external services, and AI agent to the context API to authorised data.
• Healthcare startupsHow an interoperable medical-data infrastructure spares a startup from building patient records, consent, audit and integrations from scratch, a realistic path to production, and what the startup still owns.
• Use casesWhat 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.

AI and healthcare

• AI healthcare applicationsWhat AI healthcare applications need from their data layer — structured data, relevance, sources, consent, accountability — and how Anpheros provides it without hosting models.
• AI agents and medical dataControlled access for AI agents to patient records: OAuth scopes, the tools an agent needs, audit and provenance of what it reads and writes, and event-driven agents.
• LLM applications and healthcare dataUsing large language models with healthcare data: the context API request and response, cloud and local models, agentic systems, retrieval versus context, and prompting with provenance.
• FHIR MCP server for AI agentsConnect Claude Code, Cursor, VS Code or Claude Desktop to an HL7 FHIR R4 API through MCP: 14 tools for reading records, AI-ready context, writing, lab import and sandbox reset, on 30 synthetic patients, free.
• AI medical assistantThe components of an AI medical assistant — LLM, medical context, patient data, consent, FHIR, safety and audit — a request step by step, and the warnings to build in.
• Anpheros for AI developersBuilding healthcare software with Claude Code, Cursor, GitHub Copilot, ChatGPT, Gemini, Grok or Ollama on top of Anpheros as the medical-data layer: machine-readable docs, SDKs and the sandbox.

Reference

• Getting startedFrom an API key to reading and writing a patient's FHIR R4 record in the sandbox: keys, first calls, writes with provenance, documents, AI context, IPS, consent, webhooks and lab reports.
• Authentication and OAuthAPI keys, OAuth 2.1 with PKCE (SMART on FHIR standalone launch), OpenID Connect id_token, SMART v2 patient scopes, token lifetimes and the consent lifecycle.
• Consent and access modelWho sees what: project isolation, pairwise ids, grants, write ownership, provenance and what the patient sees about every application with access.
• FHIR code systemsWhich code systems each FHIR resource type uses: LOINC for measurements and lab results, ICD-10 for conditions, ATC for medications, UCUM units, and SNOMED CT behind a licence flag.
• WebhooksSigned, retried, thin events for resource writes, consent changes and finalized documents, with signature verification in TypeScript, Dart and Python.
• Lab connectorSend a whole laboratory report as CSV, HL7 v2 ORU^R01 or JSON and get laboratory Observations with LOINC codes and reference ranges.
• ErrorsThe error catalogue: HTTP status, OperationOutcome issue codes and what to do for each.
• Limits and rate limitsRequest rate limits, body and document sizes, search pages, webhook limits and token lifetimes.
• PricingSandbox free; Starter €49, Growth €199 and Scale €799 a month for 2,500, 10,000 and 50,000 stored patients, what counts as a patient, going past a plan and the free first month of production.
• Versioning and deprecationHow the FHIR R4 and REST v1 interfaces, webhook payloads and SDKs change, and how breaking changes are announced.
• SDKsThe Dart / Flutter (anpheros_sdk) and TypeScript (@anpheros/sdk) clients: same shape, idempotent creates, retries, token refresh and the consent flow.

Machine-readable

• API reference (OpenAPI) and the OpenAPI specification
• llms.txt — what Anpheros is and where each topic is documented
• llms-full.txt — every guide as Markdown in one file; each guide is also available at /guides/<guide>.md

For patients

The same standards, explained for the people whose data it is: patient guides on anpheros.com cover the digital medical record, what FHIR is, the International Patient Summary, medical data in the EU (EHDS) and AI and the medical record, in ten languages.