Page History

...

Basic flow

Flow	Specification
Image Added	Use case ID	ATH-UC-16-BF
	Use case name	Consult the consent of a patient using the GET /consents/{patientSsin} operation
	Actors	Citizen HC party
	Short Description
	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 SSIN of the concerned patient Type of the consent (optional)
	Post-Conditions	The SSIN of the concerned patient Information about the consent (consent status, the sign date)
	Steps (basic flow)	1	The client sends a GET /consents/ {patientSsin} request
		2	The IAM connect sends the request to the WS consent
		3	The WS consent finds information about the consent of a patient
		4	The 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 of the patient
	Exceptions (exception flows)
	Frequency	Every time the user wants to consult the consent of a given patient

...