... | ... | @@ -2,6 +2,8 @@ |
|
|
|
|
|
Because of the COVID-19 outbreak and its recent occurrence in the Netherlands, friends and family might soon be unable to visit patients in hospitals. Upon Reinier de Graaf's initiative, the idea is to set up an ad-hoc-project group made up of collaborators from multiple faculties and universities.
|
|
|
|
|
|
To see the current page flow, click [here](Page Flow).
|
|
|
|
|
|
#### Stakeholders (Potential Users)
|
|
|
|
|
|
Since this lockdown will in its essence mean that patients will be reliant on online communication, our target users are the ones who cannot facilitate this themselves, i.e. those that do not have smartphones / tablets / etc. nor the knowledge of how to use them. These patients are also split into two groups capable of two levels of communication:
|
... | ... | @@ -114,53 +116,3 @@ The following database schema has been created so far: |
|
|
- end time
|
|
|
- tablet [Tablet]
|
|
|
- patient [Patient] |
|
|
\ No newline at end of file |
|
|
|
|
|
### Admin Page Flow
|
|
|
|
|
|
`admin/index.html` has several sections each of which has links to several other pages:
|
|
|
|
|
|
##### Area
|
|
|
|
|
|
- `admin/area/add.html` for adding an area
|
|
|
- `admin/area/view.html` which display a list of all the areas (and the deletion possibility) and which in turn links to `admin/area/edit.html` for editing a specific area
|
|
|
|
|
|
##### Patient
|
|
|
|
|
|
- `admin/patient/add.html` for adding a patient
|
|
|
- `admin/patient/view.html` which display a list of all the patients (and the deletion possibility) and which in turn links to `admin/patient/edit.html` for editing a specific patient
|
|
|
|
|
|
##### Tablet
|
|
|
|
|
|
- `admin/tablet/add.html` for adding a tablet
|
|
|
- `admin/tablet/view.html` which display a list of all the tablets (and the deletion possibility) and which in turn links to `admin/tablet/edit.html` for editing a specific tablet
|
|
|
|
|
|
##### Settings
|
|
|
|
|
|
This is a section leads to the `admin/settings.html` page, which contains the possibility to set defaults for:
|
|
|
- time slot length
|
|
|
- transition time length (time between on time slot and another)
|
|
|
- the number of time slots allowed per patient per day
|
|
|
|
|
|
##### Calendar
|
|
|
|
|
|
*(will be done after the above is complete - for now, settings will be automated)*
|
|
|
|
|
|
This is a calendar where the tablets and time slots will be managed daily. This is something like the settings page, so most of the queries will probably be similar, but done per day instead of globally. A few things that need to be considered here due to the fact that the volunteer availability might differ each day:
|
|
|
- there need to be the ability to set it for multiple days in advance
|
|
|
- there should be the possibility to set it once and have the option to "repeat previous day"
|
|
|
|
|
|
The settings that need to be there for each day:
|
|
|
- shift start and end time per tablet
|
|
|
- time slot length (if not default)
|
|
|
- transition time length (if not default)
|
|
|
- number of time slots per patient (if not default)
|
|
|
|
|
|
### Guest Page Flow
|
|
|
|
|
|
The `/home` or `/` page will have a text field where families or friends can enter their 'security code' or login.
|
|
|
This will send them to a `/bookings` page where they can see the current bookings.
|
|
|
|
|
|
##### Booking
|
|
|
- `/bookings/add`: they can create a new booking and select a time slot
|
|
|
- `/bookings/edit`: they are able to edit their booking or cancel it
|
|
|
- `/bookings/view`: they are able to view a specific booking as well as the link to the waiting room |
|
|
\ No newline at end of file |