locations · pittsburgh

When the hospital and the health plan share an owner, the access model has to keep them apart.

In Pittsburgh, UPMC runs hospitals and sells insurance under one roof. More than 260 robotics and AI companies across the region ship software that drives machines. Each raises the same question in a different form. Which person, or which program, is allowed to act here?

in short·15-second read

Our Pittsburgh work covers integrated health systems and their health plans, banks and financial operations centers, and robotics and AI companies.

We separate payer and provider access, govern employee records, which Pennsylvania courts say an employer must protect, and put fleet and model credentials under control. We're based in Frisco, Texas, serve Pittsburgh clients remotely, and travel in for workshops and launches.

Cohash has no Pittsburgh office. The team is led from Frisco, Texas, works with western Pennsylvania organizations remotely, and travels in for kickoff workshops, lab and data center visits, and launch weeks.

Ask an engineer facts checked 2026-10-21 · 8 sources
rules
Pennsylvania Breach of Personal Information Notification ActPennsylvania Insurance Data Security ActHIPAA Security Rule technical safeguards, 45 CFR §164.312
who and what

Who we work with in Pittsburgh, and the rules they work under

industries
  1. Integrated health systems and their health plans

    When one parent owns hospitals and an insurer, staff, contractors and analytics teams can end up with a path from claims data into clinical records, or the reverse. We map those crossings, give each side its own entitlements and approvers, and keep the shared data platform's roles scoped to the business line that owns each dataset.

  2. Banks and financial operations centers

    Bank operations, technology and servicing teams pick up access faster than anyone removes it. The sprawl lives in payments, treasury and servicing tools, plus offshore and vendor teams. We run access certification that business owners can finish, vault privileged accounts and put contractor access on a clock.

  3. Robotics, autonomy and AI companies

    A robot fleet carries device certificates, cloud API keys and over-the-air update signing keys, and an AI team adds model registry and GPU cluster credentials. Startups usually share these across a few engineers. We inventory machine identities, issue short-lived workload credentials and move signing keys into hardware-backed custody.

  4. Employee data at large employers

    After Dittman, payroll and HR systems are a negligence risk as well as a breach-notice risk. We lock down HR platform admin roles, strip standing access from integration accounts that copy employee records, and log every export of Social Security and bank details.

regulations
  1. Pennsylvania Breach of Personal Information Notification Act (73 P.S. §2301) ↗

    Since 26 September 2024 a breach requiring notice to more than 500 Pennsylvania residents also goes to the Attorney General, sent with the individual notices. Exposure of Social Security, bank account, driver's license or state ID numbers brings a 12-month credit monitoring offer.

  2. Pennsylvania Insurance Data Security Act (Act 2 of 2023) ↗

    Reaches health plans and other insurance licensees. A qualifying cybersecurity event goes to the Insurance Commissioner no later than five business days after it is identified, and third-party service provider oversight has been required since 11 December 2025.

  3. HIPAA Security Rule technical safeguards, 45 CFR §164.312 ↗

    Hospitals and health plans, and their business associates, must assign each user a unique identifier, allow ePHI access only to people or software granted rights, record and examine system activity, and verify the identity of anyone seeking access.

01What does Dittman v. UPMC mean for how we run HR systems?

The court said an employer that collects sensitive employee data and stores it online owes a duty of reasonable care, and that purely financial losses can be recovered in negligence. So treat HR and payroll like any other high-value system, with MFA for admins, short-lived integration credentials and logged exports. Your counsel can tell you what the ruling means for your exposure.

02Our provider and payer staff use one Active Directory. Do we need two?

Usually not. One directory can work if roles, groups and approvers are split by business line and the data platform enforces the same split. We look at who crosses the line today and why, then decide whether a separate tenant is worth the cost.

03We're a robotics startup. Is identity work premature?

For workforce SSO, maybe. For machine identity, no, because signing keys and fleet certificates are hard to rotate once robots are in the field. A short engagement that puts those in a vault and documents rotation is far cheaper before your first large deployment than after.

04Does Pennsylvania require breach notice within a set number of days?

For private companies the act says without unreasonable delay, with no day count for residents. The newer rules add Attorney General notice above 500 residents and credit monitoring for certain data. If you also hold data on Ohio or West Virginia residents, their own notice rules apply too, so plan with counsel.

pennsylvania

More cities in Pennsylvania

All 82 cities
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it