4 Overview of Document This document provides a description of the requirements of the product.

Section 2 of the Software Requirement Specification gives the detailed descriptions of t he product including the data requirements. Section 3 provides specific function alrequirements of the different components of the product and the performancecri teria. 2. General Description Top 2.1 User Characteristics The user will have to be familiar with the billing module. If needed, the user s hould be trained up to use this module.The user may be an administrator, nurseor a cashier. It depends upon the particular hospital. 2.2 Product Perspective The product requires a browser .It will support IE 5.0+, N 4+, Mozilla 1+, andOp era. External interfaces include keyboard and mouse, enabling navigationacross s creens. 2.3 Overview of Data Requirements The user will enter all the billing information for a particular patient. This w illinclude the type of the patient (inpatient/outpatient and corporate/individua l), type of billing (for inpatient the mode of bill payment may be postpaid but for outpatient itshould be prepaid). The user will also have to select the labo ratory tests done by the patient, the date of discharge of the patient and the a mount of discount if there isany. 2.4 General Constraints, Assumptions, Dependencies, Guidelines This application depends on client-server architecture. It will require anintern et (http) server that is able to run PHP applications. 2.5 License type Once this module is applied as a separate stand-alone product outside theframewo rk of Care 2002, this module is still licensed with the GNU GPLlicense type. 3. Specific Requirements Top 3.1 External Interface Requirements Input from the user will be via keyboard input and mouse point and click. Theuse r will navigate through the software by clicking on icons and links. The iconswi ll give appropriate responses to the given input 3.2 Detailed Description of Functional Requirements This section provides a requirement overview of the product. The project will be on PHP and the backend will be Mysql.The requirements are described below:The us er will be able to search a patient either by his name (given name or familyname ) or patient /visit no. If the search result yields more than one patient ? s data,then information (already stored in the database through ? Admission ? module)of all those patients will be displayed. The user then will be able to se lect the particular patient he is looking for.The informations that are to be di splayed automatically are:1) The patient ? s name2) Address3) Date of Birth4) Marital Status5)

Sex (M/F) 6 ) Patient no.7) Admitted By8) Date of Admission9) Patient ? s type (inpatient/outpatient)10) DiagnosisFollowing functionality will be present: The user will select the type of the patient (corporate/individual). If the pati ent is acorporate, the name/code of the corresponding organization should be ent ered. For inpatient the mode of payment will be postpaid by default and for outpatient it should be prepaid. However the user will be able to change it if he wants. If the patient is a corporate, his bill will be sent to the concerned organizati onand the payment will be postpaid irrespective of whether he is an indoor or ou tdoor patient. The billing information also includes the bill for each type of service. A patie nt ? s total bill should be shown in slabs: ? The slabs are: Hospital Service Pharmacy Billing Laboratory Billing 1) Bill for consultation1) Brand Name of theMedicine1) Type of Labtest/service2 ) Bill for LaboratoryTests or Investigations (e.g. X-ray, CT-scan)2) Batch No. 2 ) Brief description3) Bill at the time of Admission3) Date of Expiry 3) Price pe r unit4) Bill for BedAllocation4) Price Per Unit 4) Quantity (no.of.pcs)5) Bill at the time of Discharge5) Quantity (No.of pieces)5) Total Price 6 ) Total Price In case of Hospital services, there will be an interface for the user to input t hename of the services and its cost. Hospital services can include services byde partment (e.g. radiology, cardiology, and orthopedics). Also it may includecosts of equipment used when a patient is operated upon. In the case of Laboratory Tests, there will be an interface to input the name of

thetests available (in the particular hospital), its ? item/test no. ? (if there is any) and itscost /unit since the names of the tests and the corresp onding costs per unit may varyfrom hospital to hospital. All the available tests will be displayed with checkboxesin the ? select laboratory test ? form. The user will select the tests done by a particular patient. He will also enter how many times a particular test is done by the patient. In the final billing report, only the selected tests will be displayed withcorresponding ? costs per unit ? , ? Total cost of the particular test ? and ? item no ? .The total costs of all the tests will be calculated automatically. A part of the bill may have to be paid in advance at the time of admission. Ther ewill be a provision to enter the amount paid in advance. If this condition does notarise, the user will simply leave it blank and in the final bill this amount will bedisplayed as 0.00 The ? Total amount ? and ? Final amount to be paid ? by the patient will bedisplayed at the bottom of the final bill. The final amoun t to be paid is actually the ? Total amount ? ? ? Amount paid in advance ? . In case of no advance payment,the ? Total amount ? and the ?

Final amount to be paid ? will be same. If somehowthe ? Amount paid in advance ? is more than the ? Total Amount ? , the patient willget back an amount of ? Amount paid in advance ? ? ? Total amount ? . The patient may be offered an amount of discount on his total amount of bill. Th euser, in that case, will enter the amount of ? discount in percentage ? . Otherwise hewill simply leave it blank. The patient will pay either in cash or by credit card. The user will select it f rom acombo-box. There will be provision to display and print the final billing report. It should beformatted in a way that it can be simply folded and inserted in a windowed en velopeand ready for mailing There will be provision to email the billing report to a patient or to its insur ancecompany. There will be provision to batch print a batch of billing reports. The user shou ld beable to list a group of patients and just select via checkboxes the billing reports to be batch printed.A "select all" button will also be there. 3.3 User Input Validation If the user leaves a mandatory field blank, he will be prompted to enter valid d ata in that particular field.In the interface to input new bill items, when the item number is not auto-generated, thenumber that the user enters shoul d be checked against possible duplication. Once a possible duplication is detected, the interface sh ould prompt the user to select one of thesuggested numbers (smartly auto-generated basing on the user's initial entry). A list of alternatives immediately will be given to the user It will be possible to detect that a certain service is billed twice which should n

ot occur in normal cases, or a certain drug is prescribed beyond a certain dosage or frequen cy (or worse in deadly amounts). hospital management srs this is srs for hospital management system if you need something specific then l eave reply Add To Collection 5.0K Reads 41 Readcasts 5 Embed Views Published by aryan98876 TIP Press Ctrl-F to search anywhere in the document. Info and Rating Category: How-To Guides/Manuals Rating: Upload Date: 09/07/2010 Copyright: Attribution Non-commercial Tags: No tags Free download or readfalse online for free. Flag for inappropriate content Recommended