Data Sharing Manager/API calls through DSM: Difference between revisions
From Voror_Wiki
More actions
ErgoSoftUK (talk | contribs) No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
This diagram shows, at a high level, the way the API calls, and the associated projects, are given access to the correct patient details: | This diagram shows, at a high level, the way the API calls, and the associated projects, are given access to the correct patient details: | ||
# When an API call is made, Keycloak checks the user ID. | # When an API call is made, Keycloak checks the user ID. | ||
# | #Data Sharing Manager then uses the user ID to determine which project that user ID has access to. | ||
# The project information in | # The project information in Data Sharing Manager determines which organisation’s (publishers) data is made available, and the associated config entry. | ||
# The | # The Data Service Manager config entry is used to access the configuration information in the config database; this determines which internal Compass database can be accessed. | ||
The following examples show how access differs depending on the project information and publisher lists. We will assume that the Internal Compass Database holds data for 100 organisations. | The following examples show how access differs depending on the project information and publisher lists. We will assume that the Internal Compass Database holds data for 100 organisations. | ||
{{Note|These examples use the same config entry and the same Internal Compass Database, however the project information in the | {{Note|These examples use the same config entry and the same Internal Compass Database, however the project information in the Data Sharing Manager is unique to each project.}} | ||
===Example 1: The project only has access to 10 of the 100 organisations=== | ===Example 1: The project only has access to 10 of the 100 organisations=== | ||
Latest revision as of 11:29, 30 April 2025
This diagram shows, at a high level, the way the API calls, and the associated projects, are given access to the correct patient details:
- When an API call is made, Keycloak checks the user ID.
- Data Sharing Manager then uses the user ID to determine which project that user ID has access to.
- The project information in Data Sharing Manager determines which organisation’s (publishers) data is made available, and the associated config entry.
- The Data Service Manager config entry is used to access the configuration information in the config database; this determines which internal Compass database can be accessed.
The following examples show how access differs depending on the project information and publisher lists. We will assume that the Internal Compass Database holds data for 100 organisations.
| These examples use the same config entry and the same Internal Compass Database, however the project information in the Data Sharing Manager is unique to each project. |
Example 1: The project only has access to 10 of the 100 organisations
Example 2: The project only has access to 50 of the 100 organisations
Example 3: The project has access to all 100 organisations
