Requirement ID

Requirement Text

Level

GP-MI.1-01

Each data submission will cover one calendar month

Between midnight (00:00) on the first day of the calendar month being reported and 23:59 on the last day of the calendar month being reported inclusive. For example, if the report is being produced in November 2015 then the reporting period will be between midnight (00:00) on the 01/10/2015 and 23:59 on the 31/10/2015 inclusive

MUST

GP-MI.1-02

Data to be submitted to The Authority on a monthly basis in the month following the reporting period

If the reporting period is October, then the data will be submitted in November i.e. a retrospective collection

MUST

GP-MI.1-03

Data to be submitted to The Authority within 10 working days of the end of each reporting period

If the reporting period is October, the data will be submitted within 10 working days after 31^st October

MUST

GP-MI.1-04

Data to be submitted through the nominated The Authority Data Collection Service

This is the Secure Electronic File Transfer (SEFT) portal and details on using this are embedded below:

• Secure Electronic File Transfer (SEFT)

• Creating Automated SFTP Transfers - Guidance 

MUST

GP-MI.1-05

Data to be submitted in the format prescribed by The Authority

This is as a csv file and Suppliers have a choice between two templates, as below. Blank templates will be made available on the last working day of each month via the relevant SEFT folder.

1. Long and skinny csv template.csv

2. Tabular csv template.csv

Suppliers will inform The Authority which template they will be using

MUST

GP-MI.1-06

CSV data submissions will contain all fields in the same order as defined in the CSV file structure table and all applicable data as defined in the Data Fields Definition section.

MUST

GP-MI.1-06a

Where a Supplier is not required to provide or cannot provide certain fields, these fields will be included within the data submitted, but left blank, rather than giving a value of '0'.

Suppliers will inform The Authority where there are fields that they are required to return but are unable to do so and explain the reasons for this.

MUST

GP-MI.1-07

Data will only be returned for Practices which have approved the collection using CQRS

A list of the ODS codes of all Practices which have approved the collection will be made available to Suppliers as a csv file on the last working day of each month via the relevant SEFT folder.

Upon receipt of the data, The Authority will validate that the latest version of this list has been applied

MUST

GP-MI.1-08

Suppliers to have a process for checking data quality in reports before they are submitted

MUST

GP-MI.1-09

Suppliers to ensure that the processes used to produce reports preserve the meaning of data items from one reporting period to the next, so that the content of a report can be compared between periods

In cases where the Supplier does need to change the process for producing reports in a manner that means reports cannot be compared between reporting periods, they will alert the The Authority Primary Care Data team

MUST

Field ID

Data Item

Definition

Format

Level

H1

report_period_start

First day of reporting period which the report covers (the 1st of the month prior to the month in which the data is being submitted i.e. if data is being submitted in July 2018, this field will be 01/06/2018).

Date (dd/mm/yyyy)

MUST

H2

report_period_end

Last day of reporting period which the report covers (the final day of the month prior to the month in which the data is being submitted i.e. if data is being submitted in July 2018, this field will be 30/06/2018).

Date (dd/mm/yyyy)

MUST

H3

Supplier 

Name of Supplier returning the data.

String (63)

MUST

H4

Supplier_system

Name of Solution for which data is being returned.

String (63)

may

H5

Supplier_ system_version

Version number of the Supplier Solution used at the practice.

String (63)

may

H6

gp_practice_code

The GP Practice Code for the GP Practice for which the data is being returned.

String (6)

MUST

Field ID

Data Item

Definition

Format

Level

619a

update_demographics_online_trans_count

Total number of demographics update transactions: (this is the number of transactions involving an update of Patient demographic details, NOT a count of the fields updated; where a transaction includes the update of multiple demographic information fields, this should only be counted as a single transaction) 

• via any Citizen Service

• for Patients who are associated with at least one LOSA who is registered to use any Citizen Capability on their behalf whether as 'self' or 'proxy'

• at any time within the reporting period

Numeric (integer)

may

608

total_online_transactions_count

Total number of transactions recorded by the Solution:

• transaction took place at any time within the reporting period

• Solution logins (each individual login should be counted separately; this DOES include re-logins after a system time-out) 

• via View Record - Citizen Solution (each view/access of: any part of the Full Care Record, elements of the Detailed Coded Record, Summary Information Record, letters; if any element is viewed/accessed multiple times within the reporting period each view/access should be counted separately) 

• via Appointments Management - Citizen Solution (Appointment scheduling transactions, Appointment cancellation transactions) 

• via Prescription Ordering – Citizen Solution (Prescription ordering transactions; where multiple items are included within a single transaction, this should only be counted once) 

• via Communicate With Practice - Citizen Solution (messages sent from Patient to practice, messages sent from practice to Patient) 

• all transactions from update_demographics_online_trans_count (field 619a)

Numeric (integer)

may

1010

total_login_count_p

Total number of logins to a Citizen Service:

• at any time within the reporting period

• by LOSAs

• where the Citizen Service being logged into is provided by the same Supplier as provides the Patient Information Maintenance - GP Solution for the Practice

Numeric (integer)

may

1011

total_login_count_p1

Total number of logins to a Citizen Service:

• at any time within the reporting period

• by LOSAs

• where the Citizen Service being logged into is provided by a different Supplier than provides the Patient Information Maintenance - GP Solution for the Practice

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

513

new_online_Patient_count

Total number of Patients registered for at least one Citizen Service as at report_period_end who:

• were registered for any Citizen Service for the first time during the reporting period (this does NOT include Patients who were previously registered, but for whom service access was changed during the reporting period.)

• are active at the Practice (this DOES include Patients who moved from 'inactive' to 'active' during the reporting period)

• had a VUA created and associated with their record, which enables the use of any Citizen Service on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

may

511

new_vua_count

Total number of VUAs enabled for the use of at least one Citizen Service as at report_period_end where:

• VUA was created by the Practice during the reporting period (this does NOT include VUAs that were previously created, but where service access configuration was changed during the reporting period. It DOES include VUAs where the status changed from 'inactive' to 'active' during the reporting period)

• VUA account is active and associated with at least one Active Patient whether as 'self' or 'proxy' (VUAs that enable both 'self' and 'proxy' association should only be counted once)

Numeric (integer)

may

512

online_Patient_count

Total number of Patients registered for at least one Citizen Service as at report_period_end who:

• were registered for any Citizen Service as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of any Citizen Service on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

may

510

vua_count

Total number of VUAs enabled for the use of at least one Citizen Service as at report_period_end where:

• VUA was created by the Practice and exists at report_period_end (this DOES include VUAs created within or at any point before the reporting period)

• VUA account is active and associated with at least one Active Patient whether as 'self' or 'proxy' (VUAs with both a 'self' and 'proxy' association should only be counted once)

Numeric (integer)

may

409

online_appointment_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution at the Practice for enabling the use of Appointments Management - Citizen Capability for booking and/or cancelling Appointments as at reporting_end_date.

Flag (0, 1, 2, 9)

MUST

514

online_Patient_appointment_count

Total number of Patients registered to use Appointments Management - Citizen Capability as at report_period_end who:

• were registered to use Appointments Management - Citizen Capability as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Appointments Management - Citizen Capability on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

410

online_prescription_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution at the Practice for enabling the use of Prescription Ordering – Citizen Capability as at report_period_end.

Flag (0, 1, 2, 9)

MUST

516

online_Patient_prescription_count

Total number of Patients registered to use Prescription Ordering – Citizen Capability as at report_period_end who:

• were registered to use Prescription Ordering – Citizen Capability as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Prescription Ordering – Citizen Capability on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

411

online_communication_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution at the Practice for enabling the use of Communicate With Practice - Citizen Capability as at report_period_end.

Flag (0, 1, 2, 9)

may

518

online_Patient_communication_count

Total number of Patients registered to use Communicate With Practice - Citizen Capability as at report_period_end who:

• were registered to use Communicate With Practice - Citizen Capability as report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Communicate With Practice - Citizen Capability on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

may

420

online_document_view_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution at the Practice for enabling the use of the Document Access Level Record Access Service as at report_period_end.

Flag (0, 1, 2, 9)

MUST

524

online_Patient_document_view_count

Total number of Patients registered to use the Document Access Level Record Access Service at report_period_end who:

• were registered to use the Document Access Level Record Access Service to view documents as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Document Access Level Record Access Service to view documents on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

413

online_record_view_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution for enabling the use of the Full Record Record Access Service as at report_period_end.

Flag (0, 1, 2, 9)

MUST

522

online_Patient_record_view_count

Total number of Patients registered to use the Full Record Record Access Service to view their Full Record as at report_period_end who:

• were registered to use the Full Record Record Access Service to view their Full Record as at report_period_end (this DOES include registrations completed within or at any point before the reporting period) 

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Full Record Record Access Service to view documents on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

412

online_summary_record_view_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution for enabling the use of the Summary Information Record Record Access Service as at report_period_end.

Flag (0, 1, 2, 9)

MUST

520

online_Patient_summary_record_view_count

Total number of Patients registered to use the Summary Information Record Record Access Service to view their Summary Information Record as at report_period_end who:

• were registered to use the Summary Information Record Record Access Service to view their Summary Information Record as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Summary Information Record Record Access Service to view documents on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

622

coded_record_view_enabled_status

Functionality status in the Patient Information Maintenance - GP Solution for enabling the use of the Detailed Coded Record Record Access Service as at report_period_end.

Flag (0, 1, 2, 9)

MUST

623

coded_online_Patient_record_view_count

Total number of Patients registered to use the Detailed Coded Record Record Access Service to view their Detailed Coded Record as at report_period_end who:

• were registered to use Detailed Coded Record Record Access Service to view their Detailed Coded Record as at report_period_end (this DOES include registrations completed within or at any point before the reporting period)

• are active at the Practice

• have a VUA associated with their record, which enables the use of the Detailed Coded Record Record Access Service to view documents on their behalf whether as 'self' or 'proxy' (this is a count of Patients associated with VUAs, NOT of the VUAs. Patients with both a 'self and 'proxy' association should only be counted once)

Numeric (integer)

MUST

1108

total_documents_count

Total number of unique documents received into and stored by the Solution that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received via any mechanism (i.e. electronic, scanned, manual etc. are all included)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1108 in Document Management)

Numeric (integer)

may

1109

total_documents_scanned_count

Total number of unique documents received into the system that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received via scanning (i.e. documents received on paper and scanned as opposed to being received via an electronic format)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1109 in Document Management)

Numeric (integer)

may

1110

total_documents_electronic_count

Total number of unique documents received into the system that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received electronically (i.e. documents received electronically as opposed to being received in paper format and scanned)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1110 in Document Management)

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

613

comms_online_Patient_count

Total number of communications sent:

• using the Communicate With Practice - Citizen Solution 

• from Patient to practice

• at any time within the reporting period

Numeric (integer)

may

614

comms_online_clinician_count

Total number of communications sent:

• using the Communicate With Practice - Citizen Solution 

• from practice to Patient

• at any time within the reporting period

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

610

appointment_scheduled_online_trans_count

All transactions from appointment_scheduled_trans_count (field 108) where:

• the scheduling transaction took place via Appointments Management - Citizen Solution 

Numeric (integer)

may

110

appointment_scheduled_ooh_online_trans_count

All transactions from appointment_scheduled_online_trans_count (field 610) where:

• the scheduling transaction took place via Appointments Management - Citizen Solution 

• the scheduling transaction took place within the reporting period, but outside of regular working hours (outside of regular working hours is defined as between 1830 and 0759 inclusive on weekdays; weekends i.e. 1830 Friday to 0759 Monday; all day bank holidays i.e. 0000 to 2359)

Numeric (integer)

may

611

appointment_cancelled_online_trans_count

All transactions from appointment_cancelled_trans_count (field 109) where:

• the cancellation transaction took place via Appointments Management - Citizen Solution 

Numeric (integer)

MUST

111

appointment_cancelled_ooh_online_trans_count

All transactions from appointment_cancelled_online_trans_count (field 611) where:

• the cancellation transaction took place via Appointments Management - Citizen Solution 

• the cancellation transaction took place within the reporting period, but outside of regular working hours (outside of regular working hours is defined as between 1830 and 0759 inclusive on weekdays; weekends i.e. 1830 Friday to 0759 Monday; all day bank holidays i.e. 0000 to 2359)

Numeric (integer)

may

1219

appointment_scheduled_online_count

All Appointments from appointment_scheduled_count (field 210) which were:

• scheduled using the Appointments Management - Citizen Solution (A count as at the end of the reporting period of the number of Appointments booked via an online method based on the final status and booking method of each Slot made available for Patients to book in the period based on start time. NOT the number of transactions which took place for booking Appointments online i.e. an Appointment Slot which was booked online then cancelled will NOT be included in this count; an Appointment Slot which was booked over the phone, cancelled and then booked again via a Citizen Service WILL be included in this count)

Numeric (integer)

may

1221

appointment_cancelled_online_count

All Appointments from appointment_cancelled_count (field 1220) which were:

• cancelled using the Appointments Management - Citizen Solution (A count as at the end of the reporting period of the number of Appointments cancelled via an online method based on the final status and cancellation method of each Slot made available for Patients to book in the period based on start time. NOT the number of transactions which took place for cancelling Appointments online i.e. an Appointment Slot which is booked over the phone, then cancelled online WILL be included in this count; an Appointment which is booked, then cancelled online, then booked again will NOT be included in this count.)

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

612

prescription_online_trans_count

All transactions from prescriptions_ordered_trans_count (field 308) where:

• the ordering transaction took place via the Prescription Ordering - Citizen Solution 

Numeric (integer)

MUST

310

prescription_online_ooh_trans_count

All transactions from prescription_online_trans_count (field 612) where:

• the ordering transaction took place via the Prescription Ordering - Citizen Solution 

• the ordering transaction took place within the reporting period, but outside of regular working hours (outside of regular working hours is defined as between 1830 and 0759 inclusive on weekdays; weekends i.e. 1830 Friday to 0759 Monday; all day bank holidays i.e. 0000 to 2359)

Numeric (integer)

may

311

prescription_online_eps_count

All transactions from prescription_online_trans_count (field 612) where:

• the order was for a repeat Prescription

• the transaction is linked to Electronic Prescription Service (EPS) - Prescribing

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

615

online_record_view_count

Total number of accesses/views of any part of the Full Record:

• using View Record - Citizen Solution 

• by Patients enabled for the Full Record Record Access Service

• at any time within the reporting period (if any element of the Full Record is viewed/accessed multiple times within the reporting period, each view/access should be counted separately)

Numeric (integer)

MUST

616

online_summary_record_view_count

Total number of accesses/views of the Summary Information Record:

• using View Record - Citizen Solution 

• by Patients enabled for the Summary Information Record Record Access Service

• at any time within the reporting period (if the Summary Information Record is viewed/accessed multiple times within the reporting period, each view/access should be counted separately)

Numeric (integer)

MUST

624

coded_record_view_online_count

Total number of accesses/views of the Detailed Coded Record:

• using View Record - Citizen Solution 

• by Patients enabled for the Detailed Coded Record Record Access Service

• at any time within the reporting period (if the Detailed Coded Record is viewed/accessed multiple times within the reporting period, each view/access should be counted separately)

Numeric (integer)

MUST

617

online_record_document_view_count

Total number of document accesses/views:

• using View Record - Citizen Solution 

• by Patients using the Document Access Level Record Access Service

• at any time within the reporting period (if a letter is viewed/accessed multiple times within the reporting period, each view/access should be counted separately)

Numeric (integer)

MUST

Field ID

Data Item

Definition

Format

Level

208

appointment_available_count

Total number of Slots that were available for Patients to book as Appointments: (Slots made available NOT Appointments which were booked/scheduled OR actually took place)

• with a start date and time within the reporting period (based on start time of Appointment) 

• bookable via any booking method

• with any healthcare professional type

• of any Slot Type (type of Appointment is defined as routine, emergency, or specialist clinics etc. terminology may differ between Supplier systems; where Appointment Slot was available for a Patient to book i.e. exclude any Slots marked as 'blocked' or 'non-bookable') 

• of any duration

Numeric (integer)

may

209

appointment_available_online_count

All Slots from appointment_available_count (field 208) which were:

• bookable via Appointments Management - Citizen Solution 

Numeric (integer)

may

210

appointment_scheduled_count

Total number of Appointments as at report_period_end that were booked: (with status of 'booked' as at the end of the reporting period; terminology for 'booked' may differ between Supplier systems; status at the end of the reporting period may also be 'attended' or 'DNA') 

• with a start date and time within the reporting period (based on start time of Appointment) 

• via any booking method

• with any healthcare professional type

• of any Slot Type (type of Appointment is defined as routine, emergency, or specialist clinics etc. terminology may differ between Supplier Solutions) 

• of any duration

• of any attendance status

Numeric (integer)

may

108

appointment_scheduled_trans_count

Total number of Appointment scheduling transactions where: (this is a count of transactions resulting in an Appointment booking, NOT the number of Appointment Slots with a status of 'booked') 

• the scheduling transaction took place at any time within the reporting period

• the start date and time of the Appointment being booked may be within or outside of the reporting period

• the scheduling transaction took place via any booking method

• Appointment is with any healthcare professional type

• Appointment is of any Slot Type

• Appointment is of any duration

• Appointment has any attendance status e.g. An Appointment scheduling transaction takes place on 23/01/2018 to schedule an Appointment for 02/02/2018. The report for January 2018 would include an Appointment scheduled transaction (field 108) but NOT an available Appointment (field 208) or a scheduled Appointment (field 210)

Numeric (integer)

MUST

109

appointment_cancelled_trans_count

Total number of Appointment cancellation transactions where: (this is a count of transactions resulting in an Appointment cancellation, NOT the number of Appointment Slots with a status of 'cancelled') 

• the cancellation transaction took place at any time within the reporting period

• the start date and time of the Appointment being cancelled may be within or outside of the reporting period

• the cancellation transaction took place via any cancellation method

• Appointment is with any healthcare professional type

• Appointment is of any Slot Type

• Appointment is of any duration

• Appointment has any attendance status e.g. An Appointment cancellation transaction takes place on 23/01/2018 to cancel an Appointment for 02/02/2018. The report for January 2018 would include an Appointment cancelled transaction (field 109) but NOT an available Appointment (field 208), a scheduled Appointment (field 210) or a cancelled Appointment (field 1220)

Numeric (integer)

may

212

appointment_dna_appt_count

All Appointments from appointment_scheduled_count (field 210) where:

• Appointment status is 'Did Not Attend' as at report_period_end_date (terminology for 'Did Not Attend' may differ between Supplier systems)

Numeric (integer)

may

213

appointment_dna_online_appt_count

All Appointments from appointment_dna_appt_count (field 212) which were:

• scheduled via  Appointments Management - Citizen Solution 

Numeric (integer)

may

1201

appointment_available_core_hours_count

All Slots from appointment_available_count (field 208):

• with a start date and time within core hours (defined as 8am to 6.30pm on weekdays) (core hours defined as 8am-6.30pm on weekdays except Good Friday, Christmas Day or bank holidays, as set out in the GMS contract. Based on Appointment start time i.e. a 10 minute Appointment scheduled to start at 6.25pm will be counted as a core hours Appointment; an Appointment scheduled to start at 8am will be counted as a core hours Appointment; an Appointment scheduled to start at 6.30pm will be counted as an extended hours Appointment)

Numeric (integer)

may

1202

appointment_available_extended_hours_count

All Slots from appointment_available_count (field 208):

• with a start date and time NOT in core hours (core hours defined as 8am-6.30pm on weekdays except Good Friday, Christmas Day or bank holidays, as set out in the GMS contract. Based on Appointment start time i.e. a 10 minute Appointment scheduled to start at 6.25pm will be counted as a core hours Appointment; an Appointment scheduled to start at 8am will be counted as a core hours Appointment; an Appointment scheduled to start at 6.30pm will be counted as an extended hours Appointment; this is a count of Appointments which do NOT fall within core hours)

Numeric (integer)

may

1203

appointment_available_duration_less_10_count

All Slots from appointment_available_count (field 208):

• with duration of 10 minutes or less (an Appointment of exactly 10 minutes duration will be included in this count)

Numeric (integer)

may

1204

appointment_available_duration_over_10_count

All Slots from appointment_available_count (field 208):

• with duration of more than 10 minutes (an Appointment of exactly 10 minutes duration will NOT be included in this count)

Numeric (integer)

may

1207

appointment_available_mode_face_to_face_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Face to face (a count as at the end of the reporting period of the number of Slots made available for Patients to book as a face to face Appointment i.e. if an Appointment Slot is initially made available as a face to face Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1208

appointment_available_mode_phone_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Telephone (a count as at the end of the reporting period of the number of Slots made available for Patients to book as a telephone Appointment i.e. if an Appointment Slot is initially made available as a face to face Appointment and then reassigned as a telephone Appointment, this WILL be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1209

appointment_available_mode_video_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Video (i.e. Skype) (a count as at the end of the reporting period of the number of Slots made available for Patients to book as a video Appointment i.e. if an Appointment Slot is initially made available as a video Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1210

appointment_available_mode_home_visit_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Home Visit (a count as at the end of the reporting period of the number of Slots made available for Patients to book as a home visit i.e. if an Appointment Slot is initially made available as a face to face Appointment and then reassigned as a home visit, this WILL be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1211

appointment_available_mode_online_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Online (a count as at the end of the reporting period of the number of Slots made available for Patients to book as an online Appointment i.e. if an Appointment Slot is initially made available as an online Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1213

appointment_available_mode_other_count

All Slots from appointment_available_count (field 208):

• of mode of Appointment: Other (a count as at the end of the reporting period of the number of Slots made available for Patients to book as any other mode of Appointment not given above; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this; this count WILL include any unknowns)

Numeric (integer)

may

1214

appointment_available_hcptype_gp_count

All Slots from appointment_available_count (field 208):

• with healthcare professional type: General-Practitioner-(GP) (a count as at the end of the reporting period of the number of Slots made available for Patients to book with healthcare professional type of GP or similar i.e. if an Appointment Slot is initially made available with a GP and then reassigned to nurse, this will NOT be included in this count; healthcare professional groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1216

appointment_available_hcptype_nurse_count

All Slots from appointment_available_count (field 208):

• with healthcare professional type: Nurse (a count as at the end of the reporting period of the number of Slots made available for Patients to book with healthcare professional type of Nurse or similar i.e. if an Appointment Slot is initially made available with a Nurse and then reassigned to GP, this will NOT be included in this count; healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1217

appointment_available_hcptype_other_clinical_count

All Slots from appointment_available_count (field 208):

• with healthcare professional type: Other – Clinical (a count as at the end of the reporting period of the number of Slots made available for Patients to book with healthcare professional type of Other – Clinical i.e. if an Appointment Slot is initially made available with a Nurse and then reassigned to another clinical user other than Nurse or GP, this WILL be included in this count; healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1218

appointment_available_hcptype_other_count

All Slots from appointment_available_count (field 208):

• with healthcare professional type: Other (a count as at the end of the reporting period of the number of Slots made available for Patients to book with any other healthcare professional type, including clerical user types i.e. if an Appointment Slot is initially made available with a Nurse and then reassigned to another health care professional type which is not GP, Nurse or other clinical, this WILL be included in this count; see embedded document for a list of all the types which will NOT be included in this count; this count WILL include any unknowns)

Numeric (integer)

may

1220

appointment_cancelled_count

Total number of Appointments as at report_period_end that were cancelled: (with status of 'cancelled' as at the end of the reporting period; terminology for 'cancelled' may differ between Supplier systems) 

• with a start date and time within the reporting period (based on start time of Appointment) 

• using any method (A count as at the end of the reporting period of the number of Appointments cancelled based on the final status of each Slot made available for Patients to book in the period based on start time. NOT the number of transactions which took place for cancelling Appointments i.e. an Appointment Slot which is booked, then cancelled, then booked again will NOT be included in this count) 

• with any healthcare professional type

• of any Slot Type (type of Appointment is defined as routine, emergency, or specialist clinics etc. terminology may differ between Supplier systems) 

• of any duration

Numeric (integer)

may

1222

appointment_scheduled_core_hours_count

All Appointments from appointment_scheduled_count (field 210) which were:

• with a start date and time within core hours (defined as 8am to 6.30pm on weekdays) (core hours defined as 8am-6.30pm on weekdays except Good Friday, Christmas Day or bank holidays, as set out in the GMS contract. Based on Appointment start time i.e. a 10 minute Appointment scheduled to start at 6.25pm will be counted as a core hours Appointment; an Appointment scheduled to start at 8am will be counted as a core hours Appointment; an Appointment scheduled to start at 6.30pm will be counted as an extended hours Appointment)

Numeric (integer)

may

1223

appointment_scheduled_extended_hours_count

All Appointments from appointment_scheduled_count (field 210) which were:

• with a start date and time NOT in core hours (core hours defined as 8am-6.30pm on weekdays except Good Friday, Christmas Day or bank holidays, as set out in the GMS contract. Based on Appointment start time i.e. a 10 minute Appointment scheduled to start at 6.25pm will be counted as a core hours Appointment; an Appointment scheduled to start at 8am will be counted as a core hours Appointment; an Appointment scheduled to start at 6.30pm will be counted as an extended hours Appointment; this is a count of Appointments which do NOT fall within core hours)

Numeric (integer)

may

1224

appointment_attended_count

All Appointments from appointment_scheduled_count (field 210) where:

• Appointment status is 'Attended' as at report_period_end_date (terminology for 'Attend' may differ between Supplier systems)

Numeric (integer)

may

1227

appointment_scheduled_mode_face_to_face_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Face to face (a count as at the end of the reporting period of the number of Slots scheduled as a face to face Appointment i.e. if an Appointment Slot is initially scheduled as a face to face Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1228

appointment_scheduled_mode_phone_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Telephone (a count as at the end of the reporting period of the number of Slots scheduled as a telephone Appointment i.e. if an Appointment Slot is initially scheduled as a face to face Appointment and then reassigned as a telephone Appointment, this WILL be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1229

appointment_scheduled_mode_video_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Video (i.e. Skype) (a count as at the end of the reporting period of the number of Slots scheduled as a video Appointment i.e. if an Appointment Slot is initially scheduled as a video Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1230

appointment_scheduled_mode_home_visit_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Home Visit (a count as at the end of the reporting period of the number of Slots scheduled as home visits i.e. if an Appointment Slot is initially scheduled as a face to face Appointment and then reassigned as a home visit, this WILL be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1231

appointment_scheduled_mode_online_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Online (a count as at the end of the reporting period of the number of Slots scheduled as an online Appointment i.e. if an Appointment Slot is initially scheduled as an online Appointment and then reassigned as a telephone Appointment, this will NOT be included in this count; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this)

Numeric (integer)

may

1232

appointment_scheduled_mode_other_count

All Appointments from appointment_scheduled_count (field 210) where:

• of mode of Appointment: Other (a count as at the end of the reporting period of the number of Slots scheduled as any other mode of Appointment not given above; Appointment mode groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this; this count WILL include any unknowns)

Numeric (integer)

may

1233

appointment_scheduled_hcptype_gp_count

All Appointments from appointment_scheduled_count (field 210) where:

• with healthcare professional type: General-Practitioner-(GP)  (a count as at the end of the reporting period of the number of Slots scheduled with healthcare professional type of GP or similar i.e. if an Appointment Slot is initially scheduled with a GP and then reassigned to nurse, this will NOT be included in this count; healthcare professional groupings and terminology may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1235

appointment_scheduled_hcptype_nurse_count

All Appointments from appointment_scheduled_count (field 210) where:

• with healthcare professional type: Nurse (a count as at the end of the reporting period of the number of Slots scheduled with healthcare professional type of Nurse or similar i.e. if an Appointment Slot is initially scheduled with a Nurse and then reassigned to GP, this will NOT be included in this count; healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1236

appointment_scheduled_hcptype_other_clinical_count

All Appointments from appointment_scheduled_count (field 210) where:

• with healthcare professional type: Other – Clinical (a count as at the end of the reporting period of the number of Slots scheduled with healthcare professional type of Other – Clinical i.e. if an Appointment Slot is initially scheduled with a Nurse and then reassigned to another clinical user other than Nurse or GP, this WILL be included in this count; healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count)

Numeric (integer)

may

1237

appointment_scheduled_hcptype_other_count

All Appointments from appointment_scheduled_count (field 210) where:

• with healthcare professional type: Other (a count as at the end of the reporting period of the number of Slots scheduled with any other healthcare professional type, including clerical user types i.e. if an Appointment Slot is initially scheduled with a Nurse and then reassigned to another health care professional type which is not GP, Nurse or other clinical, this WILL be included in this count; see embedded document for a list of all the types which will NOT be included in this count; this count WILL include any unknowns)

Numeric (integer)

may

1238

third_next_appointment_time_GP_total

Sum of the time to third next available Appointment figures calculated for each scheduling transaction associated with Appointments:

• with a start date and time within the reporting period (based on start time of Appointment) 

• of any Slot Type (where Appointment Slot was available for a Patient to book i.e. exclude any 'blocked' or 'embargoed' Slots; terminology may differ between Supplier systems and The Authority will consult with Suppliers on this) 

• with healthcare professional type: General-Practitioner-(GP) (healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count) 

• as per the methodology

Numeric (integer)

may

1239

third_next_appointment_time_nurse_total

Sum of the time to third next available Appointment figures calculated for each scheduling transaction associated with Appointments:

• with a start date and time within the reporting period (based on start time of Appointment) 

• of any Slot Type (where Appointment Slot was available for a Patient to book i.e. exclude any 'blocked' or 'embargoed' Slots terminology may differ between Supplier systems and The Authority will consult with Suppliers on this) 

• with healthcare professional type: Nurse (healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count) 

• as per the methodology

Numeric (integer)

may

1240

third_next_appointment_time_other_clinical_total

Sum of the time to third next available Appointment figures calculated for each scheduling transaction associated with Appointments:

• with a start date and time within the reporting period (based on start time of Appointment) 

• of any Slot Type (where Appointment Slot was available for a Patient to book i.e. exclude any 'blocked' or 'embargoed' Slots terminology may differ between Supplier systems and The Authority will consult with Suppliers on this) 

• with healthcare professional type: Other – Clinical (healthcare professional groupings may differ between Supplier systems and The Authority will consult with Suppliers on this; see embedded document for a list of types to be included in this count) 

• as per the methodology

Numeric (integer)

may

1241

third_next_appointment_time_GP_trans_count

Total number of time to third next available Appointment figures which were summed together to give field 1238

Numeric (integer)

may

1242

third_next_appointment_time_nurse_trans_count

Total number of time to third next available Appointment figures which were summed together to give field 1239

Numeric (integer)

may

1243

third_next_appointment_time_other_clinical_trans_count

Total number of time to third next available Appointment figures which were summed together to give field 1240

Numeric (integer)

may

1244

appointment_Patient_sex_male_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of sex: Male (based on the sex of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1245

appointment_Patient_sex_female_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of sex: Female (based on the sex of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1246

appointment_Patient_sex_unknown_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of sex: Unknown (based on the sex of the Patient attending the Appointment NOT who booked it; this field WILL include Patients with sex recorded as 'indeterminate')

Numeric (integer)

may

1247

appointment_Patient_ethnicity_white_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: White (based on the ethnicity group of the Patient attending the Appointment NOT who booked it; see Read/CTV3/SNOMED mapping embedded below)

Numeric (integer)

may

1248

appointment_Patient_ethnicity_mixed_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: Mixed (based on the ethnicity group of the Patient attending the Appointment NOT who booked it; see Read/CTV3/SNOMED mapping embedded below)

Numeric (integer)

may

1249

appointment_Patient_ethnicity_asian_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: Asian or British Asian (based on the ethnicity group of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1250

appointment_Patient_ethnicity_black_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: Black or Black British (based on the ethnicity group of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1251

appointment_Patient_ethnicity_other_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: Other (based on the ethnicity group of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1252

appointment_Patient_ethnicity_unknown_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was of ethnicity group: Unknown (based on the ethnicity group of the Patient attending the Appointment NOT who booked it)

Numeric (integer)

may

1253

appointment_Patient_age_0-1_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 0-1 year (based on the age of the Patient attending the Appointment NOT who booked it; Patients who are less than 1 year old)

Numeric (integer)

may

1254

appointment_Patient_age_1-5_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 1-5 years (based on the age of the Patient attending the Appointment NOT who booked it; age banding is inclusive i.e. a Patient aged 1 year and a Patient aged 5 years WILL both be included in this count)

Numeric (integer)

may

1255

appointment_Patient_age_6-15_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 6-15 years (based on the age of the Patient attending the Appointment NOT who booked it; age banding is inclusive i.e. a Patient aged 6 years and a Patient aged 15 years WILL both be included in this count)

Numeric (integer)

may

1256

appointment_Patient_age_16-45_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 16-45 years (based on the age of the Patient attending the Appointment NOT who booked it; age banding is inclusive i.e. a Patient aged 16 years and a Patient aged 45 years WILL both be included in this count)

Numeric (integer)

may

1257

appointment_Patient_age_46-64_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 46-64 years (based on the age of the Patient attending the Appointment NOT who booked it; age banding is inclusive i.e. a Patient aged 46 years and a Patient aged 64 years WILL both be included in this count)

Numeric (integer)

may

1258

appointment_Patient_age_65-80_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 65-80 years (based on the age of the Patient attending the Appointment NOT who booked it; age banding is inclusive i.e. a Patient aged 65 years and a Patient aged 80 years WILL both be included in this count)

Numeric (integer)

may

1259

appointment_Patient_age_over_81_count

All Appointments from appointment_attended_count (field 1224):

• where Patient attending Appointment was in age band: 81 years and over (based on the age of the Patient attending the Appointment NOT who booked it; Patients who are aged 81 years or older i.e. a Patient aged 81 WILL be included in this count)

Numeric (integer)

may

1260

Patient_attended_multiple_appointments_count

Total number of Patients who attended three or more Appointments in the period (a count as at the end of the reporting period of the number of Patients who attended three or more Appointments) 

• with a start date and time within the reporting period (based on start time of Appointment) 

• with attendance status of 'attended' (scheduled Appointments where Patients attended their Appointment; terminology for 'attended' may differ between Supplier systems) 

• booked using any method

• with any healthcare professional type

• of any Slot Type (type of Appointment is defined as routine, emergency, or specialist clinics etc. terminology may differ between Supplier systems) 

• of any duration

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

1108

total_documents_count

Total number of unique documents received into and stored by the Solution that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received via any mechanism (i.e. electronic, scanned, manual etc. are all included)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1108 in Patient Information Maintenance - GP)

Numeric (integer)

may

1109

total_documents_scanned_count

Total number of unique documents received into and stored by the Solution that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received via scanning (i.e. documents received on paper and scanned as opposed to being received via an electronic format)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1109 in Patient Information Maintenance - GP)

Numeric (integer)

may

1110

total_documents_electronic_count

Total number of unique documents received into and stored by the Solution that were: (this does NOT include instances of duplicate documents being received and recorded against a Patient record)

• recorded against a Patient record

• recorded against a Patient record at any time within the reporting period (if the document is received by the system outside of the reporting period, but saved against a Patient record within the reporting period, then this WILL be included; if the document is received into the system within the reporting period, but not saved against a Patient record until outside the reporting period this will NOT be included)

• received electronically (i.e. documents received electronically as opposed to being received in paper format and scanned)

If same data is stored by multiple Solutions, it will only be submitted once by one Supplier (see 1110 in Patient Information Maintenance - GP)

Numeric (integer)

may

Field ID

Data Item

Definition

Format

Level

308

prescriptions_ordered_trans_count

Total number of Prescription ordering transactions: (this is a count of transactions resulting in a Prescription/s being ordered, NOT the number of items ordered; ordering several items in one transaction should only be counted as a single transaction) 

• via any Prescription ordering method

• the ordering transaction took place within the reporting period

Numeric (integer)

may

309

items_ordered_total_count

Total number of Prescription items ordered: (this is a count of the items ordered, NOT the number of transactions; if ordering several items in one transaction each item should be counted individually) 

• via any Prescription ordering method

• the ordering transaction took place within the reporting period

Numeric (integer)

may

Items on the Roadmap which impact or relate to this Standard