You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 27
Next »
Table of contents
Used documentation
- A person cannot be defined as a substitute if he is already absent for this period (or part of the period).
- It is however possible to introduce an OoO while being a substitute for someone else.
- A person may be substitute for several other persons.
- The absent person and his substitutes are persons, not organizations.
- A person is identified by his ID and his quality.
- There may be maximum five substitues per OoO.
- A maximum of ten periods OoO may exist per eHealthBox.
- OoO periods may not overlap.
- A period may not end later than J + 1 year.
- A period can last up to 1 year.
- The end date is mandatory.
A WS request contains one period and a maximum of five substitutes may be specified for that period.
The OoO activates automatically when the time is reached.
Basic flow
| Flow | Specifications |
|---|
| | ID | AP-UC04-BF | | Name | Set an out-of-office with 1 substitute | | Description | / | | Actor(s) | Two healthcare professionals: - One who will be OoO.
- One who will be the substitute.
| | Requirements | / | | Trigger | A user wants to set an out-of-office | | Precondition(s) | - The user is logged in.
- The user wants to set an out-of-office
| | Flow | - see Use case: login.
- When opening the OoO section, the application should automatically
request a list of already inserted OoO periods. - The inserted OoO period should be, for example,
from the next monday until friday of the same week. - Add the substitute (Example_Test_Actor). There are two ways to do this:
| | Postcondition(s) | - The OoO is successfully added.
| | Test Data | | | Endpoint(s) | |
|
