Sale!
Placeholder

An Intranet Application for Oakwood & Harehills Corner Surgeries

10,000 3,000

Topic Description

Summary
Oakwood Surgery and Harehills Corner Surgery are twin surgeries, half a mile apart. Each has their
own patient list and staff group, although they work closely together and are centrally managed. The
total of 22 staff care for over 6000 patients.
Both surgeries’ patient records are now ‘paperlight’. This means that all hospital correspondence is
scanned into the computer patient record, and all consultation notes are made directly into the
computer. However, patients’ GP referrals for hospital care, documents regarding the Practice’s
policies and procedures are still in paper format¸ and therefore the surgeries are both still
overwhelmed by the quantity of paper produced.
This project attempts to address this problem by creating a system using their local intranet that will
store these documents in a centrally managed location and make them easily accessible to the staff via
a user-friendly interface.
This system was successfully implemented, along with additional features which far exceed the
minimum requirements. A tightly linked staff directory & schedule, calendar and room planner was
also included in an attempt to make the Practice Manager’s job of scheduling people, rooms, times,
cover, etc easier and less time consuming.

Contents
1. Introduction 1
1.1. Statement of problem 1
1.2. Aim 2
1.3. Objectives 2
1.4. Minimum requirements 2
1.5. Extensions to the minimum requirements 3
1.6. Deliverables 3
2. Project Management 4
2.1. Development methodologies 4
2.1.1. ETHICS 4
2.1.2. Checkland’s SSM 5
2.1.3. DSDM 6
2.2. Intended approach 7
2.3. Project schedule 10
3. Analysis 13
3.1. Feasibility study 13
3.1.1. Why change? 13
3.1.2. Problem situation: unstructured 14
3.1.3. System boundaries 14
3.1.4. Costs 15
3.2. Business study 15
3.2.1. Description of existing system 15
3.2.1.1. Referral Information 15
3.2.1.2. Practice Policies and Procedure 15
3.2.1.3. Other Documents 15
3.2.1.4. Staff Contact Information 15
3.2.1.5. Calendar 16
3.2.1.6. Room Planner 16
3.2.1.7. Rota 16
3.2.1.8. Links 16
3.2.2. Definition of key objectives, tasks and information needs 17
iv
3.2.2.1. Documents 17
3.2.2.2. Directory 17
3.2.2.3. Calendar 18
3.2.2.4. Room Planner 18
3.2.2.5. Rota 18
3.2.2.6. Links 18
3.3. Technical Options 19
3.3.1. Hardware and software 19
3.3.2. Development tools 19
3.3.2.1. Web servers 20
3.3.2.2. Data storage 20
3.3.2.3. Data retrieval 21
3.3.3. Security 22
3.3.4. Usability considerations 23
4. Design 26
4.1. Refined requirements 28
4.2. Database 30
4.3. Interface 31
4.4. Test plans 32
5. Implementation 33
5.1. Database 33
5.2. Functionality 33
5.2.1. Menu 33
5.2.2. Adding data 34
5.2.3. Viewing data 34
5.2.4. Editing data 35
5.2.5. Deleting data 35
5.3. Error handling 36
5.4. Help and documentation 37
5.5. Security 37
5.6 Handover 38
v
6. Evaluation 40
6.1. System 40
6.1.1. User requirements fulfilment 40
6.1.2. User acceptance testing 41
6.1.3. Comparison to other solutions 43
6.1.3.1. Advantages 43
6.1.3.2. Disadvantages 43
6.2. Methodology 43
6.2.1. Feasibility study 44
6.2.2. Business study 44
6.2.3. Functional model iteration 44
6.2.4. System build iteration 45
6.2.5. Implementation 45
6.2.6. Summary 45
6.3. Future enhancements 46
6.3.1. Full-text searching 46
6.3.2. Convert to an extranet 46
6.3.3. Message board 46
6.4. Conclusion 46

GET COMPLETE PROJECT