Changes between Version 12 and Version 13 of Vision


Ignore:
Timestamp:
12/21/17 06:45:05 (6 years ago)
Author:
Dajana Stojchevska
Comment:

1) Target added

Legend:

Unmodified
Added
Removed
Modified
  • Vision

    v12 v13  
    1 == Vision
     1= Hospital Management Service =
     2
     3== Revision History ==
    24||'''Date'''||'''Version'''||'''Description'''||'''Author'''||
    35||05.12.2017||Version 0.1||Initial version||Dajana S.||
     
    9193 [#p10.1 10.1 User Manual]
    9294
    93  [#p10.2 10.2 On-line Help]
     95 [#p10.2 10.2 Online Help]
    9496
    9597 [#p10.3 10.3 Installation Guides, Configuration, Read Me File]
     
    123125'''1.1 [=#p1.1] Purpose'''
    124126
    125 The purpose of this document is to specify and perceive the goals and capabilities of this system named ''Hospital Management Service''. It also states the various constraints which the system will be abide to. This document further leads to clear vision of the software requirements, specification and capabilities which are to be exposed to the development, testing team and end users of the software.
     127The purpose of this document is to specify and perceive the goals and features of this system named ''Hospital Management Service''. It also states the various constraints which the system will be abide to. This document further leads to clear vision of the software requirements, specification and capabilities which are to be exposed to the development, testing team and end users of the software.
    126128
    127129'''1.2 [=#p1.2] Scope'''
    128130
    129 The system being described generally provides management of all activities among the hospital staff and the patients. The system will be used in any hospital, clinic, dispensary or pathology laboratory in order to get information from the patients and then store that data for future usage.
    130 The current system in use is a paper-based system. It is too slow and cannot provide updated lists of patients within a reasonable time frame. The intention of the system is to reduce over-time pay and increase the number of patients that can be treated accurately. Requirements statements in this document are both functional and non-functional.
     131The system being described generally provides management of all activities among the hospital staff and the patients. The system proposes solution for the current public health care institutions in Republic of Macedonia, but could be used in any hospital, clinic, dispensary or pathology laboratory which needs computerized process, or if already has one - to improve it.[[br]]
     132The current system in use in Macedonian public health facilities is a paper-based system. It is too slow and cannot provide updated lists of patients' data within a reasonable time frame. By using our system the over-time pay would be reduced and the number of patients that can be treated accurately would be increased.[[br]]
     133Requirements statements in this document are both functional and non-functional.
    131134
    132135'''1.3 [=#p1.3] Definitions, Acronyms and Abbreviations'''
    133136
     137'''Institution''' - referencing the institution which is using our system, it can be any health care institution, facility (like ''Hospital'' or ''Ministry of Health'') that has bought a licence to use the system.
     138
     139'''Patient''' - institution's patient can be any citizen of any age who is regulated as a patient in the institution according to the laws and its policy.
     140
    134141'''Appointment''' is an arrangement to meet someone at a particular time and place. In this context we are going to use it for meeting a doctor when a patient has health issues.
    135142
    136 '''Patient''' - institution's patient can be any citizen of any age who is regulated as a patient in the institution according to the laws and its policy.
    137 
    138 '''Institution''' - referencing the institution which is using our system, it can be any health care institution (like ''Hospital'' or ''Ministry of Health'') that has bought a licence to use the system.
    139 
    140 '''Appointment request''' is a request for scheduling an appointment (visit to the doctor), after which the system should return possible time slots.
     143'''Appointment request''' is a request for scheduling an appointment (visit to the doctor), after which the patient chooses one of the offered time slots in order to have made an appointment.
    141144
    142145'''GP''' is an abbreviation for General Practitioner, that is a doctor that implies prevention, education, care of the diseases and traumas that do not require a specialist, and orientate the patients towards a specialist when necessary. Each patient must have one GP.
    143146
    144 '''Available time slot''' is the slot when a patient can get a scheduled appointment for their GP. It has to be free time slot when no other patients have scheduled appointments at the same GP. The average time expected time would be 15 minutes, but it is going to be regulated by the system administrator, according to the institution's policy.
     147'''Available time slot''' is the slot when a patient can get a scheduled appointment for their GP. It has to be free time slot when no other patients have scheduled appointments at the same GP. The average time expected would be 15 minutes, but it is going to be regulated by the system administrator, according to the institution's policy.
    145148
    146149'''PIN''' - personal identification number, it is a unique identifier for each citizen.
     
    154157'''1.5 [=#p1.5] Overview'''
    155158
    156 In the further part of the document, the objectives of the system are specified, what are the benefits of using it, the description of the environment for which this system is built, its users, alternative solutions are considered, functional as well as non-functional requirements etc.
     159In the further part of the document will be given explanation of the current problems and needs of the system's users and stakeholders along with their detailed description (all users and stakeholders profiles), then our proposed solution for them is given. In the middle can be found the objectives of the system, what are the benefits of using it, but also alternative solutions are considered. In the second half, the description of the environment for which this system is built is specified, functional and non-functional requirements, as well as guides for end users.
    157160
    158161'''2. [=#p2] Positioning'''
     
    376379'''9.4 [=#p9.4] Environmental Requirements'''
    377380
    378 If users need some help (they have technical problems or they don't know how to do what they want) they can use the On-line Help.
     381If users need some help (they have technical problems or they don't know how to do what they want) they can use the Online Help.
    379382
    380383'''10. [=#p10] Documentation Requirements'''
     
    384387All current employees of the institution using the system will get username and password. Of course the password can be changed later on. The patients will be able to create new account - to register.
    385388
    386 '''10.2 [=#p10.2] On-line Help'''
     389'''10.2 [=#p10.2] Online Help'''
    387390
    388391It is predicted the system to offer online help. It means that there will be a page where will be written some general guidelines for using the system, there will be a part ''FAQ'' (frequently asked questions), and for more complex problems like not being able to login and similar technical problems will be intervened by system administrators.