Curana Health

Curana Health is a value-based senior-living healthcare company delivering on-site primary care, behavioral health, palliative care, integrated care management, and chronic-condition management to 250,000+ residents across 2,000+ senior living and skilled-nursing communities in more than 30 states, supported by 1,400+ providers, a national medical group, Accountable Care Organizations (ACOs), and Medicare Advantage Special Needs Plans. In support of the CMS Interoperability and Patient Access final rule (CMS-9115-F) and the ONC 21st Century Cures Act final rule (45 CFR 170.213 / 170.215), Curana Health publishes a standards-based FHIR R4 Interoperability (Patient Access) API at fhir.curanahealth.com that lets Medicare Advantage members authorize third-party apps to access their claims, encounter, and clinical data using OAuth 2.0, alongside a public provider-directory surface.

Curana Health publishes 1 API on the APIs.io network. Tagged areas include Company, Digital Health, Healthcare, FHIR, and Interoperability.

Curana Health’s developer surface includes documentation, API reference, signup flow, authentication, changelog, sandbox, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub

36.1/100 thin ▬ flat Agent 5/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

1 APIs

Company Digital Health Healthcare FHIR Interoperability Medicare Advantage Senior Living Patient Access Value-Based Care CMS-9115-F

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 36.1/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 5.4 / 17

Operational Transparency 2.6 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 10.7 / 15

Agent readiness — 5/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/curana-health: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Curana Health Interoperability API

Standards-based FHIR R4 (4.0.1) Patient Access API published for CMS-9115-F / ONC 21st Century Cures Act compliance. Lets Medicare Advantage members authorize third-party applic...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Curana Health Authentication

oauth2 · 1 scheme

SECURITY

Curana Health Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Curana Health Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Conformance

ErrorCatalog

Lifecycle

DataModel

Access & Security 4

Authentication, authorization, and security posture

Compliance

Authentication

OAuthScopes

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Deprecation

Deprecation

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: curana-health
name: Curana Health
description: Curana Health is a value-based senior-living healthcare company delivering on-site primary care, behavioral health,
  palliative care, integrated care management, and chronic-condition management to 250,000+ residents across 2,000+ senior
  living and skilled-nursing communities in more than 30 states, supported by 1,400+ providers, a national medical group,
  Accountable Care Organizations (ACOs), and Medicare Advantage Special Needs Plans. In support of the CMS Interoperability
  and Patient Access final rule (CMS-9115-F) and the ONC 21st Century Cures Act final rule (45 CFR 170.213 / 170.215), Curana
  Health publishes a standards-based FHIR R4 Interoperability (Patient Access) API at fhir.curanahealth.com that lets Medicare
  Advantage members authorize third-party apps to access their claims, encounter, and clinical data using OAuth 2.0, alongside
  a public provider-directory surface.
url: https://raw.githubusercontent.com/api-evangelist/curana-health/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- nea
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://curanahealth.com/wp-content/uploads/2025/04/Curana-Health-Logo-Full-Color-1000px-300x84.webp
tags:
- Company
- Digital Health
- Healthcare
- FHIR
- Interoperability
- Medicare Advantage
- Senior Living
- Patient Access
- Value-Based Care
- CMS-9115-F
apis:
- name: Curana Health Interoperability API
  description: Standards-based FHIR R4 (4.0.1) Patient Access API published for CMS-9115-F / ONC 21st Century Cures Act compliance.
    Lets Medicare Advantage members authorize third-party applications via OAuth 2.0 to read their claims, encounter, and
    clinical data (CARIN Blue Button ExplanationOfBenefit, US Core clinical resources) and exposes a public provider-directory
    / plan surface. Read-only GET access over /v1/api with offset/limit pagination; responses are FHIR Bundles.
  humanURL: https://curanahealth.com/interoperability-api/
  baseURL: https://fhir.curanahealth.com/v1/api
  tags:
  - FHIR
  - Patient Access
  - Medicare Advantage
  - Interoperability
  properties:
  - type: Documentation
    url: https://curanahealth.com/interoperability-api/
  - type: APIReference
    url: https://curanahealth.com/wp-content/uploads/2026/04/3rd_PARTY_CMS_APIS_v2.2.pdf
  - type: Authentication
    url: authentication/curana-health-authentication.yml
  - type: OAuthScopes
    url: scopes/curana-health-scopes.yml
  - type: Conventions
    url: conventions/curana-health-conventions.yml
  - type: Conformance
    url: conformance/curana-health-conformance.yml
  - type: ErrorCatalog
    url: errors/curana-health-problem-types.yml
  - type: DataModel
    url: data-model/curana-health-data-model.yml
  - type: X-MCPServerCandidate
    url: mcp/curana-health-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://curanahealth.com
- type: DeveloperPortal
  url: https://curanahealth.com/interoperability-api/
- type: Documentation
  url: https://curanahealth.com/interoperability-api/
- type: APIReference
  url: https://curanahealth.com/wp-content/uploads/2026/04/3rd_PARTY_CMS_APIS_v2.2.pdf
- type: SignUp
  url: https://curanahealth.com/patient-api-access-form/
- type: TermsOfService
  url: https://curanahealtstg.wpenginepowered.com/wp-content/uploads/CuranaCMSAPI-Terms-of-Service-Clean-and-Final.pdf
- type: PrivacyPolicy
  url: https://curanahealth.com/privacy-policy/
- type: Compliance
  url: https://curanahealth.com/interoperability-api/
- type: Authentication
  url: authentication/curana-health-authentication.yml
- type: OAuthScopes
  url: scopes/curana-health-scopes.yml
- type: Conventions
  url: conventions/curana-health-conventions.yml
- type: Conformance
  url: conformance/curana-health-conformance.yml
- type: ErrorCatalog
  url: errors/curana-health-problem-types.yml
- type: Lifecycle
  url: lifecycle/curana-health-lifecycle.yml
- type: Deprecation
  url: https://curanahealth.com/wp-content/uploads/2025/11/CuranaCMSAPI-Release-Policy-Clean-and-Final.pdf
- type: ChangeLog
  url: changelog/curana-health-changelog.yml
- type: Sandbox
  url: sandbox/curana-health-sandbox.yml
- type: DataModel
  url: data-model/curana-health-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/curana-health-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/curana-health-llms.txt
- type: WellKnown
  url: well-known/curana-health-well-known.yml
- type: DomainSecurity
  url: security/curana-health-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/curana-health"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/curana-health/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/curana-health/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.