What is PECOS?
PECOS (Provider Enrollment, Chain, and Ownership System) is the CMS database that manages Medicare provider enrollment, tracks ownership structures, and determines which providers are eligible to bill Medicare.
Updated April 2026
PECOS Explained
PECOS is distinct from NPPES. While NPPES assigns and stores NPI numbers, PECOS manages Medicare enrollment status. A provider can have an NPI but not be enrolled in PECOS, meaning they have an identifier but aren't approved to bill Medicare. The two systems use NPI as a common identifier but serve different purposes.
PECOS contains detailed information about provider enrollment status, practice locations, reassignment relationships (which organization bills on behalf of which provider), and ownership/control interests. This ownership chain data is particularly valuable for understanding healthcare organization structures.
For B2B data buyers, PECOS enrollment status is a useful signal. Providers enrolled in Medicare are actively practicing and seeing patients. Providers not in PECOS may be cash-only practices, non-clinical roles, or retired providers who may not have deactivated their NPI. PECOS data also helps identify which practice groups a provider bills through, revealing organizational relationships that aren't visible in NPPES alone.
Why PECOS Matters for Healthcare Data
PECOS enrollment confirms that a provider is actively billing Medicare, which is a strong signal that they're actively practicing. PECOS ownership data also reveals organizational relationships between providers and practice groups, useful for mapping health system hierarchies and identifying decision-makers.
Real-World Example
A pharma sales team cross-references their target physician list against PECOS to confirm active Medicare enrollment. They find that 8% of their list contains providers who aren't enrolled in PECOS, suggesting they may not be actively seeing Medicare patients. By filtering these out, the team focuses outreach on confirmed active providers. Source: CMS NPPES files.
How should a data team use PECOS?
Use PECOS for the Medicare enrollment facts it reports, then verify current practice, payer relationships, and business contacts separately. Preserve the enrollment identifier, entity type, status, reassignment evidence, and observation date. This prevents a valid Medicare relationship from being presented as proof of another current affiliation.
For PECOS, a sales list needs a different standard from a research extract. Research can retain ambiguous records for later study. Outreach requires a named entity, a current business relationship, and a contact route checked close to delivery. Store uncertainty as a field instead of hiding it inside one "verified" label. That gives campaign owners a way to exclude weak matches while preserving them for analysts who may have more context.
Which PECOS fields deserve manual review?
Review enrollment status and reassignment relationship first. Those fields carry the most weight in a match and create the most damage when stale. Compare the source value with the current practice website or official record, record the date of the check, and keep conflicting evidence visible. A clean-looking row can still connect the right name to the wrong location, organization, or specialty. Identity, affiliation, and contactability should each have their own result.
Manual review of PECOS belongs at the boundary between sources. Name differences, mergers, shared addresses, and organization aliases often create valid records that deterministic rules cannot resolve safely. Give the reviewer the source links and the reason the row was flagged. A reviewer who sees only the final spreadsheet has to repeat the research and may reach a different conclusion without knowing which conflict triggered the review.
Where do PECOS errors enter the workflow?
A frequent error is equating Medicare enrollment with payer relationships. The mistake usually appears during normalization or joining, after the source file has been collected but before the final record is assembled. Preserve source-specific identifiers through each step, compare entity type before joining, and reject matches that depend on name similarity alone. Shared surnames, brand names, and building addresses create false confidence when a pipeline collapses several signals into one score.
Staleness creates a second failure path for PECOS. A correct historical record may be wrong for a campaign sent today. Save both the source's update date and your own check date. Those dates answer different questions: when the publisher changed the record and when your team confirmed the evidence. Refresh high-change fields such as role, practice affiliation, email, and phone more often than durable identifiers.
How can buyers test PECOS data before purchase?
When testing PECOS, ask for a sample drawn from the same specialty, geography, and organization mix as the planned order. A broad national sample can hide the exact edge cases your team will encounter. Check the sample against authoritative sources, call a small set of business numbers, and review ambiguous matches with the people who know the territory. Record pass, fail, and unresolved counts by field rather than reducing the whole sample to one accuracy percentage. Source: CMS NPPES files.
A vendor supplying PECOS should explain source coverage, matching rules, refresh timing, and what happens when sources disagree. Request field-level definitions too. Terms such as current, direct, active, and verified can refer to several different checks. A written acceptance rule makes the project testable: the delivered file either satisfies the agreed condition or it does not. Keep the sample and acceptance rule with the final delivery for later QA.
What should happen before PECOS data reaches a CRM?
Before PECOS reaches a CRM, normalize names and addresses, preserve stable identifiers, separate individuals from organizations, and keep the relevant source URL or source label available for audit. Deduplicate only after entity type and affiliation have been checked. Then map the accepted fields to the CRM without overwriting a newer first-party value. Conflicts should route to review, especially when the incoming record would change an account owner, practice location, suppression status, or clinical specialty.
Finish with a dated QA summary that states the requested population, delivered record count, field coverage, excluded rows, and unresolved exceptions. That summary gives sales operations a usable handoff and makes later refreshes comparable. When campaign results arrive, feed bounces, wrong-party calls, and corrected affiliations back into the next build. PECOS becomes more valuable when source evidence and field outcomes remain connected after delivery.
Frequently Asked Questions
Is PECOS data publicly available?
Partially. CMS publishes enrollment and reassignment data through the Medicare Provider Enrollment files, but the full PECOS database is not publicly searchable in the same way NPPES is. Some data is available through the Medicare Provider Use and Payment Data files.
What is the difference between NPPES and PECOS?
NPPES assigns NPI numbers and maintains the provider identity registry. PECOS manages Medicare enrollment and billing eligibility. A provider needs an NPI first (from NPPES), then enrolls in Medicare through PECOS to bill Medicare.
How do you check if a provider is enrolled in PECOS?
CMS provides online verification through the Medicare Provider Enrollment portal. Some data vendors also include PECOS enrollment status as an enrichment field in their provider databases.
Can PECOS establish a current practice location?
PECOS supports Medicare enrollment research, but a campaign location should also be checked against current practice evidence. Enrollment and day-to-day practice are related but distinct facts.
How should PECOS status be stored?
Keep the observed enrollment status, source URL or file, and check date as separate fields. Avoid turning that observation into a broader conclusion about payer mix or current employment.
Sources and References
Related Resources
Get the Provider Data You Need
Tell us what you're looking for. We'll build a custom list matched to your target market.
Trusted by healthcare sales teams, medical device companies, and health IT vendors across the US.