Skip to main content

November 2017 newsletter

Read our quarterly Organisation Data Service (ODS) newsletter - November 2017

Access Database decommissioning

In the August newsletter we told you that from November 2017 onwards we would not publish the OrgCurDev product (also referred to as the Access Database). The product will be available by request only.

We have received some enquiries from users who wish to continue using this product. Therefore we have reviewed our decommissioning plans. Whilst we recognise that there is a need to remove this product as soon as practicable we do not wish to impact service delivery. We will adjust our decommissioning process to reflect user needs if necessary.

We have decided to:

  • ask all users requesting the database to complete a short questionnaire detailing their business need and the impact of us removing the product entirely
  • assess the migration paths for each request received and identify any potential gaps
  • collate this information until February 2018 at which point we will review how we can best meet user needs moving forwards (we will ask users who request the database to feed into this process)

If you need to continue using OrgCurDev

Contact exeter.helpdesk@nhs.net and log a call for the ODS team.

The replacement for OrgCurDev

In recent years we have made sizeable improvements in our products to provide modern interfaces to Organisation Data. Much of the functionality included in the OrgCurDev is available in many other ways, listed below:

  • the ODS portal supports many searches, including Organisation code, type, partial name and postcode to provide access to organisation data
  • all organisation reference data is available in a single XML file, which is richer than the data in ORGCURDEV. Tools which allow data transformation in to a set of landing tables for a staging database are also provided. The tools can build a set of tables which resemble those in the Access Database
  • also, we are building an Application Programme Interface (API) which aligns to the XML data model. A supported version of this product will be available before the end of March 2018.

Application Programming Interface

We have updated the approach to deliver the ODS Application Programming Interface (API) service to meet the needs of different customer groups. As a result, the "ODS API Suite" will accommodate two styles of API offered from a single service.

An interface aligned to the ods-Fundamental Standard which allows consumers to synchronise changes into a local data store. "ODS HSCOrgRefData API" will provide users with the latest view of the data published within the XML products. This allows users to baseline organisation reference data from the XML products and then connect to the API to retrieve updates.

An interface based on the Health Level Seven International (HL7) Fast Health Interoperability Resources (FHIR) standard "ODS Lookup API" will be hosted. This will support transactional use cases, generally associated with clinical messaging.

We have established a review group to support NHS Digital in delivering a service which meets consumer requirements. An early version of the service will be available to members during December.

We will be supporting a workshop in Leeds in early 2018 and then we will widen access to a beta version of the service. We plan to release the Live service by the end of March 2018.

Care homes data

We are continuing to work with the Care Quality Commission (CQC) to align our data.

We have made a decision to re-parent care home sites rather than to close them and create new codes for these sites. This will mean that users lose the ability to trace the previous HQ record of the site, using predecessor/successor site information in the successor file. We will maintain this information and be able to provide this on a request basis. Approximately 2,000 sites will be re-parented.

We plan to complete the alignment work by the February quarterly publication. In the meantime, we continue to run an interim process.

In the October monthly amendment file, we omitted fields three and four. This is a result of the interim nature of the current process. We have resolved the issue for the November 2017 publication.

Customer self-service call logging

New from 18 October 2017 for NHS HSCN only (previously known as N3 network) - Instead of emailing or phoning the help desk you can now log and monitor your own calls using our Self Service Portal.

The Portal will offer you the following benefits:

  • log calls outside of normal service desk hours
  • monitor the progress recorded on your calls
  • add updates and escalations on your calls
  • accept or reject resolutions offered for your calls
  • view your recently closed calls logged using the portal

If you would like to use the portal please contact the service desk exeter.helpdesk@nhs.net for an account to be set up, providing the following information:

  • first name
  • last name
  • telephone
  • email address
  • organisation name (and code if available)

You should allow up to 10 working days for your account request to be processed. You will receive an email with your account details when completed.

The Service Desk cannot accept requests for generic accounts. Currently your email address MUST NOT be a shared mailbox, as the Service Desk will send your account details to this address.

Health and Justice Commissioning Hubs

In the October 2017 production, we have included 9 more Commissioning Hub (proxy CCG) records in the eccg.csv file and full XML file. The codes allow specific areas of NHS England to be uniquely identified for Health and Justice commissioning. They support granular reporting and better analysis of national data for Health and Justice activity.

The codes have 'H&J' in the Organisation Code Name field to make them identifiable. At a later date, we intend to introduce a new secondary role of Health and Justice Commissioning Hub into the XML data.

Enurse file

We have replaced our processing tool that produces the enurse file. During the configuration of the new tool, we found that we were publishing more than one name for the same organisation in field 18 (Current Care Organisation Name). This was due to ODS only processing this field if the value provided in field 17 (Current Care Organisation Code) of the raw data (provided by the NHS Prescription Service) matched an existing Clinical Commissioning Group (CCG) in our system.

We have corrected this by populating this field ourselves for every record with the Official CCG name. By doing this 73% of all records in the enurse file have a change to this field.

We have created a file without this volume of change, it is available on request.

We are using the official CCG names for all but 4 CCGs, these CCGs have names that break the max character length of 40 characters for this field. For these organisations we have used their official shortened names as follows:

Code Short name Official name
03D NHS HAMBLETON, RICHMOND & WHITBY CCG NHS HAMBLETON, RICHMONDSHIRE AND WHITBY CCG
00D NHS DURHAM DALES, EASINGTON & SEDGE CCG NHS DURHAM DALES, EASINGTON AND SEDGEFIELD CCG
05Q NHS SE STAFFS & SEISDON PENINSULA CCG NHS SOUTH EAST STAFFORDSHIRE AND SEISDON PENINSULA CCG
99P NHS NORTH'N,EAST'N & WEST'N DEVON CCG NHS NORTHERN, EASTERN AND WESTERN DEVON CCG

Unique Property Reference Number Introduction and County removal

We have been working with GeoPlace to match UPRN detail to our live records.

Before we upload this data to ODS systems and publish it via ODS XML products, the service must migrate its address lookup software. We currently uses a Postcode Address File (PAF) derived product. We need to change to an AddressBase derived product to maintain UPRNs.

As previously communicated an impact of using AddressBase will be that we are no longer able to maintain county values. Residing addresses will continue to hold a county value but any new addresses will not. We documented this change in ODS' ods-Fundamental Standard published in autumn 2016. We will amend the repository to remove any occurrence of a mandatory county value and replace it as non-mandatory.

The work to implement new addressing software is likely to take place in February. Shortly after this we will begin to publish UPRN data within XML products.

NHS organisation changes

Subject to approval from NHS England, the following organisation change is effective from 1 April 2018 and will be published on November 2017.

CCG merger.

Previous CCG Previous CCG New CCG
NHS Aylesbury Vale CCG (10Y) NHS Chiltern CCG (10H) NHS Buckinghamshire CCG (14Y)

On the 1 October 2017 the following organisations have merged to create a new organisation.

Current Trust name Current Trust name New Trust name
Central Manchester University Hospitals NHS Foundation Trust (RW3) University Hospital of South Manchester NHS Foundation Trust (RM2) Manchester University NHS Foundation Trust (R0A)

We have added legal close dates for codes RW3 and RM2 to reflect the dissolution of the organisations, confirmed in SI 2017 No 932. We published this information in the ODS publication files on the 27 October 2017.

The following organisation changed its name on 6 November 2017, although the code will remain the same.

The change will be published in the November data files on the 24 November 2017.

Old Trust name New Trust name
The Whittington Hospital NHS Trust (RKE) The Whittington Health NHS Trust (RKE)

Contact us

If you have any queries regarding the articles in this newsletter please raise a service call for the attention of the ODS team with the exeter.helpdesk@nhs.net

Last edited: 4 October 2019 1:35 pm