A Long-Term Care Pharmacy Keeps SAP Crystal Reports and Automates HIPAA-Governed Delivery With Files.com

A closed-door long-term care pharmacy packages and fulfills prescriptions for skilled nursing facilities, assisted living communities, and correctional institutions, institutional customers whose staff care for patients and residents.

A closed-door pharmacy serves patients through those facilities rather than across a retail counter. Everything the pharmacy produces has to travel to the institution: statements, refill runout reports, drug regimen reviews, even photographic proof of what was dispensed. Because those documents can contain protected health information, their delivery has to stand up to HIPAA.

Rather than replace the SAP Crystal Reports server its pharmacy depended on, the company used Files.com to automate what happened after each report was generated: nightly delivery to the right facility, governed access to one-off exchanges, and a record of retrieval.

The Reports Ran Nightly, and Email Was Never an Option

The pharmacy’s transactional and pharmacy reports originated on an SAP Crystal Reports server. Statements told a facility what it owed. Refill runout reports warned a facility before a resident’s medication ran out, which made them time-sensitive by definition. Each report had to reach the right facility every night, and only that facility.

Because the documents carried PHI, the pharmacy needed a governed alternative to ordinary email attachments. Without an automated path, nightly per-customer delivery would have meant someone at the pharmacy handling files by hand, every night, for every customer. At that volume, manual handling was not a workflow. It was a standing cost that would grow with every facility the pharmacy signed.

The structural constraint made it harder. The pharmacy controlled the reporting server but not the recipients, and each recipient could be allowed to see only its own facility’s documents. The existing server and the pharmacy’s custom reporting processes still worked. The delivery layer was the part that could change.

What that layer had to do was clear. Sit between a legacy reporting server and every facility customer. Give each customer its own access, scoped to its own documents and nothing else. Run the nightly delivery with nobody touching files. Handle one-off exchanges with the same governance. And keep a record of who retrieved what.

The pharmacy selected Files.com as that delivery layer.

A Folder and a Login for Every Facility, a Delivery Nobody Touches

Files.com became the exchange layer between the pharmacy’s reporting server and every facility it served.

Each institutional customer received a Files.com login scoped to its own folder. A director of nursing at one facility saw her facility’s statements and reports and nothing else, enforced by folder-scoped permissions rather than by anyone’s discipline.

Delivery itself was built on the Files.com API. A service the pharmacy wrote uploaded the Crystal Reports output automatically every night into the customer folders. The pharmacy then built its reporting workflows the same way: automated statement delivery, “New RX Needed” alerts that flagged prescriptions needing renewal within seven days, and an automation that published drug regimen reviews for customers to download for compliance.

For everything that did not run on a schedule, the pharmacy used governed Files.com share links. Access logs and share-link visitor monitoring recorded who retrieved each document, giving the pharmacy a retrieval record for one-off exchanges involving regulated information.

The same channel carried the pharmacy’s monthly clinical deliveries, putting HIPAA-covered clinical information in front of nursing home administrators and directors of nursing on schedule.

Nightly Delivery With No Hands on It

With the Files.com workflows in production, the pharmacy had a delivery layer that ran itself.

• Report delivery to every facility customer runs automatically every night, with no manual handling at the pharmacy.
• Documents that have to be HIPAA compliant travel through one governed channel, scoped per facility, with an access record behind them.
• Onboarding a new facility requires a folder and a login on machinery that already exists. The portal absorbed substantial user growth without changing how delivery works.
• New regulated workflows are additions to the same layer rather than new delivery systems: statement delivery, refill alerts, and drug regimen reviews all ride the Files.com API.

The Reporting Server Stayed, the Delivery Problem Went to Files.com

The SAP Crystal Reports server still generates the pharmacy’s transactional and pharmacy reports. Files.com governs what happens next, from nightly distribution to photographic proof that a prescription left the pharmacy.

The pharmacy did not have to modernize its reporting system to modernize how its documents reach customers. It put Files.com between a legacy server and the facilities it serves, and regulated document delivery stopped being a nightly task and became part of the service it offers.