Amendment History:
Version Date Amendment History
Forecast Changes:
Anticipated Change When
Reviewers: This document must be reviewed by the following:
Name Signature Title / Responsibility Date Version
Approvals: This document must be approved by the following:
Name Title / Responsibility Date Version
Distribution: As Reviewers and Approvers, above. Document Status: This is a controlled document. Related Documents: These documents will provide additional information.
Contents:
1. Screen 1 - SPECIALTY NAME main screen 2. Screen 2 3. Drill-down sample report 5. Gauge definitions 6. Non-Functional Requirements 7. Reports Requirements 8. Data sources 9. User Security Groups 10. Group label help text content and links NB. This requirement specification should be read in conjunction with the SPECIALTY Feasibility Report issued following workshop 2
Screen 1: - top level
Screen 2:
Sample report Report style
COTE DASHBOARD - GAUGE DEFINITIONS (from workshop requirements document)
MetricID ScreenID GaugeID Sub-gauge ID Drill down to Drillscreen (S) / down Metric report (R): target ID
Data item - See note 1 below regarding definition of data timespans
Number / percentage
Display type
Sub-display type
DataSourceID
Frequency
Data Processing Requirements e.g. Weighting algorithm
Data Obtained (Yes/No)
Notes
Non-Functional Requirments: Introduction Requirements
ID Non-functional Category Local Requirement Description
Data Feeds Anonymisation Pseudonymisation Disaster Recovery Availability Availability Performance Volumes Volumes Volumes Supported Environment & Licensing Accessibility/Usability Reference and Meta Data Security Error Handling Audit Data Retention and ILM Training Documentation Environments Online Help Multiple Organisations
SOR Ref
Notes
SPECIALTY DASHBOARD - REPORT DEFINITIONS
MetricID ReportID Drill-down Metric GaugeID Display type
Fields and description
Notes
DataSourceID
Area of work
Source data system
Load Area
List of Data Sources and the Metrics supported: If incremental data feed is specified then details of an initial data load and the spec for this must also be documented if required. If no need then this should be explicitly documented. For consistency all weekly updates will be processed on the same day.
DataSourceID 1.1 1.2
Area of work Flowsheet Warehouse (iCM) - Falls Flowsheet Warehouse (iCM) - MUST
Source data system iCM iCM
Filename
RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT
1.3 2 3 4 5 6 7 8.1 8.2
Flowsheet Warehouse (iCM) - Waterlow Prescribing Delayed Discharges
iCM Local Database (populated from Ascribe) Local database
Ward Transactions (Admissions, Transfers, Local warehouse Discharges) Specialty / Treatment Function Data DNAR Cancer Diagnoses Referrals (MDT) Referrals (Palliative Care) Local warehouse iCM Local database - partly fed by iCM flow sheet iCM iCM Orders
RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT
9 10
Discharge Prescribing PMI
iCM iCM
RM3000_YYYYMMDDHHMM_COTE _CLINICAL_EVENTS.TXT RM3000_YYYYMMDDHHMM_PMI_ COTE.TXT tbc
11
Frail Patient Subset
iCM - tbc
Format
Pipe delimited text file Pipe delimited text file
Data Load Mechanism Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job
Detail
Anonymisation or Pseudonymisation
Incremental or Full
Falls
None
Incremental Incremental
Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file Pipe delimited text file
Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job Scheduled load via MSBI Master Load Job
MUST - referenced in None relation to 'frail patient' subset - brought through if we are to derive frailty. Details tbc. Waterlow None
Pharmacy prescribing transactions Local database Transitioned to local warehouse Local warehouse iCM feed None
Incremental Incremental Incremental Incremental Incremental Incremental Incremental Incremental Incremental
None None None None None None None
Pipe delimited text file Pipe delimited text file Pipe delimited text file
Scheduled load via MSBI Master None Load Job Scheduled load via MSBI Master Required to support None Load Job consistent patient level drill down. Scheduled load via MSBI Master Details to be confirmed None Load Job
Incremental Incremental
Incremental
Initial load for go-live number of days data
Frequency
Target load time
Weekly Weekly
<10 mins <10 mins
Weekly Weekly Weekly Weekly Weekly Weekly Weekly Weekly Weekly
<10 mins <10 mins <10 mins <10 mins <10 mins <10 mins <10 mins <10 mins <10 mins
Weekly Weekly
<10 mins <10 mins
Weekly
<10 mins
User Security Groups:
ID Name Active Directory group / account Comments
Start Page
Web Part Group
Help Page
Help Page Text