Contains wiki documentation, and issue tracker for the HSLynk Open Human Services Data Exchange Platform project. Code is in a different repo: https://github.com/servinglynk/hslynk-open-source . API docs are at https://docs.hslynk.com . General website is at:
Purpose: to allow researchers the ability to compare clients from their data set with HSLynk's. This will let them know whether a given set of individuals (with identifiers presented) are also within HSLynk. This API would not store the presented identifiers. The researchers, if they have authorization, would be able to then retrieve the particular HSLynk clients by id returned. Read-only client look-up access should probably have it's own unique read-only role.
batch client lookup (different than /search, which returns client details):
GET /search?searchentity=client&source_system_match
max 1000 clients in the JSON request body
response body would be an array, of request source_client_id and mapping to matched global client id, or null match.
no client data is presented in the response other than HSLynk global client IDs.
Add a new role for read only client match lookup
cc: @CTAJavier
@logicsandeep said we have to change our dedupe logic not to add a new dedupe ID if search returns nothing. estimated 8 hours effort
Purpose: to allow researchers the ability to compare clients from their data set with HSLynk's. This will let them know whether a given set of individuals (with identifiers presented) are also within HSLynk. This API would not store the presented identifiers. The researchers, if they have authorization, would be able to then retrieve the particular HSLynk clients by id returned. Read-only client look-up access should probably have it's own unique read-only role.
batch client lookup (different than /search, which returns client details): GET /search?searchentity=client&source_system_match
cc: @CTAJavier
@logicsandeep said we have to change our dedupe logic not to add a new dedupe ID if search returns nothing. estimated 8 hours effort