Page History

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 message 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 
• Type of the consent (optional)
• • 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

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)Information about the consent (SSIN of the patient, consent type, data of declaration, author of the declaration)
• A list of the therapeutic links fulfilling the criteria:
  • if the HCP is provided in the request
  • if the HCP is not provided in the request

Steps (basic flow)

1

3

5

Exceptions (exception flows)

• Every time the user wants to consult the consent of a given patient