Data Description
Abeyance and Dispersal codes are created to enable specific system functionality as outlined below , they are not true organisation or practitioner codes.
Usually, when a GP retires or leaves a practice, a successor is appointed prior to the departure of the outgoing GP. In such cases, if the GP in question holds their own 'list' of patients on the Practice and NHAIS systems, these are transferred to the new GP (referred to as the successor) using bulk transfer processes. There are, however, two circumstances where this is not possible:
- Where a successor has yet to be appointed, the NHAIS system currently offers the facility to set the individual GP list to 'abeyance'. This leaves the patients technically registered with the departing GP until a successor can be obtained. In practice, the patients are usually still treated by the remaining partners in the practice, or sometimes a locum is employed temporarily by the practice. This process ensures the practice list is still calculated appropriately for payment.
- When a successor is not actively being sought, the NHAIS dispersal function is used; patients registered with the GP are written to advising them to register with a new GP.
In order to ensure that National Back Office and PDS are correct, it is necessary to set up Abeyance/Dispersal codes; these take the form of GP Practitioner format codes which relate to a practice rather than an individual GP, and ODS has responsibility for this.
How Data is Maintained
Abeyance and Dispersal code requests are submitted to ODS by contacts within Integrated Care Boards / Sub ICB Locations, or Isle of Man
For Abeyance and Dispersal codes for English GPs/Practices, a 12 month life cycle has been agreed with Primary Care Support England (PCSE). This means that ODS perform an automated daily check for Abeyance and Dispersal codes that have been open for more than 12 months so that they can be closed. This maintains the efficiency of this dataset.
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 | ||
| Abeyance and Dispersal | GREEN | Green | Green | Green | Green | Green | ODS | n/a | n/a | Green | Green |
| Ad Hoc | Customer request via Service Desk | Codes created as required by practices/ICBs, in response to operational needs | Full coverage - code as required | Reliable and accurate - codes only active for a year then ODS have agreed a process by which we will auto close after 1 year. | n/a | n/a | No evidence of downstream system issues | Not required | |||
Key Information - Roles, Code Formats and Data Source
| Key Information | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Geographic coverage |
| ||||||||||||||||||
| Primary Role ID | RO88 | Role Role Name | ABEYANCE AND DISPERSAL | ||||||||||||||||
| Non Primary Role ID | RO59 | Practitioner role Name | ABEYANCE | ||||||||||||||||
RO60 | DISPERSAL | ||||||||||||||||||
| Raw Data Source | Notification from the ICB/Sub ICB | Update Frequency | Ad Hoc | ||||||||||||||||
| Code Format | England and Wales:
| ||||||||||||||||||
Permitted Relationships
Permitted Relationships - 'Prescribing Cost Centres' can be linked to (upward): | ||||
Source Primary Role ID | Relationship Type Id | Relationship Type Name | Target Primary Role ID | Target Primary Role Name |
RO88 | RE6 | IS OPERATED BY | RO177 | PRESCRIBING COST CENTRE |
Legacy .csv File Mapping
Baseline differences between ODS Data Search & Export and the legacy csv files - tbc
eabeydispgp.csv
Primary Role / OrgTypeID – RO88
Col | Data Item | Report Alias (Legacy csv) | Notes |
1 | [OrganisationCode] | Organisation Code | |
2 | [OrgName] | Name | |
3 | NULL | Column 3 | |
4 | NULL | Column 4 | |
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 | |
10 | [Postcode] | Postcode | |
11 | [LegalStartDate] | Open Date | |
12 | [LegalEndDate] | Close Date | |
13 | NULL | Column 13 | |
14 | [RoleID] | Organisation Sub-Type Code | Only populated where there is a role (PrimaryRole = 0) that is active or has a legal end date as equal to the organisation’s end date. |
15 | [TargetOrgCode] | Parent Organisation Code | Target organisation code for the RE6 'is operated by' relationship – Where LegalEndDate is null, or where the relationship LegalEndDate is equal to the organisation LegalEndDate. OrgTypeId for the target org should be RO177. |
16 | [LegalStartDate] | Join Parent Date | RE6 'is operated by' relationship legal start date |
17 | [LegalEndDate] | Left Parent Date | RE6 'is operated by' 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 using the geographies table. The default code of 'YAC' is no longer populated for Isle of Man records. |
25 | NULL | Column 25 | |
26 | NULL | Column 26 | |
27 | NULL | Column 27 |