Imagine a nurse halfway through a busy shift who needs to check a protocol quickly.

The approved version is available on the hospital intranet, but finding it means logging in, navigating several folders and working out which of several similarly named documents is actually current. Instead, the nurse opens the team WhatsApp group and asks whether anyone has the protocol. Within seconds, a colleague sends a photo of a printed copy.

The immediate problem is solved. The less obvious problem is that the printout was created months ago, and nobody in the conversation can say with certainty whether it is still the current version.

Situations like this illustrate something that exists in many healthcare organisations, although it is rarely described as a system in its own right. Alongside the official environment of controlled protocols, SOPs, IFUs, training materials and policies, there is often a second layer of knowledge. It lives in group chats, shared drives, screenshots, old presentations, email threads and the memory of experienced colleagues.

Nobody deliberately designed this second system, yet people rely on it every day.

It is a shadow knowledge network.

---

Why informal knowledge networks emerge

It is easy to frame the use of unofficial channels as a compliance or discipline problem. In reality, that explanation is often too simple.

Healthcare professionals are usually not looking for ways to bypass governance. They are trying to answer a question and continue working. If the official route requires several steps, precise search terminology or knowledge of where a document is stored, while a colleague in a group chat can answer in seconds, the informal route has an obvious practical advantage.

A 2017 study at University Hospital Limerick provides a striking example. Among 41 interns surveyed, 97% reported routinely sending sensitive patient information through instant messaging, while 90% said they felt they could not provide their best clinical care without it. The sample was small and came from a single hospital, so the figures should not be treated as representative of healthcare as a whole. What they demonstrate, however, is the tension between formal requirements and the communication tools clinicians find useful in practice.

A much more recent study from Israel shows that this tension has not disappeared. In a 2026 survey of 283 hospital physicians and nurses, professional WhatsApp use was reported by virtually all respondents. The participants highlighted benefits such as faster communication and time savings, even though formal organisational support for this type of communication remained limited.

The important point is not that WhatsApp is somehow uniquely problematic. It is that informal systems succeed because they often remove friction from a task the official system has made difficult.

---

When knowledge leaves the controlled environment

Once employees start solving information-access problems outside the official system, knowledge begins to spread into places that were never designed to manage it.

Someone downloads a protocol so they can find it more easily next time. A presentation from a training session is stored locally. A colleague takes a screenshot of a useful table. Another person forwards a PDF into a group chat. Someone creates a shared folder containing the documents the team uses most often.

Initially, these workarounds can seem harmless or even efficient. People find what they need faster, and the organisation continues to function without anyone having to redesign the underlying process.

The difficulty appears later. A locally saved document is no longer necessarily connected to the system that controls its lifecycle. When the official protocol moves from version three to version four, the copy stored on somebody’s laptop does not update itself. A screenshot taken six months earlier does not suddenly announce that the underlying guidance has changed, and a PDF buried in an old conversation does not know that it has been superseded.

This is what makes outdated knowledge particularly difficult to manage: it often continues to look completely legitimate.

The file may still carry the organisation’s logo. The formatting is familiar. The title appears correct. Unless somebody actively checks the source and version, there may be nothing in the document itself that signals that it should no longer be used.

---

The shadow network is bigger than WhatsApp

Messaging applications tend to attract attention because they make informal communication highly visible, but the wider problem is not about one particular application.

A shadow knowledge network can consist of a shared folder containing files with names such as “Protocol_FINAL_v3”, a training deck saved two years ago, screenshots from previous guidance, email attachments that keep being forwarded, or documents that were originally downloaded from an approved source but are now circulating independently of it.

Sometimes the most important node in the network is not a file at all. It is a person.

Most teams have somebody who has gradually become the person everyone asks when information is difficult to find. It may be an experienced nurse, a senior resident, a practice manager or a product specialist who knows where documents are located, remembers why a process changed and can usually point colleagues in the right direction.

That expertise is valuable, but heavy dependence on one individual also reveals something about the surrounding system. If the same person repeatedly receives questions such as “Which protocol applies here?”, “Where is the latest training deck?” or “Is this still the current version?”, the organisation has created an informal search function built around a human being.

The work involved is easy to overlook because each interruption appears small. Across a department or organisation, however, those interruptions accumulate. More importantly, the answer given to one person often remains trapped in that conversation. When the same question appears again two weeks later, somebody has to ask again.

The knowledge existed.

The problem was retrieving it.

---

Privacy is only one part of the risk

The most obvious concern associated with informal healthcare communication is patient information, and the research gives good reason to take that seriously. In the 2026 Israeli study, 77.3% of physicians and 58.9% of nurses reported sharing identifiable patient information through WhatsApp. Respondents also reported sharing items such as patient identification stickers and laboratory results.

These findings make privacy and data protection an important part of the discussion. They are not, however, the only issue created by a shadow knowledge network.

A message can be transmitted securely and still contain outdated information. A device can be protected and still hold an obsolete protocol. An encrypted conversation can contain a superseded IFU.

This distinction matters because information security and knowledge integrity address different questions. Security is concerned with who can access information and how that information is protected. Knowledge integrity is concerned with whether the information being accessed is still accurate, current and approved.

---

Why banning the workaround rarely solves the underlying problem

When leaders recognise the risks associated with informal systems, the natural response is often to restrict them. In some situations that may be necessary, particularly when patient data or regulated information is involved. But restricting a channel does not automatically remove the need that created it.

If staff previously used a group chat because it gave them an answer in seconds, replacing it with a process that takes several minutes does not eliminate the underlying workflow problem. It changes the rule without necessarily changing the experience.

This helps explain why informal knowledge networks are so persistent. If one workaround disappears while the original friction remains, another workaround can easily take its place. The team may move from WhatsApp to another messaging application, from messaging to a shared drive, or from a shared drive back to asking the same experienced colleague every time.

The technology changes, but the behaviour remains remarkably consistent.

For leaders, that makes informal behaviour useful as a signal. A frequently shared local copy may indicate that the official document is difficult to retrieve. Repeated screenshots may suggest that information is hard to access again once it has been found. A colleague receiving the same questions over and over may point to a search or discoverability problem. A folder full of duplicate documents may expose uncertainty about where the authoritative version lives.

Seen this way, the shadow knowledge network is not only a risk to be controlled. It is also evidence about where the formal knowledge environment is failing its users.

---

The problem extends beyond hospitals

The exact form of the shadow network varies between healthcare settings, but the underlying behaviour is similar.

In a residency programme, residents may exchange protocols, teaching materials and practical advice through a group chat because it is the easiest place to get an immediate response. In MedTech, a field specialist may save a local copy of an IFU or training document because accessing the controlled version repeatedly is inconvenient. In pharmaceutical medical affairs, a small number of experienced colleagues may become the informal source of truth for questions that are difficult to resolve through existing systems.

The same pattern can appear in much smaller organisations. A private practice may rely on an SOP that has lived in the same shared folder for years, even though nobody is entirely sure when it was last reviewed. A practice manager may become the person who remembers every process simply because the information was never captured in a way that made it easy for somebody else to find.

The scale changes.

The underlying knowledge problem does not.

---

What the workarounds are telling you

A useful first step is not to ask employees whether they are following the official knowledge process. That question almost guarantees a predictable answer. Instead, it is more revealing to understand how they actually find information when time matters.

Questions like these expose the real information pathways inside an organisation. They also make it possible to distinguish between a training problem and a system problem. If one person does not know where information is stored, additional training may help. If an entire team has quietly built a parallel method for finding the same information, the explanation probably goes deeper.

This is why treating the shadow network purely as a discipline problem misses an important part of the picture.

Every request for a protocol in a group chat is also a search that the official environment did not answer quickly enough. Every duplicate file exists because somebody thought keeping another copy would make future access easier. Every colleague who becomes the person “who always knows” is compensating for knowledge that is difficult to retrieve through formal channels.

The workaround is telling you where the friction is.

---

The real question is why the second system exists

The goal should not be to make informal communication the source of clinical truth. Controlled information exists for good reasons, particularly in environments where accuracy, traceability and regulatory compliance matter.

But an official source cannot rely on authority alone if people struggle to use it in practice.

When the approved system is trusted but difficult to navigate, while the unofficial system is fast and familiar but difficult to govern, employees are forced into a trade-off that should not exist in the first place.

That is the more useful way to interpret a shadow knowledge network. Its existence does not simply show that employees are using the wrong tools. It shows that somewhere between creating knowledge and applying it, the organisation has introduced enough friction for people to start building their own route around it.

The most useful question, therefore, is not simply:

It is:

---

Frequently asked questions

What is a shadow knowledge network in healthcare?

A shadow knowledge network is the informal layer of information that grows alongside an organisation’s controlled documents: group chats, shared folders, screenshots, forwarded PDFs, old training decks and the memory of experienced colleagues. Nobody designs it, but staff rely on it daily because it answers questions faster than the official system. Its weakness is that nothing in it is connected to the lifecycle that keeps protocols, SOPs and IFUs current.

Why do healthcare staff use WhatsApp and shared drives for clinical information?

Usually because the official route has friction: logging in, navigating folders, knowing the right search terms or working out which of several similar documents is current. A colleague in a group chat can answer in seconds. Surveys from Ireland (2017) and Israel (2026) both found near-universal professional messaging use among clinicians, who cited speed and time savings as the main benefits.

Is banning WhatsApp in hospitals the solution?

Restricting a channel can be necessary, particularly where patient data or regulated information is involved, but it rarely removes the need that created the workaround. If the official system still takes several minutes to answer a question the chat answered in seconds, the behaviour moves to another messaging app, a shared drive or the experienced colleague everyone asks. The more durable fix is to reduce the friction in the approved route.

What is the difference between information security and knowledge integrity?

Information security asks who can access information and how it is protected: encryption, device security, access rights. Knowledge integrity asks whether the information being accessed is still accurate, current and approved. A message can be transmitted securely and still contain a superseded protocol. Healthcare organisations need to manage both.