LaSalle Replaced Manual FileZilla Transfers With a Files.com Payer and Clearinghouse Exchange in Six Months

LaSalle Medical Associates has been delivering care in Southern California since 1984. Today it is two businesses at once. The first is an independent physician association: six staff-model clinics, a network of more than 5,000 in-network physicians, and over 380,000 managed lives across nine California counties. The second is a management services organization that runs the administrative machinery of managed care for those clinics and physicians, including eligibility, capitation, credentialing, and the review and adjudication of medical claims.

That second business runs on files. Every payer, clearinghouse, and hospital relationship in managed care is a stream of them: 837 claim files going out, 835 remittance files coming back, eligibility and capitation data moving on their own schedules, all of it carrying protected health information. And in early 2026, when LaSalle's management services arm set out to run claims adjudication on a new claims platform of its own, it had no secure file transfer infrastructure at all.

A Claims Operation Without a Governed Exchange

Every exchange was hand work. Partner connections ran through FileZilla sessions, with IP addresses, usernames, passwords, and host keys managed separately on both sides of every connection. Staff logged in to pull claims files by hand. Hospital administrators exchanging patient data with outside physicians and other hospitals had no governed repository to send it through, so PHI moved ad hoc. The operating model everyone knew was in-house, on-premises FTP, where every partner meant another bespoke connection to build and babysit.

The cost of that model landed the day a major California payer sent its security questionnaire. The form asked for a hostname, a connecting IP address, preferred authentication methods, and an outbound directory. LaSalle had none of those things to write down, because there was no file transfer presence to describe, and the payer relationship could not move forward until there was.

And the payer was one of ten. The counterparties LaSalle needed, spanning payers, clearinghouses, and hospital partners, each arrived with their own protocols, their own IP whitelisting demands, and their own preferred way of contributing files. Some pushed over SFTP. One transmitted machine-to-machine over HTTPS on a weekly schedule. One returned files three times a day and needed to be pulled from. A small systems team could not build and operate a bespoke FTP connection per partner, route claim files by hand, and satisfy HIPAA obligations, all while the same people were building and testing the claims platform itself. That platform had a production go-live in August 2026, and every route to every clearinghouse had to exist before it.

What LaSalle needed was one exchange layer every counterparty could reach in whatever way it already worked: fixed IP addresses a payer's security team could whitelist, a walled-off space per partner, a BAA covering the PHI passing through, and automated pickup from the claims system that would not disturb anything already depending on its output. LaSalle selected Files.com to be that layer.

The Router Between the Claims System and Every Clearinghouse

Files.com became the hub for LaSalle's claims file exchange. Michael Brown, LaSalle's Senior Systems Architect, put it plainly:

“I view it as our router for our files.”

The pickup runs inside LaSalle's own network. A Files.com Agent installed on an on-premises server makes an outbound-only connection to the platform, so no inbound firewall changes were needed and the claims server was never exposed to the internet. The Agent copies 837 and 835 files out of the claims platform's output directory rather than moving them. That distinction mattered: several downstream programs read that same directory for reconciliation and other reports, so the exchange had to take its copy without breaking anything that already depended on the folder.

From there, Files.com routes each file by type. 835 remittance files go to the clearinghouse that processes remittances; 837 claim files go to the clearinghouses that carry claims. For the clearinghouse that returns files three times a day, a timed sync pulls them in and delivers them to the right directory, with no one logging in to fetch anything. LaSalle's managed IT provider ran the build alongside Files.com's onboarding team, standing up the counterparties one at a time from February through August 2026.

One Front Door for Ten Counterparties

On the inbound side, every partner gets the same structure: a dedicated folder tree with separated incoming and outgoing directories, and a partner account scoped to exactly that space. The site runs on LaSalle's own branded domain with fixed IP addresses, which gave payer security teams a hostname and an IP to whitelist. Those were the exact answers LaSalle could not provide when the first questionnaire arrived.

Partners connect however they already work. Some push over standard SFTP. One trading partner transmits machine-to-machine over HTTPS on its weekly cadence. A hospital administrator with a one-off file uses the web interface. Brown's summary of that range:

“the Swiss Army knife of FTP”

Internally, staff sign in through Microsoft Entra ID over SAML SSO, with accounts provisioned automatically on first login. Inbound partner files sync on a schedule into a SharePoint library set aside for this traffic, so Microsoft 365 remains LaSalle's system of record while Files.com is the governed perimeter in front of it. Arrival notifications fire when a payer drops a file. The account carries a BAA, covering the PHI in every exchange.

Ready Before the Claims System Turned On

By August 2026, LaSalle had replaced an exchange built on FileZilla sessions and hand-managed credentials with a standing, governed platform, in place ahead of the claims system's go-live.

• File exchange with ten payer, clearinghouse, and hospital counterparties runs through one Files.com platform, built in roughly six months by a small systems team.
• Manual retrieval is gone from the claims path. Files leave the adjudication system and reach the right clearinghouse automatically, where staff used to log in and pull them by hand.
• The payer connection that exposed the original gap is live, with automated notification the moment its files arrive.
• Claims import files received through the platform follow the seven-year retention schedule that governs claims data.

Today, the claims administration behind more than 380,000 managed lives runs its file traffic through Files.com without anyone touching it, and when a new health plan arrives with its own set of transfer requirements, the exchange it needs already exists. LaSalle never built file transfer infrastructure of its own. It stood up its entire payer and clearinghouse exchange on Files.com, and it was there before the claims system it serves ever went live.