Carefluence is a US health-IT interoperability vendor whose product is an ONC-certified, FHIR-based Open API platform that EHR, telehealth, remote patient monitoring, HIE and health-analytics vendors license to reach regulatory compliance and to exchange clinical data with other systems. The Carefluence Open API R4 was certified on 2022-06-29 under CHPL ID 15.04.04.2657.Care.R4.01.0.220629 against ONC criteria 170.315 (d)(1,3,9-10,12-13) and (g)(4-7,9-10), including the § 170.315(g)(10) Standardized API for Patient and Population Services; the company states it was the first FHIR-based Open API product to earn ONC 2015 Edition certification, in July 2016, and was an early participant in the Argonaut Project. The platform is a FHIR R4 server (US Core IG v3.1.1, 24 resource types) fronted by a first-party SMART on FHIR OAuth 2.0 / OpenID Connect authorization server, with a data translator for HL7 v2 and C-CDA normalization, adapters for non-FHIR back ends, a built-in integration engine, an asynchronous FHIRops product, and an announced Model Context Protocol server for AI agents.
Carefluence is listed with 2 APIs on the APIs.io network, including Open API R4, and 1 more. Tagged areas include Company, Healthcare, Interoperability, FHIR, and HL7.
Carefluence’s developer surface includes documentation, API reference, support, engineering blog, pricing, signup flow, authentication, and 27 more developer resources.
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/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/carefluence/"><img src="https://apis.io/badge/carefluence/card.svg" alt="Carefluence on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
The ONC-certified § 170.315(g)(10) Standardized API for Patient and Population Services. A HL7 FHIR R4 (4.0.1) RESTful server conforming to the US Core Implementation Guide v3.1...
The first-party OpenID Connect / OAuth 2.0 authorization server that issues every token the Carefluence Open API R4 accepts, and the administration portal where developers regis...
aid: carefluence
name: Carefluence
description: Carefluence is a US health-IT interoperability vendor whose product is an ONC-certified, FHIR-based Open API
platform that EHR, telehealth, remote patient monitoring, HIE and health-analytics vendors license to reach regulatory compliance
and to exchange clinical data with other systems. The Carefluence Open API R4 was certified on 2022-06-29 under CHPL ID
15.04.04.2657.Care.R4.01.0.220629 against ONC criteria 170.315 (d)(1,3,9-10,12-13) and (g)(4-7,9-10), including the § 170.315(g)(10)
Standardized API for Patient and Population Services; the company states it was the first FHIR-based Open API product to
earn ONC 2015 Edition certification, in July 2016, and was an early participant in the Argonaut Project. The platform is
a FHIR R4 server (US Core IG v3.1.1, 24 resource types) fronted by a first-party SMART on FHIR OAuth 2.0 / OpenID Connect
authorization server, with a data translator for HL7 v2 and C-CDA normalization, adapters for non-FHIR back ends, a built-in
integration engine, an asynchronous FHIRops product, and an announced Model Context Protocol server for AI agents.
accessModel:
pricing: enterprise
onboarding: unknown
trial: false
try_now: false
public: false
label: Enterprise
confidence: medium
source:
- authentication
- scopes
- rate-limits
- security
- sandbox
generated: '2026-11-06'
method: derived
image: https://carefluence.com/wp-content/uploads/2018/04/Logo-WHT-nds1740.png
url: https://raw.githubusercontent.com/api-evangelist/carefluence/refs/heads/main/apis.yml
x-type: company
x-source: harvest:openehr-coalition
specificationVersion: '0.20'
created: '2026-09-02'
modified: '2026-09-02'
x-docs-platform: postman
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-09-21
tags:
- Company
- Healthcare
- Interoperability
- FHIR
- HL7
- SMART on FHIR
- Electronic Health Records
- Clinical Data
- Health IT
- ONC Certified
- USCDI
- OAuth
- Telehealth
- Health Information Exchange
- Authentication
tags_raw:
- Company
- Healthcare
- Interoperability
- FHIR
- HL7
- SMART on FHIR
- Electronic Health Records
- Clinical Data
- Health IT
- ONC Certified
- USCDI
- OAuth 2.0
- Telehealth
- Health Information Exchange
- Authentication
apis:
- aid: carefluence:openapi-r4
name: Carefluence Open API R4
description: The ONC-certified § 170.315(g)(10) Standardized API for Patient and Population Services. A HL7 FHIR R4 (4.0.1)
RESTful server conforming to the US Core Implementation Guide v3.1.1, exposing 24 resource types — Patient, Encounter,
Condition, AllergyIntolerance, MedicationRequest, Medication, MedicationStatement, Immunization, Procedure, Observation,
DiagnosticReport, DocumentReference, CarePlan, CareTeam, Goal, Device, Provenance, Practitioner, Organization, Location,
ServiceRequest, AuditEvent, Person and Group — in JSON or XML, secured with SMART on FHIR OAuth 2.0 bearer tokens. Group
declares the FHIR Bulk Data group-export operation.
image: https://carefluence.com/wp-content/uploads/2018/04/Logo-WHT-nds1740.png
humanURL: https://api.carefluence.com/
baseURL: https://classic.carefluence.com/r4/
tags:
- FHIR
- US Core
- USCDI
- SMART on FHIR
- Clinical Data
- Interoperability
- ONC Certified
properties:
- type: Documentation
url: https://api.carefluence.com/
- type: APIReference
url: https://api.carefluence.com/
- type: CapabilityStatement
url: fhir/carefluence-openapi-r4-capabilitystatement.json
- type: Postman
url: https://api.carefluence.com/
- type: PostmanCollection
url: postman/carefluence-openapi-r4-collection.json
- type: WellKnown
url: well-known/carefluence-smart-configuration.json
- type: ErrorCatalog
url: errors/carefluence-problem-types.yml
- type: DataModel
url: data-model/carefluence-data-model.yml
- type: RateLimits
url: rate-limits/carefluence-rate-limits.yml
- type: Sandbox
url: sandbox/carefluence-sandbox.yml
- type: TermsOfService
url: https://carefluence.com/openapi-terms-conditions/
- aid: carefluence:authorization-server
name: Carefluence SMART on FHIR Authorization Server
description: The first-party OpenID Connect / OAuth 2.0 authorization server that issues every token the Carefluence Open
API R4 accepts, and the administration portal where developers register applications and request grants. Publishes full
OpenID Connect discovery and a JWKS anonymously, supports PKCE (S256), RS256 ID tokens, front-channel and back-channel
logout, token introspection and revocation, and advertises 51 distinct SMART on FHIR scopes across the patient, user and
system compartments.
image: https://carefluence.com/wp-content/uploads/2018/04/Logo-WHT-nds1740.png
humanURL: https://api.carefluence.com/
baseURL: https://core.carefluence.com/cf.admin.core
tags:
- OAuth
- OpenID Connect
- SMART on FHIR
- Identity
- Authorization
- Authentication
tags_raw:
- OAuth 2.0
- OpenID Connect
- SMART on FHIR
- Identity
- Authorization
- Authentication
properties:
- type: Documentation
url: https://api.carefluence.com/
- type: OpenIDConnect
url: well-known/carefluence-openid-configuration.json
- type: Authentication
url: authentication/carefluence-authentication.yml
- type: OAuthScopes
url: scopes/carefluence-scopes.yml
- type: SignUp
url: https://core.carefluence.com/cf.admin.core/Account/RegisterDeveloper
- type: Login
url: https://core.carefluence.com/cf.admin.core/Account/Login
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/carefluence-domain-security.yml
- type: Website
url: https://carefluence.com/
- type: DeveloperPortal
url: https://api.carefluence.com/
- type: Documentation
url: https://api.carefluence.com/
- type: APIReference
url: https://api.carefluence.com/
- type: Postman
url: https://api.carefluence.com/
- type: Support
url: https://carefluence.com/reach-us/
- type: Blog
url: https://carefluence.com/news-blogs/
- type: BlogRSS
url: https://carefluence.com/feed/
- type: Pricing
url: https://carefluence.com/onc-certification/
- type: SignUp
url: https://core.carefluence.com/cf.admin.core/Account/RegisterDeveloper
- type: Login
url: https://core.carefluence.com/cf.admin.core/Account/Login
- type: TermsOfService
url: https://carefluence.com/openapi-terms-conditions/
- type: Compliance
url: https://carefluence.com/onc-certification/
- type: Certification
url: https://chpl.healthit.gov/#/listing/10922
- type: LinkedIn
url: https://www.linkedin.com/company/carefluence/
- type: Twitter
url: https://twitter.com/carefluence
- type: Authentication
url: authentication/carefluence-authentication.yml
- type: OAuthScopes
url: scopes/carefluence-scopes.yml
- type: Conformance
url: conformance/carefluence-conformance.yml
- type: ErrorCatalog
url: errors/carefluence-problem-types.yml
- type: Lifecycle
url: lifecycle/carefluence-lifecycle.yml
- type: Conventions
url: conventions/carefluence-conventions.yml
- type: DataModel
url: data-model/carefluence-data-model.yml
- type: Packages
url: packages/carefluence-packages.yml
- type: SDKs
url: packages/carefluence-packages.yml
- type: WellKnown
url: well-known/carefluence-well-known.yml
- type: CapabilityStatement
url: fhir/carefluence-openapi-r4-capabilitystatement.json
- type: Components
url: components/carefluence-components.yml
- type: Sandbox
url: sandbox/carefluence-sandbox.yml
- type: Plans
url: plans/carefluence-plans-pricing.yml
- type: RateLimits
url: rate-limits/carefluence-rate-limits.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
url: llms/carefluence-llms.txt
x-enrichment:
date: '2026-09-02'
status: enriched
artifacts_added: 24
pass: local-v1
Carefluence API — frequently asked questions
Does Carefluence have an API?
Yes. APIs.io lists 2 APIs from Carefluence, including Carefluence Open API R4 and Carefluence SMART on FHIR Authorization Server.
How do I authenticate with the Carefluence API?
Carefluence documents its authentication (2 schemes). The details are profiled on APIs.io as Carefluence Authentication.
Is the Carefluence API ready for AI agents?
Carefluence has a Kin Score of 44.0 out of 100 (developing) and an Agent Readiness score of 30.0 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: