Used Documentation

Cookbook	Version	Location
Therapeutic Exclusion Cookbook	1.2	https://www.ehealth.fgov.be/ehealthplatform/nl/search?q=therapeutic+exclusion

General Information

Therapeutic Exclusion

The existence of an active ‘therapeutic exclusion’ is a fundamental prerequisite for the citizen to prevent
healthcare providers from accessing his medical data. Therefore, the eHealth platform makes available to the
citizen a new web service (WS) called Therapeutic Exclusion.

Technically, we identify the following attributes for a therapeutic exclusion:

If the excluded healthcare party is a practitioner
o The identification number of the Belgian National Register (INSS) of the patient
o The INSS of the practitioner

Therefore, if the practitioner has multiple healthcare professions i.e. multiple NIHII, multiple professional

categories and being excluded for one profession, the practitioner is considered as excluded for other professions
as well.

If the excluded healthcare party is an organization
o The INSS of the patient;
o The NIHII (Number assigned by the National Institute for Health and Invalidity Insurance) of the
organization.

A citizen can exclude one or more healthcare parties and one or more citizens can exclude one healthcare party.

According to the current business rules, for the purpose of the therapeutic exclusion:

‘Citizen’ means any patient; parent and mandatary of the concerned patient managing therapeutic
exclusion through the Therapeutic Exclusion WS integrated in their usual software.
Only following HC Parties can be excluded by citizen:
o As practitioner: Physician, Nurse, Dentist, Midwife, Audician, Physiotherapist, Occupational
therapist, Practical nurse, Dietician, Audiologist, Podologist, Truss maker, Logopedist, Orthoptist,
Lab technologist, Imaging technologist.
o As organization: Pharmacy

The management of the therapeutic exclusions consists of the following operations

PutTherapeuticExlusion	Allows the end-user to declare a therapeutic exclusion
RevokeTherapeuticExlusion	Allows the end-user to revoke of an active therapeutic exclusion
GetTherapeuticExlusion	Allows the end-user to consult the active therapeutic exclusion(s)

Basic Flow

Flow

Specifications

ID	UC-324-BF
Name	Revoke Therapeutic Exclusion - Parent of concerned patient - Pharmacy
Description	Revoke Therapeutic Exclusion allows an end-user (parent of concerned patient) to revoke a therapeutic exclusion. The excluded HC party is a pharmacy.
Actor(s)	Parent of concerned patient
Requirements	End-user is a patient Valid e-ID Identification end-user °Parent Software information °Identification parent: SSIN Identification concerned patient: SSIN, support card number (optional), first and family name (optional) Identification excluded HC party: valid and compliant NIHII, organization category, organization name (optional)
Trigger	The user wants to revoke a Therapeutic Exclusion
Precondition(s)	The user has an account for the application The user is logged out
Flow	The user attempts to access the eHealth Consent WS The user needs to request a SAML Token by using his eID A request for a SAML Token is sent to the Secure Token Service (STS) The STS responds with a SAML Token The user has access to the eHealth WS Therapeutic Exclusions The user does a request for Revoke Therapeutic Exclusion The Revoke Therapeutic Exclusion Request is sent to the WS Therapeutic Exclusions The Therapeutic Exclusion is physically removed from the database The request is logged The WS Therapeutic Exclusions responds with a Revoke Therapeutic Exclusion Response
Post Condition(s)	The request is logged The Therapeutic Exclusion is physically removed from the database The audit data
Test Data	Example Revoke Therapeutic Exclusion Request Example Revoke Therapeutic Exclusion Response Successful Example Revoke Therapeutic Exclusion Response Unsuccessful
End point(s)	Therapeutic Exclusions Database
Remarks	The support card numbers are optional: provided or not, it will not be submitted to card status validation First and family name are optional, if not provided then they are enriched based on provided INSS NIHII: if not provided then the NIHII is not enriched based on the provided INSS. If provided, the NIHII must be valid and compliant
Comments	The INSS identifies the patient. The INSS identifies the excluded professional. The NIHII identifies the excluded organization. It is a physical deletion i.e. the exclusion is no longer stored in DB. There is no cross validation between identifier vs category professional of the excluded HC Party. If mismatch occurs , the revocation request is not rejected The revocation is applied on the INSS of the concerned patient and the INSS of the excluded practitioner or the NIHII of the excluded organization

Exception Flow