computerscience
keekkadan1
database_schema.pptxPain Management of post hand Surgery (Database Schema)
Saji Varughese
HIM 650 – Healthcare Data Management
Grand Canyon University
September 29, 2016
Entities
Patient
Physician
Surgery
Nurse
Drugs
Pharmacy
Entity Relationship diagram
Patient
Surgery
Nurse
Physician
First Name
Weight
Height
DOB
Last Name
Medical Record #
First Name
First Name
`
Last Name
Last Name
Drugs
Provider ID #
Employee #
Route
Frequency
Dose
Bone Fracture Repair
Amputation
Collar Bone
M:N
1:M
1
: M
1:1
Database Schema
| Patient | Physician | Nurse | Surgery | Drugs |
| Medical Record Number | Provider ID Number | Employee # | Surgery ID # | Drug # |
| First Name | First Name | First Name | Bone Fracture Repair | Name of Drug |
| Last Name | Last Name | Last Name | Amputation | Route |
| DOB | Collar Bone | Frequency | ||
| Height | Dose | |||
| Weight |
Data Dictionary
| Patient | Data Type | Field Size |
| Medical Record Number | Auto Number | 10 |
| First Name | Text | 30 |
| Last Name | Text | 30 |
| DOB | Date | |
| Height | Text | 10 |
| Weight | Integer | 5 |
| Physician | Data Type | Field Size |
| Provider ID Number | Text | 10 |
| First Name | Text | 30 |
| Last Name | Text | 30 |
| Nurse | Data Type | Field Size |
| Employee # | Auto Number | 10 |
| First Name | Text | 30 |
| Last Name | Text | 30 |
| Surgery | Data Type | Field Size |
| Surgery ID # | Auto Number | 10 |
| Bone Fracture Repair | Text | 50 |
| Amputation | Text | 50 |
| Collar Bone | Text | 50 |
| Drugs | Data Type | Field Size |
| Drug # | Auto Number | 8 |
| Name of Drug | Text | 30 |
| Route | Text | 30 |
| Frequency | Text | 30 |
| Dose | Integer | 5 |
Pain Management Design Challenges
How to correlate entities with processes
How to visually show the relationships between entities and the processes
Generating the data dictionary to prepare for handling the medical records for the procedures
Design the database schema to properly extract the data from the entity to generate a patient visit to create a unique case number
design chosen – Rationale - limitations
Entity relationship model visually represents entities, attributes, and relationships to produce the ERD.
Easily understood by non-technical individuals
Provides great value to technical people
Platform independent and can even be used for non-relational databases
To create an efficient ERD, technological tools and well developed software will be needed
References
Oppel, A.(2011). Databases De Mystified Hard stuff made easy, (2nd,edition) United States: McGraw-Hill.
Grand Canyon University lecture note 2 https://lc-grad2.gcu.edu/learningPlatform/user/login.html#/learningPlatform/loudBooks/loudbooks.html?viewPage=past&operation=innerPage&topicMaterialId
http://www.databaseguides.com/what-is-a-database-schema
