Download as xls, pdf, or txt
Download as xls, pdf, or txt
You are on page 1of 29

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)
Drill down to Drill-
MetricID ScreenID GaugeID Sub-gauge ID screen (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
Data Processing
Requirements e.g.
Frequency Data Obtained (Yes/No)
Weighting
algorithm
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
Drill-down
MetricID ReportID GaugeID Metric 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 Area of work Source data system Filename


1.1 Flowsheet Warehouse (iCM) - Falls iCM RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
1.2 Flowsheet Warehouse (iCM) - MUST iCM RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT

1.3 Flowsheet Warehouse (iCM) - Waterlow iCM RM3000_YYYYMMDDHHMM_COT


E_CLINICAL_EVENTS.TXT
2 Prescribing Local Database (populated from Ascribe) RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
3 Delayed Discharges Local database RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
4 Ward Transactions (Admissions, Transfers, Local warehouse RM3000_YYYYMMDDHHMM_COT
Discharges) E_CLINICAL_EVENTS.TXT
5 Specialty / Treatment Function Data Local warehouse RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
6 DNAR iCM RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
7 Cancer Diagnoses Local database - partly fed by iCM flow RM3000_YYYYMMDDHHMM_COT
sheet E_CLINICAL_EVENTS.TXT
8.1 Referrals (MDT) iCM RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
8.2 Referrals (Palliative Care) iCM Orders RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
9 Discharge Prescribing iCM RM3000_YYYYMMDDHHMM_COT
E_CLINICAL_EVENTS.TXT
10 PMI iCM RM3000_YYYYMMDDHHMM_PMI_
COTE.TXT

11 Frail Patient Subset iCM - tbc tbc


Format Data Load Mechanism Detail Anonymisation or Pseudonymisation Incremental or Full
Pipe delimited Scheduled load via MSBI Falls None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI MUST - referenced in None Incremental
text file Master Load Job relation to 'frail patient'
subset - brought
through if we are to
derive frailty. Details
tbc.

Pipe delimited Scheduled load via MSBI Waterlow None Incremental


text file Master Load Job
Pipe delimited Scheduled load via MSBI Pharmacy prescribing None Incremental
text file Master Load Job transactions
Pipe delimited Scheduled load via MSBI Local database None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI Transitioned to local None Incremental
text file Master Load Job warehouse
Pipe delimited Scheduled load via MSBI Local warehouse None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI iCM feed None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI None Incremental
text file Master Load Job
Pipe delimited Scheduled load via MSBI Required to support None Incremental
text file Master Load Job consistent patient level
drill down.

Pipe delimited Scheduled load via MSBI Details to be confirmed None Incremental
text file Master Load Job
Initial load for go-live -
number of days data Frequency Target load time
Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins

Weekly <10 mins


Weekly <10 mins

Weekly <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

You might also like