In total, sixty-one interviews were conducted (see Table 1), and thirty-seven meetings were observed (Table 2).
Table 1
Number of interview participants by profession
|
Nurse
|
Doctor
|
Safety Manager
|
AHP
|
Pharmacist
|
Administrator
|
Total
|
Acute Care
|
11
|
11
|
1
|
3
|
3
|
4
|
33
|
Mental Health
|
11
|
5
|
1
|
6
|
1
|
4
|
28
|
(AHP: Allied Health Professionals, which include medical technologist, physiotherapist.) |
Table 2
Number and type of meeting observed
|
Type of meeting
|
|
Total observations
|
Hospital-wide committee
|
Nursing-led safety meeting
|
Doctor-led meeting
|
Risk management meeting
|
|
|
Monthly
|
Monthly
|
Weekly
|
Monthly
|
Acute Care
|
20
|
4
|
3
|
13
|
0
|
Mental Health
|
17
|
4
|
0
|
9
|
4
|
This remainder of this section presents the synthesis of our results based on the four key themes in addressing the three objectives of the study: organizational resources for handling incident data (3.1.); perceived effectiveness of IRL systems (3.2.); corrective measures and systems approach in team discussions (3.3.); and factors shaping the management of IRL systems (3.4.). The first two themes were supported primarily by the interview data and the documents, while the second two themes required both interviews and observation data. In particular, with regard to the factors affecting how incident data are discussed in situ, the analysis of our data resulted in the discovery of four sub-themes. These were: professional boundaries and gendered dimension (3.4.1.); dealing with psychological burden (3.4.2.); leadership and educational approach (3.4.3.); and compatibility of patient safety with patient-centered care (3.4.4.). The Japanese data quoted below were translated by the lead author.
Organizational resources for handling incident data
The Patient Safety Office (PSO) consists of the director who is a medical doctor / senior consultant, and the Safety Manager (registered nurse, seconded to PSO), backed up by several administrators. The size of the patient safety office team was similar in the two participating hospitals. In the interviews, both Patient Safety Managers (AC and MH) referred to the limited manpower available to them for handling the great amount of data. In the Japanese acute care hospital, there was only one registered nurse, seconded to the PSO, who acted as a full-time Safety Manager. The Patient Safety Manager in Japan works directly under the Chief Executive, and may not necessarily return to their original nursing post. The Patient Safety Manager directly accesses the database, and each morning reviews incidents which occurred during the previous night, and checks the seriousness of each case.
While the IRL system can be used as an organizational tool to raise the issue of underfunding and capacity limitations, the Patient Safety Managers are trying to manage themselves within existing constraints.
“Actually, if you share it with another person and share what you do, I think that it will achieve more, but since the capacity is fixed, for example, though I did a Root Cause Analysis recently, I have not got around to summarizing it yet, as I have other things to do (…)” (Patient Safety Manager, AC)
The Patient Safety Managers’ heavy workload was also confirmed by our observations. However, unlike in the English case, the IRL system is not used as a mechanism for highlighting the issue of limited organizational resources.
Perceived effectiveness of IRL systems and risk perceptions
The interview data show that only three out of 61 participants did not find much value in using the IRL system for safety improvement. Thirteen members of staff were unsure, while 35 were positive, and a further 10 were positive with some reservations. Therefore, the majority of the participants perceived the IRL system as having a positive impact on their practice.
On the one hand, positive views expressed by interviewees stressed the importance of learning from one’s own and colleagues’ mistakes, and creating a forum for information sharing, team-building and goal-setting. These answers reflected uniformity of rule enforcement and strong norms within the two hospitals. On the other hand, negative opinions, three of which came from medical doctors, focused on the absence of a direct causal relationship between reporting activities and the betterment of clinical outcomes. However, a senior nurse in AC pointed out the usefulness of the incident data in identifying the patterns and spikes of recurring adverse events (e.g. medication errors, patient falls), which can lead to the development of preventive measures (e.g. increase in vigilance and workforce numbers during nightshifts). This indicates that some frontline staff are using the IRL system as a prospective, as opposed to retrospective, risk analysis tool (albeit haphazardly and informally within one’s own team on the ward).
Corrective measures and systems approach in team discussions
When it comes to deciding on corrective measures and checking the effectiveness of those measures, decentralized decision-making in a local team becomes clear.
“Measures are not coming out of the PSO, but rather, staff on the wards are often asked to come up with their own measures (…) And then it’s like, we at the bottom rank don't know what actually happened and was implemented.” (Senior doctor, AC)
“We created our own internal incident discussion mechanism in the pharmacy department only, and each individual writes a monthly report about cases based on his/her observation, using double checking, and proposes countermeasures, etc.” (Pharmacist, MH)
These concrete examples demonstrated that while corrective actions take place based on the use of incident data, they accompany a strong sense of identity or community, be it within a professional group or a ward-level local team.
The observation data show that generally, the meetings in both AC and MH served as a forum for sharing the information and reporting what happened, what was done and what was going to happen. Arguments and discussions were rare. In meetings in AC, the content of the incidents was explained in detail, and the cause was also mentioned at all the meetings except the hospital-wide committee. Concerning the analyses of the causal factors for the reported cases, not much was said or discussed. At the doctor-led meetings, any difference in opinion about possible causes was highlighted, although infrequently. The allocated time for these meetings was also limited. At the nursing-led safety meetings, collective learning and the exchange of practice-related information were emphasized among nurses representing different wards and specialties.
In AC, the formality of all meetings was the key feature, and the Patient Safety Manager organized and coordinated them. On the other hand, at doctor-led meetings in MH, there were cases where a discussion was held around a small table with the Clinical Director, in a much more informal manner. In this meeting, the causal factors of incidents and near-misses were mentioned, and the Root Cause Analysis (RCA) was often stated as one method of analysis. At a unit-level meeting, consideration was given to the system as a whole, although this did not happen at the hospital-wide meeting. Table 3 provides illustrative examples of the framework’s four dimensions (exploration of possible causes; consideration of systems problems; critiquing; and seeking further information).
Table 3
Illustrative examples: discussion of possible causes and the use of systems approach
|
Acute Care
|
Mental Health
|
Exploration of possible causes
|
Vascular injury due to catheterization: brief exchange of viewpoints regarding complications or catheter manipulation.
|
Missed information around food allergy: lack of communication between the nutrition department and the ward.
|
Consideration of systems problems
|
Cerebral infarction after Coronary Angiography (CAG): unclear lines of responsibility in the process of obtaining informed consent and describing the risk of complication deriving from CAG.
|
Patient’s unplanned entry to electroconvulsive therapy: miscommunication between different units
|
Critiquing of hypothesized causes
|
Very little discussion, with some exceptions
|
Not observed.
|
Seeking further information about the incident
|
Not much discussion, apart from questions as to subsequent actions made by a doctor involved in the case, and the relevant electronic medical records.
|
Follow-up information requested for cases where the information about how incidents occurred was not complete.
|
Regarding corrective actions, although the participants in both AC and MH explored a range of possible countermeasures, there was no indication that they critiqued potential solutions or considered the systems impact of potential actions. Problems spanning departmental boundaries were not evidently addressed either. At the nurse-led meetings in AC, each representative from wards and departments discussed a communication strategy. However, the issue of cross-professional communications was never raised. No further information or existing data were sought from other regulatory bodies. As the interview data show, professional groups (e.g. nurses, pharmacists, medical technologists) refer to their respective academic societies’ information sources.
Factors shaping the management of IRL systems
Professional boundaries and gendered dimension
Difficulties around co-ordination, spanning various professional groups and organizational units, were raised by several frontline staff. There was a clear demarcation between professional groups in the two hospitals.
“When problems about medical equipment are reported by a nurse, it is only when the patient is actually harmed. Preventive measures can only be provided if we find the problems ourselves before that report arrives. Even if the nurse wrote a near-miss report, it will only be dealt with at ward level and will not come up to us. These issues need to be sorted out”. (Medical technologist, AC)
There was also a comment made about the dominant role of the nursing profession in patient safety, which reflects cultural and gendered aspects within medical professions in Japan.
“Basically, the largest professional group among us, clinical staff, is nurses, and if nurses lead and do patient safety thoroughly, just like a mother-child relationship, a nurse like a mother can tell off a doctor like a child, saying ‘no, doctor, please do it this way’. I think that’d be the best way." (Senior doctor, AC)
Professional boundaries were also accentuated by the gender dimension between (mostly male) doctors and (mostly female) nurses. Among the interviewees, all the nurses in both AC and MH are female, and doctors male, with the exception that the Director of the PSO (consultant doctor) and one junior doctor in AC, and the Medical Director of MH, are female. A professional division of labor can be influenced by these gendered occupational assumptions.
Dealing with psychological burden of reporting incidents
A culture of blame was not identified in either organization, and under-reporting was not raised as a major issue. However, junior clinicians (junior doctors and nurses) expressed higher levels of sensitivity with regard to reporting being equated with admitting mistakes.
“It might be a little embarrassing to hear your incident report being discussed in a forum. For example, people must be thinking ‘Wow, he's making such an error still into his second year!’" (Junior doctor, AC)
On the other hand, a few of the staff stated that the IRL system is designed to protect them as well as patients.
“Rather, I report when something happens, and this I do also for the purpose of protecting myself.” (Junior doctor, AC)
Leadership and educational approach
Connected to the previous point, several senior staff in leadership roles showed a duty of care towards junior clinicians.
“I think experience matters…I tell my current junior staff ‘I used to wonder why I made that error, I had to write my name, like a great criminal investigation, I had to report, I felt like a criminal, I hated it. You may feel like that now when you report, but this will become your own learning and help you, so if you have an incident, you can make it your own strength.’” (Senior nurse, AC)
“It is not established as a system as such, but it is a human fortress. As the trainees spend more time with patients than I do (…) I do not rush and listen to patients' complaints in the first instance, but send the trainees to listen. If they come back with the message that the patient requested the person in charge, then I will go and take the responsibility… it is a multi-layered, problem-solving (training) system.” (Senior doctor, AC)
Compatibility of patient safety with patient-centered care
The frontline staff, particularly in MH, expressed ambivalence towards certain remedial actions (e.g. new tick-box forms), that would take up their resources.
“There were several times when I felt like making a manual would become the end in itself (…) so I feel there is a little bit of danger that we could end up making a manual for more manuals … protocolization of care.” (Doctor, MH)
There was also a reference to the fact that learning from patient safety incident data is concentrated in cases reported from facility-based inpatient care, which reflects a mainstream model of delivering mental health care in Japan.
“After all, it will be more useful thinking about medical safety if we can do home visits and such like in the future at our own discretion, rather than being stuck in a hospital environment (…) I don't think it is necessary to be excessively nervous about patient safety events (in the hospital), and it would be good to see a step being taken towards home visits or medical care in the community (...).” (Senior doctor, MH)