HIPAA-compliant IT for Westchester County practices.
White Plains, Yonkers, New Rochelle, Mount Vernon, Scarsdale, Mount Kisco, Tarrytown. A practice here answers to the HIPAA Security Rule — and, more often than anyone plans for, to more than one state at once.
Your records cross a state line. Your duties change when they do.
Westchester borders Connecticut to the east, sits a bridge away from New Jersey, and takes referrals in both directions from New York City. A practice in White Plains or Rye routinely holds records for patients who live in Greenwich and Stamford as easily as in Scarsdale. That is unremarkable clinically. It is not unremarkable legally.
HIPAA is federal and it is uniform. The Security Rule asks the same things of a practice in Mount Kisco as of one in Houston. Breach notification is where uniformity stops: those duties follow where your patients live, not where your office is.
- New York. The SHIELD Act reaches the private information of New York residents, and its notification duties attach whatever your HIPAA analysis concludes. The Attorney General enforces them.
- Connecticut. A practice holding records for Connecticut residents picks up Connecticut’s own notification statute and its own timeline, which is not the same as New York’s.
- New Jersey. Same again, with its own rules on who must be told and how quickly.
So the honest version of the question is not “are we HIPAA compliant.” It is: if something happened on Friday, could we say by Monday whose records were involved and which states that pulls in? Most practices we meet cannot, and it is not because they were careless. It is because nobody ever asked their IT to be able to answer that question.
What multiple states actually change in your IT.
Not the controls. The evidence. Four things have to be true that a single-state practice can get away with leaving vague:
Records mapped by residency
Knowing which systems hold records, and being able to break that down by where those patients live. Without it, every incident becomes a worst-case assumption about every state.
Logs that answer “whose”
Access logs that show not just that a record was opened but which record, retained long enough to answer a question asked months later by a regulator in a state you had not thought about.
Notification-ready evidence
The facts a notification decision needs — scope, timing, what was reachable — assembled in days rather than reconstructed under pressure while a clock runs in three jurisdictions.
Agreements that cover the referral path
A Business Associate Agreement with every vendor that can reach PHI, including the ones that arrived with a referral relationship rather than through procurement. Including us — we sign before we get access.
If you want the federal baseline rather than the multi-state layer on top of it, our Rockland County page sets out what the Security Rule asks of your IT and how the SHIELD safe harbour works for a HIPAA-covered practice. This page assumes that and goes to what crossing a border adds.
The first week, when more than one state is in scope.
The reason any of this matters is what happens after a bad Friday. A single-state practice has one set of questions to answer. A Westchester practice can have three, running in parallel, each on its own clock, and the answers all come from the same place: your logs and your records map.
Roughly how it goes, and where it usually stalls:
- Hours one to twenty-four — what was reachable. Not what was taken: what an account or a device could have reached. Practices with per-user accounts and real access logs can answer this in an afternoon. Practices with a shared login cannot answer it at all, and that single fact drives everything downstream toward the widest assumption.
- Day two to day four — whose records. This is where the residency map earns itself. “Four thousand patients” is not an answer a notification decision can use; “four thousand, of whom roughly three hundred are Connecticut residents and eleven are New Jersey” is. Without that split, counsel has to advise you as though every state with a claim was fully in scope.
- The rest of the week — the clocks. New York, Connecticut and New Jersey each set their own expectations on who must be told and how quickly. They do not line up neatly, and none of them pause while you reconstruct evidence.
None of that is exotic incident response. It is ordinary logging, ordinary account hygiene and a current map of where records live — done in advance, because the week it matters is the week you have no time to build any of it. When we say we keep evidence in a form you can hand over, this is the handover we mean.
What we run, day to day.
Honest about scope.
What we do not do.
We are not your lawyer and not your Privacy Officer, and we are emphatically not the people who should decide whether an incident is notifiable in Connecticut. We do not write your Notice of Privacy Practices, we do not sign off your risk analysis as though it were ours, and we will not tell you that buying managed IT makes a practice HIPAA compliant. It does not. We cover the technical half and we are precise about where that half ends — which, on a multi-state question, is earlier than most vendors admit.
Verify us before you talk to us.
Every claim on this page is checkable without speaking to a salesperson. Our technician verification page lets you confirm that whoever contacts you actually works here, before they touch a workstation holding PHI.
The questions practices actually ask.
Not for HIPAA, which is federal and applies the same either way. It changes breach notification, which follows patient residency rather than your address. Holding records for Connecticut residents brings Connecticut’s notification statute and timeline alongside New York’s, and the two are not identical. What that means practically is that your logging and your records map have to be good enough to tell the two populations apart. If they cannot, every incident has to be treated as if it touched everyone.
For SHIELD’s data-security requirements, a practice already subject to HIPAA is treated as compliant — that is in the statute. It does not follow that the two are identical: SHIELD defines private information more broadly than PHI, so you can hold New York private information HIPAA never contemplated, and the notification duties to New York residents attach regardless.
Yes, before any access. If we can reach systems holding PHI we are a business associate and a BAA is required. We also tell you which of your other vendors need one, which is usually a longer list than expected once referral-driven integrations are counted.
We are based in Warwick, New York, in Orange County, so Westchester is a drive rather than next door — we would rather say that than imply otherwise. The great majority of this work is remote by design. When something needs hands on it, we agree the window before we commit to it.
Request a HIPAA posture review.
We will tell you what we can see and what we cannot, before any agreement. If managed IT is not what your practice needs, we will say so.
