Curana Health website screenshot

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
39.2/100 thin ▬ flat Agent 33/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs 1 MCP Servers
CompanyDigital HealthHealthcareFHIRInteroperabilityMedicare AdvantageSenior LivingPatient AccessValue-Based CareCMS-9115-F

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 39.2/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 10.0 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 3.1 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 33/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 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 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. 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. Want it done for you? Prioritized profiling — $2,500 →

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

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

curana-health-mcp.yml

MCP SERVER

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

MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 WellKnown
WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 DataModel
DataModel

Access & Security 4

Authentication, authorization, and security posture

Compliance
Compliance
 Authentication
Authentication
 OAuthScopes
OAuthScopes
 DomainSecurity
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)

apis.yml Raw ↑ 
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
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.20'
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: MCPServer
    url: mcp/curana-health-mcp.yml
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: MCPServer
  url: mcp/curana-health-mcp.yml
- 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