The pharmacy day | A question to investigate
The service happened. What happened to the claim?
At the end of a busy month, pharmacy teams need to understand whether work delivered, work recorded and payment received tell the same story. Differences can have legitimate explanations, including timing, eligibility or incomplete information. They can also create repeated investigation and uncertainty about the business. The useful task is to make those differences explainable, without assuming that every gap represents recoverable income or that more claims would be appropriate.
In the conversation.
NEUVIOR and our founder’s perspectives have appeared across science, business and technology publications.
Reporting, commentary, letters and podcast appearances | Read each feature for its format and source.
Keep four records conceptually separate
Distinguish the operational event, the claim submitted, its processing outcome and the cash or adjustment appearing in payment information. These may sit in different systems and periods. A reconciliation should use explicit dates and definitions so that a timing difference does not become an apparent missing payment. MYS already supports established contractor submissions and referred-back processes (NHSBSA, n.d.). A proposed intelligence layer must demonstrate useful analysis around that environment rather than pretend the official process does not exist.
Begin with one service and one question
An owner might want to know why recorded completions differ from submitted claims, why an exception recurs or how long an item remains unresolved. Select one of those questions before requesting a broad data extract. Use the current payment references and relevant service requirements to define eligible events. The review must never recommend changing the clinical record to fit a payment target or submitting a claim that the contractor cannot substantiate.
Design the smallest useful reconciliation
A proposed PHARMORIS evaluation could compare authorised aggregate counts for a single service across a defined period, followed by a carefully controlled review of exception categories. Inputs would include existing service summaries, submission reports, payment information and the team's explanation of known timing effects. Identifiable records would only be considered if genuinely necessary and separately authorised. The first deliverable could be a reconciliation table with an owner and next action for each unresolved category.
Use an exception ledger with a closing rule
For each discrepancy category, record the period, observed difference, known timing explanation, accountable reviewer and evidence needed to close it. Separate closed with no adjustment, corrected and awaiting decision, accepted adjustment and confirmed payment. Never sum these categories as recovered income. The owner can then distinguish a recurring process problem from a one-off backlog and decide whether the proposed intervention is reducing uncertainty or merely producing a longer list.
Follow the work all the way to the account.
Delivered, submitted, accepted and paid are different events. A reconciliation should explain the difference before assigning it a value.
An owner cannot reconcile service completions, submissions and payment information without repeated checking. Some gaps are timing differences; others require a supported explanation or an appropriate correction.
Prevents theoretical discrepancies being marketed as recovered income and reveals whether a new process reduces real administrative work.
What would we need to understand?
- Service events within the selected period
- Existing authorised submission reports
- Processing outcomes and payment information
- Known timing effects and review effort
Constructed decision example | No customer results are shown.
Distinguish detection from recovered value
Finding a discrepancy is not the same as resolving it, and resolution does not always produce extra cash. Some records may correctly be ineligible; others may already be paid in a later period. Track confirmed explanation, valid correction, accepted outcome and cash separately. Include the time spent reviewing and resolving issues. This protects the owner from a business case that counts theoretical recovery while ignoring the staff effort required or the official decision on payment.
Compare against the existing monthly routine
Measure how the team currently performs the reconciliation, what information it uses and the time spent on repeated checks. A new process should be compared with that credible baseline. Outcomes could include unresolved exception age, reconciliation completeness and preparation effort. Any financial result should use confirmed payment records and a clear counterfactual. Avoid extrapolating a first month's findings across a year, especially if the pilot is clearing an old backlog rather than changing recurrent performance.
Set safeguards for a commercial evaluation
Stop if source records cannot be reconciled, access is inappropriate or the process encourages unsupported claims. Keep contractor responsibility and professional accountability explicit. A useful result might be a clearer handover between service delivery and administration, a smaller recurrent exception set or an honest finding that existing tools already meet the need. The development question is whether PHARMORIS can add decision value beyond a spreadsheet or the functionality already provided by an established supplier.
NEUVIOR Data Analysis
A source.
A question.
A clearer decision.
Useful intelligence keeps its evidence attached.
Our public analysis connects a defined question with named sources, reporting periods and methods. Each source below shows the work available today and the access still needed.
Published-data analysis, research hypotheses and evidence studies are distinct kinds of work. Their meaning should remain clear as the programme grows.
NHS Business Services Authority | Annual
Prescription Cost Analysis
How does activity differ from ingredient-cost concentration?
Analysis availableNHS Business Services Authority | Monthly
English Prescribing Dataset with SNOMED Code
Which product and organisational patterns merit a closer investigation?
Metadata retrievedMedicines and Healthcare products Regulatory Agency | Event-driven; monthly roundup also published
Medicines and device safety communications
Which official communication should a responsible team read next?
Snapshot retrievedNHS Business Services Authority and NHS England | Weekly
Dictionary of medicines and devices
Can the same product identity be followed consistently across sources?
Access reviewMake the payment conversation evidence-led
Bring an anonymised description of the recurring mismatch and the management decision it delays. We can examine a bounded review that distinguishes paperwork, entitlement, processing and cash. Any proposed capability or integration would need to be demonstrated and agreed before commitment. The commercial purpose is a more reliable account of the pharmacy's work, with fewer unexplained differences and clearer responsibilities for resolving the ones that remain.
Sources and scope
NHSBSA | MYS for pharmacies | NHSBSA | Payments and pricing
NHSBSA (n.d.) MYS for pharmacies. Available at: https://www.nhsbsa.nhs.uk/pharmacies-gp-practices-and-appliance-contractors/dispensing-contractors-information/manage-your-service-mys/mys-pharmacy (Accessed: 14 October 2026).
Another useful angle.
- Independent pharmacy | Make the next service earn its place
A practical decision framework for independent owners comparing service demand, capacity, costs and cash before expanding.
- Supermarket pharmacies | Turn access into a coherent service
Explore the operational questions between supermarket footfall, pharmacy enquiries, clinical capacity and completed services.
- Pharmacy workforce | Build readiness around the service
Explore capability, cover and implementation dependencies before introducing a new pharmacy service or workflow.