Download Group Project Poster Final

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Information privacy law wikipedia , lookup

Data vault modeling wikipedia , lookup

Microsoft Access wikipedia , lookup

Database wikipedia , lookup

Versant Object Database wikipedia , lookup

PL/SQL wikipedia , lookup

Business intelligence wikipedia , lookup

SQL wikipedia , lookup

Relational model wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Clusterpoint wikipedia , lookup

Database model wikipedia , lookup

Transcript
Kidney Transplant Waiting List Management System
Aim
To create a system (in collaboration with the Kent and Canterbury Hospital Renal
Unit) to help deal with the management of Kidney Transplant patients.
The system is being developed using Active Server Pages
(ASP.NET 2.0) with script written in Visual Basic.NET and a
Microsoft SQL Server 2005 database. The main development tool
for this project is Microsoft Visual Web Developer 2005. All of the
above will allow for good compatibility with the .NET framework and
IIS (Internet Information Services) which are both requirements of
the system in order that it will run on the hospital network. Below is
a mock up of the main menu for the system and the relational
schema for the database.
The Current Problem
Currently the hospital uses a system of spreadsheets to manage their patient data.
These are notoriously unreliable and inaccurate. Data entry is very time consuming
seeing as the data is spread over numerous spreadsheets and as a result of this,
the data often goes out of sync with the main kidney transplant list held at Guys
Hospital in London (i.e. the list kept in Canterbury will say something different to the
list kept in London). Storing the data in a spreadsheet with the current set-up means
that it can only be accessed by one person at a time on a local machine and there
are not enough security measures in place to protect access to the data.
Our Solution
Our solution was to develop a web-based database system that could be run on the
hospital Intranet. This would have the advantage of being able to be run from any
computer in the hospital and allow for certain access rights to be given to varying
members of staff (for instance, consultants could have more access rights than
nurses).
The main aim of the software is to ensure that the local copy of the active transplant
list kept by the Kent and Canterbury Hospital agrees with the list kept by UK
Transplant at Guys Hospital. To comply with this, the system will need built in Email
functionality. It should also provide data reporting functionality, online help and allow
for audit trail tracking (to keep tabs on changes to the data).
This diagram shows the
architecture of the
proposed system with
clients connecting to the
hospital web server
which in turn makes
queries to an SQL
database.
Client
HTTP interaction
Web Server
Client
Client
Account Service
Provision
SQL Query
Database Server
SQL
Patient
database
A tool for wider use?
After thorough searching, we have been unable to locate any
other systems in the medical community similar to the one we are
developing, so if the tool is a success at the Kent and Canterbury
Hospital then there is the possibility it can be migrated to other
hospitals in the South East region and possibly to others
nationwide.
KTWLMS was created as a final year project by Tristan Cuthbert, Evdokia Kolia and Lewis Webb
For more details please contact Roger Cooley ([email protected])