Choose an IT provider that can explain who owns each part of your practice's technology, how support fits around patient care, and how recovery would work if a critical system became unavailable. Ask for specific examples of access controls, vendor coordination, backup testing, and documentation. Compare the answers against your actual workflows, not a generic service list.
In This Article
- What should a medical office ask an IT provider before signing?
- How should IT support protect clinical workflows during the workday?
- What security and HIPAA questions should a practice ask?
- How can a medical practice verify that backups and recovery will work?
- How should a Carmel practice compare proposals and choose?
- Frequently Asked Questions
What should a medical office ask an IT provider before signing?

“John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed.”
Start with ownership. Your EHR vendor may support its application, but that does not automatically make it responsible for workstations, identity accounts, Wi-Fi, printers, internet connectivity, email, or another vendor's remote access. Ask the provider to map those dependencies and identify who receives and coordinates each issue.
Ask how support requests are prioritized and communicated when the front desk cannot check in patients, clinicians cannot reach records, or billing is waiting on a printer or scanner. Request the actual service agreement and escalation process. Confirm which services and hours are included rather than assuming a general promise covers every situation.
Ask what information the provider documents: devices, responsible vendors, administrative accounts, approved remote-access methods, network connections, and recovery dependencies. Find out how the practice can access those records if the relationship ends. Documentation should make transitions and troubleshooting more orderly, not leave essential knowledge with one person.
For a new suite or renovation, include building and construction dependencies in the discussion. Ask who coordinates cabling, network access, landlord requirements, and clinical vendors, and which party is responsible for each task. Put the agreed scope and exclusions in writing so a project handoff does not leave essential work unassigned.
Use the managed IT services overview to frame questions about day-to-day support, but assess the written proposal against your specific systems and responsibilities.
Choose a provider that makes accountability visible before an incident or opening-day deadline.
How should IT support protect clinical workflows during the workday?
Walk through an ordinary morning with the provider. The front desk may need scheduling, phones, email, scanning, and payment workflows at once. Clinicians may use shared workstations across rooms, while a vendor needs remote access to a specific application or device. Ask how the provider would identify the affected dependency before recommending a change.
Maintenance planning should account for patient schedules and the practice's available windows. Ask how planned changes are communicated, who approves them, and how the provider handles a change that affects a clinical workflow. A technically sound adjustment can still create operational friction if staff are not prepared or the right application vendor is not involved.
Discuss endpoint and identity ownership in practical terms. Ask how new staff receive accounts and equipment, how role changes are handled, and how access ends when someone leaves. For shared workstations, discuss individual sign-ins, session practices, and ways to keep controls usable without encouraging staff to share credentials or invent workarounds.
Confirm how connectivity and devices are treated. A wireless issue, printing fault, or unsupported workstation can affect multiple people even when the EHR itself is functioning. Ask the provider to distinguish equipment it manages from equipment supported by a manufacturer or clinical vendor, and to describe how handoffs between them are coordinated.
For a Carmel practice, ask how support will account for your office's particular building and network dependencies. If you are opening or expanding near Carmel City Center or along the US-31 corridor, clarify landlord, construction, and vendor responsibilities. These details matter because access to cabling pathways, equipment areas, and service providers can shape project coordination.
Good support protects the patient-facing workflow as well as the technology.
What security and HIPAA questions should a practice ask?
Ask the provider to explain how its work supports the practice's security responsibilities without promising that a product or service makes the practice compliant. HIPAA obligations depend on the organization and its role. A provider should discuss practical safeguards while leaving legal determinations and compliance decisions to the practice and its qualified advisors.
Ask how the provider approaches account security, multifactor authentication, endpoint protection, patching, email risk, and administrative access. Ask which controls it manages, which remain the practice's responsibility, and how exceptions are approved. The goal is to understand whether controls fit clinical work and whether responsibility is clear when an application vendor also administers an account.
Vendor access deserves its own review. Request an inventory of vendors that can connect remotely, the systems they can reach, the business owner who approves access, and how access is reviewed or removed. Ask how urgent vendor support is handled without turning a temporary exception into permanent, undocumented access.
For a security risk analysis, ask who will gather evidence, what systems and workflows are in scope, how findings will be recorded, and who will prioritize remediation. A risk analysis is not a one-time checkbox. Changes in staff, applications, office layout, or vendor access can change the practice's risk picture.
Ask how the provider separates technical assistance from legal interpretation. State requirements, contracts, and payment workflows may raise additional questions for the practice, and an IT proposal should not be treated as legal advice. Use the HIPAA and IT compliance service information as a starting point for questions about scope and shared responsibilities.
A credible security discussion names controls, owners, evidence, and open questions.
How can a medical practice verify that backups and recovery will work?
Do not stop at asking whether backups exist. Ask what data and systems are covered, how often copies are made, where they are held, who can alter or delete them, and how the practice would restore access. The answers should account for cloud services and local systems, where applicable, rather than treating every application as identical.
Ask for a recovery scenario tied to a real workflow. If the scheduling system or a shared workstation is unavailable, what must return first for the office to operate? Who contacts the EHR or device vendor? Where are recovery instructions kept? The provider should help define dependencies, while the practice decides which services matter most to patient operations.
Clarify recovery time objective (RTO), the target time for restoring a service, and recovery point objective (RPO), the target for how much recent data might need to be restored. Ask whether targets are documented, what they depend on, and how the practice can verify them. Do not accept a target as proof that a recovery test has succeeded.
A recovery review should distinguish two targets: how quickly service returns and how much recent data may need restoration.
Request evidence of a restoration exercise or a clearly described test plan. Find out what was tested, what was excluded, what problems were found, and who owns follow-up. If no test has been performed, treat that as a gap to plan for, not as a reason to assume the backup will restore as expected.
Review the disaster recovery planning information and ask what a proposed engagement includes, what remains outside scope, and how the plan would be reviewed with practice leadership and relevant application vendors.
Recovery is credible when the practice can explain the sequence and show what has been tested.
How should a Carmel practice compare proposals and choose?
Compare proposals using the same questions and boundaries. A list of security features is difficult to evaluate unless each proposal identifies who operates the control, which systems are covered, how exceptions work, and what evidence the practice receives. Ask providers to separate included work from optional projects and third-party vendor responsibilities.
Review the service agreement for support channels, escalation, planned maintenance, after-hours options, onboarding, documentation, and offboarding. Do not assume every provider uses the same definitions for monitoring, response, or incident handling. If a response target matters to the practice, ask for its exact written definition and the events that start or pause the clock.
Check whether the provider can coordinate infrastructure as well as routine IT support when your needs call for it. GDS Technology's stated service lines include managed IT, cybersecurity, cloud services, low-voltage and structured cabling, physical security, and commercial real estate technology. Confirm the scope and responsibilities in the proposal rather than assuming every service is included in one agreement.
Before deciding, ask each finalist to explain a scenario specific to your office: a clinician cannot access a system, a vendor's remote account must be removed, or a recovery test reveals a gap. The clearest answer should identify the decision-maker, next step, communication path, and evidence left behind.
Choose the provider whose written scope and working process match the practice's real dependencies.
More on this from Riser Management: Infrastructure Governance for Medical Office | Riser.Management by GDS.
Frequently Asked Questions
How can managed IT support keep our EHR available during business hours?
Ask how the provider will identify dependencies around the EHR, including workstations, identity, network connectivity, and the application vendor. Confirm who handles each issue, how changes are scheduled, and how staff receive updates. Availability depends on the systems and vendors involved, so ask for a documented escalation and coordination process rather than an absolute uptime promise.
What should a medical office look for in an outsourced IT support provider?
Look for clear service boundaries, documented escalation, practical security controls, vendor coordination, and evidence of recovery planning. Ask who owns accounts, endpoints, network equipment, and application handoffs. Review the service agreement for included hours, response definitions, onboarding, and offboarding. A provider should explain how its process fits patient-facing work without claiming that technology services alone establish compliance.
How do we evaluate an IT provider's HIPAA support?
Ask which safeguards the provider can help implement or document, how responsibilities are divided, and how findings from a security risk analysis are tracked. Confirm that the provider distinguishes technical assistance from legal advice and does not promise that a service makes the practice compliant. The practice should involve qualified advisors when interpreting its obligations or deciding how to address them.
How can we tell whether a medical office can recover after ransomware or system failure?
Ask what data and systems are backed up, who controls the copies, and how restoration is tested. Request a scenario-based recovery plan that names dependencies, vendor contacts, decision-makers, and priorities. Review the test evidence and open issues. A backup claim alone does not show how long recovery will take or whether restored systems will support the practice's essential workflows.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.