Wisdom from the Medical Journal of Oz: "Good HIT and bad HIT"
The recognition and partitioning of "good health IT" from "bad health IT" is now a mainstream meme. I have few comments about this new article; it reflects views frequently expressed here at Healthcare Renewal (indeed, one of its references is to this blog and this author):
Good HIT and bad HIT Jon D Patrick and Susan Ieraci Medical Journal of Australia 2013; 198 (4): 205.
First and foremost, do no harm. Second, do some good
One of the key issues for high-volume, high-risk workplaces like hospital emergency departments (EDs) is the struggle of conflicting aims. While hospital managers need information systems for data collection and storage, clinicians need efficient clinical documentation, data retrieval and order-entry systems that save time rather than steal it from the patient. The work of clinicians is aided by reliable data but impaired by the delays of real-time input, difficult system navigation, suboptimal presentation of information, and other problems in the user experience of health information technology (HIT).1
Mohan and colleagues’ study of the impact of an electronic medical record information system on ED performance had some limitations.2 It was retrospective and unable to control for all confounders, and therefore could only show a correlation with ED delays, not causation. However, the premise for the study delivers an important message — the work required to use the information system was perceived by the ED staff to directly conflict with time spent with patients.
Another study has shown that the same electronic medical record information system is perceived to have had a negative impact on the care of patients, as well as the productivity and morale of staff, in six EDs in New South Wales.3 The need to be hypervigilant about the accuracy of the information supplied by the electronic health record compounds an already stressful clinical environment, which in turn leads to resentment towards the technology and the people who have imposed it. This makes it “bad” HIT. Unless this is corrected, HIT efforts will overuse precious health care resources, will be unlikely to achieve claimed benefits for many years to come, and may actually cause harm.4,5
The large HIT corporations produce a type of technology that is best categorised as enterprise resource planning (ERP), which has its roots in the manufacturing industry. It is based on the idea that all processes within an organisation can be standardised, and that all processes of the same type should have their information modelled and processed in the same manner. If this high degree of standardisation were considered the best way to process and model information derived from clinical activity, then ERP would be a favoured technology to adopt, as has happened in many places.
However, there is an alternative, almost contradictory, perspective on the nature of clinical work: that it is non-deterministic and performed by a group of diverse staff working in an ecologically stable network of people that has to respond to diverse medical needs and diseases. The ecology model accommodates staff joining and leaving the process, with differing needs emerging at different times, so that the other individuals in the network have to adapt and modify their behaviour and improvise in an unpredictable manner. Amid all this variability is the ever-demanding imperative to improve the processes of care and attention to the patient, while also increasing staff productivity.6
Where the ERP model has been imposed in the clinical setting, staff may be coerced into an approach to their work that is at odds with established best practices. This could only be considered “good” HIT if it brought greater staff productivity with at least no loss (and, preferably, improvement) of patient safety and services and staff morale.
It is not enough just to identify problems: effort must be invested in transforming bad HIT into good HIT. This process must identify and optimise all the operative factors: human behaviour, system design, equipment performance, skills of the IT participants, and the operational policy framework.7 Good HIT should include clinician control of the interface design for content, dataflow and workflow. It includes the ability to change the system in real time, and it incorporates inbuilt data analytical capability, natural language processing, and native interoperability and clinical coding.8 Finally, there must be an appropriate opportunity to test systems for useability, effectiveness and suitability before their release.
There must be a move away from standardised processing models and towards improving the user experience in the clinical setting. Clinicians should not have to shoehorn their activity into predefined, externally imposed work processes that do not reflect actual activity and will not improve efficiency. A true patient-focused system aligns all its components towards the same aim. Like a good clinician, good HIT does no harm — to patients or staff.
American medical / HIT journals are perhaps a bit too beholden to industry to directly commit such health IT heresy. Thank the stars those Down Under are a bit more bold.