-
Created by Unknown User (gaelle.laurent.ext@imec.be), last modified on Mar 27, 2019
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 70
Next »
This service is a ‘KMEHR-based’ WS. We thus strongly recommend consulting the documentation related to the KMEHR normative elements. The KMEHR site aims to offer a central point for the documentation of the KMEHR normative elements.
https://www.ehealth.fgov.be/standards/kmehr/en
The three following generic elements are, in particular, essentials to build the request and the reply of eHealth MetaHub WS.
Flow | Specifications |
---|
| ID | AR-UC07-BF | Name | Put Patient Consent - Health Care professional of AR78 | Description | A health care professional of AR78 (Physician - Dentist - Nurse - Midwife) declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the health care giver is used to access to the WS Consent. | Actor(s) | - A health care giver of AR78 (Physician - Dentist - Nurse - Midwife)
| Requirements | - End-user is a health care professional AR78 (Physician - Dentist - Nurse - Pharmacist - Midwife)
- 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
- Health care professional is not holder of the Global Medical File of the concerned patient
| 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 it's personal eHealth Certificate
- 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 |
| Endpoint(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 and/or end-user e.g. first name and family name may be added for the audit purpose |
|
Alternative Flow
Flow | Specifications |
---|
| ID | AR-UC07-AF02 | Name | Put Patient Consent - Physician who is holder of the concerned patient Global Medical File | Description | A physician who is holder of the concerned patient Global Medical file declares an "Informed Patient Consent" on behalf of the patient by using the WS Consent. The personal eHealth Certificate of the physician is used to access the Consent WS. | Actor(s) | Physician who is holder of the concerned patient Global Medical File | Requirements | - Physician is holder of the patient's Global Medical File
- 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
| 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 it's personal eHealth Certificate
- 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 | Difference in flow | Put Patient Consent - Consent : Patient SSIN support card NOT mandatory | Post conditions | - Request is logged
- The informed patient consent is stored in the eHealth Database
| Test Data |
| Endpoint(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 and/or physician e.g. first name and family name may be added for the audit purpose |
|