Get your MYS claims and submissions through an API

What you can build on MYS

• Get the month's service claims

  Build this

  Reads one pharmacy's payment claims for a month, one per service such as Pharmacy First, as MYS has populated them, with each claim's status.

  Takes

  ODS code, claim month

  Returns

  Service, claim month, number of provisions, claim status, submitted date

• Get referred back and disallowed items

  Build this

  Reads the referred back and disallowed items MYS holds for one pharmacy, with the reason given and where each one stands until it is processed.

  Takes

  ODS code, dispensing month (optional)

  Returns

  Dispensing month, item, type (referred back or disallowed), reason, status

• List past end of month submissions

  Build this

  Reads the end of month prescription submissions a pharmacy has made in MYS, with the figures entered on each batch submission form.

  Takes

  ODS code, from month (optional)

  Returns

  Dispensing month, submitted date, submitted by, form figures

• Submit a reviewed service claim

  Build this

  Opens one month's populated payment claim for a service, compares its number of provisions with the one you expect and, if they match, submits it.

  Takes

  ODS code, service, claim month, expected number of provisions

  Returns

  Service, claim month, number of provisions, claim status, submitted date

Automate MYS with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Last month's service claims, ready for review

  Build this

  Starts

  On the 2nd of every month at 8:00, London time

  Step 1

  For each ODS code you name, get last month's service claims.

  Step 2

  Keep the claims that are not yet submitted.

  Step 3

  Email you the list, one section per pharmacy, so each claim is reviewed before the Pharmacy First deadline on the 5th.

• New referred back and disallowed items, every pharmacy

  Build this

  Starts

  Every weekday at 9:00, London time

  Step 1

  For each ODS code, get the referred back and disallowed items.

  Step 2

  Keep the items that were not there on the last run.

  Step 3

  Post each one, with its reason and status, to your webhook.

• Claims still open before the deadline

  Build this

  Starts

  On the 4th of every month at 12:00, London time

  Step 1

  For each ODS code, get last month's service claims.

  Step 2

  Keep the claims whose status is not submitted, and stop when there are none.

  Step 3

  Email you the pharmacies and services that still need a claim submitted.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get the month's service claims” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "manage-your-service-pharmacy.nhsbsa.nhs.uk/get_service_claims",
    "input": {
      "ods_code": "FZX41",
      "claim_month": "2026-10"
    }
  }'

{
  "status": "completed",
  "data": {
    "ods_code": "FZX41",
    "pharmacy": "Northwind Pharmacy",
    "claim_month": "2026-10",
    "claims": [
      {
        "service": "Pharmacy First",
        "provisions": 112,
        "status": "Not submitted",
        "submitted_date": null
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

MYS’s own options

The NHSBSA publishes APIs for pharmacy IT system suppliers, not for pharmacies. A supplier's system sends each service provision to the NHSBSA, which uses it to fill in the pharmacy's payment claim in MYS. The pharmacy owner still reviews and submits that claim, the end of month submission and everything else in the portal itself.

Read on November 12, 2026: MYS: Pharmacy (NHSBSA), Developer Guide to the NHSBSA API for Community Pharmacy Claims, Manage Your Service Registration and Log-in Guide.

Signing in to MYS

MYS signs you in with your personal NHSmail address and its password, after an invitation from Microsoft Invitations on behalf of MYS Registrations. With access to several pharmacies you enter the ODS code of the one you want. With Fous you sign in once through MYS's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Pharmacy First claims are due by the 5th

Pharmacy First data shows in MYS from the 1st of the following month. The pharmacy owner reviews the claim and submits it by the 5th, or the 6th when a bank holiday falls in the first five days.

Your IT system fills the claim, not you

Your clinical IT system sends service provisions to the NHSBSA by API throughout the month. The pharmacy owner checks that data in MYS and reviews the claim before submitting it.

One pharmacy at a time

A user with several pharmacies enters the ODS code of the one to open after signing in, or a YP code for a group. That is why each method here takes an ODS code as an input.

Paper prescriptions still go by post

The end of month submission is done online in MYS, but the paper prescriptions themselves are still sent to the NHSBSA as before.

More in Healthcare

• PECOS
• PCSE Online
• CAQH Provider Data Portal
• 340B ESP
• 340B OPAIS
• Henry Schein online ordering
• AAH Hub
• ABC Order
• Alliance Healthcare portal (UK)
• Cardinal Health Order Express
• McKesson Connect
• PharmaClik
• NHS Supply Chain Online Catalogue
• McKesson SupplyManager
• Medline.com

Other industries: Allianz Maklerportal, Portal Informacyjny Sądów Powszechnych, Extensiv 3PL Warehouse Manager, LPL ClientWorks, myDCLI, Carrier 360 by J.B. Hunt.