| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
❗️Warning, Old Version of the Validic APIThis is the legacy version of the Validic API. As of 01/01/2019, developers have only been issued credentials to our new Inform Platform. If you're a new Validic customer, please review the Inform API Documentation. |
Validic Legacy API Overview
The Validic API is designed to enable a simple, standardized connection between healthcare companies and mobile health and wellness apps and devices. Validic captures a user’s fitness activities and health measurements over time. Each activity and measurement contain a timestamp and a note about which integration was used to track the activity.
...
A core aspect of the Validic API is to vastly increase the speed of integration between mHealth app developers and healthcare businesses. Additionally, Validic provides critical enterprise features needed by healthcare companies that are not usually provided as a core service by app developers. These features include:
HIPAA/Safe Harbor/PHI Compliance
Validic eliminates concerns regarding the transfer of protected health information (PHI), as all data stored in and transferred through Validic follows the “Safe Harbor” de-identification standard and complies with all HIPAA regulations.
Standardized Endpoints
App developers and healthcare companies rarely speak the same language. The Validic REST API translates information to something both sides can understand.
Easy connectivity
The Validic health app marketplace allows for a simple, one-to-many connection for healthcare businesses and app developers alike. If your company wishes to connect with 200+ mHealth apps and devices, Validic makes it simple. Get started below, and if you have any questions, contact us.
Key Terms
Knowing is half the battle.
Before we begin, let's review some terms you'll encounter in the following documentation. Understanding these terms and their definitions will help you understand how Validic works.
Organization
An "Organization" is a collection of Validic users. An Organization typically represents a company that delivers the Validic marketplace through its web portal or mobile application.
Organization ID (Org ID, Organization_ID)
An "Organization ID" is used to identify your organization when making requests through the API. Your organization credentials are issued during the Validic implementation process. If you do not have an Organization ID, please contact our support team at support@validic.com.
Organization Access Token
The "Organization Access Token" is the secure token used in conjunction with your Organization ID. Your Organization Access Token is issued during the Validic implementation process. If you do not have this token, please contact our support team at support@validic.com.
User ID (User_ID)
The "User ID" is generated by Validic and used to represent a user of your system in our system. To ensure HIPPA compliance, Validic exchanges your unique User ID for a Validic User ID. The Validic User ID is then used to request data from Validic for a specific user.
User Access Token
This token part of an ID exchange mechanism that allows your users' data to remain de-identified, safe and secure. The "User Access Token" is used to tie the application marketplace to your unique users. This token is specific to a user and should not be confused with the Organization Access Token.
Marketplace
The "Marketplace", or "Application Marketplace", helps you connect with your users and obtain their permission to use their data. You'll guide users to this marketplace, they'll select their device and be led through the process of granting access to their data.
Expanded Data
Our conventional request only returns standardized data, which we call standard data. Standard data fields and data types should not change without prior notice.
...