Skip to lesson content

Practice Academy / Governance & transitions

A transition is
more than a closing date.

Plan who will own the decisions, records and unfinished work when a physician, owner or service partner changes.

Executive summary. A practice transition may involve retirement, ownership succession, a sale, closure or a change in a critical service provider. Each event has different legal and operational consequences, but all require clarity about responsibilities before, during and after the change. A signed agreement does not automatically establish that access, staffing, patient communication, payer records and unfinished work are ready. This lesson offers an administrative governance framework for organizing the transition with the appropriate clinical, legal, financial and technical leaders. It distinguishes authority from task execution, explains why records availability must be planned, and uses a fictional vendor-handoff case. It does not prescribe transaction terms, patient-notice deadlines, record-retention periods or clinical coverage arrangements. Those depend on the actual event, jurisdictions, agreements and professional obligations.

Learning outcomes: classify the transition; map decision and continuity responsibilities; define evidence for an authorized handover.

Preparation: Ownership and operating model · Estimated reading time: 8 minutes · Prepared November 15, 2026.

Name the event before designing the plan.

A physician’s retirement is not necessarily a practice closure. An equity transfer is not the same as an asset purchase. Replacing a billing vendor is not a transfer of clinical authority. Start by describing exactly what changes and what remains in place.

The Small Business Administration (SBA, 2026) recommends a deliberate plan and qualified advice when selling, transferring or closing a business. Its general guidance addresses agreement terms, assets, liabilities and remaining obligations. A medical practice requires additional profession-specific and jurisdiction-specific review; a generic business exit checklist is not sufficient.

For this lesson, succession planning means preparing for a future change in ownership or leadership. A transition plan organizes the work around a specific change. A continuity requirement identifies something that must keep functioning. These working definitions support planning; they do not create legal rights.

Build two maps: authority and unfinished work.

The authority map identifies who can approve contracts, access changes, financial actions, employment decisions and clinical arrangements. The work map identifies what remains open, who receives it and how completion will be confirmed. A task assignment does not automatically confer approval authority.

Original transition register: questions for the responsible reviewers
AreaContinuity questionReview responsibility
Clinical workWho is responsible for ongoing care, pending results and clinical follow-up?Clinical leadership with applicable professional/legal guidance
Patient communicationWhat notices, contact routes and access arrangements are required?Clinical, legal and privacy owners
RecordsWho holds them, who can retrieve them and what retention rules apply?Privacy, records and legal owners
Revenue cycleWho handles pre-transition claims, corrections, refunds and disputes?Authorized billing/finance leaders with advisors
People and vendorsWhat obligations, approvals and handoffs remain?Employer/contract owners and counsel
TechnologyWhat must remain accessible, and when should individual access change?Authorized technical and security owners

Keep effective dates distinct. A purchase closing, professional departure, payer update, system cutover and final settlement may not occur together. Review dependencies before announcing that a single date settles every responsibility.

Do not assume accounts, licenses, enrollments or contracts transfer automatically. Ask the appropriate reviewer to identify required notices, consents, applications or replacement arrangements for the actual transaction. This lesson deliberately avoids a universal deadline because the relevant rules and documents differ.

Preserve records availability without improvising data transfers.

HHS explains that a business associate generally may not block a covered entity’s access to PHI it maintains on the entity’s behalf, including using an EHR access shutdown to resolve a payment dispute. HHS also discusses limited arrangements with different data-return characteristics and the covered entity’s responsibility for availability (U.S. Department of Health and Human Services [HHS], 2023). Have counsel assess the actual services and agreement rather than applying the example without context.

HHS’s cloud-service FAQ states that, where feasible, a BAA must require return or destruction of PHI at termination. If return or destruction is infeasible, protections and limitations on further use must continue as specified. Other legal retention requirements can affect feasibility (HHS, 2016). This is not an instruction to delete records or assume that contract termination ends retention duties.

Plan authorized access, usable export, reconciliation and ongoing custody before the transition. A file count alone does not establish that records can be read or that all required material is present. The technical and privacy teams should define permitted testing, approved destinations and evidence of completeness.

Keep data-sharing authority separate from enthusiasm about the transaction. A potential buyer, successor or new vendor does not receive unrestricted access simply because a handover is being discussed. Appropriate agreements, permissions and safeguards must be resolved by the responsible parties.

Work a handoff before relying on it.

Fictional administrative transition

The vendor contract ends Friday. The work does not.

A practice is replacing a billing vendor. The departing vendor lists 120 open account tasks. The incoming team acknowledges 110 items; ten remain unmatched. Separately, the practice has not confirmed who will respond to a payer request received after the cutover.

The difference is not proof that ten records were lost. Reconcile definitions, duplicates, completed work and identifiers before reaching that conclusion. Assign an owner to every unmatched item and clarify the post-cutover response process.

The handover should identify who handles each category of unfinished work and under what authority, rather than treating the contract end date as automatic completion. Clinical questions, patient disputes and sensitive information still require the appropriate routing and safeguards.

Knowledge check: the incoming team received an export. Is the transition complete?

No. Verify authorized receipt, usability, completeness, open-task ownership and the agreed exception process. Receipt of a file is one milestone, not evidence that all obligations have been discharged.

Knowledge check: should every outgoing user account be disabled immediately?

Access changes require an authorized, risk-aware plan. Remove access when appropriate, but do not improvise a shutdown that interrupts necessary availability or leaves an unapproved shared login as the workaround. Security and continuity owners should coordinate the sequence.

Prepare for an unplanned absence as well as a planned departure.

A retirement timetable can be deliberate; an unexpected absence may not be. Ask which decisions currently depend on one person and what approved backup arrangement exists. Document where governing information is held and how authorized people can locate it without sharing personal credentials.

Clinical coverage, legal authority and financial signing rights require appropriate planning. An administrative contact list does not appoint a substitute clinician or create a power of attorney. Have qualified advisors establish the needed arrangements and make sure the operational plan accurately reflects them.

Use a discussion exercise to reveal gaps: who receives an urgent operational issue, who can authorize the response, and what evidence is available? Keep exercises fictional or otherwise appropriately authorized. Do not change real patient records, access permissions or banking authority merely to test the plan.

Close the handover with evidence.

An original transition decision record can include:

  1. The event, parties, scope and intended effective dates.
  2. The authorized decision makers and limits of delegated work.
  3. Required professional reviews, consents and unresolved conditions.
  4. Patient-care and communication responsibilities assigned by appropriate leaders.
  5. Record custody, permitted access and retention decisions.
  6. Open work, responsible recipients and reconciliation findings.
  7. Financial obligations, settlement assumptions and disputed items.
  8. System cutover, access-change and contingency steps.
  9. Acceptance evidence and any expressly unresolved exceptions.
  10. Post-transition review dates, contacts and escalation ownership.

Acceptance should state what was actually verified. A remaining exception needs an owner and plan, not a cosmetic green status. Retain the decision record through the approved records process and revisit it if the scope or conditions change.

Where MedCBO fits: within signed scope, administrative coordination may organize dependencies, registers and handoff tracking. It does not execute ownership transfers, choose clinical successors, supply legal opinions or assume authority over the practice’s assets and patient-care decisions.

Continue with acquisition diligence, vendor handoffs and security and continuity.

References & evidence notes

Primary government sources support the general business-planning and specified HIPAA principles. The 2016 FAQ is older than the preferred five-year evidence window and is used narrowly, not as a complete statement of all current retention duties. Tables, definitions and scenario are original educational frameworks. This is not a transaction, succession or fifty-state patient-notice legal opinion.

U.S. Department of Health and Human Services. (2016, October 6). Do the HIPAA Rules require a CSP to maintain ePHI for some period of time beyond when it has finished providing services to a covered entity or business associate? Read the retention and termination FAQ.

U.S. Department of Health and Human Services. (2023, January 9). May a business associate of a HIPAA covered entity block or terminate access by the covered entity to the protected health information (PHI) maintained by the business associate for or on behalf of the covered entity? Read the access guidance. HHS dates reflect displayed review dates.

U.S. Small Business Administration. (2026, January 26). Close or sell your business. Read the general exit-planning guide.

Return to the Academy