Skip to content

FousPCSE Online

Get your PCSE Online claims and statements by API

Search your GOS1, GOS3, GOS4, GOS5 and GOS6 claims and read your ophthalmic payment statements in PCSE Online with one API call each. A workflow can check for a new statement each morning and post its claim lines to your accounting system.

Works with your own PCSE Online account. Fous is an independent product.

What you can build on PCSE Online

  • Search GOS claims

    Build this

    Uses Search for Claim on the Ophthalmic Payments dashboard to find claims by claim type, claim status, performer, patient's surname or date.

    Takes
    Claim type, claim status (optional), performer's name (optional), date from, date to
    Returns
    Claim number, claim type, contractor, performer, patient's surname, claim status, date
  • List payment statements

    Build this

    Opens Statement on the Ophthalmic Payments dashboard and searches by date range, up to three months at a time, and statement type.

    Takes
    Date from, date to, statement type (optional)
    Returns
    Reference number, statement type, statement date
  • Get the claims on a statement

    Build this

    Opens one statement by its reference number, uses Expand All and reads every claim line in its line-by-line breakdown.

    Takes
    Statement reference number
    Returns
    Your reference, claim ID, patient's name, point of service date, amount submitted, amount to be paid
  • Cancel a claim not yet accepted

    Build this

    Finds a claim with Search for Claim, selects Cancel claim, chooses the cancellation reason and confirms.

    Takes
    Claim type, claim number, cancellation reason
    Returns
    Claim number, claim status, confirmation message

Automate PCSE Online 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.

  • Claims waiting for the contractor signatory

    Build this
    Starts
    Every weekday at 16:00
    Step 1
    For each claim type, search the claims whose status shows they wait for the contractor signatory.
    Step 2
    Keep the claims that were already waiting on the last run.
    Step 3
    Email you the list with claim number, claim type, performer, patient's surname and date.
  • New payment statement, claim lines to accounts

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    List the payment statements dated in the last month.
    Step 2
    Keep the statements that were not there on the last run, and stop when there are none.
    Step 3
    Get the claim lines on each new statement.
    Step 4
    Post the statement reference and its claim lines to your accounting system's webhook.
  • Weekly claim counts by performer and status

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    For each claim type, search the claims dated in the previous seven days.
    Step 2
    Group them by performer and claim status.
    Step 3
    Email you the counts, one line per performer, with the claim numbers of claims not yet 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 “Search GOS claims” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "secure.pcse.england.nhs.uk/search_gos_claims",
    "input": {
      "claim_type": "GOS1",
      "date_from": "2026-11-02",
      "date_to": "2026-11-06"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "claims": [
      {
        "claim_number": "OPH-4471920",
        "claim_type": "GOS1",
        "contractor": "Acme Opticians",
        "performer": "A. Northwind",
        "patient_surname": "Globex",
        "claim_status": "Submitted",
        "date": "2026-11-04"
      }
    ],
    "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.

PCSE Online’s own options

Practices submit GOS1, GOS3, GOS4, GOS5 and GOS6 claims in PCSE Online, free of charge, or through a PMS provider's integrated eGOS solution. PMS users get support from their provider, and every user, PCSE Online or PMS, views statements in PCSE Online.

OptionWhat it coversWhat it takes
Your practice management systemClaims sent from your PMS's eGOS integration instead of PCSE Online.A PMS that offers it. Support for online claims comes from your PMS provider.
PCSE Online by handMake a Claim, Search for Claim, Claim Submission and Statements, which print or download as PDF or CSV.A free PCSE Online account. A User Management (Organisation) role holder sets up users, with at most four user admins per practice.

Read on November 12, 2026: Ophthalmic Payments, Move to online GOS claims, Using PCSE Online for Ophthalmic Payment services (user guide).

Signing in to PCSE Online

PCSE Online signs you in with your email address as the username and a password. Five wrong passwords lock the account until PCSE is contacted, and if you belong to more than one organisation you pick it after signing in. With Fous you sign in once through PCSE Online'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

Statements in three-month windows
A statement search covers at most three months at a time, and a longer range shows an error. Statements go back seven years, including the current year, so a longer range is searched in three-month periods.
A statement follows your area's payment run
PCSE sends a notification when the payment run for your area is complete. Claims submitted close to a cut-off, or needing further action, may not appear on the current statement.
Accepted claims cannot be cancelled online
PCSE Online shows a cancel option only for a claim that has not been accepted. An accepted claim is cancelled through the Contact us form, and it shows as a deduction on your next statement.
Roles decide what an account sees
Statements need the OPHStatementView role, and only a user with the Contractor Signatory role can bulk sign and submit claims. Your organisation's user administrators assign roles, not PCSE.

More in Healthcare

Other industries: AXA Connect, eCourts e-Filing, e-SkyCargo, Empower Plan Service Center, APM Terminals TERMPoint, RXO Connect.

Frequently asked questions

PCSE's own pages describe two routes for GOS claims: PCSE Online itself, free of charge, or a PMS provider's integrated eGOS solution. Either way, every user views statements in PCSE Online.

Select Statement on the Ophthalmic Payments dashboard, search by date range and statement type, then open the statement by its reference number. Expand All shows every claim line, and Print/Download saves it as PDF or CSV. Each search covers at most three months.

PCSE says claims submitted close to a cut-off, or needing further action, may not appear on the current statement. If claims were sent in time and still not paid, PCSE asks you to use the GOS Payment Query option on its online form.

No. NHS England mandated that all GOS submissions be made online from 1 January 2024, through PCSE Online or a practice management system. Every practice, including one that claims through its PMS, views its statements in PCSE Online.

No. Fous is an independent product. You use it with your own PCSE Online account, and a method reads and does only what that account's roles allow.

Put PCSE Online behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextCAQH Provider Data Portal340B ESP340B OPAISAXA ConnectHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of PCSE Online (Primary Care Support England (delivered by Capita for NHS England)). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.