IT for small healthcare practices

Small practice.
Real HIPAA responsibility.

Dentists, chiropractors, therapists, specialty clinics, and other small healthcare offices still have to protect patient information. InView handles the technology behind that responsibility without expecting the doctor or office manager to become the IT department.

HIPAA securityMicrosoft 365Backups + recoveryRemote + on-site
Where patient data tends to live
01Practice systemsEHR · scheduling · billing
→
02Everyday technologyEmail · workstations · imaging · e-fax
→
03Outside vendorsCloud · backup · billing · support

HIPAA security is not just the EHR. If electronic protected health information touches it, it belongs in the risk conversation.

Healthcare data is still
worth attacking.

The same threats that hit hospitals also reach smaller practices. The difference is that a small office usually has fewer people available to notice, contain, and recover from the problem.

90%

of healthcare breaches in Verizon's 2025 data had a financial motive.

Patient data is valuable, and healthcare operations create pressure to restore access quickly. Verizon 2025 DBIR
$25K

was the OCR settlement paid by a small neurology practice after ransomware affected 6,800 people.

OCR found the practice had failed to conduct the accurate and thorough risk analysis required by the Security Rule. HHS OCR enforcement

HIPAA is easier to discuss
when the questions are concrete.

If OCR, your cyber insurer, or a large business partner asked tomorrow, could you show them the answers — not just say that your software vendor “handles HIPAA”?

01

Can you produce your latest security risk analysis?

HIPAA requires an accurate and thorough assessment of risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI.

02

Who is responsible for security?

The Security Rule requires an assigned security official. “Our IT guy handles that” is not the same thing as defined responsibility and documented procedures.

03

Does every employee have their own account?

Access should be authorized appropriately and activity must be attributable. Shared front-desk or clinical logins make both security and auditability harder.

04

Can you tell who accessed patient information?

HIPAA requires audit controls capable of recording and examining activity in systems that contain or use ePHI.

05

When did you last test a backup restore?

A backup that has never been restored is still a theory. HIPAA contingency planning includes data backup, disaster recovery, and emergency operations.

06

Do the right vendors have Business Associate Agreements?

IT providers, cloud services, backup vendors, billing companies, and other vendors may be business associates when their services involve PHI.

07

What happens when someone leaves?

Access should be removed promptly from email, practice systems, remote access, shared files, cloud services, and anything else that exposes patient information.

08

Are the systems touching ePHI still supported and patched?

Old Windows PCs, forgotten servers, imaging workstations, and unpatched remote-access tools belong in the risk analysis — especially when the vendor no longer provides security fixes.

09

Do staff know what to do with a suspicious email or security incident?

Security awareness and documented incident procedures are part of the Security Rule. The response should not begin with figuring out who to call.

10

Can you show what changed since the last review?

HIPAA security is an ongoing process. Practices must periodically evaluate safeguards and update protections as the environment and risks change.

More than a password
and a privacy form.

Dentists and chiropractors are specifically listed by HHS as examples of healthcare providers that can be HIPAA covered entities when they transmit standard healthcare transactions electronically, such as insurance claims.

Administrative safeguards

Know the risk and manage it.

  • Documented security risk analysis
  • Risk management and security policies
  • Assigned security responsibility
  • Workforce access and security training
  • Security incident procedures
  • Contingency and disaster recovery planning
  • Periodic technical and non-technical evaluation
Technical safeguards

Control and record access.

  • Access controls and unique user identification
  • Audit controls and activity review
  • Integrity protections for ePHI
  • Person or entity authentication
  • Transmission security
Physical + vendor safeguards

Protect the rest of the environment.

  • Workstation and facility safeguards
  • Device and media disposal / reuse procedures
  • Business Associate Agreements where required
  • Breach response and notification procedures
  • Documentation that can actually be produced

A breach can create state obligations too.

HIPAA's Breach Notification Rule can require notice to affected individuals, HHS, and in some cases the media. Indiana also has its own breach-notification law for covered personal information, requiring affected Indiana residents to be notified without unreasonable delay.

The Indiana Attorney General states that failure to comply with the state's notification requirement can lead to enforcement and civil penalties of up to $150,000.

Good cybersecurity and the current HIPAA rule are not exactly the same list.

The HIPAA Security Rule currently in effect is flexible and technology-neutral. For example, it does not simply say “every practice must use MFA everywhere.” HHS has separately published voluntary healthcare cybersecurity goals that strongly prioritize MFA, email security, encryption, vulnerability management, unique credentials, rapid offboarding, training, and incident preparedness.

Our approach is to meet the actual Security Rule requirements and build toward the modern safeguards HHS itself recommends — not stop at the minimum interpretation.

The technology behind
HIPAA security.

Your attorney or compliance advisor interprets the law. We help build, maintain, and document the technology controls underneath it.

Identity & email security

MFA, Microsoft 365, email protection, unique user accounts, admin separation, access reviews, and secure offboarding.

  • MFA & identity policies
  • Email security & phishing protection
  • User onboarding & termination

Endpoints & practice systems

Managed workstations, servers, patching, EDR, encryption, vulnerability management, imaging PCs, and the systems your staff actually uses.

  • Patch & vulnerability management
  • Endpoint security & encryption
  • Hardware lifecycle & inventory

Backup & recovery

Backups are part of the contingency plan, but the real question is whether the practice can actually recover when the server, workstation, or cloud data is unavailable.

  • Protected backups
  • Restore testing
  • Disaster & ransomware recovery

Risk, vendors & documentation

We help identify where ePHI touches technology, document the environment, work through remediation, and keep vendor relationships and technical controls from becoming a mystery.

  • Security risk analysis support
  • BAA & vendor technology review
  • Quarterly review through the InView Report

What we'd expect to see
in a well-run small practice.

Not every item below is a word-for-word mandate in the current Security Rule. They are the kinds of controls HHS itself prioritizes for modern healthcare cybersecurity and the things we would expect to discuss in a real risk-management program.

MFA on email, remote access & critical systems Unique accounts — no shared staff passwords Managed patching & vulnerability scanning EDR / modern endpoint protection Encryption for laptops and sensitive data flows Protected, tested backups Email filtering & phishing training Same-day account termination Audit logging and security alerting Documented incident response

HIPAA security should not live in somebody's memory.

Every quarter, we can turn the technical environment into a short view of what is protected, what changed, what needs attention, and what should be planned next.

  • Security and risk-remediation items
  • Unsupported hardware and software
  • Backup, patching, identity, and endpoint posture
  • Open projects, vendor issues, and upcoming costs

Useful documentation for management conversations, cyber-insurance questions, and ongoing risk management — without pretending a dashboard itself makes you compliant.

INVIEW REPORTHealthcare technology overview
Q4 / 2026
87/100
TECHNOLOGY POSTUREHealthy, with 3 prioritiesUpdated this quarter
Identity93
Endpoints82
Recovery89
NEXT PRIORITIES

01 Replace unsupported imaging PC Now

02 Complete restore test Q1

03 Review vendor access Q1

Let's see what you can actually prove.

You do not need to become a HIPAA expert before calling. We can start with the technology you have today, identify obvious gaps, and help build a more defensible security program around the practice.

Start with a free 30-minute IT review. We’ll look at what you have and what’s getting in the way, and tell you what we’d fix first. No obligation.

Email us

We reply the same business day. Opens your email app, or copy the address: