|
|
Background
Information Standard DCB0090 describes changes to Organisation code format and specifically updates to the structure and format of ODS codes that Suppliers must be able to handle.
For further information see: Health and Social Care Organisation Reference Data
Outline Plan
- See dates above
Summary of Change
Describes the changes being applied to the Standard or Capability (i.e. a delta). May be a link to a summary of change provided by and maintained by the relevant Programme e.g. Release Notes created on NHS Developers Site by GP Connect team. However, where the change relates to a GP IT Futures Standard or Capability, then the detail of the change should be provided in tabular form separating new, updated or removed items. Populate the relevant link or table below and delete extraneous text
Data Standards
Updated requirements
| Requirement ID | Requirement Text | Level |
|---|---|---|
| GP-REF-2.1.13 | Health and Social Care Organisation Reference Data - New identifier structure Adhere to the aspects of DCB0090 regarding the structure and format of organisation codes. For further information see latest version of DCB0090: Health and Social Care Organisation Reference Data |
Full Specification
This should be a link or links to the updated standard or capability including the updated requirements so Suppliers can view the full specification
The following new versions of existing Standard(s) have now been published to support this National Standard:
- Data Standard v2.0.0
Link to the Information Standard and supporting documentation
- DCB0090: Health and Social Care Organisation Reference Data
Further information aimed at helping users fully understand the changes, and its impact, can be found at the link below:
https://hscic.kahootz.com/connect.ti/O_D_S/grouphome?done=GRPJustJoined
Users can subscribe here to the Organisation Data Service newsletter, and other NHS Digital bulletins.
Assurance Approach
The structure and format for many of the codes issued by ODS will change to ANANA on 1 October 2020. Note that this doesn’t apply to all organisation types. This is a standard structure of five alternating alphabetic and numeric characters, for example A1B2C. Existing codes will be unchanged. The change will apply only to codes issued from 1 October 2020 onwards for those organisation types which are in scope.
GP IT Futures onboarded Suppliers must undertake an impact assessment of their system(s) for the above and advise Solution Assurance of the outcome: whether their system(s) can handle the new structure and format of the ODS codes without any changes to their system(s) or if changes are required.
If no changes are required to their system(s), the supplier will self-certify compliance to aspects of DCB0090 regarding the structure and format of organisation codes.
If any changes are required to their system(s) and the supplier requires any test data or test environment support to test the changes, the supplier can advise Solution Assurance of their test support needs to achieve and self-certify compliance.
Impact assessment should include, but should not be limited to, consideration of:
- system use of the structure of the ODS code determine organisation type (e.g. prior to the ANANA change a Trust was three characters starting with R)
- system design that uses the assumption that a site code can be truncated to form the Trust code
- any field length restrictions on systems / screens / schema etc. that require update to deal with 5 character codes
All Roadmap items must have the label: roadmap_item. Then add labels from these categories as appropriate. Use one or more 'group' labels depending on the type of Capabilities and Standards impacted by the Roadmap Item: capabilities, context_specific_standards, overarching_standards, interop_standards, tbc. If above label is not "tbc", then use one or more 'ID' labels for each of the Capabilities and Standards that are impacted by the Roadmap Item e.g. s27, c12.