Patient Information Maintenance - Standard v.1.1.1
ID | S13 |
|---|---|
Version | 1.1.1 |
Type | Capability Specific Standard |
Status | Retired |
Effective Date | Aug 6, 2021 |
Requirements
Sections |
|---|
Patient Information |
Online Account and Service Management |
Subject Access Requests |
Patient Information Reporting |
Epic Mapping | Requirement ID | Requirement Text | Level |
|---|---|---|---|
Patient Information | |||
C13E1 | GP-04.1-01 | Patient Registration Support Patient registration at a General Practice for all Medical Services | MUST |
C13E1 | GP-04.1-02 | Patient Registration Types Categorise Patients using Registration Types in line with legislative registration statuses as defined in NHS England Standard General Medical Services Contract (see definition of 'Patient' in Part 1) | MUST |
C13E1 | GP-04.1-03 | Patient Registration Personal Data Enforce the following Minimum Data Set at point of Patient registration (prior to clinical data being recorded)
See PDS for demographic data format. For contractual references between GPs and NHSE see: NHS England Standard General Medical Services Contract | MUST |
C13E1 | PIM9 | Patient's GP Record:
| MUST |
C13E1 | PIM10 | Registration End Date Record an end date for each Registration Type. If the Registration type is Fully Registered and the Patient has been Deducted the Registration end date must equal the Deduction date. | MUST |
C13E1 | GP-04.1-05 | Patient Verification Support Patient verification during the registration process with comprehensive tracing functionality. See PDS for details on PDS Advanced Trace functionality | MUST |
C13E1 | GP-04.1-07 | Patient Registration Status Automatically update a Patient’s Registration Status if/when registration start date, registration end date (or date of Deduction) is completed:
See GP2GP documentation for details of Patient registration and GP2GP trigger conditions | MUST |
C13E1 | GP-04.1-08 | Re-activate Inactive Patient Reactivate an Inactive Patient Record when a Patient re-registers with a General Practice (e.g. prisoner released) i.e. another instance of a Registration Type can be created for the Patient, but the original end date will not simply be deleted. See GP2GP documentation for specific Electronic Patient Record transfer requirements on returning Patients | MUST |
C13E1 | PIM8 | Record and Maintain Demographic Information Record and maintain the following national Demographic Information for all registered Patients:
Requirements for the format of these data fields can be found in the relevant NHAIS and PDS documentation – if they differ, Solutions will adhere to both formats when synchronising and transferring data between Solutions (e.g. NHAIS Requirements for address format are more prescriptive than those for the address format for PDS) See GP-PPFS-3.4-02 for notifications around demographic and preference changes | MUST |
C13E1 | GP-04.2-02 | Record and Maintain Additional Demographic Information Record and maintain the following additional Demographic Information for all registered Patients:
| MUST |
C13E1, C13E4 | GP-04.5-01A | Record and Maintain Preference Details Record and maintain the following Preference details for each registered Patient, each data item in its own explicit field(s) with values determined from standard lists wherever possible:
Default will always be implied dissent and for each Preference default to be ‘not yet set’ – any changes will be on an individual Patient basis See GP-PPFS-3.4-02 for notifications around demographic and preference changes | MUST |
C13E1 | PIM11 | Patient Alerts Add, update and remove Patient Alerts manually or automatically (e.g. rules based), to indicate key characteristics to Practice Users (e.g. that the patient is violent or is on a certain chronic disease register). | MUST |
C13E3 | GP-04.4-01 | Record and Maintain Related Persons Record and maintain the following related persons for all registered Patients, each data item in its own explicit field(s) with values determined from standard lists wherever possible. A Patient can have multiple related persons, a person can be related to multiple Patients and an individual can be a related person of multiple types to a single Patient:
Where the related person is also registered at the Practice, this related person record can be derived from / linked to their Patient Record | MUST |
C13E8 | GP-05.1-01 | Search, identify and retrieve a Patient Record Search for, identify and retrieve a Patient Record for use in the Solution by searching full or part of the contents of any combination of the following fields:
| MUST |
C13E8 | GP-05.1-02 | Find Record with Demographic Changes Ability for Practice User to explicitly select to include historic Demographic Information in a search | MUST |
C13E2 | GP-05.1-03 | Notification of Patient Record Actions Indicate to the Practice User: At any point a Patient interacts with the Practice / when accessing a Patient’s record:
Irrespective of the solution where a Practice User is Notified / Informed of any of the above, a Practice User is to have the option to directly access the relevant area of the Solution or specific information to enable rectification | MUST |
C13E2 | GP-05.1-04 | Access Patient Record with Matched Item Access a Patient Record from any area or module within the Solution where a Patient has been successfully matched or linked to the item/area e.g. when viewing a document or managing a task, a Practice User can directly open/launch the associated Patient Record | MUST |
C13E1 | GP-05.2-01 | View Events and Future Activities View all historic events and future activities planned within a journal or Patient activity log, including:
| MUST |
C13E1 | PIM17 | Problem-orientated records Support a problem-orientated approach to recording and viewing data, including:
See Good Practice Guidelines for GP electronic patient records Version 4 (2011) for guidance | MUST |
C13E1 | GP-05.2-02 | Access Data Items Identify and access related data items and documents irrespective of:
All pertinent information will be accessible to the Practice User e.g. when viewing a battery of test results, the result type, value, the unit of measure, the clinician and dates (such as date sample taken, date test requested, date test performed, date results received) will be available together for each of the tests within the received result See Role-based Access Control for required access controls | MUST |
C13E1 | PIM15 | Organise Patient Record Organise to make optimal use of the record by any combination of the following mechanisms:
It will be obvious to a Practice User when a record they are viewing has been grouped, filtered and/or sorted/ordered. | MUST |
C13E1 | PIM16 | Filter record on 'Restricted from View Record' items Ability to filter the Patient Record (as described in PIM15) on those items marked as 'Restricted from View Record' (see PIM14) | may |
C13E1 | GP-05.2-04 | Search a Patient Record
See Data Standards for coded data requirements | MUST |
C13E1 | PIM13 | Search within Documents Ability to search the contents of Documents attached to a Patient Record for a specified text string across both structured data (including clinical terms) and free text. | MUST |
C13E1 | GP-05.2-05 | Print/Export Patient Record Practice User to have the ability to Print/export the entire Patient Record with the ability to select to also print/export:
| MUST |
C13E11 | GP-13.1-01 | Patient Outside of Catchment Area Indicate to a Practice User that a registered Patient is residing outside of the catchment area of the Practice. See Patient Choice Scheme and out of area registrations for background information. | MUST |
C13E1 | PIM7 | Sexual orientation Monitoring (DCB2094) Adhere to the Sexual orientation Monitoring (DCB2094) Standard. | MUST |
Citizen Account and Service Management | |||
C13E4, C13E10 | GP-PPFS-3.2-01 | Service Access - Patient
| MUST |
C13E20 | |||