The same journal system can be experienced as a helpful tool by one professional group and as a daily struggle by another. The difference tells us something important about how documentation tools should be built.

Imagine two colleagues using the exact same journaling system. One finds it works fine – it supports their workflow, and documentation goes smoothly. The other experiences it as a source of daily friction, where each note requires too many clicks and too much customization to a setup that doesn't fit their way of working. The same tool, a completely different experience.

This is not a hypothetical scenario. The Directorate of Health's annual survey of healthcare personnel shows that satisfaction with electronic patient record systems varies significantly – not only between regions but also between professional groups using the same system. The difference is instructive, and it points to a point that is easily overlooked in the debate about artificial intelligence in healthcare: a documentation tool is never just technology. It is technology encountered by a specific profession's workflow, professional language, and everyday reality – and it is in that encounter that it is decided whether the tool is perceived as a help or a burden.

When the numbers show a gap between professional groups

The Norwegian Directorate of Health's survey on digitalization in health and care services maps how healthcare personnel experience their electronic health record (EHR) systems. One of the clearest findings is that satisfaction is not evenly distributed. Healthcare personnel in certain regions are far more often dissatisfied than the average, and within the same system, different professional groups report varying levels of satisfaction. Doctors and nurses using the same system may evaluate it differently.

It is important to interpret such a divergence correctly. It doesn't mean that one professional group is «wrong» or harder to satisfy than the other. It means they do different things. A doctor and a nurse document different parts of a patient's journey, have different needs for structure, and use the system at different times during a busy day. A setup that works well for one person's tasks might work less well for the other – without anything being «wrong» with the system itself.

We are not taking a position here on the discussion of individual systems or how they should be managed. That is a matter for those in charge. What we are looking for is the general lesson learned: Usability is not a characteristic of the system alone, but of how well it meets the individual profession's workflow.

Why «one system for all» is difficult

A large journal system must cover the entire spectrum of healthcare simultaneously: doctors, nurses, therapists, administrative staff, various departments, and specialties. This is a formidable task, and it's completely understandable that a system designed to encompass everything cannot be optimally tailored to each individual role. The more groups a tool is intended to serve, the more compromises it must make.

The consequence is familiar from many clinical settings: the note requires fields that are not relevant to your specific consultation, the structure follows a logic that better suits a different professional group, and the time that should have been spent with the patient is spent on navigation. We have previously written about what happens when Journal entries are being postponed and piling up throughout the workday. – and much of that shift is precisely about the tool not flowing with the workflow.

This is not an argument against shared systems. Shared infrastructure has obvious benefits for collaboration, patient safety, and information sharing. The point is that the more the responsibility for the documentation itself can be adapted to the individual profession, the less friction arises – and the more of the system's benefits are actually utilized.

The lesson for AI: adaptation, not standardization

This is where the real insight lies regarding how artificial intelligence should be incorporated into documentation. If an AI tool is built as a «one-size-fits-all» solution, it risks repeating exactly the same weakness that plagues large systems: it works well for some and poorly for others.

A tool like Medivox is built on the opposite principle. Instead of one fixed structure that everyone must adapt to, Do you build your own templates tailored to your profession and work method. A psychiatrist does not document like a nurse in home care, and a general practitioner does not document like a physiotherapist. Once the template is created for your profession, the threshold becomes low and friction minimal. The tool listens to the consultation and delivers a structured draft, but You own the journal and make the final assessment. Personal data is pseudonymized before it is processed further, and all data processing takes place at Norwegian data centers.

This is also why speech-to-text can be experienced so differently from the big systems. It doesn't layer itself on top of a workflow that's already grating – it starts with what you actually say in the consultation and shapes it into a template you've decided on yourself. We've seen how this plays out in practice among nurses taking over record-keeping in general practiceWhen the tool meets the task as it actually is, documentation becomes less of a burden.

Usability is a professional matter

It’s easy to think of user-friendliness as a matter of design—attractive screens and logical menus. But in healthcare, there’s more to it than that. When a tool doesn’t fit the workflow, it affects the time spent with the patient, the quality of documentation, and ultimately the work environment. We’ve previously described how Norwegian e-health is moving from pilot to everyday use, and one of the most important lessons from that journey is precisely that implementation succeeds when the tool is adapted to the user – not the other way around.

The gap between professional groups in satisfaction is therefore more than statistics. It is a reminder that there is no single universal «good» way to document, because there is no single universal way to work in the healthcare system. The technology that succeeds will be the one that allows each profession to recognize itself in the tool – and that allows the profession, not the system, to decide how the note should look.

Frequently Asked Questions

Why do doctors and nurses experience the same electronic health record system so differently?
Because they document different parts of the patient journey, they have different needs for structure and use the system in different ways. A setup that suits one group's tasks may be less suitable for another's – without anything being wrong with the system itself.

Does this mean that shared journaling systems are a bad idea?
No. Shared infrastructure has significant advantages for collaboration and patient safety. The point is that the documentation itself should be adaptable to each profession, so that friction is minimized.

How does an AI tool avoid the same weakness as large systems?
By allowing users to build their own templates tailored to their profession, instead of imposing a fixed structure. This way, the tool meets the workflow instead of disrupting it.

Will the AI tool take over professional judgment?
No. The tool provides a draft, but you own the journal and make the final judgment before anything is saved.

Use Medivox for free – Get started completely free

Wondering how a documentation tool can be customized to your professional group's workflow? Contact us - then we'll show you how to build templates for your subject.

Sources: