Database Schema
Organization of Database
Outline
Scenario
ERD (Entity Relation Diagram)
Normalization
Database Schema
Scenario
A new Healthcare Company named Take
Care is designing its database. The
current setup of an HMO is an account (a
company for instance) enrolls its
employees and family members. All
members will be assigned with its
designated plans. Then all member claims
(i.e. doctor consultation, hospitalization)
should be recorded.
ERD (Entity Relation Diagram)
Entities
 Account Entity
 Member Entity
 Plan Entity
 Claims Entity
ERD (Entity Relation Diagram)
Attributes
 Account Name
 Account Information
 Account Contract
 Member ID
 Member Name
 Member Personal Information
Plan Number
 Plan Information
 Claim Number
 Claims Information
ERD (Entity Relation Diagram)
ERD (Entity Relation Diagram)
Account Name
Account Info
Account Entity 1 TO M Member Entity
Claims Entity
Plan Entity
Account Contract Member ID
Member Name
Member Info
M TO M
1 TO M
Plan NumberPlan Info
Claim NumberClaims Info
Normalization
UNF
Account_id
Account_Name
Account_Information
Account_Contarct
Member_id
Member_Information
Plan_number
Plan_Details
Claim_number
Claim_Details
3NF
Account_id
Account_name
Account_Information
Account_Contract
1NF
Account_id
Member_id
Member_Name
Member_Information
Plan_Number
Plan_Details
3NF
Member_id
Claim_Number
Claim_Details
3NF
Account_id
Account_name
Account_Information
Account_Contract
3NF
Account_id
Member_id
Member_Name
Member_Information
2NF
Member_id
Plan_Number
Plan_Details
3NF
Member_id
Claim_Number
Claim_Details
3NF
Account_id
Account_name
Account_Information
Account_Contract
3NF
Account_id
Member_id
Member_Name
Member_Information
3NF
Member_id
Plan_Number
3NF
Plan_Number
Plan_Details
3NF
Member_id
Claim_Number
Claim_Details
Normalization
ACCOUNT
PK ACCOUNT_ID
ACCOUNT_NAME
ACCOUNT_TYPE
START_DATE
END_DATE
ADDRESS
CONTACT_NO
MEMBER
PK MEMBER_ID
FK1 ACCOUNT_ID
MEMBER_TYPE
LAST_NAME
FIRST_NAME
MIDDLE_NAME
EXTENSION
RELATIONSHIP
BDAY
GENDER
CIVIL
ADDRESS
EFF_DATE
EXP_DATE
MEMBER_PLANASSIGN
FK1 MEMBER_ID
FK2 PLAN_NUMBER
PLAN
PK PLAN_NUMBER
PLAN_CODE
DENTAL_REMARKS
MATERNITY_REMARKS
BENEFIT_LIMIT
START_DATE
CLAIM
PK CLAIM_NUMBER
FK1 MEMBER_ID
DATE_IN
DATE_OUT
CLAIM_TYPE
DOCTOR
DAIGNOSIS
RENARKS
AMOUNT
Database Schema
 Create Database
create database take_care;
 Create Tables
create table account_details
( account_id nvarchar(12),
account_name nvarchar(75),
account_type char(5),
start_date datetime,
end_date datetime,
address nvarchar(100),
contact_no nvarchar(20),
constraint account_details_pk primary key (account_id)
);
Database Schema
create table plan_details
( plan_id nvarchar(4),
plan_code nvarchar(10),
dental_remarks nvarchar(75),
maternity_remarks nvarchar(75),
benifit_limit nvarchar(10),
start_date datetime,
constraint plan_details_pk primary key (plan_id)
);
Database Schema
create table member_details
( member_id nvarchar(12),
account_id nvarchar(12),
member_type char(1),
last_name nvarchar(50),
first_name nvarchar(50),
middle_name nvarchar(50),
extension nvarchar(5),
relationship nvarchar(20),
bday datetime,
gender char(1),
civil nvarchar(20),
address nvarchar(100),
effectivity_date datetime,
exp_date datetime,
constraint member_details_pk primary key (member_id),
constraint member_details_fk foreign key (account_id) references
account_details(account_id));
Database Schema
create table member_planassign
( member_id nvarchar(12),
plan_id nvarchar(4),
start_date datetime,
end_date datetime,
constraint member_planassign_fk1 foreign key
(member_id) references member_details
(member_id),
constraint member_planassign_fk2 foreign key
(plan_id) references plan_details (plan_id)
);
Database Schema
create table member_claims
( claim_number int,
member_id nvarchar(12),
date_in datetime,
date_out datetime,
claim_type nvarchar(20),
doctor nvarchar(50),
daignosis nvarchar(255),
remarks nvarchar(255),
amount decimal,
constraint member_claim_pk primary key (claim_number),
constraint member_claim_fk foreign key (member_id) references
member_details (member_id)
);

Database schema