Tuva Health

Tuva Health, Inc. is a United States healthcare data company behind The Tuva Project, an open-source, warehouse-native data-transformation platform that harmonizes, validates, normalizes, and enriches raw healthcare data - medical and pharmacy claims, EHR clinical data, ADT feeds, and HL7 FHIR sources - into an analytics-ready Core Data Model and a library of Data Marts (AHRQ measures, readmissions, quality measures, chronic conditions, CCSR, pharmacy). It is delivered primarily as a dbt package plus Python utilities (FHIR Inferno) and a family of source connectors that run inside the customer's own cloud data warehouse - Snowflake, Databricks, Google BigQuery, Amazon Redshift, or Microsoft Fabric - rather than as a hosted service. Tuva is not a FHIR API vendor: FHIR R4 is a supported input format that Tuva flattens and maps into its Input Layer, not a live FHIR server it operates. It does ship one HTTP API - Tuva EMPI, an Apache-2.0 enterprise master patient index with a documented OpenAPI 3.0.3 contract - but that too is customer-deployed from OCI images, so there is no Tuva-operated API host. The company pairs the open-source project with a commercial Core Platform and named services. Home market is the United States.

Tuva Health publishes 11 API contracts indexed on the APIs.io network, including Config API, Data Sources API, Check API, and 8 more. Tagged areas include Healthcare, United States, Health Data, FHIR, and Interoperability.

Tuva Health’s developer surface includes engineering blog, documentation, getting-started guide, changelog, support, API reference, authentication, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.0/100 developing ▬ flat Agent 19/100 agent aware Front door AI 3/6 light Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

AccessApproval

2 published contracts

Healthcare United States Health Data FHIR Interoperability Data Analytics Data Transformation Claims Open Source dbt EMPI Patient Matching

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Health Information Management

BC-2900

matchesperson-recordspersonspotential-matches

POST /api/v1/matches GET /api/v1/potential-matches GET /api/v1/persons POST /api/v1/person-records/export

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 42.0/100 · developing

Contract Quality 6.9 / 19

Developer Ergonomics 12.1 / 15

Access Clarity 3.2 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.6 / 9

Discoverability 4.8 / 8

Regulatory Posture 2.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 18 / 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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/tuva-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 →

Standards implemented 1

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.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 11

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

The Tuva Project (dbt package)

The core open-source Tuva dbt package that transforms healthcare data from the Tuva Input Layer into the Tuva Core Data Model and Data Marts, including data-quality tests, norma...

FHIR Inferno

An open-source Python utility that flattens nested HL7 FHIR JSON (bundles / resources) into tabular CSV files so FHIR-sourced data can be loaded and mapped into the Tuva Input L...

Tuva Connectors

A family of open-source dbt connector projects (Medicare CCLF, BCDA, CMS synthetic, Aetna, BCBS, and a connector template, plus a FHIR preprocessing connector) that map raw clai...

Tuva Health Config API

The config API from Tuva Health — 1 operation(s) for config.

Tuva Health Data Sources API

The data-sources API from Tuva Health — 1 operation(s) for data-sources.

Tuva Health Check API

The health-check API from Tuva Health — 1 operation(s) for health-check.

Tuva Health Matches API

The matches API from Tuva Health — 1 operation(s) for matches.

Tuva Health Person Records API

The person-records API from Tuva Health — 2 operation(s) for person-records.

Tuva Health Persons API

The persons API from Tuva Health — 2 operation(s) for persons.

Tuva Health Potential Matches API

The potential-matches API from Tuva Health — 2 operation(s) for potential-matches.

Tuva Health Users API

The users API from Tuva Health — 2 operation(s) for users.

Scroll for all 11

Pricing Plans 1

Published pricing tiers and plan structures.

Tuva Health Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Tuva Health Rate Limits

0 limits

RATE LIMITS

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Tuva Health Empi Overlay

8 actions · documentation · tuva-health-empi-openapi.yml

GENERATED

Security Posture 2

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

Tuva Health Authentication

openIdConnect · 1 scheme

SECURITY

Tuva Health Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

DataModel

Conformance

Conventions

Lifecycle

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Package

Packages

SDKs

CLI

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 7

Status, limits, changes, and where to get help

RateLimits

IssueTracker

Releases

ChangeLog

Support

Deprecation

Community

Scroll for all 7

Commercial 4

Pricing, plans, and the legal terms of use

License

TermsOfService

PrivacyPolicy

Plans

Company 4

The organization behind the API

Blog

Blog

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: tuva-health
url: https://raw.githubusercontent.com/api-evangelist/tuva-health/refs/heads/main/apis.yml
name: Tuva Health
kind: company
description: 'Tuva Health, Inc. is a United States healthcare data company behind The Tuva Project, an open-source, warehouse-native
  data-transformation platform that harmonizes, validates, normalizes, and enriches raw healthcare data - medical and pharmacy
  claims, EHR clinical data, ADT feeds, and HL7 FHIR sources - into an analytics-ready Core Data Model and a library of Data
  Marts (AHRQ measures, readmissions, quality measures, chronic conditions, CCSR, pharmacy). It is delivered primarily as
  a dbt package plus Python utilities (FHIR Inferno) and a family of source connectors that run inside the customer''s own
  cloud data warehouse - Snowflake, Databricks, Google BigQuery, Amazon Redshift, or Microsoft Fabric - rather than as a hosted
  service. Tuva is not a FHIR API vendor: FHIR R4 is a supported input format that Tuva flattens and maps into its Input Layer,
  not a live FHIR server it operates. It does ship one HTTP API - Tuva EMPI, an Apache-2.0 enterprise master patient index
  with a documented OpenAPI 3.0.3 contract - but that too is customer-deployed from OCI images, so there is no Tuva-operated
  API host. The company pairs the open-source project with a commercial Core Platform and named services. Home market is the
  United States.'
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: true
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - pricing
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: medium
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://www.tuvahealth.com/img/TuvaHealthLogo-White@4x.png
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
tags:
- Healthcare
- United States
- Health Data
- FHIR
- Interoperability
- Data Analytics
- Data Transformation
- Claims
- Open Source
- dbt
- EMPI
- Patient Matching
tags_raw:
- Healthcare
- United States
- Health Data
- FHIR
- Interoperability
- Data Analytics
- Data Transformation
- Claims
- Open Source
- dbt
- EMPI
- Patient Matching
- Open-Source
created: '2026-07-24'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: tuva-health:the-tuva-project
  name: The Tuva Project (dbt package)
  description: The core open-source Tuva dbt package that transforms healthcare data from the Tuva Input Layer into the Tuva
    Core Data Model and Data Marts, including data-quality tests, normalization, claims preprocessing, and bundled terminology
    sets. Distributed as a dbt package (dbt Hub / GitHub) that runs inside the customer's cloud data warehouse - it is open-source
    software, not a hosted HTTP or FHIR API.
  humanURL: https://thetuvaproject.com/getting-started
  tags:
  - Data Transformation
  - dbt
  - Healthcare
  properties:
  - type: Documentation
    url: https://thetuvaproject.com/getting-started
  - type: APIReference
    url: https://thetuvaproject.com/core-data-model
  - type: Package
    url: https://hub.getdbt.com/tuva-health/the_tuva_project/latest/
  - type: SourceCode
    url: https://github.com/tuva-health/tuva
- aid: tuva-health:fhir-inferno
  name: FHIR Inferno
  description: An open-source Python utility that flattens nested HL7 FHIR JSON (bundles / resources) into tabular CSV files
    so FHIR-sourced data can be loaded and mapped into the Tuva Input Layer. A command-line data-preprocessing tool, not a
    FHIR server or HTTP API - it consumes FHIR rather than serving it.
  humanURL: https://github.com/tuva-health/fhir_inferno
  tags:
  - FHIR
  - Data Transformation
  - Python
  properties:
  - type: Documentation
    url: https://thetuvaproject.com/guides/mapping/fhir
  - type: SourceCode
    url: https://github.com/tuva-health/fhir_inferno
- aid: tuva-health:tuva-connectors
  name: Tuva Connectors
  description: A family of open-source dbt connector projects (Medicare CCLF, BCDA, CMS synthetic, Aetna, BCBS, and a connector
    template, plus a FHIR preprocessing connector) that map raw claims, EHR, ADT, and FHIR source formats into the standardized
    Tuva Input Layer. These are warehouse-native dbt projects, not HTTP API endpoints.
  humanURL: https://thetuvaproject.com/connectors/overview
  tags:
  - Connectors
  - Claims
  - Interoperability
  properties:
  - type: Documentation
    url: https://thetuvaproject.com/connectors/overview
  - type: SourceCode
    url: https://github.com/tuva-health/connector_template
- aid: tuva-health:tuva-health-config-api
  name: Tuva Health Config API
  description: The config API from Tuva Health — 1 operation(s) for config.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - Config
  tags_raw:
  - config
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-config-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-data-sources-api
  name: Tuva Health Data Sources API
  description: The data-sources API from Tuva Health — 1 operation(s) for data-sources.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - Data Sources
  tags_raw:
  - data-sources
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-data-sources-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-health-check-api
  name: Tuva Health Check API
  description: The health-check API from Tuva Health — 1 operation(s) for health-check.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - Health Check
  tags_raw:
  - health-check
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-health-check-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-matches-api
  name: Tuva Health Matches API
  description: The matches API from Tuva Health — 1 operation(s) for matches.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - Matches
  tags_raw:
  - matches
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-matches-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-person-records-api
  name: Tuva Health Person Records API
  description: The person-records API from Tuva Health — 2 operation(s) for person-records.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - person-records
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-person-records-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-persons-api
  name: Tuva Health Persons API
  description: The persons API from Tuva Health — 2 operation(s) for persons.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - Persons
  tags_raw:
  - persons
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-persons-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-potential-matches-api
  name: Tuva Health Potential Matches API
  description: The potential-matches API from Tuva Health — 2 operation(s) for potential-matches.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - potential-matches
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-potential-matches-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
- aid: tuva-health:tuva-health-users-api
  name: Tuva Health Users API
  description: The users API from Tuva Health — 2 operation(s) for users.
  humanURL: https://thetuvaproject.com/getting-started
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - User
  tags_raw:
  - users
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-users-api-openapi.yml
  - type: Documentation
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started
  - type: APIReference
    url: https://tuva-health.github.io/tuva_empi/api-docs/
  - type: GettingStarted
    url: https://tuva-health.github.io/tuva_empi/docs/getting-started/local-demo-environment
  - type: SourceCode
    url: https://github.com/tuva-health/tuva_empi
  - type: Authentication
    url: authentication/tuva-health-authentication.yml
common:
- type: RateLimits
  url: rate-limits/tuva-health-rate-limits.yml
- url: https://www.tuvahealth.com/news
  type: Blog
- type: License
  name: Apache-2.0
  url: https://github.com/tuva-health/tuva/blob/main/LICENSE
- type: CapabilityMap
  url: capabilities/tuva-health-capability-edges.yml
  name: Tuva Health Business Capability Map
- type: IssueTracker
  url: https://github.com/tuva-health/tuva/issues
- type: Releases
  url: https://github.com/tuva-health/tuva/releases
- type: DomainSecurity
  url: security/tuva-health-domain-security.yml
- type: Website
  url: https://www.tuvahealth.com
- type: DeveloperPortal
  url: https://thetuvaproject.com
- type: Documentation
  url: https://thetuvaproject.com/getting-started
- type: GettingStarted
  url: https://thetuvaproject.com/getting-started
- type: GitHubOrganization
  url: https://github.com/tuva-health
- type: LinkedIn
  url: https://www.linkedin.com/company/tuva-health
- type: Package
  url: https://hub.getdbt.com/tuva-health/the_tuva_project/latest/
- type: Packages
  url: packages/tuva-health-packages.yml
- type: SDKs
  url: packages/tuva-health-packages.yml
- type: DataModel
  url: data-model/tuva-health-data-model.yml
- type: Conformance
  url: conformance/tuva-health-conformance.yml
- type: ChangeLog
  url: changelog/tuva-health-changelog.yml
- type: LLMsTxt
  url: llms/tuva-health-llms.txt
- type: Blog
  url: https://thetuvaproject.substack.com
- type: Support
  url: https://www.tuvahealth.com/contact
- type: TermsOfService
  url: https://www.tuvahealth.com/terms
- type: PrivacyPolicy
  url: https://www.tuvahealth.com/privacy
- type: APIReference
  url: https://tuva-health.github.io/tuva_empi/api-docs/
- type: Authentication
  url: authentication/tuva-health-authentication.yml
- type: Conventions
  url: conventions/tuva-health-conventions.yml
- type: Lifecycle
  url: lifecycle/tuva-health-lifecycle.yml
- type: Deprecation
  url: https://tuva-health.github.io/tuva_empi/docs/releases
- type: Sandbox
  url: sandbox/tuva-health-sandbox.yml
- type: CLI
  url: cli/tuva-health-cli.yml
- type: Plans
  url: plans/tuva-health-plans-pricing.yml
- type: Overlay
  url: overlays/tuva-health-empi-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: Community
  url: https://thetuvaproject.com/community/community-overview
x-enrichment:
  date: '2026-08-15'
  status: enriched
  artifacts_added: 18
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/tuva-health"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/tuva-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.