Protocols - Vital to Hospital Care (Case Study)
Skip to end of metadata Go to start of metadata|
|
October 2010 |
|
||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
UZ Leuven is a University Hospital in Leuven, Belgium. Since early 2009 they have used the Ad hoc Workflows for Confluence to manage some 4,500 documents across 9 spaces. The documents they deal with are a critical part of hospital's effectiveness, covering protocols to manage health issues.
Where Wikis Would Expose to Risk
Normally a wiki would not be suitable for protocol information, as these documents must be relied on and wikis normally permit anyone to make unchecked changes. From palliative care to gastrointestinal diseases, UZ Leuven's documents cover which procedures to follow for symptoms, diagnosis, contraindications, possible causes, treatment plans and more. A freeform wiki that didn't impose checks on content before that content was used by general staff would expose patients to undue risks.
UZ Leuven had considered many Document Management platforms before settling on Confluence with Ad hoc Workflows. The hospital has a deployment of SharePoint but Confluence was favoured for this task because of its low cost, ease of use and extensive linking capabilities.
Processes and Integration with External Applications
UZ Leuven's medical practitioners use a 4 step process of checks and approvals. Only after each change has been vetted by a peer and a supervisor can the change be seen by others. UZ Leuven have built custom functionality that injects external database data into per-page metadata: this allows control of workflow access levels to be governed by an external application.

UZ Leuven enjoy the functionality provided to date and were impressed that it helped them to gain JCI accreditation (ISO-like for Hospitals) in a short time frame.



