# Anpheros Platform

> 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 the Anpheros Platform API — the same API Anpheros' own patient app (Anpheros Daily) uses — and each of them reaches a patient only with that patient's consent. Data is hosted in the European Union. The platform is in private beta.

Use it as the medical-data backend and healthcare database of a medical application, as the integration point for clinics and laboratories, or as the consented, audited source of patient context for an AI assistant or agent.

Building an AI healthcare application or an AI agent? Use Anpheros as the medical data layer: patient records live in its HL7 FHIR R4 data store (a managed FHIR backend), your application and its agents reach them through the API within the patient's consent, and POST /v1/context prepares a source-labelled context for any model, hosted or local. Worked examples: https://developers.anpheros.com/guides/ai-healthcare and https://developers.anpheros.com/guides/ai-agents-medical-data. Anpheros does not host AI models and has no official integration with any AI vendor or coding tool; it is the data layer your application or agent calls.

## Medical data infrastructure

- [Medical data infrastructure](https://developers.anpheros.com/guides/medical-data-infrastructure): what it is and where Anpheros fits — the central page
- [What is Anpheros?](https://developers.anpheros.com/guides/what-is-anpheros): definition, capabilities, who it is for, what it is not
- [Patient medical record](https://developers.anpheros.com/guides/patient-medical-record): what the record contains; patient, applications and consent
- [Digital medical record infrastructure](https://developers.anpheros.com/guides/digital-medical-record): the infrastructure under a patient-facing app
- [Security, privacy and data residency](https://developers.anpheros.com/guides/security)

## Healthcare API

- [Healthcare API: what it is and how it works](https://developers.anpheros.com/guides/healthcare-api): definition, how one call works, kinds of healthcare APIs, what to look for, the Anpheros API at a glance, FAQ
- [Healthcare API platform: what it includes and how to choose](https://developers.anpheros.com/guides/healthcare-api-platform): platform layers, build vs cloud FHIR store vs platform, vendor questions answered for Anpheros (EU data, consent, FHIR R4, Inferno, pricing, gaps)
- [EHR API and medical records API](https://developers.anpheros.com/guides/ehr-api): hospital EHR APIs (Epic, Oracle Health) vs a patient-controlled records API; GDPR/EU hosting; HIPAA as a Business Associate (BAA and US region on request)
- [Medical data API](https://developers.anpheros.com/guides/medical-data-api): where each kind of medical data goes, filters, tracing and correcting data
- [Healthcare integrations](https://developers.anpheros.com/guides/healthcare-integrations): labs, clinics, devices, third-party apps, events
- [Integration directory](https://anpheros.com/integrations): every integration with its verified status (available, beta, developer guide), data, FHIR resources, direction, authentication and docs

## FHIR and interoperability

- [FHIR platform: managed FHIR R4 with patient consent](https://developers.anpheros.com/guides/fhir): what a FHIR platform is vs a FHIR server; the 26 resource types; search, history, transactions, $everything, $summary; Inferno SMART standalone launch 22/22
- [FHIR sandbox](https://developers.anpheros.com/guides/fhir-sandbox): free private FHIR R4 test server, 30 synthetic patients with stable persona ids p01–p30, reset, limits, first requests
- [FHIR database schema](https://developers.anpheros.com/guides/fhir-database-schema): JSON + typed search indexes vs normalised vs graph; the Anpheros PostgreSQL schema (fhir_resources, fhir_history, idx_* tables, projections)
- [Medical terminology API](https://developers.anpheros.com/guides/medical-terminology-api): free lookup services for LOINC, ICD-10, SNOMED CT, RxNorm; FHIR system URIs; Anpheros bundles only a small LOINC subset
- [International Patient Summary (IPS) in FHIR](https://developers.anpheros.com/guides/international-patient-summary-fhir): IPS sections and LOINC codes, document Bundle structure, real generated excerpt, Patient/$summary validated with 0 errors
- [How to store medical records using FHIR R4](https://developers.anpheros.com/guides/store-medical-records-fhir): tutorial — Patient, Observation, Condition, transactions, history, provenance
- [FHIR vs. a custom medical database](https://developers.anpheros.com/guides/fhir-vs-custom-database): trade-offs and the usual split
- [How to implement patient consent with SMART on FHIR](https://developers.anpheros.com/guides/smart-on-fhir-backend): tutorial — OAuth 2.1, PKCE, scopes, refresh, revocation
- [Patient consent platform for health apps](https://developers.anpheros.com/guides/patient-consent-platform): consent enforced by the data layer — scopes, purpose, 30/90/180/365-day expiry, access log, revocation, consent webhooks
- [Longitudinal patient data API](https://developers.anpheros.com/guides/longitudinal-patient-data-api): one history from many writers; timeline, $everything, IPS and AI context; provenance and versions
- [Healthcare data interoperability](https://developers.anpheros.com/guides/interoperability): levels of interoperability, IPS, SMART on FHIR, HL7 v2, provenance
- [Wearable data in FHIR](https://developers.anpheros.com/guides/wearable-data-fhir): Apple Health, Health Connect and Samsung Health to FHIR Observations; which devices (Apple Watch, Galaxy Watch, Fitbit, Garmin, Oura, Withings) reach which health store; LOINC/UCUM mapping table; daily summaries
- [Health tracker API](https://developers.anpheros.com/guides/health-tracker-api): steps, heart rate, HRV, sleep, SpO₂ as LOINC-coded Observations; HealthKit and Health Connect have no web API; no direct Fitbit/Garmin cloud connection
- [Wearable APIs: Fitbit, Garmin, Oura and Withings](https://developers.anpheros.com/guides/wearable-apis): access rules as of October 2026 (Google Health API, Garmin business approval, Oura membership for Gen3+, Withings open)
- [Fitbit Web API shutdown](https://developers.anpheros.com/guides/fitbit-web-api-shutdown): support ended 30 Sep 2026, API off 30 Oct 2026; Google Health API vs Health Connect; migration checklist
- [Apple Health (HealthKit) to FHIR](https://developers.anpheros.com/guides/apple-health-fhir), [Health Connect to FHIR](https://developers.anpheros.com/guides/health-connect-fhir), [Samsung Health to FHIR](https://developers.anpheros.com/guides/samsung-health-fhir): platform-specific code and rules
- [FHIR vs HL7 v2](https://developers.anpheros.com/guides/fhir-vs-hl7-v2): v2 messages (ADT, ORU, MLLP) vs FHIR resources; same lab result in both; Anpheros accepts only ORU^R01 lab results, over HTTPS
- [Remote patient monitoring with FHIR](https://developers.anpheros.com/guides/remote-patient-monitoring-fhir): device Observations, signed webhooks, idempotent alert rule; Anpheros has no alerting or billing
- [The European Health Data Space (EHDS) for developers](https://developers.anpheros.com/guides/ehds-for-developers): Regulation (EU) 2025/327 timeline (2029, 2031), EHR system components, wellness app labelling, FHIR exchange format; Anpheros is not a certified EHR system
- [GDPR and health data for developers](https://developers.anpheros.com/guides/gdpr-health-data-developers): Article 9 requirements as engineering tasks, mapped to Anpheros; HIPAA as a Business Associate (BAA on request)
- [Synthetic patient data for testing](https://developers.anpheros.com/guides/synthetic-patient-data): Synthea vs personas; loading Synthea bundles (unsupported types removed, conditional references not resolved)
- [FHIR proof of concept in a free sandbox](https://developers.anpheros.com/guides/fhir-proof-of-concept): what a pilot must show, 30 synthetic patients, first calls, sandbox limits, synthetic data only
- [Lab results API: HL7 v2, FHIR and LOINC](https://developers.anpheros.com/guides/lab-results-api): how lab results travel between labs, clinics, apps and AI, what one result must carry, HL7 v2 OBX to FHIR Observation mapping
- [HL7 v2 to FHIR mapping](https://developers.anpheros.com/guides/hl7-v2-to-fhir-mapping): segment and OBX field mapping for ORU^R01, traps, converter over HTTPS; PID/NTE not used, no DiagnosticReport
- [HL7 v2 and FHIR for clinical dashboards](https://developers.anpheros.com/guides/clinical-dashboard-hl7-fhir): ORU^R01 to FHIR Observations with ranges and flags, webhooks to the dashboard; not bedside or ICU monitoring
- [DICOM vs FHIR](https://developers.anpheros.com/guides/dicom-vs-fhir): images (DICOM, PACS, DICOMweb) versus clinical data (FHIR ImagingStudy, DiagnosticReport); Anpheros stores reports and findings, not DICOM images
- [How to import laboratory results into a FHIR record](https://developers.anpheros.com/guides/import-lab-results-fhir): tutorial with CSV and HL7 v2 ORU^R01, LOINC mapping, provenance
- [Anpheros Symptom Engine: methodology](https://developers.anpheros.com/guides/symptom-engine): free-text symptoms in any language coded to WHO ICD-10 and ICD-11 and a body system, presence and experiencer detection, evaluation (primary code 100 %, presence and subject 98 %, 100 test cases), limits; not a symptom checker
- [Anpheros Search](https://developers.anpheros.com/guides/anpheros-search): 1,174 symptoms, conditions and treatments in 20 languages with their sources (WHO ICD-10/ICD-11, MedlinePlus, EMA and FDA indications quoted unchanged); public GET /v1/search without an API key, FHIR CodeSystems and ConceptMaps, MCP tools search_health_terms and get_health_term; no diagnosis, no treatment recommendation, ATC not served
- [Symptom data API](https://developers.anpheros.com/guides/symptom-data-api): 274 symptom concepts as REST and FHIR CodeSystem, ValueSet and ConceptMaps to ICD-10 and ICD-11; patient-reported symptom Observations and their validation profile
- [How to normalize medical data](https://developers.anpheros.com/guides/normalize-medical-data): codes, units, dates, duplicates, validation
- [Medical data provenance explained](https://developers.anpheros.com/guides/medical-data-provenance): author, organisation, source, versions
- [How to integrate clinic systems with a FHIR backend](https://developers.anpheros.com/guides/integrate-clinic-systems-fhir): tutorial for clinic EMRs

## Healthcare software

- [How to build a personal health record (PHR) app with FHIR](https://developers.anpheros.com/guides/personal-health-record-app): tutorial with the TypeScript SDK — patient-reported data, lab import, documents, timeline, IPS, consent
- [Healthcare software development](https://developers.anpheros.com/guides/healthcare-software): how a healthcare application is layered and what Anpheros provides
- [Anpheros for developers](https://developers.anpheros.com/guides/developers): what you can build and where to start, by role
- [Build with Anpheros](https://developers.anpheros.com/guides/build-with-anpheros): from access to production in nine steps
- [Build a healthcare app](https://developers.anpheros.com/guides/build-a-healthcare-app): tutorial with working API calls
- [How to build a healthcare API with TypeScript](https://developers.anpheros.com/guides/healthcare-api-typescript): tutorial with Express and the TypeScript SDK
- [How to build a healthcare app with Flutter](https://developers.anpheros.com/guides/healthcare-app-flutter): tutorial with OAuth consent and the Dart SDK
- [Medical app backend and database](https://developers.anpheros.com/guides/medical-app-backend): what a medical app backend and its database must handle and what stays yours
- [Healthcare application architecture](https://developers.anpheros.com/guides/architecture): diagrams and data flows
- [Healthcare startups](https://developers.anpheros.com/guides/healthcare-startups)
- [Anpheros for startups](https://anpheros.com/for-startups): free sandbox, runnable starter projects, the path to production and pricing
- [Use cases](https://developers.anpheros.com/guides/use-cases)

## AI healthcare

- [Medication data for healthcare apps and AI agents](https://developers.anpheros.com/guides/medication-data-ai-agents): patient medication lists (MedicationStatement, ATC) vs drug knowledge (RxNorm, openFDA, EMA); Anpheros is not a drug database
- [Virtual care and AI doctors: the patient data they need](https://developers.anpheros.com/guides/virtual-care-ai-data): a video visit as FHIR R4 (Appointment, QuestionnaireResponse, Encounter class VR, CarePlan), what each AI role should see, a tested context call; the context API does not include QuestionnaireResponse answers
- [AI healthcare applications](https://developers.anpheros.com/guides/ai-healthcare): what AI applications need from their data layer — the central AI page
- [How to build an AI healthcare app with a FHIR backend](https://developers.anpheros.com/guides/build-ai-healthcare-app): tutorial in TypeScript with the context API and an LLM
- [How to give an AI agent access to medical records](https://developers.anpheros.com/guides/ai-agent-access-medical-records): tutorial in Python, MCP, read-only tool allowlist, consent
- [AI agents and medical data](https://developers.anpheros.com/guides/ai-agents-medical-data): controlled access, tools, audit and provenance for agents
- [LLM applications and healthcare data](https://developers.anpheros.com/guides/llm-healthcare-data): the context API, cloud and local models, prompting with provenance
- [How to build a medical chatbot with structured data](https://developers.anpheros.com/guides/ai-medical-assistant): tutorial in Python — context per question, red flags, sources, log
- [Anpheros for AI developers](https://developers.anpheros.com/guides/ai-developers): building with Claude Code, Cursor, Copilot, ChatGPT, Gemini, Grok or Ollama

## Developer resources (reference)

- [Getting started](https://developers.anpheros.com/guides/getting-started)
- [Authentication and OAuth](https://developers.anpheros.com/guides/authentication): API keys, OAuth 2.1 + PKCE, SMART on FHIR, OpenID Connect
- [Consent and access model](https://developers.anpheros.com/guides/consent)
- [FHIR code systems](https://developers.anpheros.com/guides/fhir-code-systems): LOINC, ICD-10, ATC, UCUM
- [Webhooks](https://developers.anpheros.com/guides/webhooks)
- [Lab connector](https://developers.anpheros.com/guides/lab-connector): CSV, HL7 v2 ORU^R01, JSON lab reports
- [Errors](https://developers.anpheros.com/guides/errors)
- [Limits and rate limits](https://developers.anpheros.com/guides/limits)
- [Versioning and deprecation](https://developers.anpheros.com/guides/versioning)
- [SDKs](https://developers.anpheros.com/guides/sdks): Dart / Flutter (pub.dev: anpheros_sdk), TypeScript (npm: @anpheros/sdk)
- SDK source code and runnable examples (Apache-2.0): https://github.com/anpheros/anpheros-sdk
- [API reference (OpenAPI, interactive)](https://developers.anpheros.com/docs) · [OpenAPI specification](https://developers.anpheros.com/openapi.json) · [FHIR CapabilityStatement](https://platform.anpheros.com/fhir/R4/metadata)

## Free tools

- [FHIR R4 validator](https://developers.anpheros.com/tools/fhir-validator): paste a FHIR JSON resource (26 types) and get every structural, format and required-value-set error with its element path, plus optional eu-lab and ips-observation profile checks; public endpoint POST https://developers.anpheros.com/tools/fhir-validator/validate returns an OperationOutcome. Does not check terminology, invariants or implementation guides such as US Core.
- [FHIR R4 JSON examples](https://developers.anpheros.com/tools/fhir-examples/): valid Patient, Observation (blood pressure, lab result), DiagnosticReport, Condition, MedicationStatement, AllergyIntolerance, Immunization and Encounter, each with common mistakes and the exact validator errors

## Machine-readable

- Every guide as Markdown: https://developers.anpheros.com/guides/<guide>.md (for example https://developers.anpheros.com/guides/getting-started.md)
- All guides in one file: https://developers.anpheros.com/llms-full.txt

## Key facts

- API base: https://platform.anpheros.com; REST at /v1, FHIR R4 (4.0.1) at /fhir/R4, OAuth at /oauth
- Credentials: API keys (sk_test_ sandbox, sk_live_ production) or OAuth access tokens for one consented patient
- Self-service sandbox: sign in with Google and get a key in one click; each sandbox project has its own copy of 30 synthetic patients (reset any time), in a database separate from production
- Pricing: the sandbox is free (up to 10 000 writes a day per project); production is Starter €99, Growth €299 or Scale €799 a month for 2,500, 10,000 or 50,000 stored patients (prices excl. VAT), and the first month of production is free: https://developers.anpheros.com/guides/pricing
- Every write gets a Provenance (author type patient, practitioner, device, import or ai); every read is logged and visible to the patient
- Context API: POST /v1/context returns the relevant part of a record within a token budget (300–8 000), each item labelled with its source; AI-produced values are kept apart under ai_notes
- Limits: 600 requests per minute per key and per IP; documents up to 25 MiB
- MCP server for AI assistants (Claude, ChatGPT, Claude Code, Cursor, VS Code): https://platform.anpheros.com/mcp, 20 tools; with a free sandbox key on 30 synthetic patients, or through OAuth on one person's record that the person approved (read-only by default; sandbox records during the private beta): https://developers.anpheros.com/guides/mcp
- Not available yet: real records through MCP (after the privacy policy update), SMART EHR launch, general availability (private beta, single zone, no SLA)

## Company

- [Anpheros](https://anpheros.com/): the company, the patient app and the website ([llms.txt](https://anpheros.com/llms.txt))
- [Patient guides](https://anpheros.com/guides/) (ten languages): the digital medical record, what FHIR is, the International Patient Summary, reading lab results, the medication list, Apple Health and Health Connect, medical data in the EU (EHDS), AI and the medical record
- Contact: contact@anpheros.com