Versions Compared

Key

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

General Information

Basic Flow -

 Physician

 Health care giver of 78 not linked to a hospital


FlowSpecifications 


IDAR-UC01-BF
NamePut Patient Consent - Health Care giver of 78 not linked to a hospital
DescriptionA physician health care giver of AR78 not linked to a hospital (e.g. a general practitioner a health care giver  who has his own practice and isn't known in a Hub) declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the physician health care giver is used to log in. 
Actor(s)
  • A physician health care giver of AR78 not linked to a hospital and not known by a Hub (e.g. physician -  dentist - Nurse - Midwife → end-usersgeneral practitioner, dentist,..)
Requirements
  • End-user is a health care giver not linked to a hospital (e.g. General Practitioner)
  • End-user is not known in a hub
  • Valid personal eHeatlh Certificate 
  • Consent WS is integrated in the software of the end-user
  • Health care giver is not holder of the Global Medical File of the concerned patient
Trigger

The user wants to declare a Patient Consent on behalf of the patient

Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to login to the eHealth Consent WS
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Consent
  6. The user does a request for Put Patient Consent 
  7. The Put Patient Consent Request is sent to the WS Consent 
  8. ° The WS Consent responds with a Put Patient Consent Response

      ° The request is logged 

      ° The Informed Patient Consent is stored in eHealth Database

Post condition(s)
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data 
Endpoint(s)



Alternative Flow - End-user is holder of Global Medical File

FlowSpecifications


IDAR-UC01-AF01

Name

Put Patient Consent - Physician who is holder of the concerned patient Global Medical File and not linked to a hospital
DescriptionA physician who is holder of the concerned patient Global Medical file and is not linked to a hospital declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the physician is used to log in. 
Actor(s)Physician who is holder of the concerned patient Global Medical File 
Requirements
  • End-user is a physician not linked to a hospital (e.g. General Practitioner)
  • End-user is not known in a hub
  • Valid personal eHeatlh Certificate 
  • Consent WS is integrated in the software of the end-user
  • Physician is holder of the patient's Global Medical File 
Trigger

The user wants to declare a Patient Consent on behalf of the patient

Precondition(s)
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to login to the eHealth Consent WS
  2. The user needs to request a SAML Token by using it's personal eHealth Certificate
  3. A request for a SAML Token is sent to the Secure Token Service (STS)
  4. The STS responds with a SAML Token
  5. The user has access to the eHealth WS Consent
  6. The user does a request for Put Patient Consent (difference in request information → no Patient SSIN support card number needed)
  7. The Put Patient Consent Request is sent to the WS Consent 
  8. ° The WS Consent responds with a Put Patient Consent Response

      ° The request is logged 

      ° The Informed Patient Consent is stored in eHealth Database

Post conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
Endpoint(s)