Versions Compared

Old Version 13

changes.mady.by.user Rami Sellami

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (fabian.steels@cetic.be)

Saved on

Key

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

Table of Contents

Used documentation

Cookbook/ materialsVersionLocation
eHealthConsent WS Cookbook1.9

https://www.ehealth.fgov.be/ehealthplatform/file/view/7cd655bc5f9ec7be387cfbc2d8710b5d?filename=cookbook_ehealthconsent_web_service.pdf

API eHealth Consent2.0http://jira.ivlab.ilabt.imec.be/secure/attachment/17424/swagger_consent_2-0-2.json
KMEHR-https://www.ehealth.fgov.be/standards/kmehr/en
Jira ticket MHEH-12-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-12

Jira ticket MHEH-13-
Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-13
Jira ticket MHEH-18-
Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-18
Jira ticket MHEH-20-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-20

Jira ticket MHEH-26-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-26

Jira ticket MHEH-31-

Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-31

Jira ticket MHEH-32-
Jira
serverimec Validation Lab
serverIdac11aa92-3976-3161-9ddb-5020cc76f1c7
keyMHEH-32

General information

In the figure below, we present a logical view about the relationship between the three basic services of the ehealth platform that are the WS Consent, the Therapeutic link WS, and the Therapeutic exclusion services. A consent can be managed by different types of end-users:

...

The API eHealth Consent provides five methods. It is noteworthy that in this use case only the Ge tPatient Consent method is used.



Basic flow

FlowSpecification






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

This use case enables to consult the consent status 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 

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 

2The IAM connect sends 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 of the patient

Exceptions (exception flows)


Frequency

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

...