| Table of Contents |
|---|
Used documentation
| Cookbook/ materials | Version | Location | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Therapeutic Exclusion Cookbook | 1.2 | |||||||||
| Identity & Authorization Management (I.AM) Token eXchange Technical specifications | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/nl/data/file/view/83dd54fee269ec086696b0290d242907c6e9f994?name=IAM%20Connect%20Token%20eXchange%20-%20Tech%20Specs%20v1%20-%2004072018.pdf | ||||||||
| API eHealth Therapeutic Exclusion | 2.0 | http://jira.ivlab.ilabt.imec.be/secure/attachment/17431/17431_ExclusionSwagger.json | ||||||||
| KMEHR | - | https://www.ehealth.fgov.be/standards/kmehr/en | ||||||||
| Jira ticket MHEH-12 | - |
| ||||||||
| Jira ticket MHEH-13 | - |
| ||||||||
| Jira ticket MHEH-18 | - |
| ||||||||
| Jira ticket MHEH-20 | - |
| ||||||||
| Jira ticket MHEH-26 | - |
| ||||||||
| Jira ticket MHEH-31 | - |
| ||||||||
| Jira ticket MHEH-32 | - |
|
General information
In the figure below, we present a logical view about the relationship between the three basic services of the ehealth platform that are the WS Consent, the Therapeutic link WS, and the Therapeutic exclusion services. A Therapeutic link can be managed by the following end-users:
- Citizen: a patient, a parent of a patient, a mandatary
Basic flow
| Flow | Specification | ||
|---|---|---|---|
Use case ID | ATH-UC-19-BF | ||
Use case name | Consult the therapeutic exclusions of a patient using the GET /therapeuticExclusions/{patientSsin} operation | ||
Actors |
| ||
Short Description | This use case enables to consult the therapeutic exclusion of a given patient using the GET /therapeuticExclusions/{patientSsin} operation of the REST version of the Therapeutic Exclusion WS. | ||
| Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 1 | ||
| 2 | |||
3 | |||
| 4 | |||
5 | |||
| 6 | |||
Exceptions (exception flows) | |||
| |||