Versions Compared

Old Version 5

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version 6

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-19-BF

Use case name

Consult the therapeutic exclusions of a patient using the GET /therapeuticExclusions/{patientSsin} operation

Actors

  • Citizen (i.e. a patient, a parent of a patient, a mandatary)

Short Description

This use case enables to consult the therapeutic exclusion of a given patient using the GET /therapeuticExclusions/{patientSsin} operation of the REST version of the Therapeutic Exclusion WS.

Priority

1 (High)

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

Pre-Conditions

  • The identification the concerned patient (i.e. SSIN)
  • The identification the excluded HCP (i.e. SSIN)
  • The identification of the HCP (i.e. NIHII) in order to retrieve organizations like pharmacies

Post-Conditions

  • The identification the concerned patient (i.e. SSIN)

  • Information about the HCP (SSIN, NIHII, first name, last name, qualification code)

Steps (basic flow)

1

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

2The IAM connect sends the request to the Therapeutic Exclusion WS

3

The Therapeutic exclusion WS finds information about the therapeutic exclusion(s) of a patient 

4The Therapeutic  link WS sends JWT response to the IAM  

5

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

6The client receives information about the therapeutic exclusion(s) of the patient

Exceptions (exception flows)



  • Every time the end-user wants to consult the therapeutic exclusions of a given patient

...