HIPAA From the IT Side: What Your IT Provider Does and What the Practice Still Owns
The question usually reaches the office manager in one of three ways. The cyber insurance renewal asks for the name of the practice's security official. A patient asks for a copy of their chart and X-rays by the end of the month. Or a dental breach makes the local news and the doctor leans into the front office: "We pay an IT company every month. Doesn't that take care of HIPAA?" Most offices have never written down who does what, so nobody can answer with confidence.
This guide is written from the IT side. It sets out who usually owns each HIPAA Security Rule standard (the practice, the IT provider or the software vendor) with the regulation section beside it, the evidence an IT provider can hand you, what the practice can't hand off, and the questions to put to your provider. For the step-by-step list, go to the HIPAA compliance checklist for dental practices; the dental cybersecurity checklist covers the controls themselves. If you want the technical side looked after, our page on HIPAA IT support for dental practices explains how that works. Nothing here is legal advice: each reading of the rule below ends with a question for your compliance adviser or healthcare attorney, and that is deliberate.
For HIPAA compliance in a dental office, your IT provider can set up and document the technical safeguards: unique logins, MFA, encryption, patching, backups and audit logs. It can't make the practice compliant. The practice still owns its risk analysis, policies, training, named security and privacy officials, patient requests and business associate agreements. Confirm the split with your compliance adviser.
- An IT provider can set up and document technical safeguards such as unique logins, MFA, encryption, patching, backups and audit logs, but it can't make the practice compliant.
- The practice still owns its risk analysis, policies, training, named security and privacy officials, patient access requests and business associate agreements with every vendor.
- Since HITECH, the Security Rule's safeguard and documentation sections apply to business associates too (42 U.S.C. 17931): your IT provider has its own duties, but it does not carry yours.
- Ask your IT provider for dated evidence on a schedule: MFA enrollment, user lists, patch and encryption status, backup history with a tested restore, admin access and log retention.
- HHS runs no certification programme for HIPAA; in 2003 it said it did not intend to create certification criteria (68 FR 8351-8352).
- Keep Security Rule documentation for six years (45 CFR 164.316(b)(2)), and confirm how any reading applies to your practice with your compliance adviser.
In this guide
- Does HIPAA apply to your dental practice?
- Who owns what in HIPAA IT compliance: the practice, the IT provider or the software vendor?
- What can your IT provider prove for you?
- What can't the practice hand off to IT?
- Can an IT provider certify your practice under HIPAA?
- What is the IT side of a security risk analysis?
- What to ask your IT provider about HIPAA responsibilities
- Where Legend Networking fits in the matrix
- Print this: the one-page HIPAA responsibility sheet
- Frequently asked questions
- The bottom line
Does HIPAA apply to your dental practice?
For most dental practices, yes. HIPAA covers a health care provider "who transmits any health information in electronic form in connection with a transaction" that HHS has set a standard for, such as an insurance claim or an eligibility check. A practice that files electronic claims is very likely a covered entity. Confirm your own status with your compliance adviser.
That quotation is from the definition of "covered entity" in 45 CFR 160.103, read on 1 November 2026. The American Dental Association's HIPAA 20 Questions puts the same test in dental terms: "A dental practice becomes a HIPAA covered entity when it submits a claim electronically", or when it runs another HIPAA-regulated electronic transaction, "such as an eligibility inquiry".
| What the practice does | What the ADA's guidance says (read 1 Nov 2026) |
|---|---|
| Sends insurance claims electronically, directly or through practice software | The practice "becomes a HIPAA covered entity" |
| Checks eligibility or claim status electronically | Also a HIPAA-regulated electronic transaction |
| Files paper claims, but a billing service converts them and submits them electronically | "HIPAA also reaches entirely paper dental offices" that do this |
| Faxes paper claims from a paper-to-paper (non-digital) fax machine, nothing else | Does "not, by itself" make the practice a covered entity |
The last row is rare in 2026, and other laws can still apply to a practice that falls outside it. Treat the table as a starting point for the conversation with your adviser, not as the answer.
One more definition saves confusion later. Electronic protected health information (ePHI) is the patient information the Security Rule protects when it is held or sent electronically: the chart, the X-rays and intraoral images, the schedule, insurance details and billing records. Almost everything an IT provider touches in a dental office is either ePHI or a system that holds it.
Who enforces the HIPAA Security Rule?
Enforcement sits with the HHS Office for Civil Rights (OCR). The Secretary of HHS delegated that authority to the OCR Director in a notice dated 27 July 2009 (74 FR 38630, published 4 August 2009), including the authority "to make decisions regarding the interpretation and enforcement" of the standards. State attorneys general can also bring civil actions under the HIPAA statute's section headed "Enforcement by State attorneys general" (42 U.S.C. 1320d-5(d)). How either would apply to a particular practice is a question for your attorney.
The same law reaches your IT provider. Since the HITECH Act, the Security Rule's administrative, physical, technical and documentation sections "shall apply to a business associate of a covered entity in the same manner that such sections apply to the covered entity" (42 U.S.C. 17931). So an IT provider that handles your ePHI has its own duties. It does not carry yours.
Who owns what in HIPAA IT compliance: the practice, the IT provider or the software vendor?
The practice owns the decisions, the people and the paperwork. A contracted IT provider usually owns the technical work it has agreed to do and the reports that prove it. Software and cloud vendors own the security of the systems they run for you. The matrix below shows a common split, standard by standard, with the evidence each one leaves behind.
NIST's guide to the Security Rule says it plainly: "Each regulated entity (i.e., covered entity or business associate) is responsible for its own Security Rule compliance and violations" (NIST SP 800-66 Rev. 2, February 2024). Your IT provider answers for its part; the practice answers for the whole.
How to read the matrix
- Standard is the requirement and its section of 45 CFR Part 164. "Required" and "Addressable" are the regulation's own labels for implementation specifications; a standard without a label is a standard.
- Practice owns is work no contract moves off the practice.
- IT provider (if in your agreement) is what an IT provider typically does when the contract says so. If your agreement doesn't list it, assume nobody is doing it until someone confirms otherwise.
- Software or cloud vendor covers the practice-management system (PMS), imaging, email and backup services that hold ePHI on their own servers.
- Evidence to keep is what you would hand an auditor, an investigator or your insurer.
Administrative safeguards (45 CFR 164.308)
| Standard (section) | Practice owns | IT provider (if in your agreement) | Software or cloud vendor | Evidence to keep |
|---|---|---|---|---|
| Risk analysis, (a)(1)(ii)(A), Required | Commissions it, decides what risk is acceptable, signs it | Technical inventory, scans and a gap list for the systems it manages | Answers security questions about its own platform | Dated, signed risk analysis and the asset inventory behind it |
| Risk management, (a)(1)(ii)(B), Required | Approves the plan, the budget and the deadlines | Carries out the technical fixes it is contracted for and reports progress | Fixes issues inside its own platform | Remediation log: item, owner, due date, date closed |
| Sanction policy, (a)(1)(ii)(C), Required | Writes and applies it | Supplies log evidence when asked | None | Written policy and sanction records |
| Information system activity review, (a)(1)(ii)(D), Required | Decides who reviews logs and how often, and signs the review | Turns logging on, keeps it, produces the reports | Provides the PMS audit trail | Review notes with date and reviewer |
| Assigned security responsibility, (a)(2) | Names its security official in writing | Supports that person with reports and advice | None | Written designation |
| Workforce security and termination, (a)(3), termination Addressable | Tells IT the same day someone leaves; approves who needs access | Disables accounts, remote access and MFA devices; confirms in writing | Deactivates users in hosted systems on request | Offboarding tickets with dates |
| Information access management, (a)(4) | Decides who sees what, by role | Builds the groups and permissions | Supplies role settings in the PMS | Access list, reviewed and signed |
| Security awareness and training, (a)(5) | Runs training and keeps attendance records | Phishing tests, malware protection, log-in monitoring, MFA and passwords tools | Vendor training material, where offered | Training records; phishing-test reports |
| Security incident procedures, (a)(6), response Required | Owns the plan and every decision, with counsel and insurer | Detects, contains and documents the technical facts | Reports incidents to you under its contract | Incident log and the technical timeline |
| Contingency plan, (a)(7), backup, recovery and emergency mode Required | Decides what must keep running and how the office works on paper | Runs dental data backup and recovery and restore tests | Backs up the data it hosts; states where and for how long | Backup history and the last restore test |
| Evaluation, (a)(8) | Commissions a periodic evaluation | Supplies the technical findings | Shares its own audit reports, where offered | Evaluation report |
| Business associate contracts, (b)(1) | Signs an agreement with every vendor that handles ePHI | Signs its own agreement and binds its subcontractors | Signs its own agreement | Vendor register with signed agreements |
Physical, technical and documentation safeguards (45 CFR 164.310, 164.312, 164.316)
| Standard (section) | Practice owns | IT provider (if in your agreement) | Software or cloud vendor | Evidence to keep |
|---|---|---|---|---|
| Facility access controls, 164.310(a) | Locks, keys and who can reach the server closet | Places servers and network gear in a lockable space | Secures its data centers | Key and door-code list |
| Workstation use and security, 164.310(b)-(c) | Screen placement and front-desk habits | Screen locks and device settings | None | Workstation standard |
| Device and media controls, 164.310(d), disposal and re-use Required | Approves disposal of old drives and computers | Wipes or destroys drives and records it | Disposes of its own media | Disposal records by device |
| Unique user identification, 164.312(a)(2)(i), Required | Bans shared logins in policy and in practice | Creates one account per person | PMS supports named users | User list with last sign-in |
| Emergency access, 164.312(a)(2)(ii), Required | Decides who may break the glass | Sets up and documents the emergency route | Offers an emergency-access feature | Emergency-access procedure |
| Automatic logoff and encryption, 164.312(a)(2)(iii)-(iv), Addressable | Decides the timeout that works chairside | Configures logoff and encrypts laptops, servers and backups | Encrypts data on its platform | Encryption status report |
| Audit controls, 164.312(b) | Decides how long logs are kept | Configures logging and retention | Records PMS activity | Log-retention setting and a sample |
| Integrity, 164.312(c) | Reports suspected changes to records | Protects files and databases from alteration | Protects the hosted database | Integrity checks in backup reports |
| Person or entity authentication, 164.312(d) | Requires MFA where the risk analysis calls for it | Enrolls staff in MFA and reports gaps | Offers MFA in its product | MFA enrollment report |
| Transmission security, 164.312(e) | Chooses how records go to labs, specialists and patients | Configures encrypted connections and HIPAA email | Encrypts its own connections | Email and remote-access settings |
| Documentation, 164.316(b), 6-year retention Required | Keeps policies and records for 6 years | Supplies dated reports for the file | Supplies its documentation on request | One evidence folder, by year |
Your contracts and your compliance adviser decide who is responsible for what in your practice. Use the matrix to find the gaps: any row where nobody's name fits is the place to start.
The matrix is also the fastest way to read your current IT agreement. Go down the IT provider column and tick each row your contract names. Most practices find two or three rows that everyone assumed were covered and nobody had agreed to. To see how Legend approaches the IT side of those rows, read about HIPAA IT support for dental practices.
Required and addressable: why the IT column isn't a menu
"Addressable" does not mean optional. Under 45 CFR 164.306(d)(3), the practice must "Assess whether each implementation specification is a reasonable and appropriate safeguard in its environment", put it in place if it is, and "Document why it would not be reasonable and appropriate" if it isn't, adopting an equivalent measure where that is reasonable. The same section lists the factors to weigh, including "The size, complexity, and capabilities" of the practice and "The costs of security measures."
That decision sits with the practice. An IT provider can tell you what encrypting every laptop involves, or what a shorter screen-lock timer will do to chairside charting. It shouldn't be the one deciding that a safeguard doesn't fit, and the written reason belongs in the practice's file. Ask your compliance adviser to review any "not reasonable and appropriate" decision before you rely on it.
How the split moves with your setup
The rows stay the same whichever software you run, but the columns shift. When the PMS runs on a server in your office, your IT provider carries most of the technical rows. When it runs in the vendor's cloud, the vendor takes the platform and the practice and its IT provider keep the people, devices and settings.
| Setup | What the vendor runs | What stays with the practice and its IT provider |
|---|---|---|
| Server-based PMS in the office (for example Dentrix, Eaglesoft or Open Dental on a local server) | The software itself and its updates | The server, Windows, the network, backups, encryption, logins and every workstation |
| Cloud PMS | The hosting, the database, platform security and its own backups | User accounts and roles, MFA, the computers and network that reach it, offboarding, local imaging and the agreement with the vendor |
| Microsoft 365 email and files | The data centers, physical network and service platform | "For all cloud deployment types, you own your data and identities" (Microsoft): accounts, access rules, MFA and devices |
| Imaging software with local storage | The imaging application | The imaging PC or server, its backups and the network share |
Microsoft's shared responsibility page (dated 24 August 2026) lists four things a customer keeps in every cloud model: data, endpoints, accounts and access management. Practice software vendors say much the same about their own products. Open Dental's HIPAA page states that "The responsibility for HIPAA compliance falls to each dental office" and "It is up to you to make sure your practice is secure." Moving to the cloud moves some rows to the vendor. It doesn't move the practice's name off the top of the page.
What can your IT provider prove for you?
A good IT provider can hand you dated reports showing the technical safeguards are working: who has MFA, which machines are patched and encrypted, when backups ran and when one was last restored, who has admin access, and how long logs are kept. Ask for them on a set schedule and file them. Evidence you never asked for doesn't exist when someone else asks.
| Evidence | What it shows | Standard it supports | How often to ask |
|---|---|---|---|
| MFA enrollment report | Who has MFA on email, remote access and admin accounts, and who doesn't | 164.312(d) | Quarterly |
| User list with last sign-in and disabled accounts | No shared logins; leavers are switched off | 164.312(a)(2)(i), 164.308(a)(3) | Quarterly, and after every departure |
| Offboarding confirmations | Date and time each leaver's access was removed | 164.308(a)(3)(ii)(C) | Every departure |
| Patch status report | Which computers and servers are behind on updates, and why | 164.308(a)(1)(ii)(B) | Monthly or quarterly |
| Endpoint protection export | Every device is protected; detections and what was done | 164.308(a)(5)(ii)(B) | Quarterly |
| Backup job history and the last restore test | Backups run, and a restore was tested end to end | 164.308(a)(7)(ii)(A)-(B) | Monthly history; restore test at least yearly |
| Firewall and remote-access summary | What can reach the office network from outside, and how it is secured | 164.312(e), 164.308(a)(1)(ii)(B) | Twice a year, and after any change |
| Encryption status | Laptops, servers and backup copies that are encrypted, and any that aren't | 164.312(a)(2)(iv) | Twice a year |
| Admin access list | Who holds administrator rights, including the IT provider's own staff | 164.308(a)(4) | Twice a year |
| Audit-log retention setting and a sample | Logs exist, are kept, and can be read | 164.312(b), 164.308(a)(1)(ii)(D) | Yearly |
| Device inventory and disposal records | What holds ePHI, and what was wiped or destroyed | 164.310(d) | Yearly, and at every disposal |
| Security incident log | What happened, when, and what was done | 164.308(a)(6)(ii) | As it happens, reviewed quarterly |
The frequencies are a practical rhythm, not a rule; your risk analysis and your adviser set yours. They line up with the same evidence your cyber insurer asks for, so one quarterly pack can serve both. Keep it in a single folder by year; when it's time to prepare for a HIPAA audit, most of the technical file already exists.
What a useful evidence pack looks like
A useful report is dated, names the systems it covers, and shows exceptions, not only green ticks. "All devices patched" tells you little. "All but two devices current; the two imaging PCs held back until the imaging vendor approves the update, review date set" tells you what is true and who is acting on it. If a report only ever shows 100%, ask what it leaves out.
The restore test deserves its own line. A backup job that reports success shows that a copy was attempted. A tested restore shows the practice could run from it. If you want the method, the dental backup and disaster recovery checklist covers it.
What evidence can't show
Reports prove settings. They don't prove that staff know not to send a full chart to a personal email address, that the policy on shared logins is enforced at the front desk on a full schedule, or that the risk analysis reflects decisions the practice actually made. Those parts of the file come from the practice, which is the next section.
What can't the practice hand off to IT?
The practice can't hand off its decisions or its people. It signs the risk analysis, names its security and privacy officials, writes and enforces its policies, trains and sanctions its staff, answers patients' requests for their records, signs an agreement with every vendor that handles ePHI, and decides with counsel whether an incident must be reported. IT supports each one.
The risk analysis decision
The regulation asks for "an accurate and thorough assessment of the potential risks and vulnerabilities" to ePHI (45 CFR 164.308(a)(1)(ii)(A)). Your IT provider can contribute most of the technical inventory and the gap list. The practice decides which risks to fix first, which to accept and why, and signs the result. The proposed update to the Security Rule would add more detail to this work; for where that stands, see where the HIPAA Security Rule update stands.
Naming the security official and the privacy official
The Security Rule says the practice must "Identify the security official who is responsible for the development and implementation of the policies" (164.308(a)(2)). The Privacy Rule adds that "A covered entity must designate a privacy official" and a contact person for complaints, and must document both designations (45 CFR 164.530(a)). In many small offices one person holds both roles, often the office manager. Whether someone outside the practice may hold either role is a question for your compliance adviser. Whoever holds it needs the standing to make the team follow the policy.
Policies, training and sanctions
The Privacy Rule requires the practice to "train all members of its workforce" on its policies (164.530(b)), and the Security Rule requires a security awareness and training program and a sanction policy. An IT provider can run phishing tests and send security reminders. It can't decide what happens when a team member breaks the policy, and it can't make the training stick at the front desk. Many of the common HIPAA violations in dental practices are people and process failures, not technical ones.
Patient requests for their records
Patients have "a right of access to inspect and obtain a copy" of their health information, and the practice "must act on a request for access no later than 30 days after receipt of the request", with one possible 30-day extension (45 CFR 164.524). IT can make the export of a chart and its images easy. The response, its format and its timing belong to the practice; ask your adviser how the rule and any state requirements apply to your requests.
An agreement with every vendor, not only IT
The practice may let a business associate handle ePHI only with the written assurances the rule describes (164.308(b)(1)). That means every vendor that holds or reaches patient information: the PMS and imaging vendors, email and file hosting, the backup service, the clearinghouse, phone and fax services that store voicemail or faxes, the patient-forms and reminders platform, shredding, and any AI tool staff use with patient details (see the HIPAA risk of free AI tools). Keep one register: vendor, what it touches, agreement date, renewal date. What the agreements must say is covered in a separate guide, and the wording itself is a job for your attorney.
Incident and breach decisions
The agreement must require the business associate to "Report to the covered entity any security incident of which it becomes aware" (45 CFR 164.314(a)). After that report, the practice decides, with counsel and its insurer, whether an incident is a reportable breach and who must be told. IT gathers the technical facts; it doesn't make that call. State rules add their own clocks; our state guides cover examples such as the dental breach rules in DC, Maryland and Virginia and Texas notification clocks for Houston practices. Neither is a substitute for your attorney.
Keeping the records for six years
The Security Rule says to "Retain the documentation … for 6 years from the date of its creation or the date when it last was in effect, whichever is later" (45 CFR 164.316(b)(2)(i)); the Privacy Rule has a matching six-year rule in 164.530(j). Your IT provider's reports go into that file, but the file is the practice's. If you change IT providers, the evidence must stay with you: collect it before the outgoing provider's access ends, and ask your attorney how that provider's business associate agreement handles the return or destruction of ePHI. The rest of the handover is covered in how to switch dental IT providers without downtime.
Can an IT provider certify your practice under HIPAA?
No. There is no government certification programme for HIPAA, for practices or for IT providers. When it published the Security Rule, HHS said it would "not assume the task of certifying software and off-the-shelf products" and did "not intend to create certification criteria". Treat any vendor's badge as marketing, and ask what evidence sits behind it.
Those quotations are from the Security Rule's 2003 final rule (68 FR 8334, pages 8351 to 8352, read 1 November 2026). The same discussion says that "Evaluation by an external entity is a business decision to be left to each covered entity." An outside assessment can be useful. It is still the practice's assessment, of the practice's program, at a point in time.
Large vendors say the same. Microsoft's HIPAA and HITECH page (updated 11 September 2026) states: "There's currently no certification standard that the Department of Health and Human Services approves to demonstrate compliance with HIPAA or the HITECH Act by a business associate." It also answers the question most practices are really asking: using its services "doesn't on its own achieve HIPAA compliance."
Documented safeguards
A written list of the technical safeguards in place for your practice, mapped to the Security Rule standards in the matrix above.
Evidence on a schedule
Dated reports you can file: MFA, patching, encryption, backups and restore tests, admin access and log retention.
A business associate agreement
A signed agreement that sets out how the provider protects your ePHI, binds its subcontractors and reports incidents to you.
Honest limits
A clear statement of which rows of the matrix the provider does and which stay with the practice.
What is the IT side of a security risk analysis?
The IT side of a risk analysis is the inventory and the technical findings: every system that holds or sends ePHI, how data moves between them, which safeguards are in place, and where the gaps are. The practice then rates the risks, decides what to fix and when, and signs the analysis. Most of the hours are IT's; the decisions are the practice's.
NIST's guide describes a risk assessment in seven steps and notes that "Small, regulated entities may find benefit in using the HHS Security Risk Assessment (SRA) Tool" (NIST SP 800-66 Rev. 2, section 3). The flow below follows those steps and shows who usually does each one.
Seven steps, and who does each one
- 1Map where ePHI livesIT leadsList every system that creates, receives, stores or sends patient data, including cloud services, phones and fax, and each device that can reach them.
- 2Trace how data movesIT and practiceFollow a chart and an X-ray from check-in to the lab, the specialist, the insurer and the backup, and note where data leaves the office.
- 3Identify likely threatsIT leadsPhishing, stolen laptops, failed disks, ransomware, a departing employee who keeps access, and outages that stop the schedule.
- 4Find the weaknessesIT leadsScan for missing patches, unencrypted devices, shared logins, open remote access and backups that have never been restored.
- 5Rate likelihood and impactpractice decidesIT explains each finding in plain terms; the practice rates how likely it is and what it would do to patients and the business.
- 6Decide what to fix and whenpractice decidesEach gap gets an owner, a due date and a decision: fix, reduce, or accept with a written reason.
- 7Document and signpractice signsThe analysis, the inventory and the remediation plan go into the six-year file, dated and signed by the security official.
The free SRA Tool from ONC and HHS (version 3.7; page updated 18 September 2026) is built for this: "The target audience of this tool is medium and small providers." The page is also clear about its limits: "Use of this tool is neither required by nor guarantees compliance with federal, state or local laws." One workable approach is to fill it in with your IT provider in the room for the technical sections and the security official answering the rest. Whoever helps, the practice or its adviser signs off.
The inventory: systems most dental offices forget
| System | Why it holds or reaches ePHI | Who can answer for it |
|---|---|---|
| Practice-management database | Charts, schedule, insurance, billing | IT provider (server) or PMS vendor (cloud) |
| Imaging PCs, sensors and the image store | X-rays, intraoral photos, 3D scans | IT provider and the imaging vendor |
| Email and file sharing | Referrals, lab slips, attachments | IT provider; email host |
| Backup copies, on site and off site | A full second copy of everything | IT provider; backup service |
| Phones, voicemail and fax | Messages and faxed records with patient details | Phone or fax service provider |
| Patient forms, reminders and payments | Medical histories, contact and card details | Each platform's vendor |
| Laptops, tablets and staff phones | Remote access, email, photos | IT provider and the practice |
| Copiers and scanners with internal drives | Copies of every page scanned | IT provider; leasing company at return |
| AI tools staff use | Anything pasted into them | The practice, then the tool's vendor |
What to ask your IT provider about HIPAA responsibilities
Take the matrix to your next review and work through these questions. Clear, written answers are a good sign; "don't worry, we handle HIPAA" is not an answer.
The contract
- Will you sign a business associate agreement with us before you touch patient data, and do your subcontractors sign one with you?
- Which rows of the responsibility matrix does our agreement cover, and which stay with us?
- What happens to our data and our evidence if we end the contract?
Evidence
- Which reports will we receive, and how often: MFA, patching, encryption, backups, admin access, log retention?
- When was our last restore test, what did you restore, and how long did it take?
- Will you help with the technical sections of our risk analysis, and in what form will the findings come?
Access
- Who on your team has administrator access to our systems, and how is that access logged and reviewed?
- How do you remove a leaver's access when we tell you, and how do you confirm it?
- Which remote-access tools do you use on our network, and how are they secured?
Incidents and backups
- How would you support us during a security incident, and what would you document for us?
- When you detect a security incident on our systems, by what route do we hear about it, and what does the first report include?
- Where are our backups, who can delete them, and is at least one copy out of reach of an attacker on our network?
Where Legend Networking fits in the matrix
With 22+ years in dental IT (since 2004), Legend Networking has served over 3,500 practices since 2004. The service pairs 24/7 monitoring with in-house engineers (no outsourced first-level triage), and the helpdesk is staffed 24/7 at 1-800-794-1588, one general number. Legend's role is on the IT side, where it supports HIPAA compliance readiness; the practice's own decisions, policies and sign-offs stay with the practice, as this guide describes.
Ian Lynch, who wrote this guide, brings 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. On Google, practices rate Legend 4.8 across 173 reviews. Put the same questions to us that you would put to any IT provider, and hold us to written answers.
Print this: the one-page HIPAA responsibility sheet
Print this for the office manager's binder and fill in a name on every line. A blank line is a gap to raise at your next IT review.
Who owns it in our practice (fill in a name)
- Security official, named in writing: ________
- Privacy official and complaints contact, named in writing: ________
- Risk analysis: last signed on ____ by ________; technical inventory by ________
- Remediation plan owner: ________; next review date: ____
- Staff training: last session ____; records kept by ________
- Leaver process: who tells IT, and who confirms access was removed: ________
- Vendor register and business associate agreements kept by: ________
- Quarterly evidence pack (MFA, patching, encryption, backups, admin access) received from: ________
- Last tested restore: ____; tested by ________
- Incident first call: IT provider ________; insurer ________; attorney ________
- Six-year documentation folder kept by: ________
Frequently asked questions
Does HIPAA apply to dentists?
For most dentists, yes. A dental practice becomes a covered entity when it conducts a standard transaction electronically, such as submitting an insurance claim or checking eligibility, either directly or through practice software. A practice that never runs these transactions electronically, directly or through a billing service, may fall outside it. Your compliance adviser can confirm your status and explain what other laws apply.
Who is responsible for HIPAA compliance in a dental office?
The practice is, as the covered entity. It names a security official and a privacy official to lead the work, and the owner remains accountable for the result. Vendors that handle patient data, including the IT provider, carry their own duties under the Security Rule and their agreements with you, but those duties sit alongside the practice's, not in place of them.
Who enforces the HIPAA Security Rule?
The Office for Civil Rights at the U.S. Department of Health and Human Services enforces it, under a delegation of authority dated July 2009. OCR can investigate, run compliance reviews and impose civil money penalties. State attorneys general can also bring civil actions under the HIPAA statute. How enforcement could apply to a specific practice is a question for your attorney.
Can our IT company do our HIPAA risk analysis?
It can do much of the technical work: the inventory of systems that hold patient data, vulnerability scans, and a list of gaps with suggested fixes. The practice still has to rate the risks, decide what to fix and what to accept, and sign the analysis. Treat the IT company's report as an input to the practice's risk analysis, not the analysis itself.
Does cloud dental software take care of HIPAA for us?
No. A cloud vendor secures its own hosting and platform, and should sign an agreement with you, but the practice keeps the accounts, MFA, devices, office network, offboarding and policies. Even large cloud providers say their services alone don't achieve compliance. Our guide to cloud practice software covers what changes when you move.
Does the government certify dental IT providers for HIPAA?
No. HHS runs no certification programme for HIPAA, and when it issued the Security Rule it said it did not intend to create certification criteria. A badge or seal on a vendor's website is marketing. Ask instead for the safeguards in writing, regular evidence reports and a signed business associate agreement, and be cautious with any provider that claims an official approval.
What HIPAA records should a dental practice keep, and for how long?
Keep Security Rule policies, procedures and records of actions and assessments for six years from when they were created or last in effect, whichever is later. That includes the risk analysis, training records, the vendor register and the IT provider's evidence reports. Patient-chart retention is a separate question set largely by state rules, so confirm it with your compliance adviser.
Does the proposed HIPAA Security Rule update change who is responsible?
Not today. The proposal published on 6 January 2025 is still a proposal; the federal regulatory agenda lists it under long-term actions with final action projected for July 2027. The current rule stays in force meanwhile. See where the HIPAA Security Rule update stands for what the proposal would add.
Can our office manager be the HIPAA security official?
Often, yes. The rule requires the practice to identify one security official responsible for its security policies and procedures; it doesn't say which job title must hold the role. In many small offices the office manager is also the privacy official. Choose someone with the authority to make policies stick, document the designation, and check the choice with your compliance adviser.
Are shared logins on front-desk computers allowed under HIPAA?
The Security Rule requires a unique name or number for identifying and tracking each user, so a shared login for the practice software defeats the audit trail. Fast user switching, badge or PIN sign-in and shorter screen-lock timers make named logins workable at a busy front desk. Ask your IT provider to set them up and your adviser to review any exceptions.
The bottom line
The quiet weeks are the right time to find out which rows of the matrix are really covered: before the insurance renewal, the patient request or the next breach headline. Ask for a Free Dental IT Assessment. It looks at your computers, software, network security, backups and performance, and you receive written findings and prioritized recommendations to file with your risk analysis.

