THIS SPACE IS UNDER CONSTRUCTION

Used Documentation

CookbookVersionLocation
Therapeutic Link WS Cookbook1.6https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealth-therapeutic-links

General Information

Management of the Therapeutic Links: 

  • The eHealth consent WA will allow both patients (incl. patient's parents or mandataries) and authorized HC parties to manage the therapeutic links (declaration, revocation and consultation)
  • The authorized HC parties, citizin (incl. concerned patients, parents of patients or patient's mandataries) are also able to perform the same operations throughout their usual software by calling the eHealth therapeutic link WS. 
  • The authorized HC organizations are only authorized to verify the existence of the therapeutic links before allowing the HC parties ti access the medical data of the patients by calling the therapeutic link consultation WS through their application. 


The existence of a therapeutic relation is one of the fundamental prerequisites for the healthcare (HC) providers to access a patient’s medical data. Therefore, the eHealth platform makes available to the actors
involved in the exchange, storage or referencing personal data, a relay service to manage those therapeutic relations and associated means of evidence.

This relay service is obviously limited to kinds of therapeutic links made available at the eHealth platform level by the ‘owner’ of this therapeutic link (such as the HC party declaring a therapeutic link or the actor responsible
of a recognized specific database, e.g. for Global Medical File relation). A therapeutic link is a relation between a patient and a HC party for a certain type of therapeutic
relation over a period of validity depending on the given evidence. It is not possible to update an existing the therapeutic link; to update information you first need to revoke the existing therapeutic link.


However, the period of validity of an active therapeutic link could be extended on the condition that

  • The start date of the new period is greater or equal to the start date of the period to be extended 
  • The end date of the new period is greater than the end date of the period to be extended (overlap of period of validity) 


The following operations (request-response operation type) will support the management of these links:

PutTherapeuticLinkUsed to declare the therapeutic links. Its main purpose is to allow one to
declare a therapeutic link.
RevokeTherapeuticLinkUsed to revoke the therapeutic links. Its main purpose is to allow one to “end”
the (declaration of a) therapeutic link.
GetTherapeuticLinkUsed to consult therapeutic links according to basic search parameters. Its main
purpose is to allow one to check the existence of the therapeutic links when
executing a consultation process
HasTherapeuticLinkUsed to check the existence of a therapeutic link

 The therapeutic links are managed according to the rules corresponding to the type of therapeutic link through: 

  • Specific webservices (WS) by HC professionals as end-users through their usual software or through an authorized organization
  • A dedicated web application (WA), currently called eHealth Consent with following end-users: Patients and HC professionals/ HC professionals within an organization



Declare/PutRevokeConsult (Get)Has
Citizen (patient, parent, mandatary)YesYesYesYes
Authorized HC Parties (HC professionals)YesYesYesYes
Authorized HC organizationsNoNoYesYes



KMEHR

This service is a ‘KMEHR-based’ WS. We thus strongly recommend consulting the documentation related to the KMEHR normative elements. The KMEHR site aims to offer a central point for the documentation of the KMEHR normative elements.

https://www.ehealth.fgov.be/standards/kmehr/en

The three following generic elements are, in particular, essentials to build the request and the reply of the therapeutic link WS.

Basic Flow

FlowSpecifications

IDUC-233-BF
NamePut Therapeutic Link - HC Professional within a pharmacy - eID encoding 
Description

Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party.

HC professional within a pharmacy acts as author of the Put Therapeutic Link. The given proof is the e-ID encoding of the patient. Certificate used to access the WS Therapeutic Link is the eHealth Certificate of the end-user (HC Organization). 

Actor(s)HC Professional in a pharmacy who is the pharmacy holder
Requirements
  • End-user is a HC professional in a pharmacy who is the pharmacy holder
  • End-user manages the therapeutic links throughout his usual software
  • Valid eHealth Certificate of the pharmacy
  • e-ID card of concerned patient 
  • Identification HC professional 

     °Identifier pharmacy: NIHII, HC professional category

     °Identifier pharmacy holder: SSIN, NIHII (if available), HC party category

  • Information therapeutic link

     °Identification concerned patient: SSIN, e-ID card, first and family name

     °Identification concerned HC party: NIHII (8digits), HC party category, organization name (optional)

  • Type of therapeutic link: pharmacydelivery 
  • Period of validity: 15 months
  • Inclusive start date (optional)
  • Exclusive end date (optional)
  • Comment to justify the declaration (optional)
  • Type of proof: e-ID encoding
TriggerThe user wants to put a therapeutic link 
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth WS Therapeutic Link
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Therapeutic Link
  6. The user does a request for Put Therapeutic Link
  7. The Put Therapeutic Link Request is sent to the WS Therapeutic Link 
  8. The Therapeutic link is created in eHealth Database
  9. The request is logged
  10. The WS Consent responds with a Therapeutic Link Response
Post Condition(s)
  • Request is logged
  • The Therapeutic Link is created in eHealth Database
Test Data
End point(s)Therapeutic Link Database
Remarks

3 possible types of eID encodig: 

  • eidencoding_housecall
  • eidencoding_nocard
  • eidencoding_techproblem
  • Start Date: If not provided then the start date is enriched with the date when the declaration request is processed i.e. the current date
  • End Date: If not provided, then the end date is enriched with the ED=SD+ the default period of validity. Default period: ED=SD+15 months
Additional InformationFor the overlapped relations, the start date of the new period must be greater or equal to the start date of the period to extended and the end-date of the new period must be greater than the end-date of the period to be extended

Alternative Flow

FlowSpecifications

IDUC-233-AF01
NamePut Therapeutic Link - HC Professional within a pharmacy (Pharmacist isn't pharmacy holder)  - eID encoding 
Description

Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party.

HC professional within a pharmacy acts as author of the Put Therapeutic Link. The given proof is the e-ID encoding of the patient. Certificate used to access the WS Therapeutic Link is the eHealth Certificate of the end-user (HC Organization). 

Actor(s)HC Professional in a pharmacy who isn't the pharmacy holder
Requirements
  • End-user is a HC professional in a pharmacy who isn't the pharmacy holder
  • End-user manages the therapeutic links throughout his usual software
  • Valid eHealth Certificate of the pharmacy
  • e-ID card of concerned patient 
  • Identification HC professional 

     °Identifier pharmacy: NIHII, HC professional category

     °Identifier pharmacy holder: SSIN, NIHII (if available), HC party category

     °Identifier end-user: SSIN, NIHII (if available), HC party category

  • Information therapeutic link

     °Identification concerned patient: SSIN, e-ID card, first and family name

     °Identification concerned HC party: NIHII (8digits), HC party category, organization name (optional)

  • Type of therapeutic link: pharmacydelivery 
  • Period of validity: 15 months
  • Inclusive start date (optional)
  • Exclusive end date (optional)
  • Comment to justify the declaration (optional)
  • Type of proof: e-ID encoding
TriggerThe user wants to put a therapeutic link 
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth WS Therapeutic Link
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Therapeutic Link
  6. The user does a request for Put Therapeutic Link
  7. The Put Therapeutic Link Request is sent to the WS Therapeutic Link 
  8. The Therapeutic link is created in eHealth Database
  9. The request is logged
  10. The WS Consent responds with a Therapeutic Link Response
Post Condition(s)
  • Request is logged
  • The Therapeutic Link is created in eHealth Database
Test Data
End point(s)Therapeutic Link Database
Remarks

3 possible types of eID encodig: 

  • eidencoding_housecall
  • eidencoding_nocard
  • eidencoding_techproblem
  • Start Date: If not provided then the start date is enriched with the date when the declaration request is processed i.e. the current date
  • End Date: If not provided, then the end date is enriched with the ED=SD+ the default period of validity. Default period: ED=SD+15 months
Additional InformationFor the overlapped relations, the start date of the new period must be greater or equal to the start date of the period to extended and the end-date of the new period must be greater than the end-date of the period to be extended

Exception Flow 1

FlowSpecifications

IDUC-233-EF01
NamePut Therapeutic Link - HC Professional within a pharmacy - eID encoding - HC party performing the declaration does not belong to the same HC party category as the HC party concerned by the therapeutic link
Description

Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party.

HC professional within a pharmacy acts as author of the Put Therapeutic Link. The given proof is the e-ID encoding of the patient. Certificate used to access the WS Therapeutic Link is the eHealth Certificate of the end-user (HC Organization). HC party performing the declaration does not belong to the same HC party category as the HC party concerned by the therapeutic link

Actor(s)HC Professional in a pharmacy who is the pharmacy holder
Requirements
  • End-user is a HC professional in a pharmacy who is the pharmacy holder
  • End-user manages the therapeutic links throughout his usual software
  • Valid eHealth Certificate of the pharmacy
  • e-ID card of concerned patient 
  • Identification HC professional 

     °Identifier pharmacy: NIHII, HC professional category

     °Identifier pharmacy holder: SSIN, NIHII (if available), HC party category

  • Information therapeutic link

     °Identification concerned patient: SSIN, e-ID card, first and family name

     °Identification concerned HC party: NIHII (8digits), HC party category, organization name (optional)

  • Type of therapeutic link: pharmacydelivery 
  • Period of validity: 15 months
  • Inclusive start date (optional)
  • Exclusive end date (optional)
  • Comment to justify the declaration (optional)
  • Type of proof: e-ID encoding
  • HC party performing the declaration does not belong to the same HC party category as the HC party concerned by the therapeutic link
TriggerThe user wants to put a therapeutic link 
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth WS Therapeutic Link
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Therapeutic Link
  6. The user does a request for Put Therapeutic Link
  7. The Put Therapeutic Link Request is sent to the WS Therapeutic Link 
  8. The WS Consent responds with a Therapeutic Link Response: error message
Post Condition(s)Error message
Test Data
End point(s)Therapeutic Link Database

Exception Flow 2

FlowSpecifications

IDUC-233-EF02
NamePut Therapeutic Link - HC Professional within a pharmacy - eID encoding - A valid therapeutic link of the same type and for the same HC party already exists
Description

Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party.

HC professional within a pharmacy acts as author of the Put Therapeutic Link. The given proof is the e-ID encoding of the patient. Certificate used to access the WS Therapeutic Link is the eHealth Certificate of the end-user (HC Organization). A valid therapeutic link of the same type and for the same HC party already exists

Actor(s)HC Professional in a pharmacy who is the pharmacy holder
Requirements
  • End-user is a HC professional in a pharmacy who is the pharmacy holder
  • End-user manages the therapeutic links throughout his usual software
  • Valid eHealth Certificate of the pharmacy
  • e-ID card of concerned patient 
  • Identification HC professional 

     °Identifier pharmacy: NIHII, HC professional category

     °Identifier pharmacy holder: SSIN, NIHII (if available), HC party category

  • Information therapeutic link

     °Identification concerned patient: SSIN, e-ID card, first and family name

     °Identification concerned HC party: NIHII (8digits), HC party category, organization name (optional)

  • Type of therapeutic link: pharmacydelivery 
  • Period of validity: 15 months
  • Inclusive start date (optional)
  • Exclusive end date (optional)
  • Comment to justify the declaration (optional)
  • Type of proof: e-ID encoding
  • A valid therapeutic link of the same type and for the same HC party already exists
TriggerThe user wants to put a therapeutic link 
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth WS Therapeutic Link
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Therapeutic Link
  6. The user does a request for Put Therapeutic Link
  7. The Put Therapeutic Link Request is sent to the WS Therapeutic Link 
  8. The WS Consent responds with a Therapeutic Link Response: error message
Post Condition(s)Error message
Test Data
End point(s)Therapeutic Link Database

Exception Flow 3

FlowSpecifications

IDUC-233-EF03
NamePut Therapeutic Link - HC Professional within a pharmacy -  eID encoding - Sender not allowed to perform the declaration
Description

Put Therapeutic Link, service used to declare a therapeutic link between a patient and a HC party.

HC professional within a pharmacy acts as author of the Put Therapeutic Link. The given proof is the e-ID encoding of the patient. Certificate used to access the WS Therapeutic Link is the eHealth Certificate of the end-user (HC Organization). The sender is not allowed to perform the declaration according to the predefined rules e.g. validation on the author (NIHII valid, SSIN valid,...?)

Actor(s)

HC Professional in a pharmacy who is the pharmacy holder

Requirements
  • End-user is a HC professional in a pharmacy who is the pharmacy holder
  • End-user manages the therapeutic links throughout his usual software
  • Valid eHealth Certificate of the pharmacy
  • e-ID card of concerned patient 
  • Identification HC professional 

     °Identifier pharmacy: NIHII, HC professional category

     °Identifier pharmacy holder: SSIN, NIHII (if available), HC party category

  • Information therapeutic link

     °Identification concerned patient: SSIN, e-ID card, first and family name

     °Identification concerned HC party: NIHII (8digits), HC party category, organization name (optional)

  • Type of therapeutic link: pharmacydelivery 
  • Period of validity: 15 months
  • Inclusive start date (optional)
  • Exclusive end date (optional)
  • Comment to justify the declaration (optional)
  • Type of proof: e-ID encoding
  • The sender is not allowed to perform the declaration according to the predefined rules e.g. validation on the author (NIHII valid, SSIN valid,...?)
TriggerThe user wants to put a therapeutic link 
Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access the eHealth WS Therapeutic Link
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Therapeutic Link
  6. The user does a request for Put Therapeutic Link
  7. The Put Therapeutic Link Request is sent to the WS Therapeutic Link 
  8. The WS Consent responds with a Therapeutic Link Response: error message
Post Condition(s)Error message
Test Data
End point(s)Therapeutic Link Database
  • No labels