NHS Healthcare System Solutions

Simon Ambler.

Version: 1.0
Date: 8th November 2002

See associated requirements.

Introduction

Loosely based on a question from the 2002 examination paper for MC106 Software Engineering and Professional Practice.

Summary of Structured Solutions

• Database (S) A database system to hold patient records and other relevant information.
  • Central (S) A central database held at the Trust's HQs.
  • Distributed (S) Information storage is distributed across HQ and the clinics.
• PocketPC (S) Issue Careworkers with a Pocket PC device.
  • iPAQ (S) Use the Compaq iPAQ 3660.
  • Journada (S) Use the Hewlett Packard Journada 680.
  • GUI (S) Graphical user interface.
    • Questionnaires (S) Electronic forms for Health Surveys.
• Synchronization (S) Software and hardware required to synchronize mobile device against records at HQ.
  • Software (S) Software to keep track of items which have been modified.
    • ConflictResolution (S) Invoked when two careworkers submit different amendments to the same record.
  • Cradle (S) Docking cradles are supplied at each clinic.
    • Serial (S) Use a standard serial link.
    • USB (S) A USB link.
  • Phone (S) Communication between Pocket PC and HQ via a mobile phone.
    • InfraRed (S) Pocket PC connected to mobile phone via an infra-red link.
    • PhoneCable (S) Pocket PC connected to mobile phone via a suitable data cable.
    • Combined (S) Pocket PCs with an integral mobile phone.
• Survey (S) Software for preparing and running Health surveys.
  • Editor (S) Preparation and distribution of electronic questionnaire forms.
  • Analysis (S) Collection and statistical analysis of results.
    • BuyIn (S) Of-the-shelf statistics software.

Details and Impacts

• Database.Central (S) A central database held at the Trust's HQs.

  Holding all records in a central repository is likely to reduce the number of overall number of errors.

  Status: adopted

• PocketPC (S) Issue Careworkers with a Pocket PC device.

  Pocket PCs are relatively low cost and put the computing power of a PC in a handheld device.

  Requirement	Impact	Type	Justification
  CareWorker	-	achieves	-

• PocketPC.GUI (S) Graphical user interface.

  Data entry on a pocket PC is fiddly. In particular, handwriting recognition software is difficult to use quickly. The GUI should minimize the amount of input which is done through text boxes, by using menus, icons, checkboxes, etc. wherever possible.

  Requirement	Impact	Type	Justification
  CareWorker.Records.Ease	5	absolute	A well designed GUI should provide a quick and easy inteface to the system. However, it will require considerable usuability testing to ensure that this is so.

• Synchronization.Software (S) Software to keep track of items which have been modified.

  Only records which have actually been modified since last synchronization should be transfered.

• Synchronization.Software.ConflictResolution (S) Invoked when two careworkers submit different amendments to the same record.

  Requirement	Impact	Type	Justification
  HQ.Records.Accuracy	0.5 ± 0.5	relative	Pure guess!! Need to know the common sources of errors in the records.

• Synchronization.Cradle (S) Docking cradles are supplied at each clinic.

  Requirement	Impact	Type	Justification
  Clinic.Synchronization	-	achieves	-
  HQ.Records.Update	1	absolute	Do not expect careworkers to go into the clinic every day but once per week is reasonable.

• Synchronization.Cradle.Serial (S) Use a standard serial link.

  Requirement	Impact	Type	Justification
  Clinic.Synchronization.Speed	110kb/s	absolute	-

• Synchronization.Cradle.USB (S) A USB link.

  Requirement	Impact	Type	Justification
  Clinic.Synchronization.Speed	??kb/s	absolute	-

• Synchronization.Phone (S) Communication between Pocket PC and HQ via a mobile phone.

  Requirement	Impact	Type	Justification
  HQ.Records.Update	5	absolute	Careworkers will be able to upload changes from anywhere. To synchronize once per day is reasonable. If the process is easy it might be more often.

• Synchronization.Phone.Combined (S) Pocket PCs with an integral mobile phone.

  Such devices are coming on to the market. It may be possible to delay the implementation until a suitable model becomes available. This is a medium risk strategy since waiting may significantly delay the development.

  Requirement	Impact	Type	Justification
  Development.Time	3months	relative	The software running locally on the mobile device cannot be finalized until the exact model is known.

  Risk: medium

• Survey (S) Software for preparing and running Health surveys.

  Requirement	Impact	Type	Justification
  HQ.HealthSurveys	-	achieves	-

• Survey.Editor (S) Preparation and distribution of electronic questionnaire forms.

  Requirement	Impact	Type	Justification
  HQ.HealthSurvey.Responsive	-3weeks	relative	No printing time.

• Survey.Analysis (S) Collection and statistical analysis of results.

  Requirement	Impact	Type	Justification
  HQ.HealthSurveys.Responsive	-4weeks	relative	No data entry stage at HQ (as there is with paper forms).

This document was prepared using XML for Structured Solutions © University of Leicester 2002. Please send any comments and bug reports to S.Ambler@mcs.le.ac.uk.