Pillr Health Connects Specialty Pharmacies With No IT Staff to SharePoint With Files.com

Pillr Health administers the federal 340B drug pricing program, which lets eligible providers buy outpatient medication at reduced prices and use the savings to fund care for uninsured and low-income patients. The company serves more than 300 hospitals, health systems, and federally qualified health centers nationwide, and its work is data in motion: pharmacy claims, drug pricing, and patient records moving between covered entities and the national wholesalers and payers that serve them, all of it regulated under HIPAA.

Its newest service line, Pharmacy Accelerator, helps health care providers stand up and operate their own specialty pharmacies. The clients that line serves are nothing like the hospital systems the rest of the business exchanges files with. They are small pharmacy operations handling expensive therapies, and most of them have no one in charge of technology at all. Pillr Health was entering a market where its customers, by the nature of that market, could not operate a file transfer tool.

Pillr Health used Files.com browser links for pharmacies and automatically handed files to and from isolated client areas in SharePoint, without exposing SharePoint itself.

Files Too Big for Email, Clients Who Couldn't Run FTP

“Specialty pharmacies tend to be very small but high dollar, and because they're small, they don't always have the technical wherewithal to manage all their stuff.”

Launching a pharmacy meant moving HIPAA-regulated client and patient data back and forth between the client and Pillr Health's implementation team, and both of the ordinary paths had already failed. Email capped attachments at 40 MB, and client files had already reached 80 MB. The industry-standard alternative, an SFTP client on the pharmacy's own desktop, assumed a kind of staff these clients simply did not have.

“When I said FileZilla, they asked, FileZilla? And they don't know how to do all that, and they've got to wait for a techie person to come in and do stuff. What they want is me to be able to just give them a link.”

The cost landed on the launch itself. A file the client couldn't send is a pharmacy launch waiting on a technician the pharmacy doesn't employ, with data too sensitive to travel by whatever improvised path someone finds in the meantime.

And Pillr Health controlled neither end it needed to change. It could not push software or training into its clients. Its own side was SharePoint, the internal system of record holding every Pharmacy Accelerator client's data, which no external party could be allowed to see and where one client's data can never be visible to another. Every external touchpoint also had to survive the HIPAA and SOC 2 scrutiny the rest of the business answers to.

What the New Line's File Exchange Had to Do

The line was going live, and clients would arrive one at a time. Prospective pharmacies were already asking to send files during exploratory conversations. The exchange could not wait for the clients to change, and it had to be easy to extend to every client after the first.

That set the specification. A sender needed nothing but a browser: no account, no login, no software. Each client had to see its own folder and nothing else. SharePoint had to stay internal and be fed automatically. Prospective access had to be temporary. Pillr Health built the client-facing layer of Pharmacy Accelerator on Files.com.

Files.com in Front, SharePoint Behind

The design put Files.com in front and kept SharePoint behind. Everything a pharmacy client touched was a Files.com page under Pillr Health's branding. Everything internal stayed in SharePoint, which no client could see or reach.

Pillr Health built the line on a dedicated Files.com child site: a fully separate site under Pillr Health's account, walled off from the rest of the company's file estate, where each pharmacy client was limited to exactly one thing, its own folder. That folder was joined to the client's area in SharePoint through a Files.com Remote Server Mount. When a client dropped a file, a Files.com Automation moved it into SharePoint for the implementation team. When the team placed an outbound file in SharePoint, a scheduled job carried it back out to the client's Files.com folder. Nobody had to re-upload anything by hand, and no external credential ever touched SharePoint.

For the pharmacy, all of this amounted to a link. A Files.com Inbox link opened an upload page in the browser, with no account to create, no software to install, and no attachment ceiling. Going the other direction, the implementation team pasted Files.com share links into the Monday.com project boards its clients already worked from, so delivery happened inside the project plan.

Because an Inbox required no account, Pillr Health could give prospective pharmacies temporary access to exchange files during exploratory conversations, then disconnect the link when it was no longer needed.

Four Clients Live Within About a Month

With the child site in production, Pillr Health replaced email attachments and client-side FTP with a browser link and stood the whole line up as clients arrived.

The first four Pharmacy Accelerator clients were live within about a month of the November 2025 build-out.

• A pharmacy with no technical staff now sends and receives HIPAA-regulated files through a browser page, with no FTP client, no login, no waiting for a technician, and no 40 MB email ceiling.
• The SharePoint system of record is invisible to every external party, and each client sees only its own folder.
• Onboarding the next client means cloning the pattern: a folder, a mount, a link.

“They were really happy when I said they can't see the SharePoint site. They can only see their folder on Files.com, and whenever they drop something on Files.com, it will get sent over.”

The Exchange Now Matches the Client

Pharmacy Accelerator was built to serve clients that are, in Pillr Health's own description, too small to manage their own technology. Before the build-out, that fact set the pace of every exchange: a file waited until the pharmacy could find a technician, or it went by email until it outgrew email. Today the client's side of the exchange is a link that works in any browser, and Pillr Health's side is the SharePoint estate its team already works in, fed automatically and never exposed.

What the company established reaches past the initial clients. With Files.com as the client-facing layer, Pillr Health can put a governed, HIPAA-grade exchange in front of any customer who has nothing but a browser, without exposing the system of record behind it. The clients never had to become technical. The exchange became something they could use instead.