| |Name of the Project |Paperless Hospital Service (Healthcare domain) | | |Objective/ Vision |Objective of this project is to leverage paperless hospital service where patient need not do any paper-work | | | |while getting admitted to the hospital by providing seamless application that will handle the thousands of | | | |patient information and provide efficient healthcare service. It is to align with SMART PLANET theme of IBM.
| | |Users of the System |Patient/Relative | | | |Admitting Clerk | | | |Department Admin | | | |Doctor/Nurse | | | |Billing Department | | | |Healthcare Insurance Providers (External Actor) | | |Functional Requirements |Patient will go to hospital and get admitted by giving their information to the Admitting Clerk. If Patient is | | |(Atleast Eight) |in serious state, relative will help in giving information about the patient to the Admitting Clerk.
| | | |If the incoming patient is New, then Admitting Clerk will create a new record in Web Portal and store the | | | |patient information by collecting all necessary details and also about health history. And will provide Patient | | | |ID which will be sent via sms to patient’s mobile number. | | | |Admitting Clerk will assign the In-coming Patient Record to the Department Admin and direct the Patient to meet | | | |the Department Admin.
| | | |Department Admin will assign the Patient to the respective Department like ENT, ICU, Surgery, etc and also will | | | |assign Doctors/Nurses who will be responsible to treat the Patient | | | |Doctor will get patient information by querying on Patient ID and will conduct series of tests and will update | | | |their test report along with comments in the Application | | | |Billing Department will calculate the expense and will be responsible to verify if Patient has Insurance Policy,| | | |if so then they will open a secure session to charge the cost to Insurance providers.
| | | |If Patient doesn’t have Insurance Policy, then he must pay either in cash or credit/debit cards | | | |Insurance Providers will verify the claim and will confirm whether the Insurance ID and policy coverage is valid| | | |or not | | | |Following operations are exposed in Web service: | | | |Create Patient Record | | | |Modify Patient Record | | | |View Patient Record | | | |Delete a Patient Record | | | |Bill to Insurance Providers | | | |Bill to Patient | | |Non-functional requirements | Secure access of confidential data (user’s details). SSL can be used.
| | |(Atleast Four) |24 X 7 availability | | | |Better component design to get better performance at peak time | | | |Flexible service based architecture will be highly desirable for future extension | | |Optional features |None | | |User interface priorities |A. Professional look and feel | | | |B. Use of Graphical tool like JASPER to show strategic data | | | |C. Reports exportable in . XLS, . PDF or any other desirable platform independent format | | |Reports |None | | |Other important issues |None | | |Team Size |2 – 4 members | | |Technologies to be used |UML, J2EE, XML, e-Forms, XForms/Java/C,C++, AJAX, Web 2.
0, Web-services, SOA | | |Tools to be Used |Lotus Form Designer/Eclipse/RAD | | | |WebSphere Portal/ WAS, Webservices/SOA | | | |DB2 Express C | | |Final Deliverable must include |A. Online or offline help to above said users, Application deployment executive and developer | | | |B. Application archive ( . war/. ear ) with source code | | | |C. Database backup and DDL Script | | | |D. Complete Source code | | |Advantages of using pureXML? |Paperless Hospital rules will change and so do the return forms.
Every year the forms need to accommodate new | | | |change and still be able to process them effectively. This is where the XML design will make it flexible and | | | |the developer will be easily able to handle this change in design with minimum impact on the application. The | | | |database design does not change. | | | |Because of the use of XForms which generate XML data as input, its easy to consume (gather) all user | | | |information in a single XML document and store it as a single entity without breaking it up into pieces as done| | | |is case of relational database.
| | | |Since the data will be stored in a single XML document, its easy to fetch it using a simple XQuery without any | | | |complex joins. | | | |Since the data is stored as XML, it is vey easy to construct SOAP messages from this XML content as no | | | |relational to XML transformation is required. | | | |
Use of XSLT to report data in multiple format is now possible because of the XML data model | | |Pictorial Representation |[pic] | ———————– PureXML is used Web Service JSP/J2EE App JAXP & SAX IBM Lotus Forms App DB2 WAS Java App JAXP & SAX.