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

Basic Flow

FlowSpecifications

IDAR-UC12-BF
NamePut Patient Consent - HC Organization - Pharmacy
Description
Actor(s)
Requirements
Trigger 
Precondition(s)
Flow
Post Condition(s) 
Test Data
End point(s)
Remarks
Additional Information
IDAR-UC07-AF01
NamePut Patient Consent - Health Care professional of AR78 - Pharmacist
DescriptionA 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 pharmacist
Requirements
  • 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 patient
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 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-user
Post Conditions
  • Request is logged
  • The informed patient consent is stored in the eHealth Database
Test Data
End points
  • 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 of the pharmacy or pharmacist name etc. may be added for the audit purpose

Alternative Flow

  • No labels