Provisioning Users
To ensure HIPAA/PHI compliant data storage and transfer, Validic does not store identifiable user information in our system. As such, users must be provisioned in a unique way to provide user authentication and data linkage between your system and Validic.
When provisioning a user in Validic, you will be required to pass a unique User ID (UID). This UID is typically the user’s ID in your system. This information is encrypted before being stored in our system.
Users are provisioned in Validic with a POST call that includes a unique UID and the organization’s access_token (both are required), and optional profile parameters.
After the user POST request is sent, a 201 Created HTTP response code will be returned, echoing your input with the addition of a Validic User ID and User Authentication Token. It is imperative that you store the id and access token, as they will be used to help authenticate the user to Validic.
Basic User Provisioning:
POST https://api.validic.com/v1/organizations/516828cf6deddabe51000001/users.json
-H 'Content-Type: application/json'
{
"user": {
"uid": "123467890"
},
"access_token": "e61467e3845e8a66f7453dc55ea3fc445d1b879a6f96ebe7b243badbeae04f63"
}
201
{
"code": 201,
"message": "Ok",
"user": {
"_id": "51552cd7fded0807c4000017",
"uid": "123467890",
"access_token": "d18397e3845e8b66f7453dc55ea3fc445d1b879a6f96ebe7b243badabce08c98",
"profile": null
}
}