Versions Compared

Old Version 21

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version 22

changes.mady.by.user Rami Sellami

Saved on

Key

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

...

FlowSpecification









Use case ID

ATH-UC-12-BF

Use case name

Consult an active the consent of a patient

Actors

  • Citizen

  • HC party

Short Description

In order to consult the consent 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). The aim of this use case is to check a consent status after its activation or revoke.

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

Post-Conditions

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

  • An acknowledgement (status of the completion, errors if exist)
  • Information about the consent (SSIN of the patient, consent type, data of declaration, author of the declaration)

Steps (basic flow)

1

The user tries to consult the consent and the client sends a getPatientConsent request to the IAM connect

2The IAM connect routes the request to the WS consent

3

The WS consent finds information about the consent of a patient 

4The WS consent 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

6The client receives information about the consent of the patient

Exceptions (exception flows)

  • Invalid or incorrect data:
    • Invalid transaction identifier.
    • Invalid request sender.
    • Invalid healthcare party identifier.
    • Invalid patient identifier (invalid SSIN, eID, SIS numbers).
    • Invalid consent type.

Frequency

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

...