THIS SPACE IS UNDER CONSTRUCTION

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

General Information

Basic Flow 

FlowSpecifications

IDAR-UC04-BF
NamePut Patient Consent - Pharmacy
DescriptionA pharmacist who is holder of the pharmacy declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the pharmacy is used to log in. 
Actor(s)
  • A pharmacist who is the pharmacy holder
Requirements
  • End-user is a pharmacist who is the pharmacy holder 
  • End-user is not known in a hub
  • Valid eHeatlh Certificate of the pharmacy
  • 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 login to the eHealth Consent WS
  2. The user needs to request a SAML Token by using the eHealth Certificate of the pharmacy
  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
  • Informed Patient Consent is stored in the eHealth Database
Test Data
Endpoint(s)

Alternative flow: End-user is not the pharmacy holder 

  • No labels