locations · baltimore

Baltimore's biggest employers treat patients, and its federal neighbors pay for their care.

In Baltimore, a large share of the payroll sits in hospitals and universities, and the Centers for Medicare & Medicaid Services runs its headquarters just west of the city line. That puts clinical identity, research data access and federal security controls on the same short list for many local IT teams.

in short·15-second read

Our Baltimore work is for hospital systems, academic medical centers, CMS and SSA contractors, asset managers and port and logistics operators.

Typical jobs are clinical and research identity governance, privileged access, controls mapped to the CMS Acceptable Risk Safeguards, and governed data pipelines for Maryland's hospital payment model. Cohash is headquartered in Frisco, Texas; we serve Baltimore remotely and travel in for workshops and launches.

Cohash is based in Frisco, Texas and has no office in Baltimore or Maryland. We work with Baltimore teams remotely and travel to your campus for discovery, design workshops and cutovers.

Ask an engineer facts checked 2026-10-21 · 8 sources
rules
Maryland Personal Information Protection Act, Com. Law §14-3504Maryland Online Data Privacy ActCMS Acceptable Risk Safeguards
who and what

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

industries
  1. Hospital systems and academic medicine

    A faculty physician may hold a hospital EHR account, a university research login and a grant-funded data enclave account at once, each issued by a different office. We link those identities to one person, drive changes from credentialing and HR together, and end research data access when the study or appointment ends.

  2. CMS and SSA contractors

    Firms that build or run systems for agencies on Security Boulevard inherit federal control baselines. For CMS work that means the Acceptable Risk Safeguards, built on NIST SP 800-53. We implement the access control, audit and identification controls in your system, and we write the evidence your assessors will read.

  3. Asset management and banking

    Investment managers and banks headquartered downtown hold client and trading data that regulators and institutional clients both audit. We focus on privileged access to portfolio and trading systems, quarterly entitlement reviews business owners can finish, and secrets management for market data and custodian integrations.

  4. Port, utilities and logistics

    Roll-on/roll-off terminals, rail yards and the regional gas and electric utility depend on contractors who need short, specific access to operational systems. We put that access behind a PAM gateway with approvals and recording, and separate it from the corporate directory.

regulations
  1. Maryland Personal Information Protection Act, Com. Law §14-3504 ↗

    Notify affected residents as soon as reasonably practicable and no later than 45 days after discovering or being notified of a breach. The Attorney General must be notified before the individual notices go out, with the number of Maryland residents affected and a sample notice.

  2. Maryland Online Data Privacy Act (MODPA) ↗

    Took effect 1 October 2025 but does not apply to processing before 1 April 2026. Covers businesses handling data of 35,000 or more Maryland consumers, or 10,000 if over 20% of gross revenue comes from selling personal data. A discretionary 60-day cure right expires 1 April 2027.

  3. CMS Acceptable Risk Safeguards (ARS) ↗

    Sets the minimum security and privacy controls for CMS systems, and applies to CMS employees, contractors and subcontractors. ARS 5.2 is current and adds Zero Trust expectations to controls numbered and worded to match NIST SP 800-53 Rev. 5.

01How fast do we have to notify Maryland residents after a breach?

Within 45 days of discovering the breach or being told about it by a vendor, and the Attorney General's office must hear from you first. Law enforcement can ask for a delay. Build the AG notice into your playbook so it does not hold up the resident letters.

02Does MODPA apply to a hospital that is already under HIPAA?

Protected health information handled under HIPAA is treated differently from other personal data, but hospitals also run websites, apps, marketing lists and research programs that may fall outside it. Map which data sets sit outside HIPAA first, then have counsel apply MODPA to those.

03Can you help us pass a CMS security assessment as a contractor?

We implement and document the identity, access and audit controls from the ARS baseline in your system, and prepare the evidence assessors request. The assessment itself is run by the assessor CMS accepts, and system authorization is CMS's decision.

04Our researchers keep data access long after a study closes. What fixes that?

Tie each research data grant to a protocol or project record with an end date, and feed that record into the identity platform. When the IRB closes the study or the appointment ends, access drops automatically and the PI gets a report of what was removed.

05Will you come to Baltimore?

Yes, for discovery interviews, design workshops and go-live weekends. Most build and configuration work happens remotely from Frisco and our other offices.

sources 8 sources linked last checked 2026-10-21 content fingerprint aa8b0cb6
  1. 01Maryland Department of Commerce, Brief Economic Facts, Baltimore City (2025.2)commerce.maryland.gov ↗
  2. 02BLS, Baltimore-Columbia-Towson economy at a glancebls.gov ↗
  3. 03CMS, locations and facilitiescms.gov ↗
  4. 04GovInfoSecurity, RobbinHood ransomware hacker pleads guilty (May 2025)govinfosecurity.com ↗
  5. 05CMS Innovation Center, AHEAD modelcms.gov ↗
  6. 06Maryland Code, Commercial Law §14-3504mgaleg.maryland.gov ↗
  7. 07Cozen O'Connor, Maryland enacts a comprehensive data privacy lawcozen.com ↗
  8. 08CMS Information Security, Acceptable Risk Safeguardssecurity.cms.gov ↗
Reviewed by the Cohash team Product names are trademarks of their owners. how we handle facts and data →
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