Versions Compared

Old Version 3

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version 4

changes.mady.by.user Rami Sellami

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

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
KMEHR-https://www.ehealth.fgov.be/standards/kmehr/en
Jira ticket MHEH-12-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-12

Jira ticket MHEH-13-


Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-13
Jira ticket MHEH-18-
Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-18


Jira ticket MHEH-20-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-20

Jira ticket MHEH-26-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-26

Jira ticket MHEH-31-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-31

Jira ticket MHEH-32-
Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-32

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:

  • Health Care (HC) parties: a physician, nurse, dentist, midwife, a pharmacy (it is noteworthy that there is no difference between pharmacy and a pharmacist), authorized organization.
  • Citizen: a patient, a parent of a patient, a mandatary  

...

  • The "PutTherapeuticExlusion" method allows an end-user to declare a therapeutic exclusion.
  • The "RevokeTherapeuticExlusion" method enables an end-user to revoke an active therapeutic exclusion.
  • The "GetTherapeuticExlusionj'ai" method allows an end-user to consult the active therapeutic exclusions.

Basic flow

FlowSpecification

Use case ID

ATH-UC-

14

15-BF

Use case name

Consult the therapeutic exclusions of a patient

Actors

  • Citizen

HC party

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

Short Description

In order to consult the therapeutic

links

exclusions of a patient using the SOA-based version, it is important to use the Token exchange service in order to convert a JWT message into a SAML one (and vice versa). 

Priority

1 (High)

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

Pre-Conditions

  • The user is already logged in via the Token exchange service
  • Information about the request (request identifier, end-user identifier, date and time of the request
, the number of the therapeutic links to consult (=<1000))A set of criteria relative to the therapeutic links 
  • )
  • Information about the therapeutic exclusion: 
    • The identification the concerned patient
    • Optionally, the first and last name of the patient
    • Optionally, the identification of the excluded HCP
      • if
  • SSIN of the concerned patient 
    • Optionally, identification of the concerned HCPif the
        • HCP is a professional:
    SSIN
        • NISS*,
     
        • NIHII
    number
        • (11 digits), category of the HCP
    category
        • *, the first and last name of the HCP
        • if
    the
        • HCP is an organization: NIHII
    number
        • * (8 digits), category of the HCP
    category
        • *, the name of the
    organization
  • Optionally, the list of therapeutic link type
  • Optionally, the time period  [begin date - end date]
  • Optionally, the status of the consulted therapeutic link: active, inactive, all
        • HCP.

    Post-Conditions

  • Information about the evidence (Mandatory if the consultation is referral or historic)
    • Type of the proof
    • only if the type of proof is the reading of the eID card with PIN code entering, the binary proof including the encryption method (mandatory) and the binary value (mandatory).

    • Post-Conditions

  • Information about the response (response identifier, end-user identifier, data and time of the response, initial request)

  • An acknowledgement about the request completion (status of the completion, errors if exist)
  • A list of the therapeutic links fulfilling the criteria:
    • if the HCP is provided in the request
      • if the HCP is a professional identified by his/her SSIN and his/her category: all the therapeutic links containing the given SSIN - category are returned;
      • if the HCP is a professional identified by his/her NIHII and his/her category: all the therapeutic links containing the given NIHII - category are returned;
      • if the HCP is a professional identified by his/her SSIN, his/her NIHII and his/her category: all therapeutic links containing the given SSIN - NIHII - category category are returned;
      • if the HCP is an organization identified by its NIHII and its category:  all the therapeutic links containing the given NIHII - category are returned.
    • if the HCP is not provided in the request
      • if the proof is not given
        • if the end-user of the request acts as a HC professional: the therapeutic links of the concerned patient and the concerned author are returned;
        • if the end-user of the request acts for an organization: the therapeutic links of the concerned patient and the concerned HC organization of the end-user are returned.
      • if the proof is given
        • if the end-user of the request acts as a HC professional: the therapeutic links of the concerned patient and the concerned end-user, the therapeutic links of the concerned patient and other concerned HCP are returned;
        • if the end-user of the request acts for a HC organization: the therapeutic links of the concerned patient and the concerned organization, the therapeutic links of the concerned patient and other concerned HC parties are returned.
  • If a (list of) therapeutic link type is provided: the therapeutic link(s) matching this (these) type(s) are returned 
  • If a time period is provided: the list of therapeutic links found over this given time period
    • If a status (i.e. ‘active’, ‘inactive’, ‘all’) is provided: the therapeutic link matching the provided status are returned.


    Steps (basic flow)

    1

    The client sends a GetTherapeuticLink request 



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


    		4
    The Therapeutic  link WS sends a SAML-based response to the IAM  


    5

    The IAM connect receives the response and sends it to the client using a JWT format by interacting with the token exchange service


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