...
Cookbook/ materials | Version | Location | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
eHealthConsent WS Cookbook | 1.9 | |||||||||
API eHealth Consent | 2.0 | http://jira.ivlab.ilabt.imec.be/secure/attachment/17424/swagger_consent_2-0-2.json | ||||||||
KMEHR | - | https://www.ehealth.fgov.be/standards/kmehr/en | ||||||||
Jira ticket MHEH-12 | - |
| Jira ticket MHEH-13 | - |
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
General information
In the figure below, we present a logical view about the relationship between the three basic services of the ehealth platform that are the WS Consent, the Therapeutic link WS, and the Therapeutic exclusion services. A consent can be managed by different types of end-users:
...