locations · philadelphia

A CAR T dose starts as a patient's own cells. Every hand that touches the record has to be on file.

Philadelphia's medical economy runs from university labs in University City to the hospitals across the river and the payers downtown. Autologous cell therapy ties all three together around one patient record, and FDA expects a trail showing who changed what. That trail is mostly an identity problem.

in short·15-second read

In Philadelphia we work with cell and gene therapy developers, hospital systems, health insurers and large consumer service companies.

The work is identity governance for lab and manufacturing systems, privileged access, customer sign-in hardening, and data pipelines that keep chain-of-identity records intact. We're based in Frisco, Texas, serve Pennsylvania organizations remotely, and travel to Philadelphia for workshops and launches.

Our only US office is in Frisco, Texas, and we have no Philadelphia staff. Pennsylvania clients work with us remotely, and we fly in for discovery sessions, validation walkthroughs and go-live.

Ask an engineer facts checked 2026-10-21 · 9 sources
rules
Pennsylvania Breach of Personal Information Notification ActPennsylvania Insurance Data Security ActFDA 21 CFR Part 11, electronic records and signatures
who and what

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

industries
  1. Cell and gene therapy developers

    Autologous therapies move a patient's cells from an apheresis site to a manufacturing suite and back, and each step lands in a different system. LIMS, MES, quality and courier portals each keep their own accounts. We tie those accounts to one governed identity, require unique logins on every GxP system, and feed access changes into the audit trail your quality team reviews.

  2. Academic medical centers and children's hospitals

    Researchers, clinicians and trainees often carry three roles in one person, and grant-funded data access tends to outlive the study. We set lifecycle rules keyed to IRB approvals and appointment end dates, so access to research datasets ends when the protocol does.

  3. Health insurers

    Blue plans and other carriers regulated by the Pennsylvania Insurance Department now owe the state a written security program and third-party oversight. Broker portals and delegated vendors are where we see the weakest access controls. We put brokers on a separate partner identity with MFA, and give vendor service accounts owners and rotation dates.

  4. Cable, broadband and consumer accounts

    Large subscriber bases mean millions of customer logins, support agents who can reset them, and edge appliances that face the internet. We harden customer identity with phishing-resistant MFA options, limit what support staff can change without a second check, and watch for session token theft after a perimeter flaw is disclosed.

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

    Act 33 of 2024, effective 26 September 2024, added notice to the Attorney General when more than 500 Pennsylvanians must be told, and 12 months of free credit monitoring when Social Security, bank account, driver's license or state ID numbers are exposed.

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

    Insurance licensees report qualifying cybersecurity events to the Insurance Commissioner within five business days. Risk assessment and program duties were due 11 December 2024, vendor oversight 11 December 2025, and domestic insurers filed their first compliance certification by 15 April 2026.

  3. FDA 21 CFR Part 11, electronic records and signatures ↗

    Section 11.10 requires limiting system access to authorized individuals and computer-generated, time-stamped audit trails that record operator entries without obscuring earlier values. For therapy manufacturers this reaches LIMS, MES and electronic batch records.

01Can you help us pass a Part 11 audit on our LIMS and MES access?

We handle the access side. That means unique accounts, role design that separates operators from reviewers, removal of shared logins, and reports that show each access change with a timestamp. Computer system validation and the final quality sign-off stay with your QA team, and we give them the test evidence they ask for.

02Does Pennsylvania have a consumer privacy law like Virginia's or Delaware's?

Not yet. The House passed HB 78 on 1 October 2025 and sent it to the Senate, and as drafted it would take effect a year after passage. Until something is signed, the breach notification act and sector rules such as HIPAA and the insurance data security act are what apply.

03We're an insurer domiciled in Pennsylvania. What does the April certification need from identity?

Evidence that your access controls match your written program. In practice that is MFA coverage, privileged account lists, review records and a vendor access inventory. The Commissioner gets the certification. We build the reports behind it, and your officers decide what to certify.

04Our hospital and our research institute share one directory. Is that a problem?

Only if nothing separates the roles. We keep one person record but split clinical, research and teaching entitlements, each with its own owner and end date. That way a resident who leaves a lab keeps clinical access without dragging old study data along.

05Who would we work with and where are they?

A Cohash team led from Frisco, Texas, with engineering support from our other offices as the work needs. We travel to Philadelphia for the sessions that go better in a room, such as role design workshops and cutover.

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