Developer documentation
Every Fastclinic application uses the same sign-in, credit ledger and record store. Developers can connect to these services through open standards, with the patient's permission at every step.

- 01Register your app and its redirect address
- 02Send people to Fastclinic Account with PKCE
- 03Receive a signed ID token
- 04Verify it against our published keys
Services
Integration begins with Fastclinic Account, on which every other service relies for sign-in.
A standard OAuth 2.0 and OpenID Connect provider. Your application sends people to Fastclinic Account, receives a signed ID token and does not store passwords.
- OAuth 2.0
- OpenID Connect
- PKCE
- Passkeys (WebAuthn)
One credit balance per person or organisation. Your service holds credits when work starts, captures what was used and releases the hold if the work does not take place. Retried requests do not charge twice.
- OAuth 2.0
- Idempotent operations
- Hold and capture
Records are written and read through a single consent-checked interface. Every read requires a current grant from the patient, and every action is recorded in the audit log.
- OAuth 2.0
- FHIR R4
- NDPA 2023
Doorcta is built on the other three services, so connecting to it means signing people in with Fastclinic Account, paying through Fastclinic Credits and reading reports from Fastclinic Record.
- OAuth 2.0
- OpenID Connect
- Consent-checked records
Integration principles
Health systems retry, time out and lose their connection. The interfaces are designed to behave predictably under those conditions.
- 01
Open standards
Sign-in uses OAuth 2.0 and OpenID Connect, health records export as FHIR R4, and laboratory and imaging messages use HL7 v2.5.1 and DICOMweb.
- 02
Idempotent charges
Every charge carries a reference derived from the work it pays for, so a retried request or a duplicate payment notification resolves to the same entry.
- 03
Consent before data
Every record read passes through Fastclinic Record, which checks the patient's grant first and refuses the request if none exists.
- 04
Public-key token verification
Your application verifies Fastclinic Account's ID tokens against our published public keys.
- 05
Audit logging
Append-only logs record sign-ins, grants, charges and record reads for you and your auditors.

Laboratory and imaging integration
The Integration Hub connects Fastclinic to a hospital's existing systems. It validates each exchange on arrival and holds aside anything that fails.
- FHIR R4
- Resources at version 4.0.1
- HL7 v2.5.1
- Admissions and transfers, orders and results, each one acknowledged
- DICOMweb
- Query, retrieve and store. Images remain in your PACS
The Hub stores original messages encrypted and allows each connection to be switched off individually.
The Integration Hub in detailIntegration enquiries
Describe what you are building and for whom, and our team will reply with the details.