Coordinating Medicare Revalidation Across Groups Without Overlooking Enrollment Responsibilities
Medicare revalidation for providers in multiple groups requires a clear understanding of the physician’s enrollment records, practice locations, and group relationships. Each participating group needs to know which responsibilities apply to its organization and whether the physician’s revalidation submission covers the relevant relationship.
Consider a physician who sees patients with Groups A, B, and C. The groups may maintain different enrollment records, locations, and contractor relationships. A message that one office has submitted an application does not establish that every required record or reassignment has been addressed.
Revalidation planning should start with the physician’s enrolled locations, the companies involved, and the applicable Medicare enrollment records. Each separate group should verify its own enrollment obligations and the physician’s reassignment to that group. Do not assume another company’s submission completes your group’s responsibilities. Confirm which records require revalidation, which relationships the submission covers, and whether separate applications are necessary.
Key Takeaways
- Check the physician’s and each group’s revalidation obligations and due dates separately.
- Account for all intended active reassignments when preparing the physician’s applicable revalidation.
- Each participating group should verify its own enrollment responsibilities and confirm whether the physician’s revalidation submission covers the relevant relationship.
- Keep preparation access separate from the physician’s required certification and signature.
- Track MAC requests, response deadlines, corrections, and the application’s processed outcome.
- Verify intended group relationships after processing before closing the revalidation task.
- Address reportable enrollment changes between revalidation cycles under their applicable deadlines.
Table of Contents
Separate the Physician’s Revalidation From Each Group’s Revalidation
Revalidation renews and confirms Medicare enrollment information. It is not the same as renewing a medical license or completing a commercial payer’s recredentialing process. CMS generally requires providers and suppliers to revalidate every five years and may request off-cycle revalidation. The applicable due date and notice determine when the physician or organization needs to act.
Individual enrollment identifies the physician and supports the physician’s Medicare participation and billing privileges. A reassignment establishes the relationship through which an eligible group receives Medicare payment for the physician’s services. The organization maintains its own enrollment. These records are connected, but a revalidation request for one does not automatically create the same obligation for all the others.
If Group A receives a notice to revalidate its organizational enrollment, the notice does not mean every physician in that group must submit an individual revalidation immediately. Likewise, an individual physician’s revalidation does not renew each affiliated group’s organizational enrollment. Check the identity on the notice before assigning the work.
| Question | Individual physician | Group or organization |
|---|---|---|
| What is being revalidated? | The physician’s applicable enrollment record | The organization’s enrollment record |
| Which paper form generally applies? | CMS-855I | CMS-855B |
| Who provides the required certification? | The physician | The appropriate authorized or delegated official |
| How are reassignments handled? | List all active reassignments for the individual revalidation | Do not resubmit unchanged reassignment information merely because the group is revalidating; follow current instructions for changes |
| Does this complete the other party’s revalidation? | No | No |
Current paper application pathways also differ. Physicians generally use CMS-855I for their individual revalidation. Groups use CMS-855B for their organizational revalidation. The individual application instructions require all active reassignments to be listed.
First Coast explains group revalidation and reassignment changes. Its guidance says groups should omit unchanged reassignment information from a CMS-855B revalidation.
This distinction prevents two opposing mistakes: overlooking other groups on the physician’s individual application, or treating organizational revalidation as a request to resubmit every unchanged reassignment. Use the current application instructions and the responsible MAC’s guidance for the transaction being submitted.
Check Medicare Revalidation Due Dates and Enrollment Records
Start with the CMS Medicare Revalidation List and the notices associated with the enrollment being reviewed. Search the physician and each relevant organization separately. Record the enrollment identity, assigned due date, notice date, responsible MAC, and person handling the submission. A shared spreadsheet can organize that work, but its entries should trace back to current source information.
CMS posts due dates seven months ahead and generally sends notices about three to four months before the deadline. Its instructions say to revalidate within three months of the due date even if a notice has not arrived. Applications submitted more than seven months early without a revalidation notice are unsolicited. A “TBD” result means a due date has not yet been assigned; it is not a reason to submit a precautionary revalidation.
If the notice and lookup result appear inconsistent, contact the appropriate MAC promptly. Preserve the notice and document the clarification. Do not resolve the discrepancy by borrowing another group’s date or assuming that an old reminder still describes the current obligation.
One physician may have more than one enrollment record
An individual NPI does not eliminate the need to identify the affected enrollment records and contractor jurisdictions. A physician practicing across states or enrollment arrangements may have questions that one office’s records cannot answer. Review PECOS records, Medicare PTANs and their enrollment relationships, approval correspondence, and applicable MAC instructions before deciding which submissions are required.
Multiple groups do not automatically mean a separate individual revalidation application for every group. Conversely, one coordinated application should not be described as completing every enrollment record in every jurisdiction. Identify the record being revalidated, account for its intended active relationships, and confirm any additional requirements with the appropriate contractor.
Unfamiliar PTANs on a revalidation notice may identify valid reassignments to another group. The physician’s involvement is especially useful here. An unfamiliar identifier needs investigation before staff decide it is obsolete.
Gather Information From Every Group Before Preparing the Application
The physician should identify the active provider-to-group affiliations through which groups bill Medicare for their services. Each group’s enrollment contact should compare the relevant information with PECOS and enrollment correspondence. Differences should be resolved before the affected application is treated as ready for review.
Use a consistent information request rather than several vague emails asking whether each group is “still active.” Ask for the group’s legal business name, organizational NPI, tax identification number, relevant Medicare enrollment identifiers, and applicable practice locations. Request available reassignment approval or change correspondence and the name of a contact who can explain discrepancies.
| Information | What to verify |
|---|---|
| Group identity | Legal business name, organizational NPI, tax identification number, and relevant Medicare identifiers |
| Reassignment | Whether the relationship should remain active and what current records show |
| Applicable locations | Where the physician currently practices under the arrangement and what needs review |
| Enrollment correspondence | Relevant approvals, pending changes, and unresolved MAC requests |
| Group contact | Who can confirm information and obtain missing records |
Each group can confirm the information it controls. That does not mean its staff can verify the physician’s entire enrollment history or speak for every other organization. The person handling an affected enrollment record should distinguish confirmed information, information still needed, and a discrepancy referred to the MAC.
For the physician working with Groups A, B, and C, each group should identify its own obligations and confirm the physician’s relationship to that group. If an individual revalidation submission covers several active reassignments, the person preparing it needs the information required to address those relationships. That does not replace a separate organization’s own revalidation when it is due.
If Group C’s name differs from a recent approval letter, the staff should investigate the mismatch before copying one version into the application.
Operational Snapshot
When a physician works with separate companies, each group should verify its own enrollment obligations and the physician’s reassignment to that group. Confirm which enrollment records a submission covers. Another company’s completed application should not be treated as proof that your group’s responsibilities are complete.
Share enrollment information through appropriately protected channels and approved access arrangements. A list of group contacts can be shared more broadly than sensitive identifiers or application documents. Give each participant the information needed for their role without making the physician’s complete application an unrestricted shared file.
Resolve missing or unfamiliar relationships
The review should distinguish an active relationship, an actual change requiring action, and an unresolved discrepancy. A physician may have stopped seeing patients at one location while continuing to bill through the same group elsewhere. A location change should not automatically be interpreted as the end of the group relationship.
Similarly, a reassignment shown in an old letter may have been modified by a later transaction. Review the dates and subsequent correspondence. If current records do not reflect the intended arrangement, ask the appropriate MAC what correction is needed and how it should be submitted.
When an actual departure or termination is confirmed, use the applicable reassignment-termination process. Revalidation does not replace that separate departure workflow. The purpose here is to preserve intended valid relationships and report accurate information, not to keep every historical affiliation active indefinitely.
Coordinate PECOS Access, Application Review, and Required Signatures
Confirm access before the due date becomes urgent. The person preparing the application needs an approved relationship and the appropriate permissions to work on the physician’s enrollment. CMS Identity & Access permissions control access to systems such as PECOS. They do not establish a Medicare reassignment.
A credentialing employee’s ability to open PECOS is therefore a different question from whether the physician is correctly connected to Groups A, B, and C. Review both, but do not treat a user-access relationship as evidence that a billing relationship is approved.
Technical Deep Dive
Removing an enrollment preparer’s CMS access does not terminate the physician’s Medicare reassignment to a group. These relationships serve different purposes and require different actions. When staff or vendors change, review access permissions separately from the physician’s intended billing relationships so one administrative task does not conceal another.
In this video, Jennifer Blevens-Smith discusses reviewing CMS Identity & Access accounts. The discussion supports the access checks that help practices prepare for enrollment work.
Within PECOS, identify the existing enrollment and the applicable revalidation transaction. Review the information already on file, correct inaccurate information through the required process, and provide the supporting documents identified for the application. Avoid creating an unnecessary new enrollment or submitting only a change of information when revalidation is required.
If using paper, obtain the current CMS application from the official source. CMS-855R has been discontinued; older instructions that direct every reassignment action to that form should not determine the current workflow. The current CMS-855B also permits applicable reassignment transactions. Choose the route based on whether the work concerns individual revalidation, organizational revalidation, or a reassignment change.
Preparation access does not replace the physician’s signature
The physician must review the individual revalidation and provide the required certification. CMS-855I states that an individual practitioner cannot delegate the authority to sign their application. A staff member or enrollment service may help prepare it, but assistance does not transfer the physician’s certification responsibility.
Group applications have their own authorized or delegated official requirements. Reassignment additions or changes can also involve transaction-specific signature requirements. Do not apply a rule about one type of submission to every application in the file.
Before submitting, review the information with the physician. Confirm the groups that should remain active, address unresolved discrepancies, and check the application’s required documents and signatures. Retain the completed application or available submission record so later questions can be answered from what was actually sent.
Track Medicare Revalidation Through MAC Requests and Corrections
A submission confirmation shows that a submission occurred. It does not establish approval or confirm that every intended relationship was processed. Track the application until its disposition and any outstanding requests are understood.
Record the submission date, application or tracking identifier, affected enrollment, responsible MAC, and contact person. Save the confirmation and the relevant supporting records. Identify who checks for correspondence and who covers that task when the usual employee is away.
| Stage | Evidence | What it establishes |
|---|---|---|
| Submitted | Application copy and submission confirmation | What was sent and when |
| Additional information requested | MAC request and its response deadline | What remains necessary |
| Correction supplied | Response copy and receipt or acknowledgment when available | What was provided; approval remains separate |
| Processed | Disposition or approval correspondence and record review | What was processed and what still needs follow-up |
A MAC development request identifies information or documentation needed to process the application. Read the complete request and record its actual response deadline. Assign the missing item to the physician, group contact, or other person able to provide it. The person tracking the application should follow the response rather than assuming that forwarding the request completes the task.
CMS-855I states that requested supporting documentation must be provided within 30 days of the request. Follow the applicable notice and current MAC instructions for the particular request, including how to send a correction. If the application is already being processed, ask the contractor how the correction must be submitted. A phone conversation alone does not necessarily supply an acceptable application change.
For the three-group example, a request concerning Group C should reach the person who can confirm Group C’s information. Staff handling the application should not guess the answer based on another group’s records. Keep a record of what was supplied and when the contractor received or acknowledged it.
Incomplete or late revalidation can affect reimbursement and Medicare billing privileges. Current instructions address stays of enrollment and deactivation in applicable situations. The consequences depend on the enrollment, omitted information, response, and contractor action. Treat notices about missing reassignments as substantive enrollment work, even when another part of the application has been approved.
Compliance Alert
CMS requires individual revalidation applications to account for all active reassignments. Approval involving one group does not establish that omitted relationships were preserved. Respond to MAC requests about missing groups within the applicable timeframe, and review the processed outcome for each intended relationship before considering the coordination complete.
Verify Group Relationships After Revalidation Is Processed
When approval correspondence arrives, compare it with the relationships the physician and groups intended to preserve. Read what the notice actually confirms, including any listed reassignments, changes, or effective dates. A broad task label such as “revalidation approved” can hide a narrower processed result.
Use approval correspondence and the available PECOS enrollment records to verify the affected relationships. If they disagree, or an expected group is missing, contact the responsible MAC and retain the clarification. Do not assume the public due-date lookup is a complete verification of individual billing affiliations.
Operational Snapshot
An enrollment task can be approved while a discrepancy still needs follow-up. Keep the application’s disposition and the unresolved correction visible as separate items. Give the affected group a clear update identifying what was confirmed, what remains open, and who will obtain the next answer from the MAC.
Read the approval before closing the task
Returning to Groups A, B, and C, each group should check whether the processed result addresses the enrollment record or relationship relevant to its organization. When a submission involves several reassignments, affected participants need a clear update about what was confirmed. A message that another office “handled everything” is less useful than a statement identifying the record reviewed, the confirmed result, and any remaining action.
Give billing staff the verified information relevant to their group. If a discrepancy affects dates or billing privileges, obtain contractor guidance before treating claims as ready for routine handling. Successful payment on a claim may provide useful operational information, but it does not replace verification of the enrollment result.
Close the revalidation task when the processed outcome has been reviewed, required follow-up is resolved or separately assigned, and the affected participants know the result. Keep unresolved corrections visible. Do not hide an open enrollment problem under a completed application task.
Keep Medicare Enrollment Information Current Between Revalidations
Revalidation works better when each practice can find its current enrollment information before the notice arrives. Maintain relevant approval letters, identifiers, group contacts, applicable locations, correspondence addresses, and information about approved preparation access. Keep records accessible to the people responsible for the work, with appropriate safeguards.
Choose a review routine that fits the practice’s staffing and enrollment activity. A small group may combine enrollment review with an existing administrative meeting. A physician who works with several groups may use a contact list and a clear process for notifying affected enrollment staff when information changes. These are recommended operational methods, not a universal CMS meeting schedule.
Reportable enrollment changes have their own deadlines. Do not wait for revalidation to address enrollment changes after a practice relocation or another reportable change. Determine the applicable requirement from the current CMS and MAC instructions, then track that update separately from the next revalidation.
Staff turnover can create another gap. When an employee or outside enrollment service stops handling the work, transfer the relevant records and pending tasks. Review access through the appropriate CMS process. Removing an outdated preparer’s access and terminating a physician’s group reassignment are different actions.
Revalidation coordination begins with knowing which enrollment records, locations, and companies are involved. The physician and each participating group need to understand what requires submission and what the processed result confirms. Clear communication helps prevent one organization from assuming another has completed work that remains outstanding.
Frequently Asked Questions
Does every group need to submit a separate revalidation for the same physician?
Multiple group affiliations do not automatically require duplicate individual applications. Coordinate the physician’s applicable revalidation so it accounts for all intended active reassignments. Each group has its own organizational obligations. If the physician has multiple enrollment records or MAC jurisdictions, confirm the required submissions with the appropriate contractor.
Does a group’s revalidation also revalidate its physicians?
No. A group’s organizational revalidation and a physician’s individual revalidation are separate obligations. A group notice does not automatically make every member due at the same time. Check the physician’s and organization’s CMS due dates and notices separately, then coordinate the applications that are actually required.
What if another group says it already completed the physician’s revalidation?
Ask which enrollment was revalidated and whether the submission accounted for the physician’s intended active reassignments, including your group. Obtain relevant confirmation and review the processed result. Avoid submitting a competing application without checking the current status. Submission by another office does not independently confirm that your relationship was preserved.
Should a physician revalidate when the CMS lookup shows TBD?
TBD means a revalidation due date has not yet been assigned. Do not submit an unsolicited revalidation solely as a precaution. If a MAC notice appears inconsistent with the lookup result, contact the contractor promptly and follow the applicable instructions. Continue addressing reportable enrollment changes through the appropriate update process.
Can credentialing staff sign the physician’s individual revalidation?
Staff or an enrollment service may help prepare the application through approved access, but preparation does not transfer signature authority. CMS-855I states that the individual practitioner cannot delegate the authority to sign their application. Group certifications and reassignment transactions have separate requirements; follow the instructions for the submission involved.
Does an enrollment change count as revalidation?
A change of information alone does not complete a required revalidation. The submission must use the applicable revalidation process and satisfy its requirements. Track changes and revalidation as distinct tasks, even when they involve the same records. Confirm the processed outcome and respond to any remaining MAC requests.
About the Author
Jennifer Blevens-Smith is the founder and principal consultant of Integral Clinic Solutions. With more than two decades of experience supporting independent medical practices, she helps physicians, practice administrators, and healthcare leaders strengthen credentialing, payer contracting, revenue cycle operations, compliance workflows, and practice management. Her work focuses on translating complex healthcare requirements into practical operational processes. These processes improve consistency, reduce administrative burden, and support long-term practice success.
Need Help Strengthening Your Medical Practice Operations?
Integral Clinic Solutions provides practical support for medical practices navigating credentialing, contracting, revenue cycle operations, compliance workflows, front-office systems, and practice management challenges.
Explore more operational guidance, compliance insights, and healthcare business resources on the Integral Clinic Solutions blog. New articles and updates are added regularly for practice owners, administrators, and healthcare teams.
Disclaimer: This content is for informational and educational purposes only and does not constitute legal, coding, billing, compliance, financial, or medical advice. Healthcare practices must verify all operational requirements with applicable payers, regulators, and qualified professionals. Read our full Legal & Compliance Disclaimer.