Skip to main content
Guide, 11 minute read

Healthcare and Dental IT in Las Vegas: HIPAA Security Planning

IT planning for Las Vegas medical and dental practices: what the HIPAA Security Rule asks for at a high level, where the proposed update stands, backups, Microsoft 365 and email, network segmentation, Windows 10 and Windows Server 2016 dates, and a practice checklist.

Planning guidesPractice owners, office managers, and IT leads at medical and dental practices in Las Vegas, Henderson, North Las Vegas, and Boulder CityBy , Founder and CEO, Days Dynamics. Published November 10, 2026.

What IT a Las Vegas medical or dental practice needs to plan for

A medical or dental practice covered by HIPAA must meet the HIPAA Security Rule. The rule requires administrative, physical, and technical safeguards for electronic patient information, starting with a documented risk analysis. For IT, common planning areas include tested backups, protected Microsoft 365 email, a segmented network, and Windows versions that still get security updates. HHS has proposed changes to the rule, and the current rule remains in effect. This guide is planning help, not legal advice.

What the HIPAA Security Rule requires, at a high level

The Security Rule applies to covered entities, including health care providers that transmit health information electronically in connection with HHS standard transactions, and to their business associates. It requires reasonable and appropriate safeguards for electronic protected health information (ePHI). HHS calls the rule flexible, scalable, and technology neutral, so a small dental office and a multi-site clinic can meet it differently. HHS also states that an addressable specification is not optional.

SafeguardWhat HHS listsCommon IT controls for it
AdministrativeSecurity management process with a risk analysis, a security official, access authorization, workforce training, periodic evaluation, a contingency plan, and business associate agreementsA written risk analysis, a named person in charge, logins tied to job roles, staff training, a backup and recovery plan, and signed agreements with vendors that handle ePHI
PhysicalFacility access controls, workstation use and security, and device and media controlsLocked server and network closets, screens placed and locked with care, and a process for wiping or destroying old drives and devices
TechnicalAccess control, audit controls, integrity controls, authentication, and transmission securityUnique logins, activity logs, protection against altered or deleted records, strong sign-in such as multifactor authentication, and encrypted connections

See the Cybersecurity and resilience.

Start with a documented risk analysis

HHS lists risk analysis as a required implementation specification: an accurate and thorough assessment of the potential risks and vulnerabilities to ePHI. HHS states there is no single method, the analysis must be documented, and the process should be ongoing. The rule does not say how often to repeat it, so plan a review whenever something changes, such as a new system, an office move, or a new vendor.

  • Scope. Include all ePHI the practice holds, on every device and service.
  • Where the data lives. List where ePHI is stored, received, maintained, or transmitted: practice management and imaging systems, workstations, phones, email, backups, and cloud services.
  • Threats and weaknesses. Document the threats you can reasonably expect, such as ransomware, a lost laptop, or a failed server.
  • Current safeguards. Record what is in place today and how it is set up.
  • Likelihood and impact. Rate how likely each threat is and how much harm it would cause, then rank the risks.
  • Documentation. Write it down. HHS requires the analysis to be documented but does not require a specific format.
  • A starting tool for small practices. The Office of the National Coordinator for Health IT, with the HHS Office for Civil Rights, publishes a Security Risk Assessment (SRA) Tool aimed at small and medium providers. The tool page states that using it is neither required nor a guarantee of compliance.

See the HIPAA risk analysis for small practices: what OCR enforcement shows.

Where the proposed Security Rule update stands

On December 27, 2024, the HHS Office for Civil Rights issued a proposed rule to strengthen the Security Rule. It is a proposal. HHS states that the current Security Rule remains in effect during the rulemaking. As checked November 10, 2026, the Federal Register lists the proposed rule and no final rule. Several proposed items, such as an asset inventory and tested restores, are reasonable planning targets either way.

MilestoneDateSource
HHS Office for Civil Rights issues the proposed ruleDecember 27, 2024HHS
Proposed rule published in the Federal Register (RIN 0945-AA22)January 6, 2025Federal Register
Public comment deadlineMarch 7, 2025Federal Register
Final ruleNone published as of November 10, 2026Federal Register
  • Proposed: a technology asset inventory and a network map, updated at least once every 12 months and when the environment changes.
  • Proposed: encryption of ePHI at rest and in transit, with limited exceptions.
  • Proposed: multifactor authentication, with limited exceptions.
  • Proposed: network segmentation.
  • Proposed: separate technical controls for backup and recovery, and written procedures to restore certain systems within 72 hours.
  • Proposed: a compliance audit at least once every 12 months.
  • Proposed: vulnerability scanning at least every six months and penetration testing at least once every 12 months.

Backup and recovery for patient data

The Security Rule's contingency plan standard requires a data backup plan, a disaster recovery plan, and an emergency mode operation plan. A data backup plan means retrievable exact copies of ePHI. HHS ransomware guidance adds that ransomware encrypting ePHI is presumed to be a breach unless the practice can show a low probability of compromise, and that test restores and offline backups help recovery.

  • Back up every system that holds ePHI. Include the practice management system, imaging, the server, Microsoft 365 mail and files, and any data kept on workstations.
  • Keep one copy offline or isolated. HHS notes that some ransomware targets online backups and suggests considering backups kept offline and unavailable from the network.
  • Test restores on a schedule. HHS advises periodic test restorations to verify the integrity of backed up data. Record each result.
  • Time a full restore. Measure how long the practice management system takes to restore, so the disaster recovery plan rests on a real number.
  • Match retention to Nevada law. NRS 629.051 requires each custodian of health care records to keep patient records for 5 years after receipt or production unless federal law sets a longer period, and bars destroying the records of a person who is under 23 on the date of the proposed destruction. Nevada's definition of a provider of health care includes physicians and dentists. Confirm how it applies with your advisors.
  • Plan for working without systems. The emergency mode plan covers continuing critical business processes that protect the security of ePHI while operating in emergency mode. Decide how the front desk and clinical staff will work.

See the Backup and disaster recovery and the Veeam vs Microsoft 365 Backup.

Microsoft 365 and email security

Microsoft offers a HIPAA Business Associate Agreement to customers that are covered entities or business associates, included by default through its Online Services Data Protection Addendum. In-scope services include Exchange Online, SharePoint Online, OneDrive for Business, and Microsoft Teams. Microsoft also states that using its services does not on its own achieve HIPAA compliance. The practice remains responsible for how it sets up and uses them.

  • Multifactor authentication for every account. Microsoft Entra security defaults require all users to register for multifactor authentication and block legacy authentication protocols. Custom Conditional Access policies need at least Microsoft Entra ID P1.
  • Separate admin accounts. Keep administrator access on dedicated accounts and require multifactor authentication on them.
  • Patient information sent outside the practice. Decide how staff send it, such as an encrypted message option, and train them on that method.
  • Staff training. The Security Rule requires training all workforce members on security policies and procedures. Include how to spot phishing email.
  • Deleted items are not a backup. Exchange Online keeps permanently deleted items for 14 days by default, adjustable up to 30 days. A separate backup covers longer retention and larger losses.
  • Sharing review. Check shared mailboxes, OneDrive sharing links, and Teams guests against each person's role.

See the Microsoft 365 licensing and migration and the Microsoft 365 Business Standard vs Premium.

Network segmentation and Wi-Fi in the office

Network segmentation splits one office network into separate zones, so a compromised device in one zone cannot freely reach the others. The HHS proposed update would require it. For a practice, it limits what a single infected PC or guest phone can reach, and it gives older imaging or equipment computers a safer place to sit.

  • Guest and patient Wi-Fi. Keep it on its own network with internet access only.
  • Clinical and front desk workstations. Put them in a zone that reaches the practice management and imaging systems, and little else.
  • Imaging and connected equipment. Sensors, X-ray and imaging workstations, and devices that run older software can sit in their own zone with tightly limited access.
  • Phones, payment terminals, cameras, and building systems. Give them their own zones so they cannot reach patient data.
  • Servers and backups. Limit which devices and accounts can reach the server and the backup system.
  • Document it. A current network map and device list make the risk analysis and later changes easier. HHS has proposed requiring both.

See the Network and Wi-Fi and the Business Wi-Fi and network refresh guide.

Windows 10 and Windows Server 2016 support dates

An operating system that no longer gets security updates is a vulnerability to record in the risk analysis. Microsoft ended Windows 10 support on October 14, 2025, and Windows Server 2016 extended support ends January 12, 2027. Practice management, imaging, and sensor software can be tied to specific Windows versions, so ask each software vendor which versions it supports before choosing a path. Dates below are the last day of each phase, checked November 2026.

Product or versionMilestone (Microsoft term)DateSource
Windows 10 (Home, Pro, Enterprise, Education)End of supportOctober 14, 2025Microsoft Lifecycle
Windows 10 Extended Security UpdatesESU end date, Year 1October 13, 2026Microsoft ESU FAQ
Windows 10 Extended Security UpdatesESU end date, Year 2October 12, 2027Microsoft ESU FAQ
Windows 10 Extended Security UpdatesESU end date, Year 3October 10, 2028Microsoft ESU FAQ
Windows Server 2016Mainstream end dateJanuary 11, 2022Microsoft Lifecycle
Windows Server 2016Extended end dateJanuary 12, 2027Microsoft Lifecycle
Windows Server 2016 Extended Security UpdatesCritical and Important updates for up to three yearsThrough 2030Microsoft Learn

See the Windows 10 end of support for businesses, the Windows Server 2016 replacement and the Windows Server 2016 Decision Snapshot.

Options for a PC or server that is out of support

Choose a path for each device. Isolating a device reduces exposure, but it does not make an unsupported system supported, so the risk analysis should still record it.

OptionWhat it involvesUsually fits when
Replace the hardwareA new PC or server on a supported Windows version, then the data and applications move overThe device is old, out of warranty, or cannot run a supported version
Upgrade in placeInstall a supported Windows version on the existing hardwareThe hardware meets Microsoft's requirements and the practice software supports the new version
Extended Security Updates as a bridgePaid Critical and Important security updates for a limited period. Windows 10 ESU covers Enterprise, Education, and Pro in commercial use. Windows Server 2016 ESU needs Software Assurance or an equivalent Server SubscriptionOne system cannot move yet and has a dated plan to move
Isolate, then replaceMove the device to its own network zone with tightly limited access while a replacement is plannedA vendor-locked imaging or equipment PC cannot be upgraded yet
RetireArchive the data under your retention rules and shut the system downThe system is no longer used day to day

Practice IT checklist

Use this list before a risk analysis update or an IT project. Days Dynamics is based in the Las Vegas valley, works on site across Las Vegas, Henderson, North Las Vegas, and Boulder City, and coordinates change windows around clinic hours. Days Dynamics provides planning and procurement coordination only. It does not provide legal, clinical, or compliance advice, so confirm requirements with your own advisors.

  • Inventory. List every computer, server, phone, imaging device, network device, and cloud service that touches patient data, with its operating system and support date.
  • Risk analysis. Update the written risk analysis and the plan to address what it finds.
  • Business associate agreements. Confirm one is in place with every vendor that stores or handles ePHI, such as email, backup, IT support, and the practice management vendor. Days Dynamics signs a business associate agreement when a project gives it access to systems that hold ePHI.
  • Accounts. Give every person a unique login, require multifactor authentication on email and remote access, and remove access on the day someone leaves.
  • Backups. Confirm backups cover every system with ePHI, one copy is offline or isolated, and a restore has been tested. Record the date.
  • Microsoft 365. Review sign-in settings, admin accounts, sharing, and how staff send patient information outside the practice.
  • Network. Separate guest Wi-Fi, clinical devices, imaging, phones, and payment terminals.
  • Unsupported systems. List every Windows 10 PC and Windows Server 2016 server, then pick a path and a date for each.
  • Endpoint protection. Confirm every device runs current protection, and decide who reviews alerts outside office hours.
  • Training. Train all staff on security policies and procedures, and keep a record.
  • Emergency plan. Write down how the practice keeps working if systems are down, then test it.

See the MDR vs EDR vs antivirus and the Days Dynamics in Las Vegas.

Frequently asked questions

Is this guide legal advice?

No. It summarizes what HHS, Microsoft, and Nevada law publish to help plan IT work. HIPAA obligations depend on your practice's facts, so confirm requirements with your own legal or compliance advisors.

Has HHS finalized the Security Rule update?

Not as of November 10, 2026. HHS issued the proposed rule on December 27, 2024, and states that the current Security Rule remains in effect. The Federal Register lists the January 6, 2025 proposed rule and no final rule.

Does Microsoft 365 make a practice HIPAA compliant?

No. Microsoft offers a Business Associate Agreement for in-scope services and states that using its services does not on its own achieve HIPAA compliance. The practice remains responsible for its compliance program and how it uses the services.

How often should a practice update its risk analysis?

The current Security Rule does not set a frequency, and HHS states the process should be ongoing. Review it whenever systems, vendors, or locations change.

Can we keep using Windows 10 PCs?

Microsoft ended Windows 10 support on October 14, 2025 and no longer provides security fixes for it without Extended Security Updates. Commercial ESU runs in yearly terms, with Year 2 ending October 12, 2027. Record remaining Windows 10 PCs in the risk analysis and set a date to replace or upgrade each one.

How long does Nevada require practices to keep patient records?

NRS 629.051 requires a custodian of health care records to keep patient records for 5 years after receipt or production, unless federal law sets a longer period, and bars destroying the records of a person who is under 23 on the date of the proposed destruction. Confirm how it applies to your practice with your advisors.

Does Days Dynamics work on site with practices in Henderson and North Las Vegas?

Yes. Days Dynamics works on site across Las Vegas, Henderson, North Las Vegas, and Boulder City, and coordinates change windows around clinic hours.

Plan practice IT with Days Dynamics

Send us your device list, the systems that hold patient data, and how backups run today. We will map each system to a path and a sequence that fits around clinic hours. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.

Sources

Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.

Planning this project now?

Turn the checklist into a plan

The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.