The Common UserInterface Project

Paul Frosdick, Senior Clinical Pharmacist, National Programme

for Information Technology

Apologies

Mike Bainbridge

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

Objectives and ContextTo deliver a 21st century health service through

efficient use of information technology

Modernisation of the NHS:•10 year programme initiated July 2000•Access / Choice•Health outcomes•Efficiency•Societal changes and demands•IT an underpinning enabler for the modernisation programme.

Objectives and Context

•Moving from a largely paper based NHS

•Information to be available electronically

anywhere in England

•Balance between nationally available

information and local application

•Remove duplication of records and effort

•Improve accuracy of records and treatment.

Providing ‘Safe Joined up’ care

• Increased mobility of ‘service users’• Increasing needs of care• Ageing population• Safety in practice across boundaries• Safety in transfer of care• Safety of clinical systems themselves

Providing Better Care.

Changes in focus• Patient centred

– Involving in decisions– Reducing paternalism

• Clarity of purpose– Systems– Behaviour

• Professional • Systems

• Safety built in to all systems as standard• Risk assessment of the systems and implementation• Providing appropriate interfaces to information.

The Five NPfIT Clusters (NPfIT’s geographic grouping of Strategic Health Authorities in England)

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

Common user interface ?

• Patient safety – recurring theme

• Maximise uptake

• Education and training– Not minimised – Effectively targeted and delivered.

Or another example

• Date format for display– 09-11-2004 - UK– 11-09-2004 – US – 11-NOV-2004 – Safe !

• Separator– / \ . or <SPACE> for display or data

input ?– Data storage is nothing to do with it.

‘Mother who died after junior doctor’s blunder;

Tragedy highlights lack of support for inexperienced staff’

Daily MailWednesday, February 4 2003

‘The Consultant Gynaecologist highlighted the widespread problem of junior staff being left to work unsupported in unfamiliar hospital departments’

The doctor had been working in the department ‘for only ten days’

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

The Service(NHS)

Common UI project

Knowledge

NPSA

Standards(ISB)

Assurance

ISVs

LSPs

Clinician Engagement Group and NPfIT Technology Office

Edu & Training

Integrated into the fabric

Only achieved with:• 1 terminology - SNOMED CT• 1 terminology server – Health Language• 1 drug database – dm+d - UK SNOMED

extensions• 1 drug decision support – First Data Bank

Europe• 1 Decision support framework – Map of

Medicine• 1 Knowledge source - National Electronic

Library for Health• All backed by a standards board• No exceptions !• Why not the interface ?

Guiding Principles

• A vision and a journey– There are no quick fixes

• Clinical excellence meets industry excellence

• User-centred design approach– Users involved in design, users don’t

do the design

• Define once, re-use everywhere

Clinical Applications

Information and Knowledge Resources

Non-Clinical Applications – email, word processing etc

The NHS UI

The Vision

• Enable the delivery of a consistent user experience across applications and devices, that– Is useful, usable and compelling to clinicians, thus

encouraging increased adoption of technology in all care settings

– Increases patient safety– Reduces the cost of adopting NPfIT systems, in

terms of end user training and support costs– Increases the productivity and effectiveness of

clinicians, enabling the process changes required to achieve the EWTD and service modernisation goals.

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

The Journey

• Definition of “the NHS UI”• Delivery of the NHS UI Design Guide

– Generic guidelines through to detailed UI layouts for specific areas

– Publish as NPfIT Standard– Available to all NHS software suppliers

• Develop toolkit of UI components– Easier & quicker for application developers to

conform to Design Guide

• Adoption by software application developers.

Defining the NHS User Interface

• Iterative approach, starting with observations and interviews with real users doing real work

• Draft designs– Paper wireframes– On-screen prototypes– User walkthroughs at each stage– Stakeholder reviews at each stage

• NPSA, NPfIT, NICE, clinical leads

Prototype

Evaluate

Design

• Iterate designs based on feedback• Further usability evaluations• Document in Design Guide• Review, sign off and issue as NPfIT

Standard.

Outline

• Introduction– Objectives and context

• Why a CUI

• Guiding principles

• Defining the CUI

• Possible deliverables

• Questions.

Draft Focus Areas for Design Guide and Toolkit

• Prescribing• Decision support• Test requests & results• Alerts & notifications• Find / identify patient• Patient record – view and add new• Care pathways• Discharge.

Sample Components

• Patient banner• Medication selector• Test selector• Test results viewer

– Tabular vs. graphs

• Lists – Patients, medications, tests, etc

• Scheduler– Medication administration, tests/exams etc

• Alerts/warnings.

Other Design Guide Topics

• Possible topics:– General design principles for health UIs– Navigation and task flow design– Standard information display formats

• E.g. dates, patient name, address, etc

– Designing for accessibility– Writing alerts and error messages– Help & other user assistance.

Using RSS to keep up to date…

NeLH knowledge search

Any Questions?