Data Description
Pharmacies/Dispensaries in England, Wales and the Isle of Man. In ODS legacy .csv products, codes for Appliance Contractors were published alongside pharmacy/dispensary codes in the edispensary.csv file.
Each Pharmacy/Dispensary can only be linked to one Pharmacy HQ.
How Data is Maintained
The data for Pharmacy/Dispensaries are supplied by the NHS Business Services Authority (BSA) and are processed by ODS for onward publication. In order that the data is structured to fit with other organisation data that the ODS publish, and to meet Spine requirements, ODS create and maintain parent Pharmacy HQ codes and associate each pharmacy/dispensary to an HQ.
The NHS BSA relies on their contacts within Sub ICB Locations to inform them of updates and additions to Dispensaries within their area. This updating is carried out to the NHS BSA’s systems on an ongoing basis, with the NHS BSA supplying updated files to ODS weekly. ODS load the dispensary data into a bespoke database which is used to identify new dispensaries and either assign them to an existing HQ, or create new HQ codes when required.
Dispensary data for Wales are supplied by Wales to the NHS Business Services Authority (BSA), who pass on to ODS for publication.
Appliance Contractors - this data is also managed by the NHS BSA. Requests for new codes or amendments to existing are raised with the BSA by the contractors in question. ODS will identify new codes in the weekly data feeds and then manually create these in our database (new code requests are extremely rare). Amendments to existing codes are picked up in the weekly BSA files and auto imported into ODS.
See Pharmacy Headquarters for further information about change of ownership.
Data Quality Assessment
For further information re the: ODS Data Quality Assessment Framework
| Data Quality Dimension | |||||||||||
| Last updated: |
| 1 | 2 | 3 | 4 | 5 | ODS mastered or 3rd party data | 6 | 7 | 8 | 9 |
| OVERALL | Frequency of Update | Data Collection Method | Fit for Purpose | Coverage / Completeness | Reliability / Accuracy | Data Agreement | 3rd Party Escalation Routes | System Application / Downstream System Feedback | Future Refinement / Improvement Plan | ||
| Pharmacy / Dispensary | GREEN | Amber | Red | Green | Green | Amber | 3rd party | Green | Green | Green | Green |
| Weekly | Email (csv files) | Based on pharmacy/dispensary NHS contracts | Good coverage due to data source being contract driven | No hierarchy, ODS have to map to HQ/provider. No address validation at source. | SLA in place and regularly reviewed | Named contacts, regular stakeholder meeting/forum | Low volume of customer queries/issues | Not needed at this time | |||
Key Information - Roles, Code Formats and Data Source
| Key Information | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Geographic coverage |
| |||||||||||||||||||||
| Primary Role ID | RO182 | Primary Role Name | PHARMACY | |||||||||||||||||||
| RO94 | APPLIANCE CONTRACTOR | |||||||||||||||||||||
| Non Primary Role ID | RO268 | Non Primary Role Name | MEDICINE SUPPLIER | |||||||||||||||||||
| Raw Data Source | NHS Business Services Authority | Update Frequency | Weekly | |||||||||||||||||||
| Code Format |
| |||||||||||||||||||||
Permitted Relationships
Permitted Relationships - 'Pharmacy' can be linked to (upward): | |||||
Source Primary Role ID | Relationship Type Id | Relationship Type Name | Target Primary Role ID | Target Primary Role Name | Rel End Date (if applicable) |
| RE4 | IS COMMISSIONED BY | RO107 | CARE TRUST | |
| RE4 | IS COMMISSIONED BY | RO179 | PRIMARY CARE TRUST | ||
| RE4 | IS COMMISSIONED BY | RO210 | NHS ENGLAND (REGION, LOCAL OFFICE) | End dated | |
| RE4 | IS COMMISSIONED BY | RO261 | STRATEGIC PARTNERSHIP | ||
| RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO132 | HEALTH AUTHORITY (HA) | ||
| RE6 | IS OPERATED BY | RO181 | PHARMACY HEADQUARTER | ||
RO94 | RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO132 | HEALTH AUTHORITY (HA) | |
| RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO210 | NHS ENGLAND (REGION, LOCAL OFFICE) | End dated | |
| RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO261 | STRATEGIC PARTNERSHIP | ||
| Permitted Relationships - organisation types that are linked to a 'Pharmacy' (downward/dependent): | |||||
| Source Primary Role ID | Source Primary Role Name | Relationship Type Id | Relationship Type Name | Target Primary Role ID | Target Primary Role Name |
| RO280 | PHARMACY SITE | RE6 | IS OPERATED BY | RO182 | PHARMACY |
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.
*Note that for edispensary.csv, archived records were included, these will no longer be available via the ODS DSE Predefined Report.
edispensary.csv
Primary Role ID = RO182 and RO94
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 |
4 | [ICB_code] | High Level Health Geography | Change from legacy csv: Geographic extension of the postcode |
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 | [StatusName] | Status | Change from Legacy csv: The Status field is now populated with text rather than codes. FHIR R4 API users: Note that StatusName is replaced with “Proposed” if the organisation has an AATypeID = ‘9’ entry in AdditionalAttributes |
14 | [OrgTypeID] | Organisation Sub-Type Code | Change from Legacy csv: Previously populated with '1' (Pharmacy) or '2' (Oxygen Appliance Contractor). Now populated with corresponding primary RoleID (RO182 or RO94). |
15 | [TargetOrgCode] | Parent Organisation Code | RE6 'is operated by' relationship – Where LegalEndDate is null, or where the relationship LegalEndDate is equal to the organisation LegalEndDate * |
16 | [LegalStartDate] | Join Parent Date | RE6 relationship legal start date |
17 | [LegalEndDate] | Left Parent Date | RE6 relationship legal end date |
18 | [TelephoneNumber] | Contact Telephone Number | |
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 | [PCO_code] | Current Care Organisation | Change from Legacy csv: Geographic extension of the postcode |
25 | NULL | Column 25 | |
26 | NULL | Column 26 | |
27 | NULL | Column 27 |
*RO94 have no RE6 relationships, so Column 15, 16 and 17 will be null for these records
Attachments:
Dispensary Data Process Flow (application/vnd.jgraph.mxfile)
Dispensary Data Process Flow.png (image/png)
