Versions Compared

Old Version 67

changes.mady.by.user Unknown User (gaelle.laurent.ext@imec.be)

Saved on

compared with

New Version 68

changes.mady.by.user Unknown User (gaelle.laurent.ext@imec.be)

Saved on

Key

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

Used Documentation 

Cookbook / Materials

Version

Location

Consent WS

1.9

https://www.ehealth.fgov.be/ehealthplatform/nl/service-ehealthconsent

Secure Token Service 

1.3

https://www.ehealth.fgov.be/ehealthplatform/nl/service-iam-identity-access-management

MetaHub V2 Cookbook 1.9https://www.ehealth.fgov.be/ehealthplatform/nl/service-verwijzingsrepertorium-hubs-metahub


General Information

Basic Flow 


FlowSpecificationsIDAR-UC07-AF01NamePut Patient Consent - Health Care professional of AR78 - PharmacistDescriptionA pharmacist declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the pharmacist is used to access to the WS Consent. Actor(s)A pharmacistRequirements
  • End-user is a pharmacist
  • End-user acts as author of the request through his software and manages himself
  • Valid personal eHeatlh Certificate 
  • Consent WS is integrated in the software of the end-user
TriggerThe user wants to declare a Patient Consent on behalf of the patientPreconditions
  • The user has an account for the application
  • The user is logged out
Flow
  1. The user attempts to access 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

Difference in flowIdentification of the end-userPost Conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test DataEnd points
  • WS Consent
  • eHealth Database
FlowSpecifications 


IDAR-UC07-BF
NamePut Patient Consent - Health Care professional of AR78
DescriptionA health care professional of AR78 (Physician - Dentist - Nurse - Midwife) declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the health care giver is used to access to the WS Consent. 
Actor(s)
  • A health care giver of AR78 (Physician - Dentist - Nurse - Midwife)
Requirements
  • End-user is a health care professional AR78 (Physician - Dentist - Nurse - Pharmacist - Midwife)
  • End-user acts as author of the request through his software and manages himself
  • Valid personal eHeatlh Certificate 
  • Consent WS is integrated in the software of the end-user
  • Health care professional 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 access 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)
  • WS Consent
  • eHealth Database
Additional Information

Additional information about the software and/or end-user e.g. first name and family name may be added for the audit purpose

Alternative Flow -Pharmacist

Remarks
  • If support card number is provided then it must be compliant e.g. correct format, check-digit and combination
  • Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
Additional Information

Additional information about the software

of the pharmacy or pharmacist name etc.

and/or end-user e.g. first name and family name may be added for the audit purpose



Alternative Flow

FlowSpecifications


IDAR-UC07-AF02

Name

Put Patient Consent - Physician who is holder of the concerned patient Global Medical File 
DescriptionA physician who is holder of the concerned patient Global Medical file 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 access the Consent WS. 
Actor(s)Physician who is holder of the concerned patient Global Medical File 
Requirements
  • Physician is holder of the patient's Global Medical File 
  • End-user acts as author of the request through his software and manages himself
  • Valid personal eHeatlh Certificate 
  • Consent WS is integrated in the software of the end-user
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 access 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

Difference in flowPut Patient Consent - Consent : Patient SSIN support card NOT mandatory 
Post conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
Endpoint(s)
  • WS Consent
  • eHealth Database
Remarks
  • If support card number is provided then it must be compliant e.g. correct format, check-digit and combination
  • Support card number is not mandatory if the concerned patient is a new born (0 < patient < 3 months)
Additional informationAdditional information about the software and/or physician e.g. first name and family name may be added for the audit purpose