Everything written on this page and all child pages are works in progress.
They will also be used as draft pages.
Table of contents
Use cases
Glossary
The Glossary of eHealth can be found here.
Abbreviations
Abbreviation | Name |
---|---|
AP | Apollo |
UC | Use case |
BF | Basic flow |
AF | Alternative flow |
EF | Exception flow |
STS | Secure Token Service |
ehBox | eHealthBox |
WS | Web Service |
ETEE | End-to-End Encryption |
OoO | Out-of-Office |
NISS INSS INSZ | National Security Number |
NIHII RIZIV INAMI | National Institute for Health and Invalidity Insurance Number |
Legend flows
Image | Meaning |
---|---|
User action | |
Automatic action. No user input required | |
Beginpoint | |
Endpoint | |
These numbers are steps in a flow that are further explained in the flow section of the use case specification |
Legend UML
Image | Meaning |
---|---|
/ | / |
To do for alle use cases
- Create a list of possible statuscodes for each response.
- For each response, create a table with each item of the response in it. Each item is one of the following options:
- Is important and has to be shown to the user;
- Is important but shouldn't be shown to the user;
- Is not important and shouldn't be shown to the user.