Set up PatientView in a new unit

You may be able to join PatientView now as a participating unit if either

If you are, you should usually contact the leaders for your specialty or our helpdesk. If not, you may want to consider becoming a partnerContact our central helpdesk if we can be of assistance.  Info about what can a Specialty Admin do (under the Admin and Technical menu).

What the new unit needs to do

Patient leaflets, and a staff leaflet, and publicity posters, are available (see contact info)

  • Permission from your local Caldicott Guardian and data protection officer. Read more about how PatientView meets Caldicott and data protection requirements.
    • It is always useful to point to our news pages and (if there’s a recent pdf, but they’ve been mostly online recently) newsletters to show the system in operation.
  • Technical requirements – if the electronic records system you are using has been interfaced elsewhere, the technical issues are likely to have been solved, so this bit can be easy, or you may need some work undertaken to work out how to do it (these are not usually very difficult tasks). See ‘Information for IT system suppliers’ below.
  • Practical implementation
    • You should localise the patient sign-up form
    • Who will be the local contacts for PatientView?
    • Will you implement secure messaging at first?
    • Do you want to create any separate local leaflets or info sheets?
    • Boxes of patient leaflets, and a staff leaflet, and publicity posters, are available from our helpdesk, and there may be examples below.


Are low.  They are composed of

  1. Locally incurred costs in generating the files to send from your electronic records systems to PatientView.  If this has already been solved in your centre that should be minimal. If it hasn’t yet been fixed in your centre, getting prioritisation from those in charge of IT has sometimes been the key barrier, not cost. Showing the immediate patient appreciation is a big help.
  2. ‘PatientView Central’ costs.  These are population-based and because shared across many centres are low for established specialties.

Patient registration and management are managed locally, but most centres have not required extra staff to do this. There is a reduction in enquiries as a result of implementation, and while this is difficult to measure as it is widely spread, PatientView is generally felt to provide substantial quality benefits without imposing an additional burden on staff overall.

Information for local IT system suppliers

There are a couple of ways to send data from your electronic records system. Our recommended approach for sending data is the PatientView secure REST API as it is considered the most modern and flexible method of data transmission. Full documentation with worked examples is available here. Please contact us if you have any queries on the documentation or to request your API Key and Group Code, which allows your integration component to start sending data.

Alternatively, if your patient records system has an existing XML-based link to PatientView, it may be possible to re-use this link. This may require input from the previous software vendor. Again, please contact us if you are considering taking this route.

Comments are closed.