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 €99 a month with the first month free; the platform is in private beta.

Healthcare API

• Healthcare API development: what it is and how to build oneWhat a healthcare API is, how one call works, what to look for, and a free FHIR R4 healthcare API with patient consent, provenance and EU hosting — with examples and FAQ.
• 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.
• 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.
• Trust at Anpheros Platform: what we have, what we don't, what's nextWhat protects health data on Anpheros Platform today (EU hosting, DPA, encryption, consent, audit), what is missing (no own SOC 2 or ISO 27001 yet, no external penetration test) and what comes next.
• Patient consent platform for health appsConsent built into the data layer: OAuth 2.1 and SMART scopes, purpose and expiry chosen by the person, an access log they can see, revocation on the next request, and what your app still owns.
• Healthcare API platform: what it includes and how to chooseThe layers of a healthcare API platform, build vs cloud FHIR store vs platform, and questions to ask any vendor — answered for Anpheros: consent, EU data, FHIR R4, pricing.
• EHR API and medical records APIHow apps read and write health records over FHIR: hospital EHR APIs vs a patient-controlled records API, what each covers, GDPR and EU hosting, and HIPAA (BAA and US region on request).
• 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.
• APIs for retrieving patient medical records in 2026Three ways to get patient records: health information networks (TEFCA, Carequality, CommonWell), patient-access APIs (SMART on FHIR, CMS Patient Access) and patient-controlled records, compared, with how to choose.

FHIR R4

• FHIR platform: managed FHIR R4 with patient consentA managed FHIR R4 platform: 30 resource types, search, history, transactions, $everything, IPS, Inferno-tested SMART launch, consent and provenance, plus a simple REST API. Free sandbox.
• 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.
• Free FHIR server: a free FHIR R4 sandbox and databaseA 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.
• How to implement patient consent with SMART on FHIRTutorial: SMART on FHIR with OAuth 2.1 and PKCE step by step — discovery, app registration, consent screen, token exchange, scopes enforced, refresh rotation and revocation — and what Anpheros implements.
• Which FHIR server is best for a production healthcare app?Self-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.
• FHIR sandbox: a private FHIR R4 test serverA free FHIR R4 sandbox with 30 synthetic patients: base URL, authentication, stable persona ids, reset, limits and first requests — and how it differs from a public test server.
• Medical terminology API: LOINC, SNOMED, ICD-10, RxNormWhere to look up each medical code system for free, how codes appear in FHIR, and what Anpheros includes (a small LOINC subset and a catalog of symptoms, conditions and treatments) — honestly scoped.
• International Patient Summary (IPS) in FHIRThe IPS sections and LOINC codes, how the FHIR document Bundle is built, a real excerpt generated by the platform, and one call to produce a validated IPS.
• How to store medical records using FHIR R4Tutorial: create a Patient, a blood-pressure Observation and a Condition, use a transaction, search, update with history and read provenance — every request with curl and the real response, on the free sandbox.
• Longitudinal patient data APIOne patient's history over time from clinics, labs, apps and devices: what a longitudinal record needs, and four ways to read it — timeline, $everything, IPS and AI context.
• Anpheros Symptom Engine: methodologyHow free-text symptoms in any language become WHO ICD-10 and ICD-11 concepts: the AI normalizer, presence and experiencer detection, the WHO-checked vocabulary, evaluation results, similar-case matching and limits.
• Symptom data API: FHIR terminology and patient symptomsStable symptom identifiers mapped to ICD-10, served as REST and as FHIR CodeSystem, ValueSet and ConceptMap; how a patient-reported symptom Observation looks and how to validate one.
• Anpheros Search: symptoms, conditions and treatmentsOne public catalog of 1,174 symptoms, conditions and treatments in 20 languages, each entry with its source: WHO ICD-10 and ICD-11, MedlinePlus summaries, EMA and FDA indications quoted unchanged; REST, FHIR, MCP and one JSON file.
• FHIR vs. a custom medical databaseYour own tables or HL7 FHIR R4 for medical data: the same reading stored both ways, the trade-offs side by side, when each is right, and the usual split between your database and the FHIR record.
• FHIR database schemaHow to store FHIR resources: normalised tables vs JSON with search indexes vs graph, the PostgreSQL schema Anpheros runs (resources, history, typed indexes, projections) and the rules that matter.
• DICOM vs FHIR: imaging data and clinical dataDICOM carries medical images, FHIR the clinical data around them: what each covers, how ImagingStudy and DiagnosticReport connect, and what to store where.
• FHIR vs HL7 v2: practical differencesHL7 v2 messages and FHIR resources compared for developers: format, transport, the same lab result in both, translation pitfalls, and where Anpheros accepts v2.

AI in 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.
• How to build an AI healthcare app with a FHIR backendTutorial in TypeScript: read a patient's FHIR R4 record, get a budgeted, source-labelled context, send it to an LLM and answer with sources — on the free sandbox, then on a real record with OAuth consent.
• Connect ChatGPT and Claude to health data with MCPHow ChatGPT and Claude connect to health data through MCP connectors with OAuth and patient consent: Claude reads with permission, ChatGPT is write-only on real records, and what app developers need to build or not.
• How to give an AI agent access to medical recordsTutorial in Python: an AI agent that reads FHIR R4 records through the Anpheros MCP server with read-only access and a tool allowlist, tests for prompt injection, and reaches real records only with patient consent.
• Virtual care and AI doctors: the data they needA virtual visit as FHIR R4 data — booking, intake, home readings, the visit, follow-up — and how an AI assistant gets a consented, source-labelled view. Tested flow.
• Structured medication data for apps and AI agentsPatient medication lists vs drug knowledge: FHIR resources, RxNorm, ATC, openFDA and EMA sources, and a tested join of a FHIR record with RxNorm and FDA labels.
• 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: 20 tools for reading records, AI-ready context, writing, lab import and sandbox reset, on 30 synthetic patients, free.
• Health patterns for AI agents (beta)What changed in a patient's record and what recurs, computed by fixed statistical rules: trends, deviations from the person's usual level and symptom recurrence, each with its period, evidence and limitations; not diagnoses.
• How to build a medical chatbot with structured dataTutorial in Python: a multi-turn medical chatbot that answers from a person's coded FHIR R4 record with a fresh, source-labelled context per question, stops on red flags, shows sources and logs what the model saw.
• 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.

Medical data integration

• 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.
• Lab results API: HL7 v2, FHIR and LOINCHow lab results travel as HL7 v2 and FHIR R4 data, what one result must carry, and how to receive lab reports into a FHIR record, with a real example.
• HL7 v2 to FHIR mappingSegment-to-resource and OBX field-by-field mapping from HL7 v2 ORU^R01 to FHIR R4, the traps that break integrations, and a converter you call over HTTPS.
• HL7 v2 and FHIR for clinical dashboardsFrom an HL7 v2 ORU^R01 lab message to a dashboard tile: FHIR Observations with ranges and flags, signed webhooks, no duplicates — and why this is not bedside monitoring.
• How to import laboratory results into a FHIR recordTutorial: import a lab report as CSV and as HL7 v2 ORU^R01 into FHIR R4 Observations with LOINC codes and reference ranges, handle unmapped markers and resent reports, and trace each result to its laboratory.
• Health data normalization: how to normalize medical dataTutorial: turn medical data from many sources into one comparable form — LOINC lookup, UCUM units, ISO dates, reference ranges, no duplicates on retry, and validation against the European lab profile.
• Medical data provenance explainedWhat provenance records on every write to a FHIR R4 record — author type, person, organisation, source system, versions — how to set it with headers, how to read it, and how it labels data given to AI models.
• How to integrate clinic systems with a FHIR backendTutorial: connect a clinic EMR to patients' FHIR R4 records — directory of doctors, matching by record number, a visit as one transaction with the doctor as author, lab reports, other providers' data and webhooks.
• A patient data platform for clinics and hospitalsWhat a clinic, hospital or laboratory gets from Anpheros Platform: patient-approved access to a standard FHIR R4 record, results written back, an audit the patient can read, EU hosting, and how to start with the sandbox.
• ICD-10 to ICD-11 conversion API (WHO mapping tables)Translate ICD-10 codes to ICD-11 with the official WHO mapping tables: REST and FHIR ConceptMap/$translate, ICD-11 titles in the WHO translations, one-to-many maps marked for clinical choice, CSV and Excel conversion in a free account.
• Clinic access requests with patient approval (CIBA)The OpenID CIBA flow behind clinic access requests: reception enters the patient's email, the patient approves in the app or by email for 30, 90 or 365 days, and the clinic's application receives tokens.
• International patient data exchange through the patientHow hospitals in different countries can share a patient's record through the patient: a portable FHIR R4 record, an International Patient Summary, consent per clinic, and what it does not replace.
• Wearable data in FHIR (Apple Health, Health Connect)Get smartwatch, ring and scale data into a FHIR record: which devices reach which health store, a LOINC mapping table, daily summaries and a tested upsert.
• Health tracker APIStore steps, heart rate, HRV, sleep and SpO₂ from any wearable as LOINC-coded FHIR Observations: which devices reach which health store, why there is no web API, and working requests.
• Wearable APIs compared: Oura, Garmin, WHOOP, Fitbit and 15 moreTwenty wearable and CGM brands compared as of November 2026 — public API or not, who gets access, Apple Health and Health Connect sync — with a guide per brand and one FHIR format for every device.
• Oura API to FHIR: Oura sleep, HRV and heart rate in your appRead sleep, HRV, heart rate, SpO₂ and steps from the Oura API v2 and store them as LOINC-coded FHIR R4 Observations, with curl, Python and JavaScript; access, OAuth, endpoints and limits.
• Garmin API to FHIR: heart rate, sleep and steps (with code)Read Garmin Health API or Personal API data and store heart rate, sleep and steps as FHIR R4 Observations, with access tiers, auth and LOINC mapping.
• WHOOP API to FHIR: sleep, recovery and HRV (with code)Read WHOOP API v2 sleep and recovery and store them as FHIR R4 Observations: OAuth scopes, rate limits, RMSSD handling and Apple Health limits.
• Withings API to FHIR: heart rate, SpO₂, sleep and weight (with code)Read the Withings Public API and store measures, sleep and activity as FHIR R4 Observations, with OAuth, the 120/min limit and LOINC mapping.
• Polar AccessLink API to FHIR: sleep, heart rate and steps (with code)Read Polar AccessLink v3 sleep, heart rate and steps and store them as FHIR R4 Observations, with user registration, rate limits and phone sync.
• Google Health API to FHIR: Fitbit and Pixel Watch data in your appRead Fitbit and Pixel Watch data with the Google Health API, the Fitbit Web API successor, and store it as FHIR R4 Observations, with curl, Python and JS code.
• Huawei Health Kit API to FHIR: Huawei Health data in your appHuawei Health Kit REST API: approval, 100-user cap, OAuth, endpoints and data types, and how to store steps, sleep and heart data as FHIR R4.
• Xiaomi Mi Band API: get Mi Band data into FHIR (no public cloud API)Xiaomi has no public cloud API: read Mi Band data from Health Connect or Apple Health via Mi Fitness and store it as FHIR R4 Observations, with code.
• Amazfit and Zepp API: get Amazfit watch data into FHIRZepp has no public cloud API: read Amazfit data with Zepp OS Mini Programs or Apple Health and store it as FHIR R4 Observations, with code.
• COROS API to FHIR: sleep, heart rate and steps (with code)Get COROS data via the Partner API or the self-service COROS MCP and store sleep, heart rate and steps as FHIR R4 Observations.
• Suunto API to FHIR: sleep, heart rate and steps (with code)Read the Suunto Cloud API (API Zone, subscription key) and store sleep, heart rate and steps as FHIR R4 Observations, with limits and webhooks.
• Ultrahuman API to FHIR: get Ultrahuman Ring data into your appUltrahuman OAuth API, personal tokens and MCP: read Ring AIR heart rate, HRV, sleep and steps and store them as FHIR R4 Observations, with code.
• Eight Sleep API: get Eight Sleep data into FHIR without a public APIEight Sleep has no public API: read its sleep and heart data from Apple Health or Health Connect and store it as FHIR R4 Observations, with code.
• Dexcom API to FHIR: get CGM glucose readings into your app (with code)Read CGM glucose from the Dexcom API v3 and store each reading as a FHIR Observation: access tiers, OAuth, endpoints, limits and the US partner pause.
• FreeStyle Libre API: get Libre glucose data into FHIR (no public API)Abbott has no public FreeStyle Libre or LibreView API: what exists (partnerships, Lingo sync to phone stores) and how to store glucose readings in FHIR.
• Amazon Halo API alternative: where Halo users and developers go nowAmazon Halo shut down in 2023 and never had a public API: what happened, and where activity, sleep and body data come from now, stored in FHIR.
• Fitbit Web API shutdown: what to use instead (Google Health API, Health Connect)Google turns the Fitbit Web API off on 30 October 2026: the dates, the Google Health API and Health Connect paths, and a migration checklist.
• CMS Patient Access API and FHIRWhat the CMS Patient Access API requires from US health plans, the FHIR profiles it uses (CARIN Blue Button, US Core), how an app registers and authorizes, and where the data can live with consent.
• Cures Act and information blocking for health appsWhat the 21st Century Cures Act and ONC's information blocking rule mean for a health app: certified FHIR APIs, USCDI, who the rules cover and what you still have to do.
• SMART on FHIR with Epic and Oracle HealthA generic guide to reading patient data from Epic and Oracle Health with SMART App Launch: registration, discovery, EHR and standalone launch, PKCE, scopes and the differences you meet.
• TEFCA and QHINs for developersHow TEFCA and Qualified Health Information Networks work, the exchange purposes including individual access, what joining means for an app, and how FHIR is phased in.
• HIPAA for health app backendsWhen HIPAA applies to a health app backend, what the Security Rule asks (risk analysis, access control, audit logs, BAAs, breach notification) and what Anpheros does and does not claim.
• Blue Button 2.0 and the Medicare APICMS Blue Button 2.0: the Medicare claims it returns as FHIR R4, the sandbox, OAuth authorization, production review, and how to turn claims into a useful patient history.
• Apple HealthKit to FHIR: Apple Watch data in your app (with code)Read Apple Watch and Apple Health data with HealthKit in Swift, per local day, and write it to a FHIR R4 record: permissions, background sync, Apple's rules.
• Health Connect API to FHIR: Android, Fitbit, Garmin and Oura data (with code)Read Android Health Connect data from Fitbit, Garmin, Oura, Withings and Wear OS in Flutter and write it to a FHIR R4 record: permissions, history, Play review.
• Samsung Health API to FHIR: Galaxy Watch data in your app (with code)Galaxy Watch data through Health Connect or the Samsung Health Data SDK: a real comparison, partner approval, developer mode and the FHIR mapping.
• Remote patient monitoring with FHIRFrom home blood pressure readings to alerts: device Observations, signed webhooks, an idempotent rule, and what stays outside the data layer. Tested code.
• EHDS for developers: European Health Data Space (2029, 2031)Regulation (EU) 2025/327 for software teams: the 2029 and 2031 dates, EHR system components, wellness app labelling, the FHIR exchange format and what to build now.
• GDPR and health data for developersArticle 9 health data as engineering tasks: legal basis, DPA, EU residency, security, access and erasure, DPIA — mapped to what Anpheros covers. HIPAA: BAA on request. Not legal advice.

Healthcare app development

• Medical app backend: database, data residency and audit logsWhat 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 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.
• 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.
• TypeScript tutorial: build a healthcare API step by stepTutorial: an Express API in TypeScript that creates patient records, stores blood-pressure readings as FHIR R4 observations, reads them back, maps errors and verifies webhooks — without a medical database of your own.
• Personal health record (PHR) app with FHIRTutorial: the backend of a connected PHR on FHIR R4 — data from people, labs, documents and devices, a timeline, an IPS to share, consent. Tested code.
• Synthetic patient data for testingSynthea, personas and model-generated data compared, what good test data contains, and what happened when we loaded Synthea patients into a FHIR server.
• FHIR proof of concept for pharma: free sandboxRun a FHIR R4 proof of concept for a pharma or clinical pilot the same afternoon: what to demonstrate, a free sandbox with 30 synthetic patients, the first calls, limits and the rules that apply.
• How to build a healthcare app with FlutterTutorial: a Flutter app that connects to a person's FHIR R4 record with OAuth consent and PKCE, stores tokens securely, reads and adds blood-pressure readings with the Dart SDK, and handles revoked access.
• 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.

Reference

• Evaluating a medical data platform: questions for hospitalsThe questions a hospital should ask a medical data platform vendor, answered for Anpheros from its security documentation: residency, isolation, audit, agreements, certifications and what is not in place yet.
• Your first API call in 2 minutesOne path from nothing to a real API answer: sign in, create a free sandbox with 30 synthetic patients, copy the key and make one call in curl, Python, JavaScript or Dart, with the expected result and the usual errors.
• Your first write: an Observation and a ConditionStep 2 of the developer path: write a LOINC-coded Observation and an ICD-10 Condition to a sandbox patient with an author and an Idempotency-Key, in curl, Python and JavaScript, then check the timeline, FHIR and provenance.
• Create an OAuth app and the consent screenStep 3: register an OAuth application, send the person to the consent screen with PKCE and SMART v2 scopes, exchange the code for a 30-minute token, refresh and revoke, with copyable JavaScript and Python.
• Receive your first webhookStep 4: register a webhook endpoint, verify the Anpheros-Signature HMAC in Node and Python, send a test ping, and handle retries, the delivery log and redelivery.
• Patient summary (IPS) and SMART Health LinksRead a patient's International Patient Summary with $summary, and open a SMART Health Link a person shares with your clinic: decode shlink:/, POST the manifest with a passcode and decrypt the JWE in Python.
• Build your integration with Claude Code or CursorLet an AI coding tool write your Anpheros integration: the sandbox over MCP, a project rules file for medical data and a ready prompt to copy, for Claude Code, Cursor, VS Code or any assistant.
• 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.
• Single sign-on for your teamSign in to the console through your company's SAML 2.0 or OpenID Connect provider (Okta, Entra ID, Google Workspace, Keycloak), optionally required for every member of your organisation.
• 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.
• Troubleshooting API errorsThe errors you meet while building, with the exact message and a fix for each: 401 missing or invalid key, 403 scope or ownership, 404, 422 references and idempotency, 429 rate limits.
• Limits and rate limitsRequest rate limits, body and document sizes, search pages, webhook limits and token lifetimes.
• PricingSandbox free; Starter €99, Growth €299 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.
• Go live: from sandbox to productionWhat changes when real patients use your app: a checklist for your code, organization verification and the DPA, the plans, switching to a production key and what to watch after launch.
• Versioning and deprecationHow the FHIR R4 and REST v1 interfaces, webhook payloads and SDKs change, and how breaking changes are announced.
• Reliability, status and incidentsWhere Anpheros runs, what is monitored, daily backups and point-in-time recovery, how incidents are communicated, data export and deletion, and what is not in place yet (no SLA, no public status page).
• SDKsThe Dart / Flutter (anpheros_sdk) and TypeScript (@anpheros/sdk) clients: same shape, idempotent creates, retries, token refresh and the consent flow.

Free tools

• FHIR R4 validatorPaste a FHIR JSON resource and see every structural and value-set error with its path. No account.
• FHIR R4 JSON examplesValid Patient, Observation, Condition, MedicationStatement and other resources, next to the mistakes that break them.

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.