JUDUL Harris Dwi Putra 0700688844

(1)

iv

BINUS INTERNATIONAL

UNIVERSITAS BINA NUSANTARA

Major Information Systems Sarjana Komputer Thesis Semester EVEN year 2007

JUDUL

Harris Dwi Putra 0700688844

Abstract

Objectives, this study will make an analysis about the current business process in RSPI (Rumah Sakit Pondok Indah) which has many flaws, this flaws will potentially reduce the income of the hospital. This study will only discuss the out-patient.

Methods , the requirements methods that were used in creating this thesis are interview, direct observation and also from printed documentation (prescription, invoice, etc). The system design techniques that were used to document the current/ old system are Entity Relationship diagram, Data Flow Diagram, and also Flowchart. To develop the proposed system the techniques that were used are Use case, Entity Relationship diagram, Class Diagram, Collaboration Diagram, Data Flow Diagram, Sequence Diagram and also Flowchart.

Results, the expected result of the proposed system are an increase in hospital income, reduce the human error, streamline business process, and also faster response time. By generating those advantages hopefully the hospital image will increase and more potential customer will come to them.

Conclusion, To be able to run this new system and to optimized all its functions, all the hospital stakeholders that will interact directly with the system has to learn to use this system seriously, because the proposed system is a fully computerize and will remove some process that they usually do in the current system.

Key words

(2)

v

Acknowledgement

First of all I want to thank you to Allah SWT because without God bless this thesis will meet many obstacle, and will not finish on time.

To Mr. Totok A. Soefijanto as the author supervisor for his support and guidance from the beginning of this thesis until it finished

To Mr. Abubakar Siddiq who gave the author suggestions and critic about how to build and design a good system

To other lectures in BINUS International who thought the author for the past 4 years. Thank you for all the knowledge that you share.

(3)

vi

List of Figures

Figure 2.1 Activity Diagram examples ... 10

Figure 2.2 Use case for a restaurant ... 11

Figure 2.3 Use Case Include relationship ... 13

Figure 2.4 Use Case Extend relationships ... 14

Figure 2.5 Aggregation example... 15

Figure 2.6 Generalization... 16

Figure 2.7 multiplicity example ... 17

Figure 2.8 Sequence diagram... 18

Figure 2.9 context diagram example... 20

Figure 2.10 DFD components ... 21

Figure 2.11 DFD level 1 examples ... 22

Figure 2.12 ERD examples ... 23

Figure 2.13 Java Servlet execution... 32

Figure 2.14 frameworks for interactive SMS ... 34

Figure 2.15 U-Commerce framework ... 35

Figure 2.16 The wall of U-commerce ... 39

Figure 3.1 RSPI organizational structure ... 47

Figure 3.3 Context diagram RSPI current system ... 51

Figure 3.4 DFD booking level 0 ... 52

Figure 3.5 DFD prescription level 0 ... 54

Figure 3.6 DFD Selected doctor payment level 0 ... 57

(10)

xiii

Figure 3.8 DFD prescription level 1 ... 59

Figure 3.9 DFD Booking level 2... 60

Figure 3.10 Workflow for current booking process... 61

Figure 3.11 Workflow for patient check without booking ... 63

Figure 3.12 Workflow for creating prescription... 65

Figure 3.13 ERD current System... 67

Figure 4.1Use case Computerize Booking System... 72

Figure 4.2 Use Case Automated Prescription... 76

Figure 4.3 Use Case Paperless Doctor Payment ... 79

Figure 4.4 Context Diagram ... 82

Figure 4.7 Booking level 2 – SMS Booking... 86

Figure 4.8 Booking level 2 – Waiting List Handler... 87

Figure 4.9 Booking level 2 - SMS Cancellation... 88

Figure 4.10 Booking Level 3 – SMS outpatient cancellation... 89

Figure 4.11 Booking Level 2 – Next Appointment ... 90

Figure 4.12 Prescription Level 0... 91

Figure 4.13 Prescription Level 1... 91

Figure 4.14 Prescription Level 2 – SMS Prescription Order ... 93

Figure 4.15 Prescription Level 2 – Direct prescription order ... 94

Figure 4.16 SMS Queue Checking Level 0 ... 95

Figure 4.17 SMS Queue Checking Level 1 ... 96

(11)

xiv

Figure 4.19 Doctor Payment Level 1 ... 97

Figure 4.20 Patient Updater level 0 ... 98

Figure 4.21 Entity Relationship Diagram ... 99

Figure 4.22 Class Diagram ... 109

Figure 4.23 Sequence Create Booking Request... 110

Figure 4.24 Sequence Patient’s Booking Cancellation... 111

Figure 4.25 Sequence Create Next Visit Booking ... 112

Figure 4.26 Sequence Stated max. # of patients/ day ... 113

Figure 4.27 Sequence Update Queue ... 114

Figure 4.28 Sequence Change Booking Status ... 114

Figure 4.29 Sequence Add New Direct Booking... 115

Figure 4.30 Sequence Doctor Booking Cancellation... 116

Figure 4.31 Sequence Check Patient’s Medical Record ... 117

Figure 4.32 Sequence Create Prescription... 119

Figure 4.33 Sequence Medicine Search... 120

Figure 4.34 Sequence Print Prescription... 121

Figure 4.35 Sequence View and Update Order List ... 122

Figure 4.36 Sequence Print Medicine Label... 123

Figure 4.37 Sequence Print Invoice ... 123

Figure 4.38 Sequence Create Doctor Payment ... 124

Figure 4.39 Sequence Print Doctor Payment Invoice ... 125

Figure 4.40 Create Online Booking Request ... 126

Figure 4.41 Patient’s Booking Cancellation... 126

(12)

xv

Figure 4.43 Stated max.# of patients/ day... 127

Figure 4.44 Change Booking Status ... 127

Figure 4.45 Update Queue ... 128

Figure 4.46 Add New Direct Booking ... 128

Figure 4.47 Doctor’s Booking Cancellation... 128

Figure 4.48 Create Prescription ... 129

Figure 4.50 Print Prescription... 129

Figure 4.49 Check Patient Medical Record ... 130

Figure 4.51 Medicine Search... 130

Figure 4.52 Print Medicine Label ... 131

Figure 4.53 View Update & Order List ... 131

Figure 4.54 Print Medicine Invoice ... 131

Figure 4.55 Doctor Payment ... 132

Figure 4.56 Print Doctor Payment Invoice ... 132

Figure 4.57 SMS Booking Flowchart ... 133

Figure 4.58 Waiting List Flowchart ... 135

Figure 4.59 SMS Booking Cancellation... 136

Figure 4.60 SMS Prescription Flowchart... 137

Figure 4.61 SMS Queue Checking ... 138

Figure 4.62 Login Page ... 139

Figure 4.63 Doctor GUI –Home ... 140

Figure 4.64 Doctor GUI - After Click OK... 141

Figure 4.65 Doctor GUI - Medicine Search... 142

(13)

xvi

Figure 4.67 Doctor GUI - Click for more (all) ... 145

Figure 4.68 Doctor GUI - Create Booking ... 146

Figure 4.69 Doctor GUI - After click "Submit Form" in create booking ... 147

Figure 4.70 Nurse GUI – Home... 148

Figure 4.71 Nurse GUI - after click "Add List"... 149

Figure 4.72 Nurse GUI - delete Tommy & change status Harris ... 150

Figure 4.73 Nurse GUI - Doctor Cancellation... 151

Figure 4.74 Pharmacist GUI – Home ... 152

Figure 4.75 Pharmacist GUI - Click PRINT... 153

Figure 4.76 Patient GUI - website Index ... 154

Figure 4.77 Patient GUI - search Doctor ... 155

Figure 4.78 Patient GUI - after patient choose doctor ... 156

Figure 4.79 Patient GUI - Confirmation page ... 156

Figure 4.80 Patient GUI - Booking Cancellation... 157

Figure 4.81 Patient GUI - choose which one to cancel... 157

Figure 4.82 Patient GUI - Considerations page ... 158

Figure 4.83 Patient GUI - Cancellation confirmation... 159

Figure 4.84 Patient GUI - Prescription order ... 159

Figure 4.85 Patient GUI - Patient prescription list ... 160

Figure 4.86 Patient GUI - Prescription details ... 161

Figure 4.87 Patient GUI - Delivery option ... 162

Figure 4.88 Patient GUI - Successful order request ... 162

(14)

xvii

List of Tables

Table 2.1 use case restaurant description... 12

Table 2.2 use case include relationship ... 13

Table 2.3 use case extend relationship... 14

Table 2.4 common multiplicities ... 17

Table 2.5 sequence diagram example explanation... 19

Table 2.6 Database Standard Language ... 33

Table 2.7 research issues related to-commerce... 40

Table 3.1Puspita Foundation Organizational Structure ... 43

Table 3.2 Current organizational structure explanation... 48

Table 3.3 Current organizational structure explanation (continue) ... 49

Table 3.4 Booking level 0 - Data Flow Patient... 52

Table 3.5 Booking level 0 - Data flows Nurse... 53

Table 3.6 prescription level 0 - data flow Doctor ... 54

Table 3.7 Prescription level 0 - data flow patient ... 54

Table 3.8 prescription level 0 - Data flow pharmacy... 55

Table 3.9 prescription level 0 - Data flow management ... 55

Table 3.10 prescription level 0 - Data flow cashier ... 56

Table 3.11 selected doctor payment level 0 - Data flow nurse ... 57

Table 3.12 selected doctor payment level 0 - Data flow Patient ... 57

Table 3.13 selected doctor payment level 0 - Data flow Cashier ... 58

Table 4.1 Use case Computerize Booking System - Outpatient ... 73

(15)

xviii

Table 4.3 Use case Computerize Booking System – Nurse... 75

Table 4.4 Use Case Automated Prescription – Doctor ... 78

Table 4.5 Use Case Automated Prescription – Pharmacist... 79

Table 4.6 Use Case Automated Prescription – Cashier ... 79

Table 4.7 Use Case Paperless Doctor Payment – Doctor ... 81

Table 4.8 Use Case Paperless Doctor Payment – Cashier ... 81

Table 4.9 Data Dictionary – Department ... 100

Table 4.10 Data Dictionary – Rooms ... 100

Table 4.11 Data Dictionary – Nurse ... 101

Table 4.12 Data Dictionary – Equipment ... 101

Table 4.13 Data Dictionary - Doctor Schedule... 102

Table 4.14 Data Dictionary – Doctor... 102

Table 4.15 Data Dictionary - Medical Supply ... 103

Table 4.16 Data Dictionary – Action... 103

Table 4.17 Data Dictionary – Invoice ... 104

Table 4.18 Data Dictionary – Prescription... 104

Table 4.19 Data Dictionary – Booking ... 105

Table 4.20 Data Dictionary – Medicine... 106

Table 4.21 Data Dictionary – Diagnosed... 106

Table 4.22 Data Dictionary – Cashier... 107

Table 4.23 Data Dictionary – Therapy... 107

Table 4.24 Data Dictionary – Outpatient ... 108

Table 4.25 Data Dictionary – Pharmacist ... 109

(16)