Application Functions
The Application Functions describe the abilities of the software functions in an EPR application by Capability. The Application Functions Catalogue extends links to the User Stories and Core Requirements.
ID | Capability | Application Function | Description |
---|---|---|---|
AF101 | Patient Record Management | Create Patient Record/Register Patient | This is the ability of an application to create a common reference number for a patient record electronically where one did not exist before (confirm this would be via PAS) |
AF102 | Patient Record Management | Search for Patient Record (local reference) | This is the ability to search for, identify and read an existing patient record according to an internally (within the application) assigned common reference number (identifier). |
AF103 | Patient Record Management | Search for Patient Record (NHS Number) | This is the ability to search for, identify and read an existing patient record according to the patients NHS Number. |
AF104 | Patient Record Management | Search for Patient Record (demographics) | This is the ability to search for, identify and read an existing patient record according to demographics information provided by or known about the patient. |
AF105 | Patient Record Management | Search for Patient Record (location) | This is the ability to identify and read an existing patient record according to information known about the location of the patient eg. ward, clinic, theatre, etc |
AF106 | Patient Record Management | Add Patient Identifier | This is the ability of an application to associate an additional patient identifier with the patient record to enable automatic patient identifier. |
AF107 | Patient Record Management | Search for Patient record (secondary identifier) | This is the ability of an application to search for, identify and read an existing patient record according to a secondary identifier associated with a patient. To enable this functionality the application should be able to integrate with electronic devices used to read secondary identifiers. e.g. barcode scanner. |
AF108 | Appointments Management | Create Appointment Slot | This is the ability of an application to allow an administrator to create appointment slots for any appointment type). |
AF109 | Appointments Management | Search and fulfil Appointment Slots | This is the ability of an application to allow appointment slots to be searched via structured appointment data (time/location/clinician etc.) and for an authorised user to be able to book the Appointment slot. |
AF110 | Appointments Management | Amend Appointment Record | This is the ability of an application to allow an appointment record to be updated or cancelled. |
AF111 | Appointments Management | Reschedule Appointment | This is the ability of an application to allow cancelled appointments to be rescheduled. |
AF112 | Appointments Management | Record Appointment Outcome | This is the ability to record to the patient record the clinical outcome of any appointment. |
AF113 | Appointments Management | Patient Communications | This is the ability of an application to send an electronic notification to a patient (via email/SMS). |
AF114 | Documentation Provision | Patient Correspondence | This is the ability of an application to generate and send a letter to a patient. |
AF115 | Appointments Management | Add to Waiting List (Inpatient and Outpatient) | This is the ability of an application to add a patient to a waiting list so that other scheduling processes can operate. |
AF116 | Appointments Management | View Waiting List (Inpatient and Outpatient) | This is the ability of an application to hold or see a waiting list (in data format)Â so that other scheduling processes can operate. |
AF117 | Bed Management | Define Bed configuration | The ability to maintain data on what beds are available to be assigned to patients
|
AF118 | Bed Management | View Bed Availability | The ability to view which beds do not have a patient assigned |
AF119 | Bed Management | Assign Patient to Bed | The ability to assign a patient to a bed under a particular speciality. The system should be able to flag where a patient has not been assigned to the correct speciality so this can be flagged to clinicians. [estimated length of stay] |
AF120 | Bed Management | Update Bed Status | The ability to change the status of a bed:
|
AF121 | Patient Record Management | Patient Record Search | The ability of an application to enable a clinician to search for a patient record using a combination of coded or structured data held within or linked to the Patient Record. |
AF122 | Patient Record Management | Link Patient Records | The ability of an application to be able to link Patient records, e.g. Mother to Child |
AF123 | Patient Record Management | Clinical Form Templates | This is the ability of an application to enable the configuration of clinical forms/clinical note templates to support the capture of clinical data to be stored against the patient record. This must includes the setting of rules for forms, e.g. mandatory/optional fields. |
AF124 | Patient Record Management | Clinical Form Objects | This is the ability to be able to re-use the same data objects/attributes across different clinical forms/clinical note. |
AF125 | Patient Record Management | Clinical Form Pre-Population | This is the ability of the application to be able to pre-populate a clinical form with existing data taken from a patient record. The system must be able to set data to being read-only where data should not be amended/overwritten. |
AF126 | Patient Record Management | Clinical Form Prompts | This is the ability of an application to be able to prompt a user to validate that existing pre-populated data is correct or to complete mandatory fields. |
AF127 | Patient Record Management | Clinical Form Validation | This is the ability of an application to provide data validation on Clinical forms. |
AF128 | Patient Record Management | Clinical Form Part-Saving | The ability of an application to enable a partially completed form to be saved for completion at a later date. |
AF129 | Patient Record Management | Audit changes to Clinical Record | The ability of an application to audit all changes to a Patient medical record. |
AF130 | Patient Record Management | Maintain Patient Record | The ability for an application to be able to select the appropriate clinical form to record care against the Patient record whilst maintaining a history of changes. |
AF131 | Patient Record Management | Record Clinical Notes | This is the ability to record a new clinical against a a patient record including being able to incorporate additional data from the patient record and tag the source of the data. |
AF132 | Record Observation | Record Observation | This is the ability to record a new observation as structured data against a patient record whilst maintaining an history of changes. As part of recording an observation an application must be able to analyse the recorded parameters and provide a prompt to clinicians where these fall outside pre-configured ranges. |
AF133 | Patient Record Management | Directly record observation from device | This is the ability for the application to accept an observation directly from a clinical device and store this against the patient record whilst maintaining an history of changes. |
AF134 | Patient Record Management | Record Care Plan | This is the ability to record a new or amended care plan against a a patient record whilst maintaining an history of changes. |
AF135 | Patient Record Management | Record Allergies | This is the ability to record a new or updated allergy as structured data against within a patient record whilst maintaining a history of changes. |
AF136 | Patient Record Management | Record Admission | This is the ability to record an admission as structured data against a patient record whilst maintaining a history of changes. |
AF137 | Patient Record Management | Record Problems/Diagnosis | This is the ability to record a new or updated problem/diagnosis (conditions/comorbidities) as structured data against patient record whilst maintaining a history of changes. |
AF138 | Patient Record Management | Record Procedure/Intervention | This is the ability to record an intervention/procedure as structured data against a patient record whilst maintaining a history of changes. |
AF139 | Patient Record Management | Record Outcomes | This is the ability to record a patient outcome (PROMS) as structured data against the patient record whilst maintaining a history of changes |
AF140 | Patient Record Management | Directly record observation from device | This is the ability of an application to receive and process observations taken from an external device and incorporate into the patient medical record. As part of recording an observation an application must be able to analyse the recorded parameters and provide a prompt to clinicians where these fall outside pre-configured ranges. |
AF141 | Patient Record Management | Record intake/outtake | This is the ability of an application to be able to record intake/outtake information, e.g. fluid intake and store against the Patient record. |
AF142 | Patient Record Management | Record Ceiling of Care | The ability to record patient decisions/ceiling of care as structured data against a patient record whilst maintaining a history of changes. Includes: |
AF143 | Patient Record Management | Configure clinical coding lists | The ability to configure lists of pre-structured clinical codes. The pre-configured lists must be able to make available to support any data collection activity, e.g. via drop down lists. |
AF144 | Patient Record Management | Access clinical coding lists | The ability to access clinical coding lists whilst recording information at the point of care. |
AF145 | Patient Record Management | Search clinical coding lists | The ability of the system to display clinical codes that correspond with the characters being typed by Healthcare Professionals at the point of care, and display them for selection. |
AF146 | Patient Record Management | Translate information into codes | Computer assisted coding - the use of natural-language processing (NLP) with machine learning (ML) to provide or suggest diagnosis and treatment codes to medical coders based on reading and interpretation of clinical documentation. |
AF147 | Patient Record Management | Note dictation (voice to text translation) | The ability of an application to allow a clinician to directly dictate notes which will be stored against the Patient record. |
AF148 | Patient Record Management | Import results/reports from medical devices | The ability to import data electronically from compatible files and systems. |
AF149 | Patient Record Management | Derive data and store against Patient record | The ability of an application to be able to calculate derived data, e.g. BMI from Patient Height and Weight and store this against the patient record. |
AF150 | Patient Record Management | Create audio file | Create an audio file in any format, add relevant metadata to the audio file and store it as part of the patient record. |
AF151 | Patient Record Management | Save, search and playback audio file | Playback the audio file/s for the selected patient record. |
AF152 | Patient Record Management | Create video file | Create a video file in any format, add relevant metadata to the audio file and store it as part of the patient record. |
AF153 | Patient Record Management | Save, search and playback video file | Playback the video file/s for the selected patient record. |
AF154 | Patient Record Management | Voice recognition (voice to text translation | The ability of an application to capture notes which a clinician has dictated which can be stored against a Patient record. [Longer term requirement] speech recognition, natural language processing (NLP), artificial intelligence (AI) and machine learning (ML) to automate documentation of the spoken aspects of a clinical encounter. These solutions use ambient listening and speech recognition technology to convert captured audio to text. Relevant information from the clinical encounter is extracted and summarized before being uploaded to the EHR. |
AF155 | Patient Record Management | View Patient Record (current) | This is the ability to view the data and documents added to a patient record as part of the current episode. |
AF156 | Patient Record Management | View Patient Record (historic) | This is the ability to view the data and documents added to a patient record as part of a historic episode. |
AF157 | Patient Record Management | Visualise Patient Data | This is the ability of an application to take a sequence of data recorded in the patient record and present it graphically. The application must be able to overlap results against standard charts, e.g. UK growth chart. |
AF158 | Patient Record Management | View Patient Record (summary) | The ability to present a summary view of a patient record including pertinent information, e.g Did Not Attend (DNA), Allergies etc. |
AF159 | Patient Record Management | Configure Clinical views | This is the ability to be able to configure clinical views to present different information based upon criteria including:
|
AF160 | Patient Record Management | Configure default clinical views | This is the ability to enable a user to configure a view when they access a Patient Record including: Sorting/ordering – re-ordering the sequence of record either chronologically or via any other data grouping Filtering and grouping – identifying a subset of the record based on the type or value of a data item or a specific date range The user interface must highlight where views have been configured. |
AF161 | Patient Record Management | View drill downs | The ability to be able to drill down into specific parts of a clinical record |
AF162 | Patient Record Management | Intelligent record searching | The ability of an application to be able to present information within a clinical view based upon criteria selected by the user or based upon the profile of the user. This could include:
The application should apply techniques to improve the relevance of the information presented to a user. |
AF163 | Bed Management | Ward, Unit or Department View Configuration | This is the ability to configure views for a ward, unit or department. |
AF164 | Bed Management | View Ward, Unit or Department Data | This is the ability of an application to generate a patient view by a specific ward, unit or department.  |
AF165 | Bed Management | Update Ward, Unit or Department Views | The ability to manually add information to a ward, unit or department view and store this information within the system. |
AF166 | Bed Management | Generate historical view | The ability of the system to generate a view to represent the state at a particular date/time. |
AF167 | Consent Management | Record Patient Consent | The ability of an application to allow legal consent for a procedure to be captured via appropriate legal forms. |
AF168 | Consent Management | Identify relevant risk factors | The ability of an application to identify any risk factors relevant to a patient when undergoing a specific treatment or procedure. |
AF169 | Consent Management | Consent Management | The ability of an application to provide links to relevant content including:
Note: All multimedia content must be supported. |
AF170 | Documentation Provision | Patient Correspondence | The ability of a an application to electronically transmit documentation to a patient (including links to relevant multimedia content, and receive and store returned (electronically signed) documentation. |
AF171 | Clinical Decision Support | Business Rules configuration | The ability of an application to support the configuration of rules based upon data which has been captured about a patient. This includes:
Note: Need something around ranges related to context, e.g. condition of patient, which determines whether notification is required. {Which clinician/groups of clinicians receive each alert]. Potentially break down all of this into separate functions. Note: Look at possibility of linking with machine learning to refine algorithms |
AF172 | Clinical Decision Support | Business Rules authoring | The ability to support the implementation of business rules in accordance with standards such as DMN (Decision Model Notation) |
AF173 | Clinical Decision Support | Generate clincal alerts | The ability of an application to run algorithms based upon patient data (observations, conditions, test results etc.) to proactively identify conditions or deterioration in conditions and generate clinical alerts where issues are identified (scores are beyond defined thresholds). |
AF174 | Clinical Decision Support | Review Patient Alerts | The ability of an application to be able to display relevant alerts to a clinician and for the clinician to be able to respond to them. The application must allow a clinician to be able to override an alert and provide a clinical reason for why the alert has been overridden which is stored against the patient record. |
AF175 | Clinical Decision Support | View and Respond to Patient Alerts | The ability of an application to flag to a user an alert when the predefined factors are met and for the user to be able to provide an auditable acknowledgement that they have actioned the alert. (Need to clarify what is required in terms of acknowledgment) |
AF176 | Clinical Decision Support | Configure alerts | Potentially consider machine learning to check where alerts are acted upon - where consistently overridden may look to update rules |
AF177 | Clinical Decision Support | Issues alert | The ability of an application to send a clinical alert to a clinician or group of clinicians. |
AF178 | Clinical Decision Support | Escalate alert | The ability of an application to resend an alert to a relevant clinician or group of clinicians when no acknowledgement of the alert has been recorded within a configurable time period. |
AF179 | Clinical Decision Support | Decision Support Audit | The ability of an application to record when an alert is generated or responded to. |
AF180 | Clinical Decision Support | Workflow Decision Support | The ability to engage decision support, record the action on the patient record, and on the relevant decision support systems. |
AF181 | Clinical Decision Support | Calculate Risk Scores | The ability to calculate risk scores, e.g. risk of re-admission, risk of morbidity based upon a patients medical history which can be presented to clinicians to support clinical decision making. |
AF182 | Clinical Decision Support | Test Results Configuration | The ability to configure rules for analysis of electronic result updates including:
|
AF183 | Clinical Decision Support | Test Results analysis | The ability of an application to analyse an electronic results update and identify where an urgent health issue is identified according to pre-configured rules, i.e. classify results as 'normal' or 'abnormal' |
AF184 | Clinical Decision Support | Send Results Notification | The ability of an application to send a notification to the clinician who ordered a test and concerned clinical groups where a test result indicates that a patient has an urgent health need. |
AF185 | Clinical Decision Support | Results Acknowledgement | The ability of an application to request an acknowledgement from a clinician that results have been viewed and actioned where the results fall outside normal parameters for the specific clinical speciality of the requesting clinician. |
AF186 | Clinical Decision Support | Clinical notification configuration | The ability of an application to enable either opt out of receiving a notification when requesting a test or to set the parameters for the specific test which would trigger a notification being sent. This function should be enabled/disabled centrally. |
AF187 | Clinical Decision Support | Acknowledgement Reminders | The ability of an application to send a reminder notification to a clinician when no acknowledgement has been received that the results have been reviewed. |
AF188 | Clinical Decision Support | Escalate notifications | The ability to re-route a notification to another clinician (using pre-configured escalation rules) when no acknowledgment is received within a pre-configured timeframe. |
AF189 | Clinical Decision Support | Display Visual prompts | The ability of an application to analyse results and to display visual prompts where an issue is identified. |
AF190 | Clinical Decision Support | Decision Support Machine Learning | The ability of an application to analyse the acknowledgments received by clinicians and to adapt rules automatically related to when a notification is required based upon the responses provided by clinicians. |
AF191 | Referral Management | Configure referral lists | The ability to configure the list of clinical specialities to which a referral can be made and the clinicians within each of the specialities who can be assigned to a referral. |
AF192 | Referral Management | Configure referral forms | The ability to configure specific electronic referral forms per clinical speciality so the appropriate information can be provided. |
AF193 | Referral Management | Create Patient Referral | This is the ability of the system to enable an authorised clinician to initiate an electronic referral via a standardised referral form which will be sent to the applicable clinical service for review and stored against the Patient record. The form must support conditional logic to only display fields relevant to the speciality where the referral is being made. |
AF194 | Referral Management | Referral Validation | This is the ability of the system to ensure that all relevant information has been provided and that the referral is not a duplicate. |
AF195 | Referral Management | Review Patient Referral | The ability of a receiving service/clinician to referrals new referrals that have been made which they can accept, reject or request further information. Where a referral is rejected or further information is required the sender must be notified and be able to provide additional supporting information in a resubmission of the referral. |
AF196 | Referral Management | View Patient Referral History | The ability of the system to display a view of referrals made on behalf of a patient and the outcome of those referrals. |
AF197 | Referral Management | Amend Patient Referral | The ability for a clinician to select an existing referral record with the appropriate status and provide additional information. |
AF198 | Referral Management | View referral requests | The ability of the system to enable a clinician to view referrals which they have made including the current status of those referrals |
AF199 | Referral Management | View referral worklists | The ability for a clinician to view all referrals that that have been allocated to them or to their clinical speciality and the status of those referrals. The system must be able to display referrals in an order specified by the clinician, e.g. status or clinical priority. |
AF200 | Referral Management | Allocate referrals | The ability of the system to enable a clinician to assign themselves to a referral or enable a clinician with the appropriate role to assign a referral to another clinician. |
AF201 | Referral Management | Redirect referrals | The ability for an authorised user to redirect a referral to another clinical speciality |
AF202 | Referral Management | Update internal referral | The ability to update a referral record (including the outcome of the referral). The update must be able to trigger a notification to the originator of the referral informing them of the outcome. |
AF203 | Referral Management | Referral escalations | The ability to send a notification/reminder when a referral has not been acknowledged within a configurable period of time. |
AF204 | Referral Management | Create external Patient referral | The ability of the system to enable a clinician to refer a patient to an external service via an electronic notification (Messaging or Email) |
AF205 | Referral Management | Amend external Patient Referral | The ability for a clinician to select an existing referral record with the appropriate status and provide additional information. |
AF206 | Referral Management | External referral updates | The ability to receive a notification of the outcome of an external referral |
AF207 | Discharge | Record Patient Discharge | This is the ability to update inpatient service administration records (including destination, GP tasks and additional information) and to remove the location of the patient from the patient record.  |
AF208 | Discharge | Send Task to GP | The ability to send a task to a GP related to the discharge of a patient and to receive an acknowledgement when the task has been completed. |
AF209 | Discharge | Generate and send Discharge Notification | The ability to send a notification to all clinicians and services involved in the care of a patient when the patient is due to be discharged |
AF210 | Discharge | Generate Discharge summary | The ability of an application to generate a discharge summary document |
AF211 | Discharge | Complete Discharge summary | The ability of an application to allow a clinician to add additional information to a discharge summary document |
AF212 | Discharge | Distribute Discharge summary | The ability of an application to enable a clinician to select relevant organisations that should receive the discharge summary |
AF213 | Discharge | Send Discharge summary | The ability to send an electronic discharge summary once completed in accordance with nationally defined standards. |
AF214 | Discharge | Update Discharge summary | The ability of an application to allow a clinician to amend an already submitted discharge summary and resend the updated document |
AF215 | Order Comms | Order History - Patient | The ability to view a record of order requests made on behalf of a patient including:
This should be for current or historic care episodes |
AF216 | Order Comms | Non-Patient centric views | The ability to view a record of orders and investigations by MDT or patients assigned to a clinician including:
The view must also include patients where no test/order history exist The view must include a link to be able to order new tests/investigations |
AF217 | Order Comms | Place Test/Investigations Order | The ability to engage testing services in real time and record the action that a request has been made on the patient record.
The application must be able to support the following:
The application may support the following:
 |
AF218 | Order Comms | Proxy Order | The ability to place an order on behalf of another Clinician. |
AF219 | Order Comms | Order/Investigation rules | The ability to apply rules to prevent ordering of duplicate investigations/orders |
AF220 | Order Comms | Place multiple orders | The ability to place multiple orders at the same time. |
AF221 | Order Comms | Place recurring order | The ability to place a recurring order for a test/investigation |
AF222 | Order Comms | Configure Order/Investigations Orders | The ability to be able to create configurable sets of orders/investigations for a patient based upon the clinical speciality to which the patient is assigned |
AF223 | Order Comms | Create customer order/investigation lists | The ability to allow a user to create a custom list of order/investigations they make on a frequent basis. |
AF224 | Order Comms | Link Patient to Sample | The ability to generate and print a label to associate a sample with the correct patient. |
AF225 | Order Comms | Track Test/Investigation Order | The ability to view all outstanding orders (by patient, by clinician) and track the status of these including when the result is expected to be available. The system should allow the user to filter orders by status or type. The system should allow this information to be exposed externally, either via a patient portal to enable patients to view the status of their tests/orders or via the publishing of order events (change in status) which can be consumed by subscribing systems. |
AF226 | Order Comms | Order alerts | The ability to generate an alert to the requestor when an order is delayed |
AF227 | Order Comms | Modify/Cancel Test/Investigation Order | The ability of an application to allow a clinician to modify/cancel an order which has already been submitted. This includes orders where samples have already been sent to labs. |
AF228 | Order Comms | Receive and Process Test Results | The ability of an application to be able to receive and process results received from Lab systems (including correlating results with requests). |
AF229 | Diagnose Problem | View Test/Investigation Results | The ability to view the results of all tests/investigations carried out on behalf of a patient including any associated artefacts (images etc.) captured via the testing application. |
AF230 | Clinical Decision Support | Results Decision Support | The ability to provide a visual indicator of where results fall outside expected range of values. |
AF231 | Clinical Decision Support | Visualise Test/Investigation results | The ability to visualise a set of corresponding results, e.g. via time-series graphs. This should include the ability to overlap significant events onto views, e.g. interventions, procedures |
AF232 | Record Observation | Capture and View Clinical Data | The ability to add test results to the patient record either manually or from a specific purpose clinicial equipment (eg radiology cameras) and to view the clinical data. |
AF233 | Order Comms | Acknowledge test results | The ability to update order comms systems to complete the order comms processes |
AF234 | Medication Management | Configure Medications Data | The ability of an application to manage medication reference data in accordance with the dm+d standard and SnoMed CT coding for non-dm+d terms (e.g. route, formulation, Unit of Measure):
|
AF235 | Medication Management | Configure Medication Alerts | The ability to create alerts for medications linked to known allergies or intolerances |
AF236 | Medication Management | Configure Medication efficacy rules | The ability of an application to apply rules which determine when prompts should be issued to clinicians when a medication has been ordered a configurable number of times. |
AF237 | Medication Management | View Historic Medication | This is the ability to view the medications added to a patient record as part of a previous episode. This includes the ability to present a unified medication view via access to all systems where medication data is held. |
AF238 | Medication Management | Medication Stock Check | The ability of an application to make an external system check that the medication being selected by a prescribing solution features in the formulary and is in stock. |
AF239 | Medication Management | Specimen Check | The ability of application to make an external system check that a valid specimen exists for a patient and where one does exist place an order for a compatibility test against it. |
AF240 | Medication Management | Create Prescription (medicine) | The ability to electronically create a new medication prescription for a patient. This should include the ability to select from a configured list of medicines per speciality or to allow the clinician to perform a free text search of all available medications. |
AF241 | Medication Management | Create Prescription (Blood transfusion) | The ability to prescribe/request blood transfusion products linked to a specimen and the ability to track the progress of the request. |
AF242 | Medication Management | Amend Prescription | This is the ability to change the current medications within a patient record whilst maintaining a history of changes. |
AF243 | Medication Management | Medication Decision Support - Allergies | The ability to check prescribed medicines against known patient allergies and stop the prescription and alert the clinician where a conflict is identified by the system. This should also include the ability to check against cross-allergies (where a specific allergy indicates the potential for the patient to be allergic to another type of medication) and cross-reactions. The system must allow a clinician to override the alert, provide a reason for the override and audit this action. |
AF244 | Medication Management | Medication Decision Support - Intolerances | The ability to check prescribed medicines against known patient intolerances and stop the prescription and alert the clinician where a conflict is identified by the system. The system must allow a clinician to override the alert and audit this action. |
AF245 | Medication Management | Medication Decision Support - Dosage | The ability to check dosage of prescribed medicines against expected ranges and stop the prescription and alert the clinician where a conflict is identified by the system. The dosage matching process must incorporates patient safety based on age ranges, weight ranges, therapeutic doses, maximum doses and cumulative doses. The system must allow a clinician to override the alert and audit this action. |
AF246 | Medication Management | Schedule Medications | The ability to create a schedule of medications (medications provided on a determined schedule) |
AF247 | Medication Management | Medication Notification | The ability to provide a prompt that scheduled medication is due to be administered. |
AF248 | Medication Management | Transfer Prescription | The ability of an application to be able to electronically transfer a completed prescription to the Pharmacy dispensing system or medicine cabinet for fulfilment |
AF249 | Medication Management | Verify Patient and Medication | The ability to an application to be able to scan patient, medication, dosage identifiers (via a set of dosage options), route (via a set of route options) to verify that the correct medication and dose is to be administered via the correct route and at the right time. The application must alert the administering clinician where any mismatch is identified which the clinician can override where necessary. |
AF250 | Medication Management | Verify Patient and Blood order | The ability to an application to be able to scan patient, and blood order to verify that the transfusion to be administered is being given to the correct patient.. The application must alert the administering clinician where any mismatch is identified. |
AF251 | Medication Management | Record Medication Administration | The ability of an application to electronically record when medication has been administered (medication, dose, route and exact time) or where medication was unable to be administered (with a list of valid reasons why the medication could not be administered). This should include recording medication that is has been self-administered. |
AF252 | Medication Management | View Medications Administered | The ability of an application to provide a view of all medications that have been administered to a patient. |
AF253 | Medication Management | Record Medication Effectiveness | The ability of an application to allow a clinician to record the effectiveness of a medication. |
AF254 | Medication Management | Medication re-ordering prompt | The ability of an application to calculate when the medication being administered to a patient is due to run out and to provide a notification to the clinician to prompt them to place a new order. |
AF255 | Medication Management | Medication re-ordering | The ability of an application to allow medication to be re-ordered and the re-order to be electronically transferred to the pharmacy. |
AF256 | Medication Management | Closed Loop Med Dashboard | The ability of an application to generate a configurable dashboard demonstrating compliance with closed-loop med procedures |
AF257 | Medication Management | Medication schedule | The ability to display a schedule of when medication should be given. |
AF258 | Staff Clinical Messaging | Message Directory | The ability to hold a directory of clinicians/clinical group who messages can be sent to. |
AF259 | Staff Clinical Messaging | Messaging group configuration | The ability of a message group administrator to maintain lists of clinicians within specific group. |
AF260 | Staff Clinical Messaging | Send Message - Internal | The ability to send a secure message to a specific clinician or groups of clinicians selected from a directory regarding specific aspects of a Patients care and store this message against the patient record. This includies being able to include provide links to patient records including but not limited to:
|
AF261 | Staff Clinical Messaging | Message acknowledgement | The ability of an application to record that a message has been acknowledged by a recipient. |
AF262 | Staff Clinical Messaging | Message inbox | The ability for an authenticated user to view a list of relevant messages to which they can respond. The application must be able to provide links to the relevant part of a patient record relevant to the message. |
AF263 | Staff Clinical Messaging | Group Message Management | Placeholder - How to manage message sent to group - many messages or to a single group mailbox |
AF264 | Staff Clinical Messaging | Message Response | The ability of a clinician to be able to respond to a clinical message and for this response to be recorded against the patient record. |
AF265 | Staff Clinical Messaging | Retract Message | The ability for a user to retract a message they have sent in error |
AF266 | Staff Clinical Messaging | Message notifications | The ability to issue a notification to a clinician that they have a new message in their inbox. [Need to think about type of notification - SMS, Push notification to Mobile App etc.] Will also need to include linking clinician to mobile device. {link to need to be authenticated to see messages] - notification contains no clinical data |
AF267 | Staff Clinical Messaging | Audit | The ability to retain a timestamped audit record of messages exchanged between clinicians. |
AF268 | Staff Clinical Messaging | Send Message - external | The ability to send a secure message to external organisations selected from a directory regarding specific aspects of a Patients care and store this message against the patient record, eg. patient due to be discharged. |
AF269 | Provide Multiple User Digital | E-Consultation | The ability to provide communication through the use of video conference technology or teleconference technology or audio interpretation technology |
AF270 | Provide Single User Digital | Externl Device Integration | The ability to collect medical data from individuals outside of a traditional care setting and incorporate within the patient care record. The data can by collected via by the individual (rekeying data into an App) or directly from a medical device. |
AF271 | Information Analysis | Data Visualisation | Â |
AF272 | Information Analysis | Reporting extracts | The ability to generate standardised reports on a scheduled or ad hoc basis, e.g. reporting clinical outcomes, reports on numbers of referrals, breaches to targets and standards finding data to respond to complaints, coroner report requests. |
AF273 | Bed Management | View/update Ward Dashboard | The ability of an application to present data relevant to the administration of the selected Ward. |
AF274 | Information Analysis | View/update ED Dashboard | The ability of an application to present data relevant to the administration of the Emergency Department. |
AF275 | Dataset Management | Data extracts | The ability to extract relevant data from the application to support reporting and analytics. |
AF276 | Identity Management | User Authentication | The ability of an application to verify the identity of the user attempting to access the system |
AF277 | Identity Management | Biometric Authentication | Placeholder |
AF278 | Identity Management | User onboarding/enrolment | The ability to create a new user account |
AF279 | Identity Management | Role Based Access Control | The ability to grant/restrict access to functionality of the system based on user rights. |
AF280 | Identity Management | Single Sign On | The ability to grant access to a system using SSO. |
AF281 | Document Management | Manage content | The ability of an application to be able to support the upload and storage of generic content, e.g. clinical procedure overviews |
AF282 | Document Management | Access Content | The ability of an application to support the ability to link to content to support clinician or patient decision making. |
AF283 | Document Management | Configure Document Templates | The ability of an application to enable document templates to be created including providing support for pre-population of forms where existing data is held in the system/ |
AF284 | Document Management | Generate/Create Document | The ability to /create generate a document from a template, pre-populate this with existing data from the patient record and enable a authorised user to amend the document to:
|
AF285 | Document Management | Document validation | The ability of an application to enforce that all mandatory information is captured before a document can be sent to recipients. |
AF286 | Document Management | Store Document | The ability to save a document to a patient record once clinician has confirmed it can be committed to the data repository including the creation of meta data about the document including (but not limited to):
|
AF287 | Document Management | Update Document | The ability to retrieve and amend (add further information) an existing a clinical document. |
AF288 | Document Management | Electronic Signatures | The ability of an application to enable electronic signatures to be added to a document |
AF289 | Document Management | Configure document views | The ability of an application to enable different views of a document to be created which can be shared with different audiences, e.g. one version of a document for a GP and one for a Patient. |
AF290 | Document Management | Configure document destinations | The ability of an application to enable configuration of which external services or individuals should be sent specific documents generated within the application. The configuration must allow sending to be mandatory (automatically sent) or optional (user selected). |
AF291 | Document Management | Send Document | The ability for a document to be sent to an external service in a non-proprietary format in real-time once committed by the user. The application must allow users to select additional recipients of a document from a configured list of external services in addition to any services sent the document by default. |
AF292 | Document Management | Lock Document | The ability to lock a document so that it can no longer be amended (providing a point in time view) once a document has been transmitted. |
AF293 | Document Management | Print / Send document | The ability to electronically send a document to another electronic system or to a physical media device. |
AF294 | Document Management | Search and View Admin Letter / document | Retrieve and view letters and documents relevant to a patient record. |
AF295 | Document Management | Scan/Upload Document | The ability of an application to be able to scan a document and incorporate the scanned image into a Patient record |
AF296 | Document Management | Incorporate Document | The ability of an application to be able to receive an externally generated document (image, letter etc.) and store this against the Patient record |
AF297 | Documentation Provision | Send Correspondence | The ability of an application to send relevant documentation to a Patient. |
AF298 | Document Management | Record Patient Correspondence Preference | The ability of an application to record how a patient wishes to receive correspondence (Email, Letter) |
AF299 | Referral Management | Assign Patient to Clinician | This is the ability to assign patients to clinicians. The system must audit when a patient was assigned to a clinician |
AF300 | Admissions and Transfers | Reassign Patient | This is the ability to reassign a patient to a different ward, unit or department and to a different clinician. |
AF301 | Care Plans Management | Configure Tasks | This is the ability of the system to allow a set of clinical tasks to be created including the category of tasks and which clinical specialities are able to fulfil the tasks. |
AF302 | Care Plans Management | View Task List | This is the ability to create a view of outstanding tasks by Patient or Clinician The application should allow lists to be configured including:
|
AF303 | Care Plans Management | Assign Tasks | The ability to enable an authorised user to assign/reassign tasks to a specific Clinician or team. |
AF304 | Care Plans Management | Record Clinical Activity | This is the ability for the application to record that an activity/task has been undertaken including details of the patient, performing clinician and any items used in the activity. The system must be able to audit when tasks were completed and by which clinician. |
AF305 | Care Plans Management | Identify Clinical items | This is the ability for the application to identify (via scanning) clinical items which can be associated with an activity that is being performed. |
AF306 | Care Plans Management | Task Configuration | The ability to be able to create a new task that can be assigned to a clinician. This includes setting the classification of a task. |
AF307 | Care Plans Management | Configure Task List | The ability of an application to configure a set of tasks (and the sequence in which these are performed) that are to be performed based upon a clinical event trigger, e.g. admission, pre-discharge etc. |
AF308 | Care Plans Management | Create Task Templates | The ability to configure the information which is associated with a specific task including what information needs to be captured to close the task. |
AF309 | Care Plans Management | Auto-generate Tasks | The ability of the system to auto-generate a set of tasks (including repeating tasks) for a patient based upon a clinical event occurring (e.g. patient admission, patient diagnosis) together with a schedule of when tasks need to be undertaken. |
AF310 | Care Plans Management | Configure task rules | The ability to define task rules. This includes defining the timeframe for when a task needs to be completed from the time of it being generated. |
AF311 | Care Plans Management | Task Notification | The ability of the system to generate an alert when a task has not been completed within a configurable timeframe |
AF312 | Care Plans Management | Manual task generation | The ability of the system to allow a clinician to manually create new tasks including being able to add notes, pull in relevant clinical content and set the urgency level for the task. |
AF313 | Care Plans Management | Manual task duplication | The ability of the system to prompt a user where a duplicate task is being created. The user must be able to override the prompt/warning. |
AF314 | Care Plans Management | Update Tasks | The ability of the system to allow a clinician to pull in clinical content from the patient medical record to add context or provide additional free format information to the task. |
AF315 | Care Plans Management | Configure Workflow rules | The ability to configure automated workflows consisting of sequences of tasks, data flows (messages), notifications and alerts which can be triggered via events (system or manually generated). |
AF316 | Care Plans Management | Cross Organisational Workflow | E.g. support transfer of patient from hospital to home Review of care plan by clinicians across multiple organisations |
AF317 | Digital Access Management | Patient access to records | The ability of an authenticated patient to be able to view their own medical record including:
Note: It must be possible for clinicians to be able to restrict information for sharing with the patient via the portal where necessary. |
AF318 | Provide Single User Digital | Patient data submission | The ability for a patient to provide a submission of information via their own personal devices, e.g. a pre-admission questionnaire or a current symptoms and for this information to be saved against the patient record so it can be accessed by clinical staff. |
AF319 | Documentation Provision | Patient information provision | The ability to send relevant information electronically to a patient. This includes the ability to assign patients to particular groups so that the information they receive is relevant. |
AF320 | Digital Access Management | Delegated Self Service access | Enabling an authenticated user self-service access on behalf of another person. |
AF321 | Provide Single User Digital | Patient self service Appointment Booking | The ability to allow patients or nominated representatives of the patient to make/cancel appointments. [Need to link to patient receiving an invite to make an appointment] |
AF322 | Documentation Provision | Subject Access Requests | This is the ability of an application to be able to support the extract of data held about a patient in response to a subject access request. |
AF323 | Asset Management | Clinical Stock Management | The ability to capture and categorise a list of clinical items and products, present this data in a catalogue and to allow clinical users to request items for clinical use. Also to monitor quantities and facilitate the re-ordering of items. E.g. blood products |
AF324 | Compliance Management | Audit | The ability of an application to provide comprehensive audit of all user actions including:
|
AF325 | Compliance Management | Audit Reporting | The ability of an application to be able to generate audit reports and make these available to relevant users |
AF326 | Mobile Apps - Provide Single User Digital? | Maintain Patient Record via Mobile Device | The ability for a user to view/update a Patient medical record via a Mobile Device |
AF327 | Mobile Apps - Provide Single User Digital? | View/Maintain Tasks via Mobile App | The ability for a user to view/update tasks which have been allocated to them via a Mobile Device |
AF328 | Integrated Care | Device Integration | The ability of an application to accept information from peripheral devices, e.g. patient monitoring equipment and incorporate into the patient record. |
AF329 | Patient Record Management | Shortcuts to launch clinical forms | The ability to launch clinical forms while documenting at the point of care using synonyms |
AF330 | Patient Record Management | Show source of auto populated data | The ability to see the source of clinical information auto-populated in the electronic system form I am using to document care |
AF331 | Patient Record Management | Insert structured data form into free text | The ability to insert pre-configured/standardised clinical form templates into free text notes |
AF333 | Clinical Coding | Duplicate coding warning | the ability to automatically warn Healthcare Professionals when they attempt to enter a clinically coded diagnosis that already exists in a patient record. |
AF334 | Clinical Coding | Provide flexible clinical cooding options | the ability to describe a clinical code in more than one way i.e. fully utilise SNOMED aliases. |
AF335 | Patient Record Management | Redact Data for extract | the ability to redact information prior to export |
AF336 | Document Provision | Produce hardcopy data extracts | the ability to export/share healthcare data in hard copy. |
AF337 | Care Administration | Share summary patient data | the system to make every patient’s digitally recorded consent decisions electronically accessible to services across the Trust and region and with the national care record |
AF338 | Diagnostic management | Digitally Request Consultation | Request a consultation digitally and have the consultation and its results automatically recorded in the patient record |
AF339 | Diagnostic management | Send Results Notification | The ability of an application to send a notification to the clinician who ordered a consultation or test |
AF340 | Referral Management | Review Recommended Referrals | The system displays recommended internal referral routes within a clinical workflow and allows the clinician to choose an appropriate referral route |
AF341 | Referral Management | Digital Presentation of Handover Data | The system provides a digital presentation of patient data including context as part of a digital handover to enable the sharing of relevant patient data without the need for paper based handover notes |
AF342 | Referral Management | Access National Directory of Services | The system provides access to the National Directory of Services to enable selection of appropriate external services to use in transfers |
AF343 | Consent Management | Obtain consent to access patient data remotely | The system obtains and records consent from the remote patient to access their data to enable legal monitoring and use of that data |
AF344 | Identity Management | Authenticate Patient | The system Authenticates a patient in order to allow access to the patient record |
AF345 | Discharge | Create discharge documentation | On discharge of a patient the discharge notes and outpatient letter(s) are created automatically by the system compliant with PRSB guidelines. All documentation is recorded in the patient record for digital access |
AF346 | Patient Tracking | Create patient wristbands | Produce patient wristbands with bar code identification to allow patient to be identified and any relevant data such as allergies displayed |
AF347 | Asset Management | Track clinical assets | The ability of the system to track key clinical assets and resources. This must include assets assigned directly to patients. |
AF348 | Patient Record Management | Notify key changes to patient record | The ability of the system to notify staff and other systems of significant changes to the patient record e.g. births and deaths |
AF349 | Patient Record Management | Longitudinal access to patient record | The ability of the system to present access to all relevant data about the patient. The data will be presented in an appropriate form given the context in which it is accessed. The appropriately authorised member of staff will be able to navigate to all data that they are authorised to access |
AF350 | Information Security | Provide Pseudonymised Patient Data | When sharing data with external data the system must provide the capability to de-identify, pseudonymize and re-identify records as required |
AF351 | Information Security | Configure Role Based Access | Access to specific data within the patient record can be configured by role to ensure only data authorised for the user can be viewed or processed |
AF352 | Medications Management | Electronic Prescribing | Ability of the system to generate/record prescriptions digitally
|
AF353 | Medications Management | Non-Medical Prescriptions | Support for Patient Group directions and non-medical prescribng including
|
AF354 | Care Administration | Workforce management | Ability to view and configure staff rosters and worklists based on capacity and acuity scores |
AF355 | Care Administration | Share summary patient data | the system to make summary patient records electronically accessible to services across the Trust and region and with the national care record |
AF356 | Interoperability | Integrated use and retrieval of patient data | The solution should be integrated such that data is retrieved at the point of use to ensure only up to date date is presented. This may include on demand retrieval of data from external systems rather than local storage of potentially stale copies |
AF357 | Decision Support | Triage support | System to provide recommendations to transfer patients based on configured best practice and evidence based guidance
|
AF358 | Patient Tracking | Track Patient Flow | Ability to visualise the patient journey showing all areas visited and the activities conducted at each step |
AF359 | Bed Management | Define bed management reporting | Ability to create standard reports showing bed management statistics. This must include the ability to define KPIs and measure captured bed management data against them. |
AF360 | Order Comms | AF360 Order Progression | System indicated the progression of an order through the lifecycle of an order |
AF361 | Order Comms | Order Prioritisation | The system will allow an urgency to be set when placing an order to ensure that urgent orders receive prioritised attention and an appropriate escalation of alerts to manage the timeliness of order processing |
AF362 | Patient Connection | Accessibility | The system will allow configuration of accessibility settings such as font size, colours etc |
AF363 | Consent Management | Emergency Consent | When emergency care is required and it is not possible to confirm consent in the normal way the system should record that consent was assumed in order to proceed with the necessary emergency care |
AF364 | Discharge (or admission/bed management) | Estimated Discharge Date | On admission the system should generate and Estimated Discharge Date (EDD) based on the SMOMED admission code. The EDD can be changed by:
|
AF365 | Discharge | Referral on Discharge | The ability of the system to create a referral as part of the discharge process |
AF366 | Patient Record Management | Assign ownership | The ability of the system to assign an owner to a particular patient record and change the owner with a full audit trail of all owners assigned the record over time |
AF367 | Discharge | Configure Discharge Pathways | The System will allow pathways to discharge to be configured and amended as required.
|
AF368 | Bed Management | Pre-op Information | Provide views of pre-operative information
|
AF369 | Bed Management | Out of Area Beds | Overlay details of out of area beds on ward/department views |
AF370 | Bed Management | View Bed Status | The ability to view the status of a beds
|
AF371 | Reporting | Produce Standard Reports | Produced all standard reports required by national bodies |
AF372 | Patient Record Management | Override Clinical Coding | The ability for a user to override the system provided clinical codes |
AF373 | Patient Record Management | Medical Spell Checker | The system will provide a medical spell checker |
AF374 | Patient Record Management | Session Persistence | The system will simplify recalling a recently used patient record by persisting working sessions so that if a user navigates away from the patient record temporarily they can easily return to it without having to search again for the record |
AF375 | Admissions and Transfers | Admit patient from primary care | The system need to be able to receive a patient transfer from a primary care system and create an admission record for the patient based on the data provided |