Legal Issues• Legal issues include copyright / intellectual property infringements,

libel / defamation, disability discrimination and data protection.• Any statement of copyright (eg to results / logos on results .pfd files

etc) should be made to the user (the GP) in the small print / terms and conditions of website use.

• Also included in the terms and conditions should be information for the user on the intellectual property of the content, how their data is used / stored / disposed of, whether cookies / web statistics are used, and how much information they log, any virus protection offered to the user (eg has the .pdf sent back to them been scanned?) and (if necessary) the linking policy of the site (if any outside links are used, need a disclaimer to state that content is outside webmaster’s control).

Legal Issues cont.• Important parts of the Data Protection Act to consider are:

– Information that you have on or collect through the site must only be used for the purpose for which it was obtained.

– You should specify the purpose on the site and, where possible, give users the opportunity to ‘opt out’ of the data collection.

– You should not collect or store more personal data than you need for the specified purpose.

– All personal information should be accurate, up-to-date and available to the individual on request.

• The Disability Discrimination Act requires that “reasonable adjustments” are made to make the site accessible for the widest range of people, for example the learning disabled, the physically impaired, or those with less computing experience. This isn’t hugely important when regarding only GPs, as they can quite safely be assumed to have at least basic computing skills.

Social Issues

• These issues, as far as I can work out, are to do with the sectors of society being addressed, and making sure that all are included equally. This crosses over a little with ethical issues.

Ethical Issues

• Ethical issues involves what documentation is non-sensitive enough to be kept on the server (if any), and making sure that all the legal issues are considered in the acquiring and handling of the data.

• All ethical issues in reality have to go through the National Research Ethics Service, whose guidelines can be found here:

http://www.nres.npsa.nhs.uk/EasySiteWeb/GatewayLink.aspx?alId=4798

Information Collection for Specification

• This could be to do with presenting to the client, in which case the information will be collected by all members of the group, and collated into one specification.

• It could also be to do with how information will be collected within the system itself, in which case it will be through user input (in specified file types, according to the inner workings of the statistical analysis modules), then the output of the modules, with (so far as we decided at client meetings) as little residual data collected on the server as possible.

Network Diagram 1

Design Contraints

• The controller needs to know what modules are available, and be able to (extensibly) report this to the user for them to choose from.

• The entire system needs to be outsourced to an external server/cluster. Starting small, it needs to be monitored in case business grows, requiring another server / more servers to be added.

• Presentation to the user, in whatever format, needs to be sure not to get stuck in spam filters.

Design Idea 1

The design as drawn at the client meeting. All held on external server.

Design Idea 2

Statistical analysis modules held externally to the server. Saves space, much less processing to be done on server saving money, but more security issues in sending sensitive data to an outside processor.

Design Idea 3

With user login system, and the addition of an updater. Updater checks the available modules from a module bank where all are held (on the server/cluster), on a call from the controller, returning a list of the available modules, with descriptions, for the user to pick from.

Design Idea 4

As design 3, but with creation of presentation outsourced.

Gantt ChartNumber Task Start End Duration

20/10 27/10 3/11 10/11 17/11 24/11 1/12 8/12 15/12

20/10 21/10 22/10 23/10 24/10 25/10 26/10 27/10 28/10 29/10 30/10 31/10 1/11 2/11 3/11 4/11 5/11 6/11 7/11 8/11 9/11 10/11 11/11 12/11 13/11 14/11 15/11 16/11 17/11 18/11 19/11 20/11 21/11 22/11 23/11 24/11 25/11 26/11 27/11 28/11 29/11 30/11 1/12 2/12 3/12 4/12 5/12 6/12 7/12 8/12 9/12 10/12 11/12 12/12 13/12 14/12 15/12 16/12 17/12 18/12 19/12 20/12 21/12

Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun Mon Tues Wed Thurs Fri Sat Sun

1 Understanding of brief 22/10/2008 26/10/2008 4

2 Preparation for Client Meeting 1 26/10/2008 31/10/2008 5

3 Writing trial weekly reports 31/10/2008 6/11/2008 6

4 Setting up weekly meeting times 22/10/2008 6/11/2008 15

5 Setting up and attending Client Meeting 1 26/10/2008 31/10/2008 5

6 Researching Web Services / XML / SOAP 31/10/2008 6/11/2008 6

7 Setting up & joining group WikiSpace 26/10/2008 6/11/2008 11

8 Getting trial weekly report feedback 6/11/2008 13/11/2008 7

9 Deciding on questions for Client Meeting 2 31/10/2008 13/11/2008 13

10 Researching similar existing systems 31/10/2008 13/11/2008 13

11 Setting up and attending Client Meeting 2 12/11/2008 13/11/2008 1

12 Sorting weekly report rota 22/10/2008 13/11/2008 22

13 Chris G - Understanding brief points 1&6 31/10/2008 2/11/2008 2

14 Matt - Understanding brief points 2&7 13/11/2008 20/11/2008 7

15 Chris P - Understanding brief points 3&7 13/11/2008 20/11/2008 7

16 Nick - Understanding brief points 4&6 13/11/2008 20/11/2008 7

17 Katie - Understanding brief points 5&6 13/11/2008 20/11/2008 7

18 Bethan - Understanding brief point 7&8 13/11/2008 20/11/2008 7

19 Chris G - Looking into outsourcing 20/11/2008 27/11/2008 7

20 Matt - Looking into web services 20/11/2008 27/11/2008 7

21 Chris P - Looking into output formats 20/11/2008 27/11/2008 7

22 Nick - Looking into possible interfaces 20/11/2008 27/11/2008 7

23 Katie - Looking into design overview 20/11/2008 27/11/2008 7

24 Bethan - Looking into statistical modules 20/11/2008 27/11/2008 7

25 Chris G - Finding data analysis modules 27/11/2008 5/12/2008 8

26 Matt - Researching web services in detail 27/11/2008 5/12/2008 8

27 Chris P - Looking up radar charts in detail 27/11/2008 5/12/2008 8

28 Nick - Researching NHS applications 27/11/2008 5/12/2008 8

29 Katie - Creating Gantt chart/network diag 27/11/2008 5/12/2008 8

30 Bethan - Looking into GPs' software. 27/11/2008 5/12/2008 8

31 Chris G - Looking into module inputs 5/12/2008 11/12/2008 6

32 Matt - Looking up Service Oriented Arch. 5/12/2008 11/12/2008 6

33 Chris P - Creating sample questionnaire 5/12/2008 11/12/2008 6

34 Nick - Creating designs for user interface 5/12/2008 11/12/2008 6

35 Katie - Adding tasks to Gantt/network 5/12/2008 11/12/2008 6

36 Bethan - Researching output options 5/12/2008 11/12/2008 6

37 a 15/12/2008 17/12/2008 2

38 b 15/12/2008 17/12/2008 2

39 c 15/12/2008 17/12/2008 2

40 d 15/12/2008 17/12/2008 2

41 e 15/12/2008 17/12/2008 2

42 f 15/12/2008 17/12/2008 2

43 g 15/12/2008 17/12/2008 2

44 h 15/12/2008 17/12/2008 2

Buy SmartDraw!- purchased copies print this document without a watermark .

Visit www.smartdraw.com or call 1-800-768-3729.