NHS DSCR: assurance in progress
Salstead is built to the NHS Digital Social Care Records standards. Records follow the PRSB information models and use SNOMED CT codes, and you can take your data with you. This page shows where we stand on each standard.
Salstead is not yet listed on the NHS DSCR Assured Supplier list. We describe the platform as architected to the standards, with assurance in progress, and never claim to be assured or certified until that listing is granted.
The difference
Salstead covers care records and the running of the service around them, such as staffing, incidents and invoicing. It all sits on one data model with one login. The standards below shape how the whole platform is built, not just one module.
How it's built
PRSB About Me (v2.01) records the person's own words in seven coded sections. It is written by them or with them.
You can export a resident summary today, with demographics and About Me in SNOMED CT codes. It is shaped for FHIR, ready for GP Connect.
Row level security on every table. Sensitive fields are also encrypted by the application with AES-256-GCM, and roles are checked on the server.
A DCB0129 hazard log and clinical safety case are prepared. A named Clinical Safety Officer still needs to own and sign them off.
Mapped to the National Data Guardian's ten data security standards, and set out ready for a Data Security and Protection Toolkit submission.
The application and database run in the same London region. A health check is monitored, and tests run before every release.
Interoperability, shipping today
Any resident record can be exported as a summary. It holds the person's demographics and their PRSB About Me, with each section coded to SNOMED CT. That means you can move your data if you leave, and it is the shape GP Connect will map to FHIR once NHS onboarding is complete.
resident-summary.json
{
"standard": "PRSB About Me v2.01 + demographics",
"person": {
"nhsNumber": "943 476 5919",
"preferredName": "Maggie",
"gp": { "practice": "Mansfield Road Surgery" }
},
"aboutMe": [
{
"section": "What is most important to me",
"snomedCode": "1515861000000103",
"text": "My independence, and a cup of tea first."
}
]
}Full coverage
5 are in the product today. The rest are in progress, or waiting on an NHS onboarding step or an appointment we need to make.
Business continuity
Daily backups and a written recovery plan. Point-in-time recovery is not yet switched on.
Clinical safety (DCB0129)
Hazard log and safety case prepared. A Clinical Safety Officer is still to be appointed.
Commercial
Contract, service levels and exit terms, awaiting legal sign-off.
Data migration
Export is live. Import from other systems is being built.
Data standards
Records follow the PRSB information models and use SNOMED CT codes.
About Me (PRSB v2.01)
The person's own words, in 7 coded sections, on every resident record.
Personalised care & support plan
Care plans are being aligned to the PRSB model.
Hosting
The application and database are hosted in London. Evidence for assurance is being prepared.
Information governance (DSPT)
Mapped to the 10 National Data Guardian standards. We will make the toolkit submission ourselves.
Non-functional
Performance, availability and health monitoring.
Testing
Automated tests run on every change before release.
Interoperability
A coded resident summary you can export, with demographics and About Me.
GP Connect
An export shaped for FHIR is in place. NHS onboarding is still to come.
Electronic communication
Authenticated email. No clinical personal data is sent by email.
The 2026 data standard
The Minimum Operational Data Standard sets a common baseline of care data in nine groups. Salstead records all nine today, and a conformance view shows how complete your own records are.
All nine groups are captured today; three are being structured to the full MODS shape. We never claim MODS certification or NHS assured status until it is formally granted.
Compare Salstead with other care software, or book a short walkthrough of the record, the export and how we protect data.