In order to create an Assessment Unit Analysis with the Performance Toolkit you will have to import a ward movement data file that meets a certain set of specifications. This document will provide you with the necessary information to successfully set up such a file.
The setup of your file will look similar to the example extract below.
The next few bullet points form a short summary of the data set requirements; the following sections explain each point in more detail.
The Performance Toolkit only accepts comma-separated value files, referred to as CSV files. Most commonly you will set up your CSV file in one of two ways:
You can follow this link to learn more about importing and exporting CSV files by using Microsoft Excel.
The CSV file has to contain seven columns in the order specified below. The permissible values for each column are either free text, integer/decimal number or defined according to local definitions. The required columns are summarized in the tbale below.
Field Name |
Description |
Defined By |
Hospital Name |
Name of Hospital |
Local |
Row Identifier |
Unique identification of data set row |
Local |
Ward Start Date & Time |
Date and time of arrival in curent wrad |
Local |
Ward End Date & Time |
Date and time of discharge from current ward |
Local |
Current Ward |
Ward code of current ward |
Local |
Next Ward |
Ward code of next ward of inpatient stay (blank if discharged home) |
Local |
Stay Index [Optional] |
Position of current ward stay in whole inpatient journey |
Local |
Several data quality checks will be executed upon import of the data file to the Performance Toolkit. Data rows that do not pass these checks will be highlighted and omitted from analysis. To correct invalid data items you are able to export your data set with additional columns that indicate whether the data rows have passed validation.
The Ward Start Date & Time is defined to be the date and time of arrival to the current ward.
The Ward End Date & Time is defined to be the date and time of discharge from the current ward.
The Performance Toolkit accepts DateTime values in any of the en-GB culture formats shown in the below table. You can follow this link to learn more about how to set a custom number format in Excel.
Excel Custom Format |
Example Output |
dd MMMM yyyy HH:mm |
28 August 2014 12:28 |
dd MMMM yyyy H:mm |
28 August 2014 12:28 |
dd MMMM yyyy hh:mm tt |
28 August 2014 12:28 PM |
dd MMMM yyyy h:mm tt |
28 August 2014 12:28 PM |
d MMMM yyyy HH:mm |
28 August 2014 12:28 |
d MMMM yyyy H:mm |
28 August 2014 12:28 |
d MMMM yyyy hh:mm tt |
28 August 2014 12:28 PM |
d MMMM yyyy h:mm tt |
28 August 2014 12:28 PM |
dd MMMM yyyy HH:mm:ss |
28 August 2014 12:28:30 |
dd MMMM yyyy H:mm:ss |
28 August 2014 12:28:30 |
dd MMMM yyyy hh:mm:ss tt |
28 August 2014 12:28:30 PM |
dd MMMM yyyy h:mm:ss tt |
28 August 2014 12:28:30 PM |
d MMMM yyyy HH:mm:ss |
28 August 2014 12:28:30 |
d MMMM yyyy H:mm:ss |
28 August 2014 12:28:30 |
d MMMM yyyy hh:mm:ss tt |
28 August 2014 12:28:30 PM |
d MMMM yyyy h:mm:ss tt |
28 August 2014 12:28:30 PM |
dd/MM/yyyy HH:mm |
28/08/2014 12:28 |
dd/MM/yyyy H:mm |
28/08/2014 12:28 |
dd/MM/yyyy hh:mm tt |
28/08/2014 12:28 PM |
dd/MM/yyyy h:mm tt |
28/08/2014 12:28 PM |
dd/MM/yy HH:mm |
28/08/14 12:28 |
dd/MM/yy H:mm |
28/08/14 12:28 |
dd/MM/yy hh:mm tt |
28/08/14 12:28 PM |
dd/MM/yy h:mm tt |
28/08/14 12:28 PM |
d/M/yy HH:mm |
28/8/14 12:28 |
d/M/yy H:mm |
28/8/14 12:28 |
d/M/yy hh:mm tt |
28/8/14 12:28 PM |
d/M/yy h:mm tt |
28/8/14 12:28 PM |
d.M.yy HH:mm |
28.8.14 12:28 |
d.M.yy H:mm |
28.8.14 12:28 |
d.M.yy hh:mm tt |
28.8.14 12:28 PM |
d.M.yy h:mm tt |
28.8.14 12:28 PM |
yyyy-MM-dd HH:mm |
2014-08-28 12:28 |
yyyy-MM-dd H:mm |
2014-08-28 12:28 |
yyyy-MM-dd hh:mm tt |
2014-08-28 12:28 PM |
yyyy-MM-dd h:mm tt |
2014-08-28 12:28 PM |
dd/MM/yyyy HH:mm:ss |
28/08/2014 12:28:30 |
dd/MM/yyyy H:mm:ss |
28/08/2014 12:28:30 |
dd/MM/yyyy hh:mm:ss tt |
28/08/2014 12:28:30 PM |
dd/MM/yyyy h:mm:ss tt |
28/08/2014 12:28:30 PM |
dd/MM/yy HH:mm:ss |
28/08/14 12:28:30 |
dd/MM/yy H:mm:ss |
28/08/14 12:28:30 |
dd/MM/yy hh:mm:ss tt |
28/08/14 12:28:30 PM |
dd/MM/yy h:mm:ss tt |
28/08/14 12:28:30 PM |
d/M/yy HH:mm:ss |
28/8/14 12:28:30 |
d/M/yy H:mm:ss |
28/8/14 12:28:30 |
d/M/yy hh:mm:ss tt |
28/8/14 12:28:30 PM |
d/M/yy h:mm:ss tt |
28/8/14 12:28:30 PM |
d.M.yy HH:mm:ss |
28.8.14 12:28:30 |
d.M.yy H:mm:ss |
28.8.14 12:28:30 |
d.M.yy hh:mm:ss tt |
28.8.14 12:28:30 PM |
d.M.yy h:mm:ss tt |
28.8.14 12:28:30 PM |
yyyy-MM-dd HH:mm:ss |
2014-08-28 12:28:30 |
yyyy-MM-dd H:mm:ss |
2014-08-28 12:28:30 |
yyyy-MM-dd hh:mm:ss tt |
2014-08-28 12:28:30 PM |
yyyy-MM-dd h:mm:ss tt |
2014-08-28 12:28:30 PM |
yyyy'-'MM'-'dd'T'HH':'mm':'ss.fffffffK |
2014-08-28T12:28:30.0000000 |
yyyy'-'MM'-'dd'T'HH':'mm':'ss.fffffffK |
2014-08-28T12:28:30.0000000 |
ddd, dd MMM yyyy HH':'mm':'ss 'GMT' |
Thu, 28 Aug 2014 12:28:30 GMT |
ddd, dd MMM yyyy HH':'mm':'ss 'GMT' |
Thu, 28 Aug 2014 12:28:30 GMT |
yyyy'-'MM'-'dd'T'HH':'mm':'ss |
2014-08-28T12:28:30 |
yyyy'-'MM'-'dd HH':'mm':'ss'Z' |
2014-08-28 12:28:30Z |
dd MMMM yyyy HH:mm:ss |
28 August 2014 12:28:30 |
dd MMMM yyyy H:mm:ss |
28 August 2014 12:28:30 |
dd MMMM yyyy hh:mm:ss tt |
28 August 2014 12:28:30 PM |
dd MMMM yyyy h:mm:ss tt |
28 August 2014 12:28:30 PM |
d MMMM yyyy HH:mm:ss |
28 August 2014 12:28:30 |
d MMMM yyyy H:mm:ss |
28 August 2014 12:28:30 |
d MMMM yyyy hh:mm:ss tt |
28 August 2014 12:28:30 PM |
d MMMM yyyy h:mm:ss tt |
28 August 2014 12:28:30 PM |
The current ward is defined to be the ward code for the current ward observation.
The next ward is defined to be the ward code for next ward in the patient’s journey. If the patient was discharged home from the current ward, then the next ward cell should be left blank.
The stay index is an optional column. It is defined as the position of the current ward observation in the patient’s whole inpatient journey. For example, if, during the same episode, the patient had previously stayed in two other wards before the current ward observation, then the stay index would be 3.