Versions Compared

Key

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

...

FlowSpecification




Use case ID

ATH-UC-17-BF

Use case name

Consult the consent history of a patient using the GET /histories/{patientSsin} operation

Actors

  • Citizen

  • HC party

Short Description

This use case enables to consult the consent history of a given patient using the REST version of the WS Consent. 

Priority

1 (High)

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

Pre-Conditions

  • The user is already logged-in in the IAM connect 
  • SSIN of the concerned patient 
  • The limit of number of history entries

Post-Conditions

  • The SSIN of the concerned patient 
  • Information about the consent (consent status, the sign date)
  • A list of authors that managed a consent

Steps (basic flow)

1

The client sends a GET /histories/{patientSsin} request 

2The IAM connect sends the request to the WS consent

3

The WS consent finds information about the consent history of a patient 

4The WS consent sends a JWT response to the IAM  

5

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

6

The client receives information about the consent management history of the patient

Exceptions (exception flows)


Frequency

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

...