Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Root cause report documents

Check whether a documented system is in place, which covers the reporting, investigation, root cause analysis and corrective actions taken. [Pg.197]

Thorough documentation of medication errors provides information about the severity of the error as it relates to the effeet on the patient, the product(s) involved, the competence of staff handling the produet or proeessing the order, any contributing factors that may predispose a product to misuse, and the suspected root cause of the error. USP adds certain codes to MER Program data in order to characterize the error as it was reported. These codes include the type of error and the possible eause(s) of error. The following list shows some of the produet eharaeteristics that have been recorded over 9 years to have caused or eontributed to a medication error. [Pg.156]

If the root cause is assignable, corrective action needs to be taken and documented. If three consecutive runs over action levels occur, a problem analysis corrective action report (PACAR) must be issued. [Pg.316]

Information from production loss events is stored in the databases (as shown in Fig. 2). Root causes of failures and near misses are documented in offshore databases in the form of reports that include a summary of actual event(s), field observations, corrective actions and recommendations. These reports include documentation such as alarm logs, summary of personnel interviews/ observations, process diagrams and pictures etc. [Pg.116]

The accident analysis report determines and documents the root causes of accidents associated with the end product and includes new hazards, hazards inadequately controlled or analyzed, and new baseline information identified by the accident analysis in the system safety effort. [Pg.84]

A document containing the information and facts about an individual incident put in chronological order to provide a complete picture as to what happened. The report is useful for the investigation to help establish the root cause of the incident. [Pg.21]

Safety, patient safety, sentinel event, medical accident, near miss, good catch, Office of Patient Safety, JCAHO, focused event analysis, disclosure, peer review, confidentiality, maltreatment of minors, root cause analysis, patient safety report, accident, documentation... [Pg.294]

It is essential that all incidents are reported promptly, and in detail—even those that have only minor consequences or that are first aid cases or that are near misses. In the United States, incidents that meet the OSHA guidelines for recordability must also be documented and reported. (The topics of Incident Investigation and Root Cause Analysis are discussed in Process Risk and Reliability Management). [Pg.100]

Once the near miss has been reported, it is the supervisor s responsibility to evaluate the severity and probability of the loss. Near misses with a medium-to-extreme potential severity or a medium-to-extreme likely recurrence are required to be investigated by the supervisor. As part of the investigation, the supervisor shall identify the root/hasic causes of the unsafe act or condition, and then implement corrections to prevent recurrence. The near miss program includes a standardized investigation form that aids the supervisor in the investigation and documentation of the near miss. [Pg.146]


See other pages where Root cause report documents is mentioned: [Pg.147]    [Pg.272]    [Pg.222]    [Pg.451]    [Pg.2243]    [Pg.1875]    [Pg.128]    [Pg.282]    [Pg.337]    [Pg.146]    [Pg.291]    [Pg.432]    [Pg.139]    [Pg.118]    [Pg.247]    [Pg.107]    [Pg.174]    [Pg.472]    [Pg.368]    [Pg.17]    [Pg.466]    [Pg.328]    [Pg.27]    [Pg.228]    [Pg.235]    [Pg.263]    [Pg.263]    [Pg.121]    [Pg.464]    [Pg.26]   
See also in sourсe #XX -- [ Pg.26 ]




SEARCH



Report documents

Report documents Documentation

Root cause

© 2024 chempedia.info