Used documentation

Cookbook/ materialsVersionLocation
Therapeutic Link Web Service1.5

https://www.ehealth.fgov.be/ehealthplatform/fr/data/file/view/3399dfc3f0cb61fd23ece9aee958084544888395?name=therapeutic_link_ws_cookbook_1_5_dd_20170905.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 Link2.0http://jira.ivlab.ilabt.imec.be/secure/attachment/17425/swagger_therlink_2-0-3.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 Link provides four methods. It is noteworthy that in this use case only the Get a therapeutic link method is used.


Basic flow

FlowSpecification








Use case ID

ATH-UC-18-BF

Use case name

Consult the therapeutic links of a patient using the GET /therapeuticLinks/{patientSsin} operation

Actors

  • Citizen

  • HC party

Short Description


Priority

1 (High)

Must have: The system must implement this goal/ assumption to be accepted.

Pre-Conditions

  • SSIN of the concerned patient 
  • SSIN of the HCP
  • Identifier of the healthcare party qualification (NIHDI) 
  • Qualification code of the healthcare party, also called quality (e.g.  persphysician, orgpharmacy, etc.)

Post-Conditions

  • Information about the patient (i.e. SSIN, first name and the last name)

  • The start date and the end date
  • Information about the HCP (i.e. SSIN, first name, last name and the qualification code)
  • The proof type of the therapeutic link

Steps (basic flow)

1

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

2The 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 

4The Therapeutic  link WS sends a response to the IAM  

5

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

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

Exceptions (exception flows)



  • Every time the end-user wants to consult the therapeutic link(s) of a given patient