1upHealth

1upHealth is a US healthcare data interoperability company, founded in 2017 and headquartered in Boston, Massachusetts, that operates an HL7 FHIR-first health data platform for claims and clinical data acquisition, exchange, and compute. Built on a lakehouse architecture, the platform lets health plans, providers, and digital health developers ingest, normalize, store, and query patient and member data as FHIR, and ships modular solutions aligned to US federal interoperability mandates - Patient Access, Provider Access, Payer-to-Payer Data Exchange, Provider Directory, Formulary, and Electronic Prior Authorization (CMS Interoperability & Prior Authorization, CMS-0057-F). 1upHealth runs a managed, HIPAA-compliant FHIR REST API cloud server exposing FHIR R4 (4.0.1), STU3 (3.0.2), and DSTU2 (1.0.2) endpoints, each publishing a live CapabilityStatement, secured with SMART-on-FHIR OAuth 2.0. The company is HITRUST, SOC 2, and HIPAA aligned. Home market is the United States. Developer documentation is public at docs.1up.health, while provisioning API credentials and the developer console require an account (gated self-serve / partner onboarding).

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

How we profile 1upHealth

Each block below is one kind of artifact we hold for 1upHealth. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 10

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

1up FHIR API (R4)

1upHealth's managed HL7 FHIR R4 (4.0.1) REST API cloud server, exposing 144 FHIR resource types with SMART-on-FHIR OAuth 2.0 security. Publishes a live CapabilityStatement at /f...

1up FHIR API (STU3)

1upHealth's managed HL7 FHIR STU3 (3.0.2) REST API cloud server, exposing 117 FHIR resource types. Publishes a live CapabilityStatement at /fhir/stu3/metadata.

1up FHIR API (DSTU2)

1upHealth's managed HL7 FHIR DSTU2 (1.0.2) REST API cloud server, exposing 94 FHIR resource types. Publishes a live Conformance statement at /fhir/dstu2/metadata.

1up Patient Access API

CMS Patient Access solution delivering member clinical and claims data to patient-authorized third-party apps over FHIR, aligned to the CARIN Blue Button and US Core implementat...

1up Provider Access API

CMS Provider Access solution enabling payers to share member data with in-network providers over FHIR, aligned to the Da Vinci implementation guides.

1up Payer-to-Payer Data Exchange API

CMS Payer-to-Payer Data Exchange solution for sharing a member's historical clinical and claims data between health plans over FHIR when a member changes payers.

1up Provider Directory API

Publicly accessible FHIR Provider Directory publishing accurate provider and network listings, aligned to the Da Vinci PDEX Plan-Net implementation guide.

1up Electronic Prior Authorization API

CMS-0057-F Electronic Prior Authorization solution automating prior authorization submission and decisioning over FHIR, aligned to the Da Vinci PAS / DTR / CRD implementation gu...

1up Patient Connect

Connectivity solution that acquires patient-authorized clinical records from a national network of EHR/provider and payer connections and normalizes them into the 1up FHIR data ...

1up Population Connect (Bulk FHIR)

Population-scale connectivity and Bulk Data (Flat FHIR) export solution for acquiring and computing over large member/patient populations as FHIR.

Scroll within the panel for all 10 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

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

1uphealth-mcp.yml

MCP SERVER

Event Specifications 1

Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.

AsyncAPI definitions for this provider's event-driven and streaming APIs.

1Uphealth Subscription Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

1Uphealth Authentication

oauth2 · 2 schemes

SECURITY

1Uphealth Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

1Uphealth Trust Center

SOC 2, HIPAA, CSA STAR

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

1Uphealth Scopes

1 scope · clientCredentials/authorizationCode

1 scopes

SCOPES

Resources

Every other property we hold for 1upHealth — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

← All providers · Data indexed from github.com/api-evangelist/1uphealth · machine-readable index on apis.io