Virtually Priceless Thoughts

Several years ago I discovered Christopher Alexander’s work on Architectural Patterns and have been meaning to write about it here for some time — so here goes.

In “The Timeless Way of Building” and his other books, the author describes and illustrates universal solutions to architectural design problems in a way that allow for reuse and flexibility to be adapted to specific situations. Patterns were designed to allow communication between users / dwellers and the builders in a way that they could be a lingua franca. Alexander’s work has had an influence on software engineering, where patterns are commonly discussed. Alexander pushes the idea from patterns to a Pattern Language, that includes a complete set of options for the space. Knowing the patterns in the language allows you to speak completely. Several groups have reflected on the concept of patterns and adapted it to domains outside of physical architecture.

In Software engineering, the patterns are used for discussion more between developers than with users / clients. In usability and user interface design, patterns have been applied as well in multiple settings. Here, the sense of the lingua franca is back — showing users standard approaches in wireframes / sketches allows the client / user to be able speak with the designers on a more equal playing field. There has been some recent thoughts are Creativity Patterns from Merlin Mann and Productive Patterns, based on some of David Allen’s Getting Things Done approaches. These tend to be collections of patterns rather than the more ambitious languages.

I have been collecting “EMR Patterns” in a little black book — approaches to repeatable problems faced in the EMR or EHR. The NHS CUI program has developed many good solutions to address some of the challenges of the management / viewing / input of clinical data. Several EMR vendors have good solutions to address specific problems.

Patterns scope is quite varied – Alexander’s range from patterns for organizing large geographic regions to (#2. The Distribution of Towns) to quite specific (#252 Pools of Light). So, too, can EMR Patterns. Patterns could range, especially for the larger regional EHR tools, to address problems at many layers and aspects of care provision, care planning, organizational management, etc.

As a practitioner, I have been more focused on the aspects of point of care and point of reflection patterns.

Patterns, with sufficient evidence behind their usefulness, may well be a mechanism to quantify requirements such as “EMR is easy to use” “Consistent User interface” and “Displays information required to address common problems in a safe manner”. Ongoing development of evidence will need to come from review of current published literature and the exploration, through a variety of studies, including usability testing, outcomes measurements, etc.

With patterns at the right levels, users can also engage in discussions with their vendors / software developers — they can have a lingua franca to discuss issues such as “Refilling Prescriptions” “Processing Incoming Test Results,” etc. These patterns could provide benefit to those discussions and improve ongoing standardization of functions, reducing errors, need for retraining, etc.

A simple example EMR pattern is below:

Patient Banner

Problem Addressed

Safety and privacy issues of reviewing / accessing / documenting on the wrong patient chart. Documentation on the wrong chart / reviewing information on the wrong patient by accident can lead to significant clinical errors and adverse events.

Example

Solution Description

By displaying, clearly, at the same position on the screen key patient information that is required for positive identification, users are able to quickly identify the patient. This should be displayed on all screens and not be able to scroll off the screen.

Data elements should include: name, date of birth, gender and patient ID at a minimum. Picture would also be helpful, if supported. In the second layer of the banner, additional information can be made available, including address and contact information. The Patient banner can be used to support clinical safety issues in other ways. By displaying the presence of Allergies and Alerts, clinicians are made aware of these elements from any screen. Allergies, alerts, etc can be accessed from the panner by a simple click.

Rationale

Positive patient identification is a key requirement to the safe use of Clinical Information Systems. The Patient Banner supports identification and additional safety activities, such as check allergies and alerts.

Discussion

The NHS CUI project has done considerable work on the patient banner and their understandings have greatly influenced this pattern.

Related Patterns  

…

Related posts:

1. CIA Principle 5: Documentation Patterns “Documentation will be constructed from standardized building blocks or “patterns”...
2. CIA Principle 7: Preferred Approach to Interoperability “Across VIHA Regional Clinical Information Systems, clinical information must have...

Related posts brought to you by Yet Another Related Posts Plugin.