Table of Contents |
---|
Used documentation
Cookbook/ materials | Version | Location | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Therapeutic Link Web Service | 1.5 | |||||||||
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 Link | 2.0 | http://jira.ivlab.ilabt.imec.be/secure/attachment/17425/swagger_therlink_2-0-3.json | ||||||||
KMEHR | - | https://www.ehealth.fgov.be/standards/kmehr/en | ||||||||
Jira ticket MHEH-12 | - |
| Jira ticket MHEH-13 | - |
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
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:
...
The API eHealth Therapeutic Link provides four methods. It is noteworthy that in this use case only the Get a therapeutic link method is used.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-1418-BF | ||
Use case name | Consult the therapeutic links of a patient using the GET /therapeuticLinks/{patientSsin} operation | ||
Actors |
| ||
Short Description | |||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 1 | The client sends a GET /therapeuticLinks/{patientSsin} request | |
2 | The IAM connect sends the request to the Therapeutic link WS | ||
3 | The Therapeutic link WS finds information about the therapeutic link(s) of a patient | ||
4 | The Therapeutic link WS sends a JWT response to the IAM | ||
5 | The IAM connect receives the response and sends it to the client | ||
6 | The client receives information about the therapeutic link(s) of the patient | ||
Exceptions (exception flows) | |||
|
...