Skip to main content
Transactional API

Workflow

The Workflow section of the Transactional API covers operational processes that go beyond a simple read or write: multi-step actions a clinical system carries out on a patient's behalf over the course of an integration. Workflow builds on the base Transactional API: the same authentication and base URL apply.

Two workflows are covered today:

  • Investigation report filing: list a patient's unfiled reports, fetch one's full detail, optionally list their unfulfilled investigation requests to offer as fulfillable, then file the report.
  • Patient intake and inbound referrals: create (or find) a patient's Medicus record from their NHS number, fetch the tenant's referral metadata, then create the referral and clinical case together. Today this is used by mental health provider integrations, but the endpoints aren't mental-health-specific.

๐Ÿ“„๏ธRegister Patient Without NHS Number

Registers a new GMS permanent registration for a patient who has no NHS number yet (not yet traced, non-UK arrival, private-only, etc), the same effect as a receptionist completing the 'without NHS number' GMS registration in Medicus. User-restricted only. **Do not use this endpoint if the patient has an NHS number** - use register-permanent-nhs-patient instead, which registers via PDS and keeps the patient's NHS number correctly linked. This endpoint never checks whether one exists, and registers the patient without one regardless.