locations · louisville

Louisville sorts the world's parcels overnight and runs health plans by day. Both lean on machine credentials.

A sort hub that scans millions of labels a night and an insurer that pays claims for millions of members share one habit. They connect to hundreds of outside systems through service accounts and API keys that nobody has counted in years. In Louisville we start by finding those accounts and giving each one an owner.

in short·20-second read

For Louisville organizations we work on identity and data in parcel and freight logistics, health insurance and claims technology, and vehicle and appliance manufacturing.

That means machine and partner credentials, member identity and consent, payer data pipelines and plant-floor access. Kentucky's consumer privacy act took effect on 1 January 2026, so data inventories are part of most projects. We serve Louisville remotely from Frisco, Texas, and travel in for workshops and launches.

We have no office in Louisville. Our only US office is in Frisco, Texas, and our team works with Kentucky organizations remotely, flying in for discovery sessions, design workshops and go-live support.

Ask an engineer facts checked 2026-10-21 · 11 sources
rules
Kentucky breach notification, KRS 365.732Kentucky Consumer Data Protection Act, KRS 367.3611 to 367.3629CMS Interoperability and Prior Authorization Final Rule
who and what

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

industries
  1. Parcel, freight and medical logistics

    A hub this size runs on integrations with airlines, customs brokers, shippers and the warehouses around the airport. Each one holds an API key, an EDI login or a certificate, and seasonal surges add thousands of temporary badges. We inventory those machine credentials, set expiry and rotation, and give short-term workers access that ends on the day their contract does.

  2. Health insurance and claims technology

    Medicare Advantage, Medicaid and revenue-cycle platforms move member and claim records between plans, providers and clearinghouses. The hard part is knowing which partner app can call which API on whose behalf. We design that authorization layer, wire consent into it and build the data pipelines that feed interoperability endpoints and analytics.

  3. Vehicle and appliance manufacturing

    Retooled assembly lines bring new robots, vision systems and supplier portals onto the plant network. Engineers and integrators often share local admin accounts to keep a line moving. We move that access behind a vaulted jump point, separate the plant network from corporate identity, and log every vendor session.

regulations
  1. Kentucky breach notification, KRS 365.732 ↗

    Information holders must notify affected Kentucky residents in the most expedient time possible and without unreasonable delay. A breach requiring notice to more than 1,000 people also requires notice to the nationwide consumer reporting agencies. Entities subject to GLBA Title V or HIPAA are carved out.

  2. Kentucky Consumer Data Protection Act, KRS 367.3611 to 367.3629 ↗

    Effective 1 January 2026 for businesses that control or process data on 100,000 Kentucky consumers, or 25,000 if over half of revenue comes from selling data. HIPAA covered entities, GLBA financial institutions and nonprofits are exempt. The Attorney General enforces it after a 30-day cure notice, with damages up to $7,500 per continued violation.

  3. CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) ↗

    Reaches Medicare Advantage organizations and Medicaid managed care plans, including those serving Kentucky members. Most of the Patient Access, Provider Access, Payer-to-Payer and Prior Authorization API requirements apply from 1 January 2027.

01Does the Kentucky Consumer Data Protection Act apply to a health plan?

The act exempts HIPAA covered entities and business associates as organizations, and it separately exempts protected health information. A plan's affiliates that sell non-HIPAA products, run wellness apps or market to consumers may still fall inside it. Map which legal entity holds which data set before deciding, and confirm the answer with counsel.

02We run a peak-season workforce of temporary sorters and drivers. How should their access work?

Tie accounts to the staffing agency feed or your contractor system rather than to HR, set an end date when the account is created, and use badge or passkey sign-in on shared scanners. The goal is that nobody has to remember to switch accounts off in January.

03How fast does Kentucky expect breach notices to go out?

KRS 365.732 sets no fixed day count. It asks for notice in the most expedient time possible and without unreasonable delay, with room for a law-enforcement hold. If more than 1,000 people need notices, you also tell the nationwide credit bureaus. Residents of other states bring their own deadlines.

04Can you help a plant meet supplier and OEM security questionnaires?

On access control, yes. We document who can reach line controllers and engineering workstations, put remote vendor access through a recorded gateway and produce the evidence that most automaker supplier questionnaires ask for. Network monitoring products stay with your OT team.

sources 11 sources linked last checked 2026-10-21 content fingerprint e8fe5da5
  1. 01Louisville Muhammad Ali International Airport, about SDFflylouisville.com ↗
  2. 02One Louisville, logistics industry profile (2026)onelouisville.org ↗
  3. 03One Louisville, life sciences industry profile (2026)onelouisville.org ↗
  4. 04One Louisville, automotive industry profile (2026)onelouisville.org ↗
  5. 05GE Appliances company sitegeappliancesco.com ↗
  6. 06Kentucky Department for Medicaid Serviceschfs.ky.gov ↗
  7. 07BLS, Louisville/Jefferson County economy at a glancebls.gov ↗
  8. 08KRS 365.732 (Kentucky Legislature)apps.legislature.ky.gov ↗
  9. 09KRS 367.3613, KCDPA applicability (Kentucky Legislature)apps.legislature.ky.gov ↗
  10. 10KRS 367.3627, KCDPA enforcement (Kentucky Legislature)apps.legislature.ky.gov ↗
  11. 11CMS, Interoperability and Prior Authorization Final Rulecms.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