Managing and responding to reported events

Overview

This workshop provides instruction on how to respond to reported events, for example, incidents, feedback, repairs, non-conformances and suggestions for improvement.

Training level: Advanced

Participants: All LOGIQC Users who have 'Manager' or 'Approval Officer' status in the LOGIQC QMS. 

Duration: 60 minutes

Preparation

Related on-boarding requirement:

  • Reporting pathways in the LOGIQC QMS
  • Instructions for standard tasks

Pre-requisite training for this workshop:

Additional Information for Trainers

  • When scheduling this training session, participants should be advised of any pre-requisite training required prior to attending this learning session.
  • Trainer must verbally present the background and set the scene around the expected learning outcomes for this session.
  • Trainer to prepare for demonstrating key functionality of the LOGIQC QMS to participants.

Background

Reporting events in the LOGIQC QMS allows your organisation to:

  • Respond to adverse events in a timely manner
  • Delegate and track action that needs to be taken in response to an event, where applicable
  • Maintain records relating to action taken in managing an event
  • Give consideration to what action needs to be taken to avoid same or a similar event occurring again in the future 
  • Manage reporting requirements to external agencies, if required
  • Move to a paperless reporting environment

Expected Learning outcomes

On completion of this course participants will have an understanding of the scope and purpose of the incident, feedback, repairs and improvement registers and how to:

  • Request action to be taken in response to a reported event
  • Apply restricted access to a reported event - only applicable to an incident and feedback
  • Upload records related to managing an event
  • Assess the level of risk of the event using the Risk Wizard or where the Risk Module has been activated, link an event to an identified risk 
  • Request additional action beyond the first response, and or change the instructions of what action is to be taken
  • Approve action that has been taken and close the reported event
  • Generate a related improvement in the system to avoid or reduce the same or a similar event occurring again in the future
  • Read the system event history to understand how the event has been managed
  • Sort, filter and search the Incident, Feedback, Repairs and Improvement Registers
  • Generate trend reports on incident and feedback that have been closed in the past

Demonstration

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.