1. TPP Standard PCS Requirements
User group clarification 29/01/16
Sam Congdon v0.2

2. Contents Contents Background Clarification 1- Practice Email Addresses
Clarification 2- Patient Related Persons Addresses
Clarification 3- Related Organisations Information
Clarification 4- Data Entry Form Templates
Clarification 5- Preferred Site- Printing Prescriptions
Clarification 6- Preferred Site- Communications
Clarification 7- Synthetic Patients in Search Results
Clarification 8-

3. Background and purpose
GPSoC are currently assuring TPP’s SystmOne for compliance against the GP Principal System Requirements V2 1.1 Some of the evidence supplied by TPP advises they don’t currently fully meet specific requirements and that TPP do not intend to meet them in future releases. The following slides will detail specific elements of the requirements that aren’t being delivered, along with any relevant TPP evidence or discussions GPSoC have had internally or with TPP. The purpose of this pack is to seek user group insight into the requirement to provide detail to help inform HSCIC decision making. We would like to ask the user group to give a view on each query we have, providing detail to support the view, this may include scenarios, workarounds and/or mitigation.

4. Clarification 1- Practice Email Addresses
Requirement GP a- Functionality MUST include the ability to define and maintain information about the practice and any branch sites, including; multiple addresses (and associated labels). TPP Response- SystmOne does not define or maintain addresses for the practice. Question to user group- Do users require SystmOne to define and maintain addresses for the practice and branch sites? If yes, how do users currently record this information? User group response: Response given by: Role:

5. Clarification 2- Patient Related Persons Email Addresses
Requirement GP a- Functionality MUST include the ability to Record and maintain the following for related persons for all registered Patients, each data item in its own explicit field(s) with values determined from standard lists wherever possible:
At least two addresses (and associated category)
TPP Response-SystmOne only allows one address to be entered in the relationship dialog.
Question to user group- Do users require SystmOne to record more than one address for any related persons to a patient? If so, how do users currently record this?
User group response :
Response given by: Role:

6. Clarification 3- Related Organisations Information
Requirement GP a – Functionality MUST include the ability to define and maintain information about Related Organisations and their departments (NHS or otherwise), including:
Multiple addresses (and associated labels)
Relationship(s) (between the General Practice and this organisation, indicating the direction of Relationship where applicable – available subset dependent on Role)
TPP Response- The relationship between the practice and organisations is not captured and neither are multiple addresses.
Question to user group- Do users require SystmOne to record the relationship and addresses for related organisations? If so, how do users currently record this?
User group response:
Response given by: Role:

7. Clarification 4- Data Entry Form Templates
Requirement GP b- Functionality MUST include the ability to continue data entry of a partially completed form – where a form has become obsolete, system to Notify / Alert User to this and allow User to continue to complete data entry using a new data entry form TPP Response- The user is provided with an error explaining that the data entry template has been deleted and cannot be continued, they are not directed to a new data entry template. If the user is writing a letter using a Word letter template, and the template is deleted they will have the option to continue writing the letter even though the template has been deleted. Question to user group- Are there scenarios where the TPP data entry template solution would cause issues in live? Is the Word response acceptable? User group response: Response given by: Role:

8. Clarification 5- Preferred Site- Printing Prescriptions
Requirement GP b –Functionality MUST include the ability to enable recording/declaration of a Patient’s Preferred Site (specifying the main site of the Practice or one of the branch sites). The Preferred Site data to drive certain functionality and system behaviour, including:
Prescribing – default printing of Prescriptions to the Preferred Site
TPP Response- The physical location at which the prescription is printed is determined by the prescription printing settings set on each PC within SystmOne. Prescriptions will be printed according to the printers specified in these settings.
Question to user group- Are there scenarios where you would want a prescription printed at a different site than the user is located?
User group response:
Response given by: Role:

9. Clarification 6- Preferred Site- Communications
Requirement GP c–Functionality MUST include the ability to enable recording/declaration of a Patient’s Preferred Site (specifying the main site of the Practice or one of the branch sites). The Preferred Site data to drive certain functionality and system behaviour, including:
Communications – default Sender merge fields to Preferred Site if/as appropriate
TPP Response- When sending patient communications, the Sender merge field defaults to the sender details that the user has set prior to creating the communication. However, a merge field for 'Usual Branch Address' is available for SystmOne Integrated Word letters. This allows users to easily insert the name, full address and telephone number for a patient's usual branch (preferred site). The output can be configured to only show the address, or only show the telephone number for example. This merge field can be used in letter templates, meaning that the patient's usual branch details are always populated in patient communications without end users having to check them each time.
Question to user group- Is the TPP response acceptable?
User group response:
Response given by: Role:

10. Clarification 7- Synthetic Patients in Search Results
Requirement GP d- • Allow Users to explicitly indicate that they wish to include synthetic Patients within Search Results where the Patient Record meets Search Criteria (default to exclude such Synthetic Records) TPP Response- SystmOne does not include synthetic patients within Clinical Report results (Search results). Synthetic patients are not included as a number of reports are submitted for financial purposes and including synthetic patients could cause confusion. Question to user group- Would there be scenarios where you would use synthetic patients in search results, e.g. to define/configure/test report criteria? User group response: Response given by: Role:

11. Clarification 8- Standard Reports Document Errors/Failures
Requirement GP eii- Generate standard practice-based Reports as pre-defined within the Principal System. Standard Reports to include: • Document receipt (numbers of documents received into the practice within a date received or date sent range), by any combination of the following: o Errors/failures TPP Response- SystmOne does not support received document errors being reported to practices. However DTS message failures, are generated via a Task & a task report can be run to see these specific failures. Question to user group- Do practices need the ability to report on all received document errors? Is the DTS message element of the response acceptable? User group response: Response given by: Role: