Published on August 21, 2007
Clinical Record Management: Clinical Record Management By Shimna KP Introduction: Introduction Since the medical information system has becoming more and more important in nowadays, the role of Clinical Record Manager has been increased. Whenever a patient enquire after some days, data must be available and it should be retrieved fast. Clinical Record Manager provides an efficient system to document the treatment process from the point of initial contact up to termination of treatment. Background : Background Existing System Problems of existing system Need for the proposed system Proposed System Existing System: Existing System The current existing system stores only the inpatient details only. When a new patient arrives for consultation, a registration is maintained and a number is provided. Each patient is then referred further. At sometimes patient will be admitted. In that case an inpatient number is provided there also. All the outpatient details are stored manually since they are in many. Problems of Existing System: Problems of Existing System Since the outpatient details are stored manually whenever a patient enquires his/her details of earlier visit details it cannot be retrieved soon. It takes time to search and find the details. Need for Proposed System : Need for Proposed System Storing Outpatient details will provide fast retrieval of data for enquiry purpose. Maintaining separate record will easy be retrieved. Proposed System : Proposed System In the proposed system it maintains both the inpatient as well as outpatients details separately. This software provides an easy way to handle registration and other storing details. The Proposed System includes: The Proposed System includes Department information system Doctors information system Lab information system Room information system Patients information system Specification and Design: Specification and Design Hardware Specification Processor : Pentium IV Processing speed : 2GHz RAM : 128 MB Hard Disk : 80 GB Software Specification Operating System : Windows 2000 Front End : VB.Net Back End : MS -SQL Server Design : Design Use-Case Model survey Use-Case Diagram Sequence Diagram Class Diagram Architecture Diagram Use-Case Model Survey: Use-Case Model Survey Problem analysis Hence the first step is to identify actors and use cases. Actors are: Patient Doctor Lab technician Terminal operator Use Case Diagram: Use Case Diagram Sequence Diagram: Sequence Diagram Class Diagram : Class Diagram Architecture Diagram: Architecture Diagram Data Design : Data Design Slide17: Slide18: Slide19: Slide20: Slide21: Implementation : Implementation This project turned into an automated system which stores both inpatient and outpatient details separately. RESULTS & EVALUATION: RESULTS andamp; EVALUATION Slide24: Test Case 2: Future Work: Future Work This software stores inpatient as well as outpatient details from the registration up to the termination of the consulting process. This software is better if it is done using web based. So that doctor can also login and by entering the patient number directly he can store the patient details. This will be very useful if it is stored separately. In other case the lab also can maintain this software very well if the patient data is transferable across different sections. Conclusion: Conclusion In the old system the details of only the inpatient are stored in computer. The outpatient details are kept manually. This is done since the numbers of patients are many. By doing this process it is time consuming for to get the details whenever patient comes for further enquiry of his earlier visit. But in our software it provides easy to maintain both the outpatient as well as inpatient details separately. References: References Roger S. Pressman, 'Software Engineering', Sixth Edition Ali Bahrami, 'Object Oriented Systems Development'