HIPAA-compliant IT for Teaneck practices.
Teaneck, Englewood, Hackensack, Bergenfield, New Milford. Holy Name Medical Center is in the township and Hackensack University Medical Center is the next town over — which means the practices here carry an IT problem a standalone office never has.
A practice beside a hospital has a different problem.
Most HIPAA guidance imagines a self-contained practice: your network, your records, your vendors. Teaneck is not that. A practice here is very likely affiliated — admitting privileges, a shared specialty group, a referral pathway, a credentialing portal, an imaging or lab interface that reaches into a hospital system and back out again.
Every one of those is a door, and the doors were installed by different people at different times for good clinical reasons. The result is a practice whose real attack surface is not the one on its network diagram.
The question that catches people out is not technical, it is definitional: who is a business associate of whom? A hospital is not your business associate because you refer to it. A billing company reaching your records is. A specialty group sharing a practice-management system may be, in one direction and not the other. We have seen the same practice hold a BAA with its cloud vendor and none with the group whose staff log into its scheduling system daily.
Where affiliated access actually goes wrong.
Four patterns, and we have unpicked all four more than once:
Hospital access on a practice device
A clinician reaching a hospital system from a practice laptop that the practice manages and the hospital does not. Both parties assume the other is securing it.
Portal logins shared by role
One credentialing or imaging login used by whoever is covering. Convenient, and the reason “who retrieved this study” sometimes has no answer.
Leavers with two sets of accounts
Staff offboarded from the practice and still active in an affiliated system, because nobody owns the second list. This is the most common finding we make.
Interfaces nobody owns
A lab or imaging feed configured years ago by a vendor who has since changed hands, still moving PHI, still trusted, still unreviewed.
New Jersey adds its own layer: the state’s breach notification law applies to records of New Jersey residents, and a Teaneck practice two miles from the George Washington Bridge very often holds records for New York residents as well — which pulls the New York SHIELD Act in alongside it. Our Bergen County page covers the county-level picture; this one is about what proximity to a hospital changes.
The questionnaire you will eventually be sent.
Being affiliated cuts both ways. The access is useful; it also makes your practice part of somebody else’s risk assessment. Sooner or later a hospital compliance office, a specialty group’s IT function or an insurer sends a security questionnaire, and the practice has a fortnight to answer it.
They are not exotic documents. They ask the same handful of things, and the honest answer is either immediate or it is a scramble:
- Is multi-factor authentication enforced for everyone? Not available — enforced. “For most staff” is a finding.
- Is data encrypted at rest and in transit? Including the laptop that goes home and the backup sitting in a cupboard.
- How quickly are systems patched, and how do you know? A number you can evidence, not an intention.
- How long do you keep access logs? Long enough to answer a question raised months later, which is longer than most defaults.
- Who holds administrative rights? A list, including every vendor, and ideally a short one.
- What is your offboarding process? This is where affiliated practices come unstuck, because the honest answer covers systems the practice does not administer.
- Who do we contact at 2am? A name and a route, agreed before it is needed.
We keep those answers current as a matter of course, because assembling them reactively is how a practice ends up either guessing or overstating — and an overstated questionnaire answer is a worse position than an honest gap with a plan against it. When the questionnaire arrives, the work is already done and you are reading it rather than writing it.
What we run, day to day.
Honest about scope.
What we do not do.
We do not administer a hospital’s systems and we will not pretend to. Where an interface is theirs, our job is to document our side of it accurately and tell you plainly which questions have to go to them. We are not your lawyer and not your Privacy Officer, we do not sign off your risk analysis as though it were ours, and buying managed IT does not make a practice HIPAA compliant.
Verify us before you talk to us.
Every claim here is checkable without speaking to a salesperson. Confirm that whoever contacts you actually works here before they touch a workstation holding PHI.
The questions practices actually ask.
Generally no, and this is the distinction that causes the most trouble. Referring patients to a hospital, or holding privileges there, does not make it your business associate — both of you are covered entities treating the same patient. A BAA is needed where someone performs a function for you and can reach PHI while doing it: billing companies, IT providers, practice-management hosts, transcription. We map that for you, and the list is usually longer than expected once affiliated systems are counted.
Yours, and it is worth being blunt about it. The hospital secures its system; the device reaching it is on your network and in your risk analysis. That is the single most common gap we find in hospital-adjacent practices, because both sides reasonably assume the other has it.
It can, and it depends on your patients rather than your address. SHIELD reaches the private information of New York residents wherever the holder sits, so a Teaneck practice seeing patients from Manhattan or the Bronx is inside it. New Jersey’s own notification law applies to New Jersey residents at the same time. The practical consequence is that you need to be able to tell the two populations apart.
We are based in Warwick, New York, so Teaneck is a drive down the Garden State Parkway rather than around the corner. Most of this work is remote by design; when something needs hands on it, we agree the window before committing 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.
