Capital S Consulting
Specialty Pharmacy Data That Reaches Your Team
One set of dashboards across every pharmacy in your network. Executives see how the network is performing, operations sees which patients missed a dispense and follows up, and PII stays inside the specialty pharmacy and hub systems, with nothing identified reaching your reporting, your Tableau workspace, or Salesforce
One View Across Every Pharmacy
What commercial teams need from specialty pharmacy data is one set of dashboards everyone reads. Executives see how the network is performing: patients on therapy, time to first fill, dispense volume by pharmacy. Operations staff see the exceptions, the patients whose next dispense has not happened, and follow up before a gap in therapy turns into a discontinuation. Both views run on the same numbers, and neither one needs a patient name in it. PII stays inside the specialty pharmacy and hub systems, and nothing identified reaches your reporting, your Tableau workspace, or Salesforce. Getting there means absorbing the differences between partners. Every pharmacy sends data in its own format on its own cadence, one dropping a status file before six every morning, the next posting a weekly feed with different column names and a different idea of what shipped means. We do that mapping work once, so the answer to how many patients are on therapy comes out of a system instead of someone's afternoon
Four Ways Specialty Pharmacy Data Goes Sideways
These show up on nearly every engagement, whether the network is two pharmacies or twelve
Four Formats, One Therapy
Fixed width from one pharmacy, a delimited file from the next, an EDI transaction from the third. Column names, date formats, and status codes rarely agree. Every partner you add brings another set of rules that lives in one analyst's head
No Single Read on the Network
Leadership asks how the launch is tracking and gets a number per pharmacy, assembled by hand, current as of whenever the last file was opened. Patients on therapy, time to first fill, and partner-to-partner comparison each come from a different file and a different person
Missed Dispenses Nobody Chases
A patient's next fill does not happen and the record sits in a file until someone notices. By the time it reaches a care coordinator the gap in therapy is weeks old, and what should have been a reminder call is a recovery call
Patient Detail Where It Should Not Be
A dashboard needs patient counts and time-to-fill trends. It does not need names. When identified records get copied into a spreadsheet to make the math work, you have taken on exposure the reporting never needed in the first place
Specialty Pharmacy Data Integration, End to End
We adapt to the files your pharmacies already send. No spec sheet handed to your partners, no waiting in their IT queue. Feeds go into a commercial data warehouse you own, then flow to Salesforce and your reporting tools from there
Feed Definition and Onboarding
We map every field, normalize the values, and write validation rules per pharmacy, whether you run one specialty pharmacy or a limited distribution network of six. Each feed gets onboarded with its own rules because no two arrive alike. Status codes get translated into one shared vocabulary before anything loads, so a record marked shipped means the same thing regardless of who sent it. The mapping is documented, so the next person to touch it does not start from scratch
Dispense Visibility
Pharmacy feeds generally arrive nightly, carrying dispense information, therapy starts and stops, and benefit adjudication results. Those records link to the patient and prescriber records in Salesforce, so field reimbursement managers, care coordinators, and leadership see therapy status without logging into a pharmacy portal or learning someone else's workflow. Ship date, fill number, quantity dispensed, and refill status sit alongside them. Pair the feed with your hub feeds and the enrollment-to-first-fill gap becomes something you can measure instead of estimate. When a hub sits in the middle, the pharmacies report to it and your copy arrives on the hub's consolidated feed
EDI 852 and 867 Channel Data
Inventory and sell-through from the distribution channel, parsed and loaded on the schedule your partners send them. We reconcile 852 inventory movement against 867 resale detail and against dispense volume, then separate the variances that are real from the ones that are timing. Trade and finance stop debating which number is right because both are reading the same model
Aggregation Across Partners
One consolidated view across every pharmacy in the network, matched on DEA, HIN, and NPI so the same prescriber does not appear three times under three spellings. Volume, patient counts, and time to fill compare across partners without anyone stitching tabs together. When you add a pharmacy, it joins the existing model instead of starting a new spreadsheet
Ordering and Inventory Dashboards
Portal-based reporting in Power BI or Tableau covering ordering patterns, inventory on hand, days of supply, and pharmacy performance side by side. Trade sees where stock is running thin before it turns into a backorder call. Leadership reads the same numbers as the analyst who built them, refreshed on the cadence the feeds allow rather than on request
Ongoing Feed Operations
We monitor arrivals, validate each load against the prior one, and flag anomalies when a file arrives short or includes a status code we have not seen before. When a pharmacy updates its file layout, validation catches the change and we fix the mapping. Break/fix on these feeds is a standing service, not something we hand back at go-live and wish you luck with
When Every Dispense Counts
In rare disease every dispense record moves the numbers. Volume is small enough to read row by row, which is exactly why accuracy matters more. One missed dispense moves the patient count and the forecast with it, and one patient who stops refilling is a visible share of the cohort. The distribution network may be one or two pharmacies, which keeps the feed count small and the tolerance for error smaller. Time to therapy, the days between prescription and first fill, stops being an operational metric and becomes a number the board asks about by name. We build these feeds so the gap between a status change at the pharmacy and a status change in Salesforce is measured in hours, not in reporting cycles. That work runs alongside our rare disease launch platform and rare disease CRM builds, where the same patient record carries identification, hub enrollment, and dispense history in one place
Why Pharma Firms Bring Us These Feeds
Feed Onboarding Is a Defined Process
Every feed runs through the same steps: field mapping, value normalization, validation rules, and a status vocabulary shared across the network. The mapping is documented per pharmacy, which means fewer surprises in month two and a shorter list of questions for your pharmacy partners
Built on Infrastructure You Own
Feeds land in a warehouse in your AWS account rather than a platform we control and rent back to you. You own the data, the pipeline definitions, and the history. If we part ways, all of it stays where it is and your next partner picks it up
Trade, Finance, and Commercial in One Model
We model 852 inventory, 867 resale detail, and pharmacy dispense volume so they reconcile against each other. When the numbers disagree, and at some point they will, the model shows where the difference came from instead of leaving three teams to argue about it
Frequently Asked Questions
Do you work with the file formats our specialty pharmacies already send?
Yes. We adapt to the formats your pharmacies already produce rather than handing them a spec and waiting in their IT queue. Fixed width, delimited, Excel, EDI, SFTP drop or API, we map what arrives.
Where a pharmacy is willing to change a file, we will take the improvement. But nothing in the build depends on it, and your reporting does not wait on a partner's release schedule.
What is the difference between EDI 852 and 867?
EDI 852 is product activity data. It reports inventory and demand from the wholesaler or pharmacy: units on hand, units sold, and reorder signals for a product at a location.
EDI 867 is resale detail, sometimes called sell-through or chargeback data. It reports who sold what to whom, tying a shipment to the end customer.
Trade teams use 852 to watch stock and demand at the distribution point. Finance and commercial use 867 to understand where product ended up. We load both and reconcile them against dispense records so the three tell one story.
Can you combine specialty pharmacy data with our hub data?
Yes, and most firms should. The hub knows enrollment, benefits verification, prior authorization, and consent. The pharmacy knows dispenses, therapy starts and stops, and benefit adjudication results. Neither one answers time to therapy on its own.
We build consolidated daily reporting across both, so the patient journey reads end to end from enrollment through first fill and refills, with the handoff between hub and pharmacy visible instead of assumed. Our patient services hub integration work covers how those feeds get built.
Where does the data live?
In a commercial data warehouse inside your own AWS account. We build the pipelines and the data model, you hold the keys and the bill.
That matters the day you change vendors or bring analytics in-house, because the history stays with you. Salesforce and your BI tools read from that same governed source, so a number in a dashboard and a number on a patient record come from one place.
How do you handle patient privacy in these feeds?
Feeds move de-identified data keyed to tokenized patient identifiers where the use case requires it, so records link across pharmacies and the hub without moving names between systems. Anything patient-level that reaches a commercial user is consent-gated.
Data is encrypted in transit and at rest, access is role-based, and every load is logged for audit. Where a use case does not need patient-level detail, we aggregate before the data leaves the warehouse.