Free Network Build Assessment
Score your buildIf CMS asks how your network looked at a past date, your current roster won't answer the question. You need records made at the time. Here's how to build a dependable audit trail from day one.
We can't cite a public CMS checklist of the network adequacy records an auditor will request, so treat this article as our recommendation for being ready. The useful test is specific: can you show how the network looked at a particular point in time, for a specific benefit year, a specific county, and a specific provider type?
That covers the full cycle: the outreach log showing which providers were contacted and when, the contracts showing that providers were active during the period, the credentialing records, the panel status verification, the directory records, and the HSD tables you uploaded to HPMS, along with the results you got back.
The key words are "at a particular point in time." This is what distinguishes a genuine audit trail from a retrospective reconstruction. A plan with current contracts and current credentialing files can document its current network. A plan with dated records made at the time can document its network as it stood on a past date.
Retroactive reconstruction is what happens when a plan receives an audit request for documentation of its network adequacy during a prior benefit year and must assemble that documentation from whatever records remain. Contract files are searched. Credentialing files are pulled from storage. HPMS screenshots may not exist. Outreach logs, if they were maintained at all, may be in email threads across multiple staff members' inboxes. The plan pieces together a story of its network that is internally consistent but not contemporaneous.
Retroactive reconstruction tends to show. Documents carry creation or modification dates after the request arrived, outreach logs are unnaturally uniform in format, credentialing files are complete for the current year but incomplete for prior years, and directory records miss changes known to have occurred during the period. Reconstruction is not necessarily dishonest, and it is often genuinely the best the plan can do given how its records were maintained, but it is inherently less reliable than records made at the time.
A genuine audit trail is built in real time, during the network operations work itself. Outreach logs are created when calls are made. Contract execution is recorded when signatures are obtained. Credentialing committee actions are recorded in minutes at the time of the committee meeting. HPMS updates are logged when they are submitted. Directory changes are recorded when they are made. The result is a record that is contemporaneous by construction: it was created at the time of the activity, not after the fact.
Provider outreach records are where network teams are often weakest, because the work happens across many people and inboxes. They matter most around an exception request. A request under 42 CFR 422.116(f) turns on whether the providers are actually available, and on accounting for each provider in the county and specialty. Your record of who you contacted and what they said supports that account, though inability to contract is not itself a valid reason.
A useful outreach log entry includes the provider's name and NPI, the date of contact, the contact method (phone, written, email, in-person), the outcome of the contact (no response, declined, interested but not available, agreed to contract), and if the provider declined, the reason given. Logs that record only a date and a provider name are incomplete. Logs that record contacts by specialty without identifying the individual provider are of little use.
Timing is as important as content. A log showing a burst of contacts all made in the week before a deadline doesn't look like a sustained effort, and it probably wasn't one. The log should show contacts spread across the recruitment window, with follow-up attempts documented for providers who did not respond to initial outreach.
Outreach records should be kept in a system that discourages backdating: ideally one that stamps entries when they are created. Email-based outreach logs where the outreach emails themselves are retained (with original headers) are more credible than logs entered manually into a spreadsheet, because the email headers provide an independent timestamp that cannot be altered after the fact.
For each provider on your HSD tables, CMS expects a fully executed contract; letters of intent signed by both parties can stand in only during an initial or service area expansion application. The contract chain should include: the initial provider agreement with a clear effective date, any amendments that modify terms relevant to the specialty or service covered, and documentation of the credentialing decision that predates or coincides with the effective date of the agreement.
The effective date of the contract is critical. A contract executed on May 20 cannot be used to count a provider toward an HPMS submission filed on May 15. This seems obvious, but a team scrambling to close a gap near a deadline can lose track of it. Check contract execution dates against your upload dates before anyone else does.
Contract records should be maintained in a way that preserves the entire execution history. Fully executed agreements should be stored with the date they were countersigned (not just the date the plan signed), because the contract is not effective until both parties have executed it. Electronic signature platforms that generate audit logs of the signing sequence are particularly useful here: the audit log establishes the date each party signed and eliminates disputes about when the contract became effective.
For delegated contracting arrangements, where a medical group or IPA contracts with the plan and individual providers contract with the group, the records should extend to the delegation agreement, the subcontract between the group and the individual provider, and evidence that the group's credentialing processes meet your standards. Keep delegation files alongside the direct contract files, and make sure the effective dates of the subcontracts line up with the period in which the providers were on your tables.
Credentialing committee minutes are the record of the decision itself. They should show that each provider file was individually reviewed by the committee, that the committee made an affirmative decision on each file (approve, deny, or conditionally approve), and that the decision was recorded at the time of the meeting. Minutes that are vague, that approve files in undifferentiated batches, or that are dated after the meeting are weak evidence.
A strong set of committee minutes for a credentialing action includes: the meeting date, the names of committee members present (with credential), the list of files reviewed (by provider name and NPI, not just by count), the decision for each file, any adverse findings discussed and the committee's rationale for its determination, and the signature of the committee chair or secretary attesting to the accuracy of the minutes.
For plans using a credentialing committee designee model, where a single medical director approves files between full committee meetings, the designee's review should be documented with the same specificity as full committee review. The dates of designee review should precede the effective date of the credentialing approval, and any ratification your policy or accreditor requires should appear in the full committee minutes.
Check that your document retention policy doesn't quietly override your CMS obligations. General corporate records schedules can be shorter than what a CMS contract requires, so have compliance confirm the retention period against your contract and 42 CFR 422.504(d).
The provider directory is a real-time document. Providers join networks, terminate contracts, change locations, go on leave, change panel status, add or drop hospital affiliations. Under 42 CFR 422.111(m), MA plans must update directory data within 30 days of learning of a change, and under 42 CFR 422.120 the Provider Directory API must be updated no later than 30 calendar days after the plan receives new information.
A directory change log is the audit trail for this requirement. It should record the nature of each change (location update, panel status change, contract termination, specialty addition), the date the plan learned of the change (whether from the provider, a participating facility, or its own review), and the date the directory was updated. The difference between those two dates is the number to watch: 30 days or fewer for each entry.
Without a change log, a plan has no easy way to show it met those limits. It is one of the simplest records to set up, so there is little reason to go without one.
Keep your own record of what went to HPMS as well: a copy of each HSD upload, its date, and the Automated Criteria Check result that came back. The internal change log and those uploads should be reconcilable, since a difference between your directory and your HSD tables is something you want to find first.
Medicare Advantage contracts carry a long record retention requirement. Have your compliance team confirm the period against your CMS contract and 42 CFR 422.504(d), and apply it to outreach logs, contracts, credentialing files, directory records, and copies of what you uploaded to HPMS.
A long retention window creates practical challenges without systematic document management. Outreach logs kept in individual staff members' email accounts can become inaccessible after those people leave. Paper credentialing files stored off-site are slow to retrieve. Copies of HPMS uploads may be hard to find later unless you keep them yourself.
Common weak spots to check for include: outreach logs that don't cover the full recruitment period, credentialing files missing verification for specific elements, contracts with effective dates after the upload that relied on them, directory change logs that are absent or incomplete, committee minutes that do not identify files individually, and missing records for prior benefit years.
Blueprint keeps a history of work on each provider, showing who did what and when, along with outreach sequences and recorded decline reasons, and your data can go out by CSV export. It covers the work done in Blueprint, not every action in your organization, so contracts, committee minutes, and HPMS records still need a home of their own.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.