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 9 Next »

General Information

Basic Flow 

FlowSpecifications

IDAR-UC06-BF
NamePut Patient Consent - Patient
DescriptionA patient declares his own "Informed Patient Consent" by using the WS Consent. The Certificate from the eID of the patient is used to access to the WS Consent. 
Actor(s)
  • A patient
Requirements
  • End-user is a patient
  • End-user acts as author of the request through his software and manages himself throughout his usual software
  • Valid eID
  • Consent WS is integrated in the software of the end-user
TriggerThe user wants to declare his Patient Consent 
Precondition
  • 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 his eID
  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
End point(s)WS Consent

Alternative Flow - Parent of patient requests consent

Alternative Flow - Mandatary of patient requests consent

  • No labels