A Microsoft Access Intermediate Database (IDB) for collating data for submission to the Mental Health Services Data Set (MHSDS).
The IDB can be populated with the relevant data and submitted to the landing platform.
The structure of the IDB must not be altered in any way. All tables must be present, even if some are not appropriate to the submission (based on the activity that has taken place). All fields listed in each table must also be present and field types must be exactly as specified.
The data items required to populate the IDB should be extracted directly from the appropriate service provider systems, such as a clinical system or Patient Administration System.
Read more on our Intermediate Database (IDB) guidance pages.
Tests of the submission portal have found a technical issue with this release.
This release stores entered text with padded spaces up to the maximum field length.
This does not affect the structure or population of the IDB, but could impact downstream processing after submission to NHS Digital.
We’re working on a new release that will contain identical table and field names, field types and sizes - the only difference will be that entered text will not be stored with padded spaces up to the maximum field length.
This is an internal change to the IDB concerning the physical storage of data after entry. All Provider/Supplier processes and systems that have been developed to populate this release should not be affected and will work with the new release.
The new release will be available shortly.
Released on Tuesday, 10 August 2021.
The submission portal is being developed and tested, and part of that testing includes testing this release of the IDB - the content is subject to change as development continues.
We’ll announce and publish the final IDB as soon as possible. Subscribe to this item to receive updates on the IDB.
Released on Friday, 18 June 2021.
This release is useable from 9 June 2020.
This amended release incorporates format changes to 6 data items to resolve submission validation errors identified at go-live. All table and field names remain the same. Please see the production log included in the release for details of the changes.
This release should be used for all 4.1 submissions going forward.
Released on Monday, 2 March 2020.