Versions Compared

Key

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

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 NAKIJKEN CHECK PARENT LINK

FlowSpecifications


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

Difference in flowIdentification of the parent
Post Conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
End point(s)WS Consent



Alternative Flow NAKIJKEN CHECK MANDATARY!

FlowSpecifications


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

Difference in flowIdentification of
patient requests consent
the Mandatary
Post Conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
End point(s)WS Consent 


ent

To Do 

Exceptional flows