Creating Entities

[Guest]

I am creating a database for a class project. It is for a outpatient health
clinic, we are responsible for capturing a patients personal informaiton,
next of kin, insurance data, payment and credit data. Along with all of the
patients session, the initial and subsequent diagnoses should be maintaned.
We also have to orivde suggestions for handling discharged patients.
Can anyone suggest what entities and attributes I should create?

 

[tina]

sounds like a fairly advanced project. if this class, or previous classes,
have not provided you with instruction on relational data modeling (many
Access classes don't), then i recommend you fill that gap now. it will
enable to you design your database correctly for this project, and for any
future relational databases you may build.

one good text is Database Design for Mere Mortals by Michael Hernandez.
that's the text used in the class i took on relational data modeling several
years ago - but the concepts remain relevant today. you can also find
information on relational data modeling (and tons of other valuable info on
database development) at
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html
beginning with the Starting Out and Database Design 101 links.

hth

 

[Guest]

Unfortunately, we have create, the whole thing from scratch. We have to
create an ERD, normalize, convert into access tables and create SQL queries.
And it's just for a management class. but thanks for you reply, I will refer
to the text.

 

[peregenem]

Unfortunately, we have create, the whole thing from scratch.

I have some good somone has already done it for you ...

http://www.nhsia.nhs.uk/datastandar...ionary/attributes/attributes_Person_child.asp

.... but the bad news is, this data model is huge!

 

[melspence]

Stevie,

Wewlcome to the wonderful world of requirements analysis!

You could start with following entities, Patient, Physician,
Diagnosis, etc

Then ask youself some questions like:
Does a Patient have many doctors?
Does a doctor have many patients?
Doess a patient have many sessions?
Does a doctor have many sessions with many patients?
etc.

These questions and many others will help you decide how the database
should be designed.

Have a go and post back what you come up with