| Table of Contents |
|---|
Used documentation
| Cookbook/ materials | Version | Location |
|---|---|---|
| eHealthConsent WS Cookbook | 1.9 | |
| API eHealth Consent | 2.0 | http://jira.ivlab.ilabt.imec.be/secure/attachment/17424/swagger_consent_2-0-2.json |
| KMEHR | - | https://www.ehealth.fgov.be/standards/kmehr/en |
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 consent can be managed by different types of end-users:
...
The API eHealth Consent provides five methods. It is noteworthy that in this use case only the Ge tPatient Consent method is used.
Basic flow
| Flow | Specification | ||
|---|---|---|---|
| Use case ID | ATH-UC-16-BF | |
Use case name | Consult the consent of a patient using the GET /consents/{patientSsin} operation | ||
Actors |
| ||
Short Description | This use case enables to consult the consent status of a given patient using the REST version of the WS Consent. | ||
| 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 /consents/ {patientSsin} request | |
| 2 | The IAM connect sends the request to the WS consent | ||
3 | The WS consent finds information about the consent of a patient | ||
| 4 | The WS consent sends a response to the IAM | ||
5 | The IAM connect receives the response and sends it to the client | ||
| 6 | The client receives information about the consent of the patient | ||
Exceptions (exception flows) | |||
Frequency |
| ||
...