Renal PatientView

Sep 2008

Neil Turner

Renal PatientView

www.renalpatientview.org

Renal PatientView

RIXG

Sample Proton screens

The worldNHSnet

Renal server(e.g. Proton)

Webserver

Satellite unit

Other hospitals

Aug 2008

8000 patients

33 units

Renal PatientView

Design principles

Internet: view anywhere Open source engineering Specification by patients, renal IT staff and

clinicians All would share same view Implementation to require minimal extra work

in units Simple to use for patients Opt in

Treatment choices

Renal PatientView

Patient evaluation

In essence – extremely positive (details available)

Tests are the things looked at most frequently

40% of patients have shared passwords with others and we know some are dependent on others for access

Renal PatientView

Formal evaluation

Barriers to use– 64% non-users didn’t know of RPV – Gender profile same– 45% of non-users over 66yrs cf 10.5%– Lack of computer/internet access the

second most common stated reason

Renal PatientView

Impact on unit

Not leading to extra consultation time Or to increased patient anxiety Anecdotes of info availability helping

patients beyond simple confidence Some improved compliance? Effect on data quality – direct and indirect IT people speak to patients more

Renal PatientView

Hidden cost?

RPV admin’s extra time 6 mins per enrolment Lost passwords More corrections (a good thing though)

Versus savings Fewer phone calls about results Data quality Better compliance with treatment?

Renal PatientView

What next?

• More units

• More items

• Graphics

• Availability through other portals

Renal PatientView

What next?

• Patients discuss

• Patients enter data

• Patients send feedback to unit, clinician

• Primary care integration

• Your ideas

Renal PatientView

Beach scene

Further info

neil.turner@ed.ac.ukwww.renal.org/rixg/users.html

[Caption competition]

neil.turner@ed.ac.uk

www.edren.org