Used documentation

Cookbook/ materialsVersionLocation
Therapeutic Exclusion Cookbook1.2

https://www.ehealth.fgov.be/ehealthplatform/fr/data/file/view/ddac01f047142783690a4e7fa39019bfd0615e81?name=Therapeutic%20Exclusion%20WS%20-%20Cookbook%201.2%20dd%2025102018.pdf

Identity & Authorization Management (I.AM) Token eXchange Technical specifications1.0https://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 Exclusion2.0http://jira.ivlab.ilabt.imec.be/secure/attachment/17431/17431_ExclusionSwagger.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 Therapeutic link can be managed by the following end-users:


The API eHealth Therapeutic Exclusion provides five methods. It is noteworthy that in this use case only the Get therapeutic exclusion method is used.

Basic flow

FlowSpecification






Use case ID

ATH-UC-19-BF

Use case name

Consult the therapeutic exclusions of a patient using the GET /therapeuticExclusions/{patientSsin} operation

Actors

  • Citizen (i.e. a patient, a parent of a patient, a mandatary)

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

  • The identification the concerned patient (i.e. SSIN)
  • The identification the excluded HCP (i.e. SSIN)
  • The identification of the HCP (i.e. NIHII) in order to retrieve organizations like pharmacies

Post-Conditions

  • The identification the concerned patient (i.e. SSIN)

  • Information about the HCP (SSIN, NIHII, first name, last name, qualification code)

Steps (basic flow)

1

The client sends a GET  /therapeuticExclusions/{patientSsin} request 

2The IAM connect sends the request to the Therapeutic Exclusion WS

3

The Therapeutic exclusion WS finds information about the therapeutic exclusion(s) of a patient 

4The Therapeutic  link WS sends response to the IAM  

5

The IAM connect receives the response and sends it to the client

6The client receives information about the therapeutic exclusion(s) of the patient

Exceptions (exception flows)



  • Every time the end-user wants to consult the therapeutic exclusions of a given patient