ATH-UC-14-BF

Use case name

Actors

• Citizen

• HC party

Short Description

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

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 
  • SSIN of the concerned patient 
  • Optionally, identification of the concerned HCP
    • if the HCP is a professional: SSIN,  NIHII number (11 digits), the HCP category, the first and last name
    • if the HCP is an organization: NIHII number (8 digits), 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
• 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

3

5

Exceptions (exception flows)

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