Development of a computerized provider order entry system for laboratory

• DECLARATION
  
• DEDICATION
  
• ACKNOWLEDGEMENT
  
• 1. ABSTRACT
  
• TABLE OF CONTENTS
  
• LIST OF FIGURES
  
• LIST OF TABLES
  
• LIST OF ABBREVIATIONS
  
• CHAPTER 1
  
• 2. INTRODUCTION
  
  • 2.1. Background
    
  • 2.2. Problem statement
    
  • 2.3. Framework of the laboratory test order management system
    
  • 2.4. Justification of the study
    
  • 2.5. Objectives
    
    • 2.5.1. General objectives
      
    • 2.5.2. Specific objectives
      
• CHAPTER 2
  
• 3. LITERATURE REVIEW
  
  • 3.1. The useof automated laboratory data management with an EMR
    
  • 3.2. The benefits of improving laboratory data management on the patient safety in care delivery
    
  • 3.3. The importance of laboratory data for public health monitoring of diseases and epidemics
    
  • 3.4. The benefits of Electronic Health Record and problems associated with their implementation.
    
  • 3.5. The mobile Health (mHealth)
    
    • 3.5.1. Cell phone text messages for communication of lab results in Uganda
      
    • 3.5.2. The Mobile Technology for Community Health (MoTeCH) Initiative in Ghana
      
  • 3.6. The common categories of Computerized Provider Order Entry
    
  • 3.7. Works on the design and implementation of Health Information system
    
    • 3.7.1. Design of the Open Medical Record System (OpenMRS) to support HIV treatment in Rwanda
      
    • 3.7.2. The LabPush system in Swaziland
      
    • 3.7.3. Design of an application for the chemotherapy treatment process at University Hospital of Geneva
      
• 4. Conclusion
  
• CHAPTER 3
  
• 5. METHODOLOGY
  
  • 5.1. Data collection
    
  • 5.2. System development life cycle
    
  • 5.3. The planning phase
    
  • 5.4. The analysis phase
    
    • 5.4.1. The existing situation
      
    • 5.4.2. Improvements identification
      
    • 5.4.3. Requirements definition
      
      • Business requirements
        
      • Functional requirements
        
      • Nonfunctional requirements
        
  • 5.5. System design
    
    • 5.5.1. System Architecture
      
    • 5.5.2. The process modelling
      
      • Activity Diagrams
        
      • Use case diagrams
        
      • Class diagrams
        
      • Sequences diagrams
        
    • 5.5.3. The data modelling
      
      • Conceptual data design
        
      • Logical data design
        
      • Physical data design
        
• CHAPTER 4
  
• 4. SYSTEM DEVELOPMENT
  
  • 4.1. The users and system administration module
    
  • 4.2. The medical staff management module
    
  • 4.3. The patient management module
    
  • 4.4. The appointment and consultation module
    
  • 3.1. The laboratory test order management module
    
  • 4.5. The laboratory test result management module
    
  • 4.6. The report module
    
• CHAPTER 5
  
• 5. DISCUSSION
  
  • 5.1. The design consideration
    
  • 5.2. Benefits of the system
    
  • 5.3. Limitation
    
  • 5.4. Future works
    
• CHAPTER 6
  
• 6. CONCLUSION AND RECOMMENDATION
  
• 7. Conclusion
  
  • 5.5. Recommendation
    
• Reference