Significant issues - Trust
I. Loss of Data
II. Incorrect reporting data for over 16months periods
III. Duplicate reporting incident
IV. Incident management and review team failed to review incident due to wrong
security group set-up
V. Reporting boundaries were incorrectly set-up with no knowledge of
programming parameters – broke the links & etc.
Issues resolved:
Diagnosed and resolved problems experienced by users in a timely manner, enabling
organisations to continue to report regularly and accurately.
Produced measurable increases in completeness and accuracy of data sent to the
NRLS
Designed and developed an CG Reporting Scorecard of key data quality standard
indicators which allowed monitoring reporting activity and prioritising of improvement
action and Security Group - ongoing
Collaborated with users and colleagues in order to identify ways of improving the
accuracy of monitoring patient safety & etc
Set up LRMS’s (Local risk management systems) providing advice for web based
reporting and ensuring accurate NRLS dataset code mapping - Ongoing
Further planned actions/proposals
Implementation of DatixWeb and training in its use; administration and configuration
of Datix and production of incident analysis reports. Audited the data input during 3
month pilot, formulating various solutions to problems identified
Projected Project Dates
1st
Phase
Datix report integration and programming configuration 10weeks’. Technical Service
to perform the system integration for database.
2nd
Phase
System Integration - Technical Services import reporting form into your CIM
database. Require minimum of 3 weeks of technical support to complete integration
3rd
Phase
System Configuration
System would be configured with requirements as regard the existing MRS
(Mandatory Reporting System). Databases will require additional review. (Maximum
of 4 weeks)
Notes
Datix Progress
Issues Identified Prior to joining trust
1. Poor reporting Standard
2. CIM incorrectly set-up with unrelated parameters
3. Mapping Errors
4. Inaccuracy of data sent to the NRLS
5. Data conflicts each other

Datix progress report

  • 1.
    Significant issues -Trust I. Loss of Data II. Incorrect reporting data for over 16months periods III. Duplicate reporting incident IV. Incident management and review team failed to review incident due to wrong security group set-up V. Reporting boundaries were incorrectly set-up with no knowledge of programming parameters – broke the links & etc. Issues resolved: Diagnosed and resolved problems experienced by users in a timely manner, enabling organisations to continue to report regularly and accurately. Produced measurable increases in completeness and accuracy of data sent to the NRLS Designed and developed an CG Reporting Scorecard of key data quality standard indicators which allowed monitoring reporting activity and prioritising of improvement action and Security Group - ongoing Collaborated with users and colleagues in order to identify ways of improving the accuracy of monitoring patient safety & etc Set up LRMS’s (Local risk management systems) providing advice for web based reporting and ensuring accurate NRLS dataset code mapping - Ongoing Further planned actions/proposals Implementation of DatixWeb and training in its use; administration and configuration of Datix and production of incident analysis reports. Audited the data input during 3 month pilot, formulating various solutions to problems identified Projected Project Dates 1st Phase Datix report integration and programming configuration 10weeks’. Technical Service to perform the system integration for database. 2nd Phase System Integration - Technical Services import reporting form into your CIM database. Require minimum of 3 weeks of technical support to complete integration 3rd Phase System Configuration System would be configured with requirements as regard the existing MRS (Mandatory Reporting System). Databases will require additional review. (Maximum of 4 weeks) Notes Datix Progress Issues Identified Prior to joining trust 1. Poor reporting Standard 2. CIM incorrectly set-up with unrelated parameters 3. Mapping Errors 4. Inaccuracy of data sent to the NRLS 5. Data conflicts each other