Versions Compared

Old Version 6

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version 7

changes.mady.by.user Rami Sellami

Saved on

Key

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

...

Basic flow

FlowSpecification










Image RemovedImage Added

Use case ID

ATH-UC-12-BF

Use case name

Consult the consent of a patient using the GetPatientConsentStatus method

Actors

  • Citizen

  • HC party

Short Description

In order to consult the consent management history 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). The aim of this use case is to consult the consent management history status.

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)
  • Set of criteria related to the consent
    • 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 about the completion of the response (status of the completion, errors if exist)
  • Information about the consent if there is no error and the consent exists (active or inactive):
    • SSIN of the patient,
    • consent type,
    • data of declaration,
    • author of the declaration,
    • The consent status (GIVEN, REVOKED or DECEASED)

Steps (basic flow)

1

The user tries to consult the consent and the client sends a getPatientConsentStatus 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 response to the IAM  

5

The IAM connect receives the response and sends it to the client

6The client receives information about the consent management history 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 management history of a given patient

...