Professional Documents
Culture Documents
The Well Meadows Hospital Case Study Solution
The Well Meadows Hospital Case Study Solution
The Well Meadows Hospital Case Study Solution
2008
Data Dictionary
Table
column name
keys
Appointment
Staff_ID
FK
Contract
Appointment_Tim
e
Appointment_NO
PK
Patient_NO
FK
Type
work_hrs
Salary_payment
Staff_ID
Experience
PK,FK
Position
Organization
Start_Date
Finish_Date
Staff_ID
Qualification
PK,FK
Date
type
Institute
Requisition
Staff_ID
PK,FK
Date_Order
Staff_ID
FK
Req_NO
PK
Drug_NO
FK
Surgical_ID
FK
Description/Alia
ses
Code relating to
the Staff table
The appointment
time
The ID for the
Appointment
record
Code relating to
the Patient table
Data
type
int
datetime
int
int
Type of contract,
permanent or
temporary
how many time
did they work
Money that
employees
receive for doing
their job
Code relating to
the Staff identifier
varchar(1
0)
Code relating to
the Position
identifier for the
position held by
the staff member
for this work
experience entry
The name of work
place
The date the staff
member
commenced
employment for
this work
experience entry
The date the staff
member finished
employment for
this work
experience entry
Code relating to
the Staff identifier
to whom this
work experience
record relates
When the
qualification is
got
Type of
qualification
The name of work
place
Code relating to
the Staff table
varchar(2
0)
Order date
Code relating to
the Staff table
The ID for the
Requisition record
that this item is
requisitioned on
Code relating to
the
Pharmaceutical
table
Code relating to
datetime
int
int
int
int
varchar(5
0)
datetime
datetime
int
datetime
varchar(2
0)
varchar(5
0)
int
int
Physical Model
The decision was made to build the database in SQL. This Physical Model is in the 3NF
normalization and its according to LDM rules.
Diagram:
ADD
CONSTRAINT
USE [WellMeadow]
GO
/****** Object: Table [dbo].[Contract]
Script Date: 04/11/2008 12:04:35
******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[Contract](
[Type] [varchar](50) COLLATE Chinese_PRC_CI_AS NULL,
[Work_Hrs] [int] NULL,
[Salary_Payment] [int] NULL,
[Staff_ID] [int] NOT NULL,
CONSTRAINT [PK_Contract] PRIMARY KEY CLUSTERED
(
[Staff_ID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
GO
USE [WellMeadow]
GO
ALTER TABLE [dbo].[Contract]
WITH
[FK_Contract_Staff] FOREIGN KEY([Staff_ID])
CHECK
ADD
CONSTRAINT
ADD
CONSTRAINT
ADD
CONSTRAINT
USE [WellMeadow]
GO
/****** Object: Table [dbo].[Requisition]
Script Date: 04/11/2008 12:05:36
******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Requisition](
[Date_Order] [datetime] NULL,
[Staff_ID] [int] NULL,
[Req_NO] [int] NOT NULL,
CONSTRAINT [PK_Requisition] PRIMARY KEY CLUSTERED
(
[Req_NO] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
USE [WellMeadow]
GO
ALTER TABLE [dbo].[Requisition]
WITH CHECK
[FK_Requisition_Staff] FOREIGN KEY([Staff_ID])
REFERENCES [dbo].[Staff] ([Staff_ID])
ADD
CONSTRAINT
USE [WellMeadow]
GO
/****** Object: Table [dbo].[Staff] Script Date: 04/11/2008 12:05:48 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[Staff](
[Staff_ID] [int] NOT NULL,
[Sex] [real] NULL,
[Last_name] [varchar](15) COLLATE Chinese_PRC_CI_AS NULL,
[First_name] [varchar](15) COLLATE Chinese_PRC_CI_AS NULL,
[NIN] [int] NULL,
[Position] [varchar](10) COLLATE Chinese_PRC_CI_AS NULL,
[DOB] [datetime] NULL,
[Address] [varchar](50) COLLATE Chinese_PRC_CI_AS NULL,
[Salary_Scale] [int] NULL,
[Current_Salary] [int] NULL,
[Phone] [int] NULL,
CONSTRAINT [PK_Staff] PRIMARY KEY CLUSTERED
(
[Staff_ID] ASC
)WITH (IGNORE_DUP_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO
SET ANSI_PADDING OFF
USE [WellMeadow]
GO
/****** Object: Table [dbo].[Staff_Allocation]
Script Date: 04/11/2008
12:06:03 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_PADDING ON
GO
CREATE TABLE [dbo].[Staff_Allocation](
[Shift] [varchar](5) COLLATE Chinese_PRC_CI_AS NULL,
[Staff_ID] [int] NULL,
[Ward_NO] [int] NOT NULL,
CONSTRAINT
Transaction Analysis
Transaction/
(a)
(b)
(c)
Insert
Read
Read
Relation
Staff
Requisition
Staff_Allocation
Qualification
Read
Insert
Read
Appointment
Contract
Insert
Experience
Insert
Read
(a) Create and maintain records recording the details of members of staff ( Personnel
Officer )
(b) Search for staff who have particular qualifications or previous work experience
( Personnel Officer )
(c) Produce a report listing the details of staff allocated to each ward ( Personnel
Officer )
Security
For consideration of security in this RDBMS will set these Users to manage it:
SUPERVISOR
This user have global authority can operate whole RDBMS.
e.g. (sa at mssql, root at mysql)
BACKUP OPERATOR
This user has responsibility to backup the whole system, so this user can readonly all tables in this RDBMS.
PERSONAL OFFICER
This user has responsible for ensuring that the appropriate staffs are allocated
to each ward. For that this user can operate this table: staff_allocation.
MEDICAL DIRECTOR
This user has overall responsibility for the management of the hospital, including
staff, beds and supplies. Therefore this user can operate these tables: staff,
ward, requisition, surgical Non-Surgical supplies and Pharmaceutical supplies.
CHARGE NURSE
This user is responsible to manage all resources (staff, beds, and supplies) are
used effectively in the care of patients. So this user can operate these tables:
staff_allocation, surgical Non-surgical supplies, pharmaceutical supplies,
requisition, ward_required.
Area
Appropriate Decisions
Justification Provided
Securit
security problem.
Staff
Experience, Contract,
relationship
connect to Staff.
Patient
Ward_Required and