Versions Compared

Old Version 7

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version 8

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

Use case name

Consult the therapeutic links of a patient using the GET /therapeuticLinks/{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

  • SSIN of the concerned patient 
  • SSIN of the HCP
  • Identifier of the healthcare party qualification (NIHDI) 
  • Qualification code of the healthcare party, also called quality (e.g.  persphysician, orgpharmacy, etc.)

Post-Conditions

  • Information about the patient (i.e. SSIN, first name and the last name)

  • The start date and the end date
  • Information about the HCP (i.e. SSIN, first name, last name and the qualification code)
  • The proof type of the therapeutic link

Steps (basic flow)

1

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

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

3

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

4The Therapeutic  link WS sends a 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 link(s) of the patient

Exceptions (exception flows)



  • Every time the end-user wants to consult the therapeutic link(s) of a given patient

...