html5-img
1 / 9

Unified Hospital

Unified Hospital. SIDDHARTH GUPTA SURABHI SATAM RAMAKRISHNAN CH COLLEGE OF COMPUTING GEORGIA INSTITUTE OF TECHNOLOGY. Case Study. A doctor has just been called-in for an emergency surgery in ICU/OT. He wants to administer local anesthesia to the patient.

myra-hurley
Download Presentation

Unified Hospital

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unified Hospital SIDDHARTH GUPTA SURABHI SATAM RAMAKRISHNAN CH COLLEGE OF COMPUTING GEORGIA INSTITUTE OF TECHNOLOGY

  2. Case Study • A doctor has just been called-in for an emergency surgery in ICU/OT. • He wants to administer local anesthesia to the patient. • He also is aware of the fact that the medication which this patient is on, may not allow him to administer some types of anesthesia. • He goes to the nearby computer to access the patients medical record, only to find that this data is not available there and he will have to run and check this information from the OPD.

  3. What is the problem? • The problem here is simply the fact that • Lot of software is available in hospital but the software is incompatible with each other… • Lot of data is still available in paper.

  4. ProblemStatement - Detailed • Piedmont Hospital - Case Study • Lot of scattered data from heterogeneous databases • Multiple paper documents which need to be managed centrally • Mismanagement of patient records and report history • Various applications such as billing, scheduling, emergency, cardiac, operating theater, etc are not inter-operable. • Leads to complexities during data/info retrieval • Leads to inserting/adding same data into different applications.

  5. Solution • Abstract application layer that accesses the underlying heterogeneous sources of data and presents a unified view • Access to one centralized database management system • Physicians update patient records in any application will be pulled into the new database. • Patients will have access to Personal Health Records(PHR) • Secure access to the database by both physicians and the patients.

  6. Solution Architecture DB 1 New - Database Application 1 DB 2 Application 2 Unified Hospital DB 3 Application 3

  7. Solution Architecture - Explained • Create a new application which will be having modules to operate multiple databases. • It will periodically pull the information from these databases and populate its global database. • The application will also give a unified view of all the information. • Slowly this application will replace all the existing heterogeneous application.

  8. Pros and Cons … • Pros.. • Best solution under the circumstances. • Will allow the usage of older applications. • No need for educating the new software • Highly efficient due to redundancy • Collapses all the information into central repository • Cons.. • Duplication of information • New solution will take time to replace existing one.

  9. Conclusion • Ease out the documentation and information retrieval. • More control over the data and representation. • More flexibility • Faster and unified data access • Need to learn only one software

More Related