173,853 Individuals and the Line You Didn't Draw: What the Atlantic Digestive Specialists Breach Asks About Where an Incident's Boundary Gets Set
A small practice may have no dedicated IT team. In that environment, it is easy to think of “the data” as only the clinical record. But an incident’s boundary is not set by what a practice instinctively classifies as medical information. It depends on what information is actually held on the network and in the records that network reaches.
That distinction matters to the financial survival of a practice. Gaps in access records, staff training, incident reporting, risk analysis, or written policies can leave leaders struggling to explain what information was in scope and what safeguards were in place. The possibility of crushing HIPAA penalties and the burden of responding to an incident can threaten a practice’s ability to keep its doors open. A breach-register listing, however, is a submission, not a finding of a violation or a fine.
What the practice reported
Atlantic Digestive Specialists, a New Hampshire gastroenterology physician group, reported the following events:
In March 2026, the practice was alerted to suspicious activity in its network.
The investigation determined that some information may have been viewed or acquired without authorization between March 16, 2026 and March 17, 2026.
The practice's review of all potentially affected information concluded in August 2026.
On September 8, 2026, it arranged for notification to potentially affected individuals.
Notification began on September 30, 2026, and the breach was submitted to the register on that date.
These are separate facts reported by the practice; they are not a basis for drawing conclusions about anyone's conduct.
The HHS OCR breach portal register row lists exactly 173,853 individuals. The practice’s own notice does not give a count.
The practice’s notice said the following information may have been involved: first and last name; Social Security number; driver's license or state identification number; date of birth; financial account information; payment card information; alien registration number; taxpayer identification number; passport number; clinical information; diagnosis; medical history; medical record number; medical treatment/procedure information; mental or physical condition; prescription information; Medicaid/Medicare number; medical cost; medical dates of service; medical provider name; patient account number; health insurance policy-related number; username and password information; and digital/electronic signature.
The phrase “may have been involved” matters. The notice’s list does not say that every item applied to every individual.
The notice also said the practice took measures to secure its network, initiated an investigation, and engaged cybersecurity experts. It listed a call center at 1-866-200-0962, Monday through Friday 9:00 am - 9:00 pm Eastern Time, excluding U.S. holidays.

The boundary follows the information, not the label
The range in the notice is the point. It extends from diagnosis, treatment, and prescription information to payment card and financial account information, taxpayer identification and passport numbers, and username and password information. That range challenges the assumption that a practice can define the scope of an incident by asking only which clinical records were involved.
A useful starting point is a current written record of what information the practice holds, where it sits, and who can reach it. That record can help a practice answer scope questions from existing documentation rather than relying entirely on memory or reconstructing the environment under pressure. The HHS Security Rule guidance and HHS risk analysis guidance provide authoritative resources for thinking about safeguards and risk analysis.
In practical terms, leaders should be able to ask:
What categories of information does the practice hold?
Which systems, records, or locations contain that information?
Which roles and individual accounts can reach those systems?
How are access changes and departures recorded?
Username and password information was among the categories the practice’s notice said may have been involved. That makes access records and offboarding documentation relevant to the boundary question. When a team member changes roles or leaves, a documented process for reviewing and recording access changes helps keep the practice’s account of access current.
A record does not resolve every incident question. Systems change, and the facts of an event must be investigated. But having a written baseline gives the practice a clearer place to begin: what information exists, where it is maintained, and which access pathways need review.

A survival tool for documenting safeguards
Veri-Hub is a Security and Access Management System. It is a documentation and workflow management system for organizing key administrative safeguards; it cannot guarantee compliance, prevent every incident, or determine an audit outcome.
For small practices, the goal is practical: maintain a consistent record of core security work without adding unnecessary complexity. Veri-Hub supports these workflows in the following order:
Access Tracking: Document employee access levels and track changes over time.
Incident Reporting: Record and manage incident reports and related follow-up.
Awareness Training: Assign and monitor annual cyber-awareness training.
Risk Analysis: Maintain records of risk analysis activities.
HIPAA-Aligned Policies: Keep professional security policies organized and track related review and acknowledgment workflows.
Audit Trail: Support audit trail and regulatory documentation.
A dependable process gives managers a clearer view of what has been recorded and what still needs attention. It can also reduce the scramble to locate scattered records when leadership needs to explain its safeguards. The intended transformation is not a promise that incidents will not happen. It is more organized work, greater visibility into administrative responsibilities, and more peace of mind from knowing key records have a defined home.
I'm Darlene Collins, RN, BSN, Certified Cybersecurity & Risk Expert, founder and CEO of Veri-Se3ure. I have more than 30 years in healthcare and more than 25 years implementing EHR systems, including Epic. We live this experience.
Learn more about Veri-Se3ure, or Book Online to discuss a practical approach for your practice.
Sources
Veri-Hub cannot guarantee compliance, prevent every incident, or determine an audit outcome. Every practice's systems, risks, and responsibilities are different.
Supports documentation. No guarantee of compliance or an audit outcome.
This content is provided for informational purposes only and does not constitute legal advice. Organizations should consult qualified legal and cybersecurity professionals regarding their specific HIPAA responsibilities.



Comments