Here is something we hear from pharmacists constantly, and it never stops hitting home: "I didn't go to school for this. I don’t even know where to start."
Medical billing is a specialty. It is dense, it is payer-specific, it is full of CPT codes and remark codes, and eligibility nuances and payer-specific rules that seem to change without warning. Pharmacists are trained to care for patients, not to navigate the labyrinthine world of Medicare Advantage plans, E&M codes, and timely filing windows. And yet, more and more, pharmacy success depends on getting the billing right.
That gap, between the clinical work pharmacists already do and the billing knowledge required to get paid for it, is exactly why DocStation Copilot exists.
When we first launched Copilot's claim summary feature, the goal was straightforward: give pharmacies a starting point when a claim goes wrong. Explain the error. Reduce the guesswork. That was a good start. But we kept listening. We kept watching where pharmacies got stuck, where the questions piled up, where the support queue filled with variations of the same underlying problem. And we kept building.
What we have been working toward, and are actively testing right now, is a version of Copilot that goes far beyond claim summaries. The vision is an AI billing assistant that actively investigates your claims alongside you, searches for answers, surfaces coverage details, and helps you understand what is happening and what to do next, and eventually taking that action for you automagically. We designed it to be the billing expert you can reach at any hour, on any claim, without having to know exactly what question to ask.
We are not calling this finished. Beta testing is where you find the edges, and we are genuinely enjoying this process. But what Copilot is already doing in our testing is exciting enough that we want to share it, and more importantly, we want real pharmacies in the room to help us make it great.
Here is what we have built.
A Smarter First Responder for Every Claim
One of the first things we redesigned is what happens when a pharmacist needs help on a specific claim. The "Request Support" button now routes directly to Copilot, with a prompt already filled in based on what the claim summary found. The goal: when you need help, you should not have to re-explain the problem. Copilot should already know what the summary said and pick up from there.
From that point, Copilot is designed to do more than answer the question you typed. It makes tool calls, pulls the claim record, reviews the claim history, and checks for relevant guidance before composing a response. In testing, we can watch it work through those steps in real time. And when Copilot cannot do something, like trigger a real-time eligibility check from a certain context, it says that directly rather than guessing. We think that honesty matters.
This is the biggest shift in the direction we are taking Copilot. From a summary tool to something closer to an active research partner.
Eligibility Answers Without the Payer Portal Detour
Eligibility questions are one of the most common reasons claims fail and one of the most time-consuming things to track down. Which plan is the patient actually on? Do they have Part B? Are they Medicare Advantage? Is this service covered, and at what rate?
We designed Copilot to surface existing eligibility check results from a patient's profile and summarize the coverage details, including service types, co-pays, co-insurance, deductibles, and Medicare Advantage status, all inside the platform. In our testing, asking it a natural question about a patient's coverage and getting a direct, readable answer has been one of the most satisfying things to watch.
There is also a detail worth calling out separately: when an eligibility check comes back with an incorrect subscriber ID, DocStation is now designed to look up and return the correct member ID directly from the payer. For pharmacies that deal with subscriber ID mismatches regularly, this is the kind of friction point that sounds small until you are doing it manually for the fifteenth time. We want Copilot to handle that.
How well these eligibility workflows hold up across different payer configurations is exactly the kind of thing beta testing will tell us. We are paying close attention.
The Financial Picture, Right Where You Are Working
DocStation's Analytics and Insights dashboards give pharmacy owners a view of their billing performance. We are building toward making that same data accessible through a conversation directly on the Claims page.
The design intent is this: ask Copilot what the financial impact of your invalid, rejected, and denied claims is, and it gives you a breakdown by status, by dollar value, and by what is most at risk. Follow up to dig into root causes, and it categorizes the denial and rejection reasons in your claim set at a level the query builder does not currently reach on its own.
For pharmacy owners, financial exposure from unresolved claims can be invisible until it is already a real problem. We built this to make that a conversation you can have before it becomes one. Testing is showing us where the data connections are solid and where they need more work.
Find Any Claim Set, Just by Asking
The Query with AI feature has gotten a meaningful refresh and is one of the capabilities we are most excited to get in front of real pharmacy workflows.
The idea: describe what you want to see in plain language. "Show me all my invalid claims." "Show me rejected claims for HealthPartners of Minnesota." Copilot generates the filter, shows it to you for review before applying it, and you can refine it with a follow-up message if needed. It also works well with voice dictation, which for a pharmacy counter environment is not a small thing.
This is designed to be the on-ramp for pharmacies that have not fully adopted the manual query builder. Whether it actually feels that way in practice is something we are learning.
Upload a Remittance File, Let Copilot Do the Matching
This capability is one of the more ambitious things we are testing, and we want to be upfront about that.
The goal: upload ERA files or EOB PDFs directly in Copilot chat and ask it to update the corresponding claims in DocStation. For pharmacies where ERA files are not yet flowing through an EDI connection, or where paper remittance is still part of the reality, claims can sit in limbo long after a payer has fully adjudicated them. We want Copilot to close that gap.
In testing, Copilot is reviewing the files, identifying which claims are referenced, and matching them to records in DocStation. But file size and certain payer export formats are presenting real limitations we are actively working through. This one benefits enormously from real-world variation, and that is exactly what beta access will give us.
A Knowledge Base That Gets Sharper Over Time
One of the pieces of this we are most quietly proud of is something you mostly will not see directly. Copilot searches DocStation's internal Help Center articles in real time as part of its research process, the same articles our support team maintains and updates. When guidance gets written down, Copilot has access to it immediately.
And when a question takes it outside of what lives internally, Copilot is designed to search the web. Coverage policies, prior authorization requirements, formulary details: if the answer is findable, Copilot should go find it. In testing, this has worked well for drug coverage questions that previously required a tab switch to a payer portal.
What we are learning is that Copilot's quality is directly tied to the quality of the guidance available to it. That is actually an empowering thing for the pharmacies who will use it: the more your team documents how specific issues get resolved, the smarter Copilot gets for your context specifically.
It Gets Better When You Talk Back
The most important thing we can say about where Copilot is right now is this: it needs to hear from real pharmacists doing real billing work.
Every thumbs up or thumbs down tells us something. A thumbs down with a note tells us exactly where the gaps are. A thumbs up confirms what is landing. We are building a free-text feedback field into the Copilot chat shortly, and a version is already active on claim summaries. We look at this feedback closely and use it to shape what gets built next.
That is not a courtesy note at the bottom of an article. That is the actual mechanism by which Copilot improves. Beta testers are not just early users; they are co-authors of what this becomes.
This Is What "Pharmacy Beyond Pills" Actually Looks Like in Progress
Pharmacists are doing the work. Clinical services, patient consultations, vaccine administration, chronic care management. The clinical future of pharmacy is not hypothetical. It is happening at pharmacies across the country right now.
Getting paid for that work requires navigating a billing system that was not built with pharmacists in mind. DocStation Copilot is our answer to that gap. The vision is to be everywhere, for every pharmacy, at every step of a claim's life, without requiring a billing degree to get there.
We are proud of how far this has come, honest about how much further it has to go, and genuinely excited about what it becomes when it meets the reality of pharmacy billing at scale.
That is why we are opening beta access. We want your pharmacy in the room.
Join the Beta
DocStation Copilot is in active beta testing. We are inviting a select group of pharmacies to get early access, use the features described here, and give us the real-world feedback that shapes what comes next at no cost.
Request beta access if you are a current or prospective DocStation customer who wants to be among the first pharmacies to put Copilot through its paces. We’ll be in touch shortly with guides and tutorials.
We will be sharing more as testing progresses. Stay close.
DocStation is a unified clinical services platform for pharmacies. We handle medical billing, patient management, scheduling, and revenue analytics, everything beyond the dispensing system, so pharmacists can focus on the work that matters.
