About PV2

A new version of PatientView, PV2, was released on 20th Jan 2015. See a simple guide on how to use it.

Why  |  FAQ for patients  |  FAQ for Admins  |  Old code

Why are you changing it?

  • Half of logins in early 2014 were from mobiles or tablets, but PV1 didn’t work well on mobile devices.
  • PatientView was written 10 years ago for a pilot project.  It had grown much bigger and it was proving a strain to get the old system to do all the things we wanted.  (more info at foot of page)
  • Some other specialties were joining us, and we needed to sort out how to show them best.
  • There are lots of exciting things that PatientView could do, but it has been difficult to implement them.
  • It would do all the things that existing PatientView did, plus more, and better.
  • We wanted to have increasing flexibility for people to enter things in via PatientView – symptoms, feedback to units, and so on.  This is easier in PV2
  • It will be possible to make apps so that data can be entered from mobiles.
  • More things will be possible too!

Why all this now?  We always imagined that the NHS would come up with national systems to do this for all specialties. But there still isn’t any strong sign of this. So we thought we should make it work better for modern devices, and be able to offer it to other users too, if they want it.  After all, many patients attend more than one specialty, in addition to their GP.

FAQs for Patients who used ‘old’ PatientView

What is ‘My Conditions’?  We already have some patients with Diabetes PatientView and IBD PatientView, and more specialties might join.  If you are in more than one, you will see them listed here, and be able to flip between them.  My conditions inludes

  • Information links about your treatment, diagnosis etc
  • Things like Transplant Status, Diabetes checks have moved to here

What’s happened to the old Results table?  It was horrible on mobile devices so we’re showing them in a slightly different way.  However if you loved the old big table view with lots of results, you can still see it. And now you can choose which items to show, and in what order. Instructions.

My GP can’t log in.  We’ve put a temporary solution in for GPs but are planning a much better method for GP logins early in the new year.  The old system wasn’t very suitable. You can of course share your login with GPs or anyone else if you choose to.

Security.  All the same measures as before are in place and PV2 has had the same testing by an external company that we have always given to PV1.

What are alerts?  New in PV2, you can choose to see your latest results as soon as you log in, and to receive email notifications when new results are available.  Set this up on the screen you see when you first log in. ‘Alert settings’.

See ‘How-To’ info for more things

FAQs for Admins

Some key differences …

GP logins have gone.  We’re working on a better system for managing them.  More to follow.

Radar registration has changed.  We’ll be in touch and post new info about just how, but essentially, continue to use renalradar.org and don’t worry about PatientView just now.

If you see patients listed as belonging to additional groups (e.g. Alport Syndrome, Membranous Nephropathy) you can ignore for now.

Messaging is switched on.  In PV2, messages to unit admins from patients come from secure messages rather than emails.  Secure messaging to any staff user can be enabled by checking the ‘Message Recipient’ option in the Staff User list. More about messaging.

Admin interface greatly improved. Immediate access to stats, lists of patients in trouble, requests to reset logins – better info with fewer alerting emails.

This website has extended guidance for admins, staff users, patients, as well as for organisations that could use PatientView.  For admins, see the unit admin guide.

Old code

The code base of PatientView was 10 years old, and the system was doing far more than originally intended. Integration with Radar exposed some of the difficulties that caused. Other threats from not rebuilding include difficulty in retaining good developers to work with it, even though we now have an exciting project that could expand beyond renal-only functionality.

Comments are closed