- 医師:(この表は、医師の詳細を持つことになります) 患者:
- 専門(このテーブルには、患者の詳細を持っています): (医師、歯科医師などの専門医を定義しています)
- 予定:
- 予約状況/:[スケジュール表デザイン](HTTPの任命予約をifferentステータス)
- 予約(ユーザー書籍特定のスケジュールのための特定の日時の予約)
-- Table structure for table 'appointment_schedule'
CREATE TABLE IF NOT EXISTS 'appointment_schedule' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'doctors_id' int(11) NOT NULL,
'working_days' varchar(50) NOT NULL,
'morning_time_start' time DEFAULT NULL,
'morning_time_end' time DEFAULT NULL,
'morning_tokens' int(11) NOT NULL,
'afternoon_time_start' time DEFAULT NULL,
'afternoon_time_end' time DEFAULT NULL,
'afternoon_tokens' int(11) NOT NULL,
'evening_time_start' time DEFAULT NULL,
'evening_time_end' time DEFAULT NULL,
'evening_tokens' int(11) NOT NULL,
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1;
-- --------------------------------------------------------
-- Table structure for table 'bookings'
CREATE TABLE IF NOT EXISTS 'bookings' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'doctors_id' int(11) NOT NULL,
'appointment_schedule_id' int(11) NOT NULL,
'patients_id' int(11) NOT NULL,
'diseases_description' text NOT NULL,
'datetime_start' datetime NOT NULL,
'datetime_end' datetime NOT NULL,
'status_id' int(11) NOT NULL DEFAULT '1',
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
-- --------------------------------------------------------
-- Table structure for table 'booking_status'
CREATE TABLE IF NOT EXISTS 'booking_status' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'name' varchar(25) NOT NULL,
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ;
-- Dumping data for table 'booking_status'
INSERT INTO 'booking_status' ('id', 'name') VALUES
(1, 'Pending for Approval'),
(2, 'Approved & Booked'),
(3, 'Cancelled by User'),
(4, 'Visited'),
(5, 'User failed to Visit');
-- --------------------------------------------------------
-- Table structure for table 'doctors'
CREATE TABLE IF NOT EXISTS 'doctors' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'name' varchar(50) NOT NULL,
'specialization_id' int(11) NOT NULL,
'clinic_name' varchar(50) NOT NULL,
'address' varchar(1000) NOT NULL,
'qualification' varchar(50) NOT NULL,
'rating' int(11) NOT NULL,
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
-- --------------------------------------------------------
-- Table structure for table 'patients'
CREATE TABLE IF NOT EXISTS 'patients' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'first_name' varchar(50) NOT NULL,
'last_name' varchar(50) NOT NULL,
'address' varchar(500) NOT NULL,
'contact' varchar(100) NOT NULL,
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
-- --------------------------------------------------------
-- Table structure for table 'specialization'
CREATE TABLE IF NOT EXISTS 'specialization' (
'id' int(11) NOT NULL AUTO_INCREMENT,
'name' varchar(100) NOT NULL,
PRIMARY KEY ('id')
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;
可能重複/stackoverflow.com/questions/16497386/schedule-table-design) – Pondlife
参考:http://www.vertabelo.com/blog/technical-articles/a-database-model-to-manage-appointments-and-organize -schedules –