Organisation Data Service : Other Application / System / Service Providers

Data Description

Several different organisation types which either did not warrant their own dedicated file at the point of creation, or did not easily fit within an existing file.

  • Local Service Providers(LSP)
  • Local Service Providers(LSP) Sites
  • Application Service Providers
  • Application Service Providers - Legacy Primary Role/Organisation Type (no longer used)
  • National Application Service Providers (NASP)

How Data is Maintained

The ODS team check the Government website of the Office for Public Sector Information (OPSI) on an ad-hoc basis and implement any changes required. Information on minor changes, is relayed to ODS via the organisations in question. Where possible, this is facilitated by an established ODS contact based within the organisation (referred to as an OC1). No changes to the records associated to an organisation can be carried out without the express permission of the contact for that organisation, although exceptions can occur such as where a contact is no longer working at an organisation, or changes have been agreed with an NHS England national programme (i.e. COVID vaccination programme).

Where organisation details are not published by OPSI, ODS may accept requests for new codes direct from the provider. A business justification as to why an ODS code is required is sought from the provider and their status/function as an Application Service Provider is confirmed.

Data Quality Assessment

For further information re the: ODS Data Quality Assessment Framework



Data Quality Dimension
Last updated:

 

12345ODS mastered or 3rd party data6789

OVERALLFrequency of UpdateData Collection MethodFit for PurposeCoverage / CompletenessReliability / AccuracyData Agreement3rd Party Escalation RoutesSystem Application / Downstream System FeedbackFuture Refinement / Improvement Plan
Application / System / Service ProvidersGREENGreenGreenGreenGreenGreenODSn/an/aGreenGreen

Ad HocODS mastered, customer logs via helpdesk requesting amendments

Codes created to meet demand

Code created to meet demand - only code as required for ASP to interact with the NHS

Good - dependent on org informing ODS of changes or closures


n/an/aNo known issuesNot required

Key Information - Roles, Code Formats and Data Source

Key Information
Geographic coverage
  • England
Primary Role ID





RO146Primary Role Name





LOCAL SERVICE PROVIDER (LSP)
RO147LSP SITE
RO159NATIONAL APPLICATION SERVICE PROVIDER
RO92APPLICATION SERVICE PROVIDER
RO93APPLICATION SERVICE PROVIDER - LEGACY
Non Primary Role ID
N/ANon Primary Role Name
N/A
Raw Data SourceGovernment website of the Office for Public Sector InformationUpdate FrequencyAd-hoc
Code Format
Organisation TypesCharacter PositionsComments
12345678
All Applicable 
Organisations
A-Z0-9A-Z0-9A-Z


Issued after 1 October 2020

Local Service Providers (LSP)

LSP0-90-9


Issued before 1 October 2020

Local Service Providers (LSP) Sites

LSP0-90-90-90-9
Issued before 1 October 2020

Application Service Providers

YGMA-Y, 0-9A-Y, 0-9


Issued before 1 October 2020

Application Service Providers - Legacy

YGA-Y




Issued before 1 October 2020

National Application Service Providers (NASP)

YEA-Y, 0-9




Issued before 1 October 2020

Permitted Relationships

Permitted Relationships - Local/National/Application Service Providers can be linked to (upward):

Source Primary Role ID

Relationship Type IdRelationship Type NameTarget Primary Role IDTarget Primary Role Name

RO146

RE3IS DIRECTED BYRO189SPECIAL HEALTH AUTHORITY (SPHA)
RE3IS DIRECTED BYRO209NHS ENGLAND (REGION)
RE3IS DIRECTED BYRO91EXECUTIVE AGENCY PROGRAMME
RE5IS LOCATED IN THE GEOGRAPHY OFRO185REGIONAL OFFICE (RO)
RO147RE6IS OPERATED BYRO146LOCAL SERVICE PROVIDER (LSP)
RO159RE3IS DIRECTED BYRO91EXECUTIVE AGENCY PROGRAMME

Legacy .csv File Mapping

Click here for an explanation of the baseline data differences between legacy csv files and ODS Data Search and Export and the ODS APIs.

eother.csv

Primary Role / OrgTypeID – RO89, RO90, RO91, RO92, RO93, RO102, RO103, RO105, RO116, RO126, RO131, RO134, RO146, RO147, RO150, RO158, RO159, RO162, RO168, RO169, RO191, RO261

Change from legacy csv: ASP organisations that did not have YGM* codes were missing from the legacy eother.csv report but are included in current products.

Col

Data Item

Report Alias (Legacy csv)

Notes

1

[OrganisationCode]

Organisation Code


2

[OrgName]

Name


3

[NHSER_code]

National Grouping

Change from legacy csv: Geographic extension of the postcode using the geographies table

4

[ICB_code]

High Level Health Geography

Change from legacy csv: Geographic extension of the postcode using the geographies table

5

[Address1]

Address Line 1


6

[Address2] 

Address Line 2


7

[Address3] 

Address Line 3


8

[Town]

Address Line 4


9

[County] 

Address Line 5

Change from legacy csv: As this is a legacy field, not populated for new addresses since 2018, this field within the ODS Data Search & Export tool (including pre defined reports) will not be populated.

Note that the value (where populated) is available via the FHIR Organization Resource in the address.district property.

10

[Postcode] 

Postcode


11

[LegalStartDate] 

Open Date


12

[LegalEndDate] 

Close Date


13

 NULL

Column 13


14

 NULL

Column 14


15

[TargetOrgCode]

Parent Organisation Code

RE6 relationship – Where LegalEndDate is null, or where the relationship LegalEndDate is equal to the organisation LegalEndDate

Only populated for RoleID RO191

16

 NULL

Column 16


17

 NULL

Column 17


18

 NULL

Column 18


19

 NULL

Column 19


20

 NULL

Column 20


21

 NULL

Column 21


22

‘1’

Amended Record Indicator

Set to 1 for Report

23

 NULL

Column 23


24

 NULL

Column 24


25

 NULL

Column 25


26

 NULL

Column 26


27

 NULL

Column 27