| ID | AR-UC12-BF |
| Name | Put Patient Consent - HC Organization - Pharmacy holder |
| Description | A pharmacist, who is the 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 access to the WS Consent. |
| Actor(s) | |
| Requirements | - End-user is a pharmacy holder
- Informed patient consent is managed in a recognized pharmacy throughout its usual software
- Valid personal 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 | - The user attempts to access the eHealth Consent WS
- The user needs to request a SAML Token by using the eHealth Certificate of the pharmacy
- A request for a SAML Token is sent to the Secure Token Service (STS)
- The STS responds with a SAML Token
- The user has access to the eHealth WS Consent
- The user does a request for Put Patient Consent
- The Put Patient Consent Request is sent to the WS Consent
- ° 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
- 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 Information | Additional information about the software of the pharmacy or pharmacist name etc. may be added for the audit purpose |