Skip to content
HIPAA ComplianceConsulting

Dallas Service Coverage

HIPAA Compliance Consulting for Dallas Healthcare Organizations

For Dallas-area hospital systems, revenue cycle and billing companies, and growing provider groups: the HIPAA issues that come with scale, acquisitions and outsourced operations.

Reviewed Request a HIPAA Consultation

The Dallas–Fort Worth area is home to large hospital systems, national revenue cycle management (RCM) and medical billing companies, and physician groups that have grown through acquisition across many sites. Each faces HIPAA challenges driven by scale: many systems, many vendors, many hands touching PHI.

Texas state law — including Chapter 181’s broad covered entity definition, training requirements and AG breach notice — applies to Dallas organizations and is summarized on our Texas page. This page focuses on the operational issues specific to these three types of organization.

Key points

  • Hospital systems need enterprise-wide risk analysis that keeps pace with acquisitions and new systems.
  • RCM and billing companies are business associates with large PHI volumes and offshore or subcontracted labor risks.
  • Multi-location groups often run inconsistent practices across sites after acquisitions.
  • Texas law applies on top of HIPAA — see the Texas page rather than relying on HIPAA alone.

How we serve Dallas-area organizations

Engagements are delivered remotely, with on-site visits by arrangement — for example, site walkthroughs at a sample of clinic locations or a leadership tabletop exercise. Multi-site assessments typically combine remote evidence review across all sites with targeted visits where risk is highest.

Hospital systems: keeping the risk analysis current

For hospital systems, the most common HIPAA weakness is not a missing policy — it is a risk analysis that no longer reflects the environment. New service lines, acquired facilities, connected medical devices, and cloud applications adopted by departments all change the risk picture. OCR enforcement actions frequently cite failure to conduct an accurate and thorough risk analysis under §164.308(a)(1)(ii)(A).

  • Tie risk analysis updates to change events: acquisitions, EHR migrations, new cloud platforms, major vendor changes.
  • Include biomedical and IoT devices that store or transmit ePHI, not only traditional IT.
  • Track remediation in a risk management plan with owners and dates, per §164.308(a)(1)(ii)(B).
  • Use HHS 405(d) Health Industry Cybersecurity Practices as a practical control reference — recommended practice, not a HIPAA mandate.

Revenue cycle and medical billing companies

RCM and billing companies are business associates of the providers they serve, and often handle PHI for many clients at once. That concentration makes them attractive targets, and their incidents can trigger notifications across dozens of covered entities.

RCM risk areas and the HIPAA requirement they touch
Risk areaHIPAA requirementWhat we look at
Offshore or subcontracted coding and billing staffSubcontractor BAAs, §164.308(b) and §164.314Contract flow-down, access scope, monitoring
Access to many client EHRs and payer portalsAccess control and unique user IDs, §164.312(a)Shared credentials, provisioning and removal across client systems
Large volumes of claim dataMinimum necessary, §164.502(b)Whether staff see more PHI than their task needs
Client-specific BAA termsBAA compliance, §164.504(e)Tracking differing breach notice deadlines across clients
Email and file transfer of remittancesTransmission security, §164.312(e)Encryption and secure transfer methods

Managing many BAAs

Billing companies often sign client BAAs with different breach notice deadlines, audit rights and security terms. A central register of BAA obligations, linked to the incident response plan, avoids missing a client-specific deadline during an incident. Our medical billing HIPAA consulting page covers this further.

Multi-location provider groups

Physician groups, specialty practices and outpatient networks that have grown through acquisition commonly inherit a patchwork: different EHRs, different policies, different front-desk practices and varying levels of IT maturity. Integrating them into one HIPAA program is a significant piece of work.

  1. 1

    Inventory every site

    List systems, vendors, devices and responsible staff at each location — including legacy systems kept for record retention.

  2. 2

    Run a group-wide gap analysis

    A HIPAA gap analysis across sites shows where practices differ and which sites carry the most risk.

  3. 3

    Adopt one set of policies

    Replace inherited policies with a single group-wide set, with site-specific procedures only where necessary.

  4. 4

    Standardize training and onboarding

    Use one training program that includes Texas-specific content, with records tracked centrally.

  5. 5

    Build acquisition due diligence

    Assess HIPAA posture before closing future deals, so integration costs and risks are known up front.

Incident readiness at scale

Scale changes breach response. A ransomware event at a hospital system or RCM vendor can involve HHS notification, media notice where 500 or more residents of a state are affected, Texas AG notice, notices to multiple covered-entity clients and coordination with law enforcement. Tabletop exercises that walk through these parallel tracks are one of the most valuable preparation steps. Our breach response consulting service can help design and run them.

Business associates should also check the deadlines in each client BAA: many require notice to the covered entity well inside HIPAA’s 60-day outer limit, and the covered entity’s own clock may depend on when the business associate discovered the breach.

Vendor and third-party risk

Large Dallas-area organizations rely on long vendor chains: EHR hosting, clearinghouses, collection agencies, transcription, cloud backup, managed IT and staffing firms. Each one that creates, receives, maintains or transmits PHI needs a business associate agreement, and each is a potential source of a breach you will have to manage.

A BAA is a legal requirement; vendor due diligence is good practice on top of it. We help organizations tier vendors by PHI volume and access, decide which ones warrant security questionnaires or evidence requests, and track remediation commitments. A signed BAA with a cloud or hosting vendor does not transfer your own Security Rule obligations — responsibility is shared.

  • Keep a single vendor inventory linked to BAA status, PHI categories and access type.
  • Tier vendors and set review depth by tier rather than sending the same questionnaire to everyone.
  • Confirm offboarding steps: return or destruction of PHI and removal of access when contracts end.

Frequently asked questions

Our billing company only processes claims. Are we a business associate?

Almost certainly. Processing claims on behalf of a provider involves PHI, which makes you a business associate under HIPAA. Texas law may also treat you as a covered entity in your own right; see our Texas page.

Can you assess all of our clinic locations?

Yes. Multi-site assessments are typically remote across all locations, with on-site visits arranged for a sample of sites or those with higher risk.

How often should a hospital system update its risk analysis?

HIPAA does not set a fixed interval, but the risk analysis must be accurate and current. Updating it on a regular cycle and whenever significant changes occur is the common approach.

Should we assess HIPAA before acquiring a practice?

It is good practice. Pre-acquisition review identifies remediation costs and inherited risks — for example, an unreported incident or a missing risk analysis — before you take them on.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.