1.Industrial Training 2.Mini Project 3. Major Project(Phase 1)

1. 1.Industrial Training 2.Mini Project 3. Major Project(Phase 1) Guide: Asst.ProfAnju S.S Presented By Josmy T Jose S3-Mtech CSE Roll No:09

2. Overview of work done • Industrial visit -Location: Jubilee Mission Medical College & Research Institute, Thrissur -Period:Dec 22 to Feb 22 • Mini project -As Is document -To be document -IEEE paper: Integration of ICU data into electronic medical records-Issues & solutions - Android applications: Working on it • Major Project - Problem definition -Literature Survey -Solution Strategy -Implementation

3. Contents • Industrial training @ JMMC • Mini Project : Laboratory Linkage for NICU Automation in JMMC. • IEEE conference paper “Integration of ICU data into Electronic Medical Records- Issues and Solutions” • Main Project: Server side architecture for ICU automation system

4. INDUSTRIAL TRAINING @ JMMC Thrissur

5. Health Care Industry • The healthcare industry is one of the world’s largest industry and India is emerging as a major player in this industry, because of its high population.  • The major inputs of health care industries • Hospitals • Medical insurance • Medical software • Health equipments • The service marketing structure • Company • Customer • Provider

6. JMMC- Introduction • JMMC, a Christian Minority Institution, established in the year 1952 makes the modern medical facilities available to common man • 35 departments running successfully in the 4 blocks • Golden Jubilee Block • Hridayalaya • St. Thomas Block • Medical College Block • Super specialty departments • Medical education and research. • Hospital Information Management System • Biomedical Department • MRD • Laboratories

7. Departments.. • Anesthesiology • Anatomy • Biochemistry • Blood Bank • Cardiology • Cardiovascular Science • Community Medicine • Dentistry Maxillofacial Surgery • Ophthalmology • Orthopedics • Pediatrics

8. Cont.. • Forensic Medicine • Gastroenterology • General Surgery • Laboratory Medicine • Microbiology • Neonatology • Nephrology • Neurology • Obstetrics & Gynecology • Dermatology • Endocrinology • ENT Head & Neck Surgery

9. Cont.. • Pathology • Pharmacology • Physiology • Physiotherapy & Rehabilitation • Psychiatry • Pulmonary Medicine • Radiology • Urology and • Vascular Surgery

10. Working Model of JMMC Internet Administration, Emergency Hridayalaya Central Server Biomedicalunit Intranet St.Thomas Block Medical College Block Golden Jubilee Block Laboratory

11. Further Details are Given in the Industrial Visit Report

12. Mini project Laboratory Linkage For ICU Automation in JMMC

13. Introduction • ICU patients is having need of constant monitoring and support using specialized equipments and medication • Patients are transferred to the ICU either from a ward, casuality ,or immediately after a surgery • The interactions among doctors, nurses ,equipments and the patients constitutes the ICU workflow • Even though hospital automation is present in other departments, ICU still operates on paper and pen. JMMC is no exception. • The current system study done here brought out the necessity of automation of ICUs for PMR to EMR transition.

14. ICU Proceedings.. • New patient admission to ICU • Primary diagnosis and Test prescriptions • Lab Tests • Patient Care • Updating PMR • Discharge/Death • PMR moved to MRD

15. Workflow –Nurse’s Perspective

16. Workflow –Patient Perspective

17. Laboratory- Present scenario • Nurses updates Investigation laboratory record • Test request is forwarded to the laboratory with the test code and category name using system • Sample collection. • Transfer samples and request form to the lab • Results are available from the central server in the lab • A barcode indicating result is stamped in the request form and returned back to ICU

18. Lab proceedings-Proposed Architecture Hospital LAN ICU SERVER LAB SERVER Request Tablet wi-fi Response

19. Proposed System • Nurses can submit the request queries by selecting the patient id • The prescribed tests will be available in the selection box • The corresponding test codes are also selected and request is submitted • The laboratory of JMMC is fully automated • So the results are available in the ICU tablet • Results are notified with some notifications or alerts. • Integration of ICU and Lab databases need to be done for the proper working.

20. UI Design for the lab request

21. UI design for the lab result

22. Advantages • Avoids the bidirectional transfer of request forms • Thus avoids the barcode sticking process in the request form • Print out of the result can be directly taken from the ICU • Alerts and Notifications simplifies the process • The result will be automatically added to the EMR of patient

23. IEEE Conference Paper:Integration of ICU data into Electronic Medical Records- Issues and Solutions • Paper Submitted on : February 12 • Paper get accepted on : February 27 • To be presented on : April 11 or 12 • Venue : Kanyakumari • Category : Networks – e-health • Co-ordinator : Dr.GeorgeVarkey • Guide : Ast.ProfAnju S.S • Authors : Dhanyaja . N, AshaYeldose,Josmy T Jose,

24. MAJOR PROJECT(PHASE 1) Server Side Architecture For ICU Automation System

25. Problem Statement • Develop the Server Side Architecture most optimum for ICU Automation System with Tablet PCs • Tablet PC communication is characterised by: • Limited band width • Small packets • Unpredictable delaybetween consecutive packets • Existence of alternate channels with differing priority values • Server Side Architecture Should Account for these • Extension of Mini Project • The system should become operational in JMMC

26. ICU Automation System . • There is a central server in the ICU ,which is responsible for all the information flows among the tablets and the server. • The ICU sever is connected to the hospital central server • The information stored in the central server is available everywhere • Each nurse in the ICU will have a tablet PC connected to the ICU server through Wi-Fi

27. Hardware Architecture

28. Representative software Architecture • Tablet Platform – Android (Ginger Bread or above) • Java Framework-Spring • Technology-Hibernate • Database – PostgreSQL • Server OS-Ubuntu • Server – JBoss • Developing Environment –Eclipse

29. Constraints • Selection of server side architecture depends mainly on the nature of our application requirement • Architecture that supports tablet platform is the prime concern • Cost of Implementation

30. Solution Strategy • Literature Survey • Examination of Different architectural plans • Client-Server • n-Tier • SoA • HTML 5 • Trial Implementation • Finalization of Selected architecture • Final Implementation

31. Development Process Development Running

32. Test Plan • Applications can be tested in the android emulator by creating an AVD • The ADT pluggin will automatically create a default run configuration for the project • The Android framework includes an integrated testing frame work • Following this we will use testing systems like “Load Runner” to decide on load performance • The above will decide on the design to be used for final product

33. Integration Issues • The problem of connecting with the central hospital server • Modifications in Central DBMS • Low signal strength of Wi-Fi • Malware • Staff training and system acceptance • Change Management and version control

34. THANKYOU

35. QUESTIONS