Prime ReportStream

Name: Prime ReportStream API
Brand: Prime ReportStream
Availability: InStock

★ Only Publicly Available OpenAPI DocumentHealthcareClinical DataapiKey, oauth213 EndpointsREST

For Agents

Submit public health reports to the CDC ReportStream hub and manage the organizations, senders, and receivers that route data between labs and health departments.

Quickstart

Get started with Prime ReportStream in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"submit a public health report to CDC ReportStream"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Prime ReportStream API.

Submit public health reports to the ReportStream hub for routing to downstream receivers

Manage organization records that group senders and receivers in the topology

Configure sender profiles for labs and providers transmitting reports

Configure receiver profiles for state, local, and territorial health departments

GET STARTED

Start building with Prime ReportStream API

Explore with Jentic

View OpenAPI Document

Use for: I need to submit a lab report to ReportStream for routing to a state health department, List all organizations registered in ReportStream, Set up a new sender configuration for a clinical lab, Update the receiver configuration for a state health department

Not supported: Does not handle EHR record retrieval, patient appointment booking, or pharmacy operations — use for routing public health reports between senders and receivers through the CDC ReportStream hub only.

Jentic publishes the only available OpenAPI document for Prime ReportStream, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Prime ReportStream, keeping it validated and agent-ready. Prime ReportStream is the U.S. Centers for Disease Control and Prevention's data hub that routes public health data — case reports, lab results, immunization records — from senders such as labs and providers to receivers such as state and territorial health departments. The API exposes a reports submission endpoint and configuration endpoints for managing organizations, senders, and receivers in the routing topology. Authentication is either an Okta-issued OAuth 2.0 token or an Azure Functions API key for service-to-service callers.

Use Cases

Patterns agents use Prime ReportStream API for, with concrete tasks.

★ Lab Report Routing to Public Health

Clinical labs use the reports endpoint to send case reports, COVID test results, or immunization data into ReportStream, which then routes the records to the appropriate state, local, or territorial health departments. This replaces bespoke point-to-point integrations between every lab and every jurisdiction with a single CDC-operated hub.

POST a batch of lab results to /reports with the configured sender identifier and confirm the routing receipt

Sender Onboarding Configuration

Health technology vendors integrating new clinical labs use the senders configuration endpoints to register the lab and define how its reports are formatted and validated. Agents can stand up the configuration on a vendor's behalf, then update it as the lab adds new test panels or jurisdictions.

PUT a sender configuration to /settings/organizations/{organizationName}/senders/{senderName} with the new lab's ELR format and topic

Receiver Management for Health Departments

State and territorial health departments register as receivers in ReportStream, declaring which jurisdictions and report types they want delivered. Operations teams use the receivers endpoints to add new jurisdictions, change transport settings, or sunset old configurations as health department systems migrate.

List receivers under an organization via GET /settings/organizations/{organizationName}/receivers and update the transport for one receiver

AI Agent Integration via Jentic

A public health integrations agent uses Jentic to discover ReportStream operations, load their schemas, and execute calls without holding the OAuth credentials or function key directly. This lets a single assistant span ReportStream and complementary public-health systems while CDC-issued credentials stay isolated in the vault.

Use Jentic to search 'submit a public health report to ReportStream', load the schema for POST /reports, and execute with the lab's payload

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for prime reportstream, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/reports

Submit a report to the data hub

GET

/settings/organizations

List all organizations

PUT

/settings/organizations/{organizationName}

Create or update an organization

GET

/settings/organizations/{organizationName}/senders

List senders for an organization

PUT

/settings/organizations/{organizationName}/senders/{senderName}

Configure a sender

GET

/settings/organizations/{organizationName}/receivers

List receivers for an organization

PUT

/settings/organizations/{organizationName}/receivers/{receiverName}

Configure a receiver

POST

/reports

Submit a report to the data hub

GET

/settings/organizations

List all organizations

PUT

/settings/organizations/{organizationName}

Create or update an organization

GET

/settings/organizations/{organizationName}/senders

List senders for an organization

PUT

/settings/organizations/{organizationName}/senders/{senderName}

Configure a sender

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ReportStream OAuth 2.0 tokens and Azure Functions keys are stored encrypted in the Jentic vault. Agents call /reports and /settings endpoints through scoped execution requests; no credential ever enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'submit a public health report') and Jentic returns the ReportStream /reports operation along with any sender or receiver configuration calls needed in the workflow.

Time to first call

Direct ReportStream integration: 1-2 weeks including onboarding, Okta app registration, and sender configuration. Through Jentic: under 1 hour for the API surface once onboarding is complete — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

cBioPortal Public API

Cancer genomics cohort data that pairs with public health reporting workflows

Pair with ReportStream when an agent combines population-level surveillance with molecular cohort context

Complementary

US Census API

Population denominators for normalising case rates from ReportStream feeds

Use Census data to compute incidence per population from ReportStream-derived case counts

Alternative

CBP AESDirect WebLink API

Different domain — included only as a corpus-verified neighbour US government API

Not a substitute for public health reporting — choose ReportStream for any case or lab report routing

FAQs

Specific to using Prime ReportStream API through Jentic.

Why is there no official OpenAPI spec for Prime ReportStream?

ReportStream's Open API definition lives in the cdcgov/prime-reportstream GitHub project but is not published as a stable, validated artifact for general consumption. Jentic generates and maintains this spec so that AI agents and developers can call Prime ReportStream via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Prime ReportStream API use?

ReportStream supports two schemes: an Okta-issued OAuth 2.0 authorization code flow at hhs-prime.okta.com with org_admin, system_admin, and user scopes, and an Azure Functions API key passed in the `x-functions-key` header for service-to-service callers. Through Jentic both credential types are stored in the encrypted vault.

Can I submit lab reports through ReportStream?

Yes. POST /reports accepts the report payload from a registered sender and routes it to all configured receivers that match the report's jurisdiction and topic. The sender must be onboarded via the senders configuration endpoints first.

What are the rate limits for the Prime ReportStream API?

The OpenAPI spec does not declare specific rate limits. ReportStream is operated as a public health utility and applies throttling at the function-app and Okta token levels. Coordinate volume expectations with the ReportStream onboarding team rather than assuming a published limit.

How do I onboard a new sender through Jentic?

Search Jentic for 'configure a ReportStream sender', load the schema for PUT /settings/organizations/{organizationName}/senders/{senderName}, and execute with the lab's organization name, sender name, and topic configuration.

Is the Prime ReportStream API free?

Yes. ReportStream is operated by the CDC as public infrastructure and is free for senders and receivers in covered public health categories, subject to onboarding and approval.