Tuva Health website screenshot

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 1 API on the APIs.io network: Tuva EMPI API. Tagged areas include Healthcare, United States, Health Data, FHIR, and Interoperability.

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

47.3/100 developing ▬ flat Agent 28/100 agent aware Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
4 APIs
HealthcareUnited StatesHealth DataFHIRInteroperabilityData AnalyticsData TransformationClaimsOpen-SourcedbtEMPIPatient Matching

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 47.3/100 · developing
Contract Quality 9.2 / 21
Developer Ergonomics 13.7 / 17
Access Clarity 3.6 / 17
Operational Transparency 2.9 / 11
Contract Governance 3.1 / 10
Discoverability 6.1 / 9
Regulatory Posture 4.7 / 15
Agent readiness — 28/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
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.
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/. 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. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

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 EMPI API

The HTTP API of Tuva EMPI, Tuva Health's open-source (Apache-2.0) enterprise master patient index. A containerized Django backend that ingests person records, runs Splink-based ...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Tuva Health Rate Limits

0 limits

RATE LIMITS

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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.'
image: https://www.tuvahealth.com/img/TuvaHealthLogo-White@4x.png
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
created: '2026-07-24'
modified: '2026-08-15'
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-empi
  name: Tuva EMPI API
  description: The HTTP API of Tuva EMPI, Tuva Health's open-source (Apache-2.0) enterprise master patient index. A containerized
    Django backend that ingests person records, runs Splink-based probabilistic matching, and lets reviewers adjudicate potential
    matches into unified person IDs. Twelve JSON operations under /api/v1 cover configuration, data sources, person-record
    import/export, persons, potential matches, match creation, users and a health check. Tuva EMPI is customer-deployed -
    the OCI images run in the customer's own Kubernetes cluster or via Docker Compose - so there is no Tuva-operated base
    URL; the host is whatever the customer deploys it to.
  humanURL: https://tuva-health.github.io/tuva_empi/
  baseURL: https://{tuva-empi-host}/api/v1
  tags:
  - EMPI
  - Patient Matching
  - Healthcare
  - Open-Source
  tags_raw:
  - EMPI
  - Patient Matching
  - Healthcare
  - Open Source
  properties:
  - type: OpenAPI
    url: openapi/tuva-health-empi-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
  - type: Overlay
    url: overlays/tuva-health-empi-overlay.yaml
common:
- 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