Switching IT Providers: A Continuity Checklist for Medical and Dental Practices
Slow support, recurring problems and unclear cybersecurity can make a healthcare practice question its IT provider. But changing providers creates another concern: what happens to the systems employees rely on while patients are being seen?
A well-managed transition is not a sudden cutover. It is a controlled handoff that accounts for access, documentation, vendors, backups and the daily rhythm of the practice. The goal is to let the new provider begin managing the environment while the practice retains control of its systems and keeps employees informed.
What practice owners and administrators should protect during the switch
- Patient-care operations: Plan the handoff around clinical systems, practice hours and vendor dependencies.
- ePHI and administrative access: Complete the BAA and establish controlled access before the new provider begins managing systems containing ePHI.
- Control of essential systems: Keep ownership and current administrative access for Microsoft 365, domains, security tools and vendor portals.
- Your staff’s time: After you authorize the transition, Pronto Tech coordinates the technical handoff with the outgoing provider.
Start with the concerns that are making you consider a change
Practice owners and administrators usually do not begin looking for a new IT provider because of one ticket. More often, several problems have accumulated:
- Slow response: Employees wait too long for acknowledgment or help while patients are waiting.
- Recurring problems: The same technical issue returns without a root-cause fix or lasting explanation.
- Unclear security: Nobody can clearly describe which cybersecurity controls or HIPAA safeguards are in place.
- Reactive spending: Technology decisions are made without a plan for equipment replacement, licensing or growth.
- Vendor middleman fatigue: The practice has to coordinate the IT company, EHR vendor and internet or telephone provider itself.
Before changing providers, write down the problems you want the new relationship to solve. That list should become part of the transition plan and the standard used to evaluate the new provider.
Confirm the BAA before the new provider receives access
An IT provider may need access to systems that create, receive, maintain or transmit electronic protected health information. When that access makes the provider a business associate, the practice needs a written business associate agreement before providing access to PHI.
The agreement should define the provider’s permitted use of PHI, required safeguards, incident-reporting obligations and what happens to PHI when the relationship ends. HHS guidance on business associate contracts also explains that, when feasible, a BAA must require PHI to be returned or destroyed when the agreement terminates.
Pronto Tech signs a BAA before receiving access to systems containing PHI. The practice should also review the outgoing provider’s agreement and confirm its obligations for returning information, relinquishing access and appropriately handling any PHI it maintains.
The BAA is important, but it is not the entire transition plan. The practice still needs an operational inventory of the accounts, systems and vendors involved.
Make sure the practice–not the provider–controls the essential accounts
The transition is easier when the practice can confirm that its essential accounts are registered to the business and that current administrator access is available.
The inventory should include:
- Microsoft 365 and identity: Tenant ownership, administrator accounts and multifactor-authentication recovery methods.
- Domains and networking: Internet domains, DNS hosting, firewall and wireless management, and any VPN connections used by clinical or business systems.
- Device encryption and backups: Recovery keys for encrypted equipment, backup platforms and restore procedures.
- Clinical and communications vendors: EHR, practice-management, imaging, laboratory, internet and telephone contacts and portals.
- Documentation and licensing: Current network, device and application documentation, software licensing and device-management systems.
If an account is controlled by the outgoing provider, the new provider can help identify the correct transfer or recovery path. Missing credentials should be discovered early, not while an employee is waiting for help.
Pronto Tech structures essential accounts so the client retains ownership and receives the administrative access and current documentation needed to control its environment. Clients retain that information if they later choose another provider.
You approve the transition; Pronto Tech handles the handoff
The practice should not have to manage a prolonged exchange between two IT companies.
After the owner approves the change and authorizes the outgoing provider to cooperate, Pronto Tech takes over the technical communication and discovery. We request the documentation and access needed to manage the environment, follow up on missing items and organize the information as it is received.
The practice remains informed and approves material decisions, but it does not have to relay every technical question between providers.
This approach also keeps the conversation professional. The purpose is to establish reliable access and continuity, not criticize the outgoing provider.
A practical healthcare IT transition sequence
1. Review the current environment and agreements
Confirm the current provider’s notice requirements, renewal date and transition obligations. Identify the practice’s important applications, locations, employees, vendors and patient-facing workflows.
2. Define what the new provider will manage
Document the services included in the new relationship, support hours, escalation process, on-site coverage, project boundaries and after-hours arrangements. The practice should know what belongs in the monthly service and what requires separate approval.
3. Sign the BAA and authorize the handoff
Complete the necessary agreements before the new provider receives access to systems containing PHI. Once the practice authorizes the transition, the providers can exchange access and documentation directly.
4. Establish and verify administrative access
Confirm access to Microsoft 365, domains, networking equipment, security tools, backups and vendor portals. Create provider-specific administrative accounts where appropriate instead of relying on shared credentials. Verify multifactor authentication and recovery methods.
5. Understand clinical and business dependencies
Map the systems employees depend on during the workday: the EHR, practice-management platform, imaging or laboratory connections, shared drives, secure messaging, phones, printers and internet connectivity.
The new provider should also know which outside vendors must be involved when one of those systems fails. A slow clinical application, for example, may originate in the workstation, the local network, the internet connection or the application provider’s environment. The practice needs an IT team that will test the path and coordinate the right next step rather than send employees from vendor to vendor.
6. Introduce the support process to employees
Employees should know how to request help, what information to include and how urgent issues are escalated. Responsive support means acknowledging the problem, beginning the work, communicating clearly and staying engaged until the employee can work again.
7. Remove obsolete access and stabilize the environment
At the appropriate point in the transition, rotate credentials and remove access that the outgoing provider no longer needs. Confirm that monitoring, security tools, backups and support contacts are functioning under the new arrangement.
After takeover, review unresolved issues and build a practical roadmap for security, aging equipment, licensing and future projects. Upgrades identified during onboarding may take longer than the initial takeover and should be planned separately rather than rushed into the handoff.
Why timely, documented access changes matter
One healthcare practice asked Pronto Tech to create Microsoft 365 access for a temporary employee. The account was created and the access details were returned in approximately 90 minutes. When the staffing plan changed the following morning, the practice asked for the access to be removed. The same support team removed it in under one hour and confirmed completion.
The value was not simply speed. The practice completed the full access cycle: access was created for a legitimate need and removed promptly when that need ended. The requester thanked the team and rated the resolution “Extremely satisfied.”
Medical and dental practices regularly add temporary, contract and changing-role staff. Timely account creation, role changes and deactivation support the practice’s access-control and security responsibilities. Promptly removing access reduces the risk that former or temporary personnel retain access they no longer need.
A provider transition is a useful time to confirm that onboarding, role changes and offboarding follow a documented, repeatable process.
Questions to ask before choosing the new provider
HIPAA responsibilities and account ownership
- Will you sign a BAA before receiving access to systems containing PHI?
- Will our Microsoft 365 tenant, domains and administrator accounts remain registered to our practice?
- Will we receive the administrative credentials and current documentation needed to control our environment?
- If we later leave, how will our credentials, documentation and any PHI you maintain be returned or handled?
The transition handoff
- Who communicates with our current IT provider after we approve the change?
- How will you verify backups, security tools and administrative access?
Ongoing support and vendor coordination
- How will employees request help, and when is the help desk available?
- Will you work directly with our EHR, imaging, internet, telephone and other technology vendors?
- How will you identify projects or upgrades that should be planned after takeover?
Clear answers are more valuable than a promise that nothing will ever go wrong. The practice needs to know who will perform each part of the handoff, how employees will be supported and how control of its systems will be preserved.
Start with a confidential second opinion
You do not have to notify your current provider before speaking with Pronto Tech. We start with a brief, confidential conversation about what is not working and the practical next step. We will not contact your current provider without your permission.
Pronto Tech provides managed IT, cybersecurity and Microsoft 365 support for medical and dental practices in Manassas and across Northern Virginia, Maryland and Washington, DC.
Plan the transition before you notify your provider.
Tell us what is not working. We will help you identify the practical next step without contacting your current provider.
Request a confidential second opinion
Or call 703.881.4605.
Sources and guidance
- HHS, Business Associate Contracts
- HHS, When a software vendor is a business associate
- HHS, A business associate may not block a covered entity’s access to PHI
This article provides general operational information and is not legal advice. Healthcare organizations should review contractual and regulatory requirements with qualified advisers.
