Who signs in, and who signs the certification statement?

The agent signs in through the CMS Identity & Access Management System under credentials for an authorized official or an approved surrogate, held in a login profile you control and can revoke. Certification statements and e-signatures belong to the authorized official. The agent prepares the application to that point and returns the signature prompt to the person. It never certifies on anyone’s behalf.

What happens when the packet is missing something PECOS requires?

The run stops with the exact field named: a license number, an ownership answer, a location PECOS will not accept. No placeholder is ever entered and nothing is submitted incomplete. A person supplies the missing value once and the run resumes. Portal downtime and login failures are reported separately as technical failures, so your queue separates data gaps from retries.

How does this fit with our commercial payer enrollments?

It uses the same enrollment payload as every payer enrollment in the library, so a provider is entered once and the same record feeds PECOS, national payer web forms, and regional plans. Sequence PECOS first when Medicare participation gates other contracts, or run it alongside. Each enrollment is its own run with its own tracking ID, so your credentialing tracker sees one row per provider per payer.

What evidence does each run leave?

One provider in, one PECOS tracking ID out. Each run records every field entered, every document attached, the reviewer’s approval, and the submission status, with the portal’s wording on any exception. Runs execute on HIPAA-compliant, SOC 2 Type II infrastructure under a BAA. See the security page.

Provider Enrollment

Enroll and Revalidate Providers in Medicare

Complete a provider’s Medicare enrollment or revalidation in PECOS from a single structured payload: identity, practice locations, reassignments, and supporting documents entered as provided, reviewed by a person, then submitted and tracked. The same payload feeds every payer enrollment in the library.

Go-live in as little as 30 minBrowser agentCustomer portal login

See it run on your systems.

We map your process, volume, and exception paths, then recommend a practical first scope.

Scope this workflow See how it works ↓

Building internally? Read the docs →

How Asteroid runs this workflow

From an enrollment packet to a submitted PECOS application

A provider’s enrollment packet arrives, Asteroid signs in to PECOS under the authorized official’s credentials, builds the application from the packet, stops for a person to review, then submits and captures the tracking ID, and any field the packet does not answer stops the run by name.

Medicare PECOSCMS Identity & Access Management System

How it actually runs

01Sign in to PECOS through the CMS Identity & Access Management System under the authorized official or surrogate’s credentials.
02Locate the provider’s enrollment record for a revalidation or change, or start an initial enrollment for the correct provider type.
03Enter identity, licenses, practice locations, reassignments, and ownership answers exactly as the packet provides them.
04Upload the supporting documents supplied with the run.
05Stop for a person to review the completed application. Submit on approval, capture the tracking ID and status, and return e-signature prompts to the authorized official.

A dry-run flag completes the application without submitting, so a new provider type can be checked end to end before the first live run. The human gate on submit is built in and stays on.

A structured enrollment packet for one provider: identity, NPI, licenses, practice locations, reassignments, and documents

A submitted application with its tracking ID in your credentialing system
The PECOS tracking ID, submission status, and a record of every field entered write back to your credentialing tracker, traceable to the packet that produced them.

A required field the packet does not answer: A missing license number, an unresolved ownership question, or a practice location PECOS will not accept returns with the exact field named. A person resolves it once and the run resumes. No placeholder is ever entered.

One payload feeds Medicare and every payer

The provider data in a PECOS application is the same data in every commercial payer enrollment: identity, NPI, licenses, locations, reassignments. Asteroid’s enrollment agents share one payload schema across PECOS and payer web forms, so a provider is entered once and enrolled everywhere. What differs per portal is the form. PECOS also carries certification statements and e-signatures that belong to the authorized official, and the agent never signs on their behalf. It prepares, a person certifies.

At scale

What runs today

The PECOS agent is in the catalogue pipeline. The payload schema and the review-before-submit gate it uses run today in payer web-form enrollment and behavioral provider enrollment. Upstream, NPI registration and updates run through the same CMS identity login. The rest of the category is in the provider enrollment library; scope your provider mix to sequence PECOS with your payers.

Book a demo, bring a revalidation that’s due

Questions

Frequently asked questions

All three run from the same payload. An initial enrollment starts a new application for the provider type. A revalidation opens the existing record and confirms or updates each section. A change of information updates the specific sections that changed, such as a new practice location or reassignment. The agent determines which path from your packet and the provider’s current PECOS record, and a person reviews the completed application before anything is submitted.

Book a demo Map this workflow

Disclaimer

Third-party names, including government agencies and registries, are used only to identify systems commonly involved in healthcare operations workflows. Asteroid is not affiliated with, endorsed by, sponsored by, or certified by those third parties unless expressly stated. Workflow availability depends on customer authorization, account permissions, configuration, and applicable system terms.