HealthJibe Connect makes integrating your communications-enabled medical or fitness device to consumer selected health management services as easy as integrating an eCommerce application to the payment card networks.
HealthJibe leverages OAuth and requires the use of an OAuth Consumer (an open source OAuth library for your development platform is likely to be available). Here’s how it works:
- Implement an OAuth Consumer capability that adheres to the OAuth core authorization protocol.
- The HealthJibe authorization and configuration process for your device and its associated website is done in five steps when the user clicks on the Connect with HealthJibe button on your website or application:
- Your website obtains an unauthorized Request Token (Endpoint: https://www.razcode.net/request-token.ashx)
- Your website redirects the user to the HealthJibe authorization page where the user authorizes the Request Token by simply entering their HealthJibe email address and password (Endpoint: https://www.healthjibe.net/jibe/authorize)
- Your website exchanges the Request Token for an Access Token that should be stored with the user information on your website (Endpoint: https://www.razcode.net/access-token.ashx) and is used to sign future data transfer requests as discussed below.
- Your website redirects the user to the HealthJibe Configuration endpoint URL (https://www.healthjibe.net/jibe/configure) where the user is able to choose one or more destination health management services for the device measurement data. This signed OAuth request must contain a callback URL query parameter (raz_callback) that HealthJibe will use to redirect the user back to your website.
- HealthJibe redirects the user back to your website at the completion of the configuration process, providing a seamless user experience for the user. In addition to the oauth_token query string parameter and the oauth_verifier parameter, HealthJibe will append a query string parameter to the callback request (raz_notification_status) that indicates if future device notifications should continue to be sent for this user/device (false = no longer send notifications).
- Once the initial connection is made using the OAuth process described above, your website, web application, or device sends device notification messages whenever a measurement event occurs and is captured by the device or its related software.
- The notification message is an OAuth signed request ( URL: https://www.razcode.net/gateway/devicenotification) that includes the following query strings parameters:
- meas_date: the date the measurement was taken using the device (format: yyyymmdd)
- meas_time: the UTC time that the measurement was taken using the device (format: hhmm)
- meas: the measurement data utilizing OMHE commands formatted as a JSON string (e.g. {“wt”:”105″} which indicates a weight in kilograms)
- the measurement parameters can also be sent in the body of a POST request with the content-type set to: “application/x-www-form-urlencoded”
- A sample of currently supported OMHE commands include:
- bp (blood pressure and pulse e.g. “{bp133d85p65}”)
- wt (weight in kg e.g. “{ wt105}”)
- bg (blood glucose e.g. “{ bg145}”)
- lip(lipid profile e.g. “{lip190h170l130t90}” – total cholesterol, HDL, LDL, and triglycerids)
- bmi (body mass index e.g. “{bmi27.2}”)
- fm (fat mass in kg e.g. “{fm15}”)
- fr (fat ratio e.g. “{fr23}”)
- ffm (free fat mass in kg e.g. “{ ffm60}”)
- ca (calories consumed e.g. “{ca700}”)
- wbe (strength exercise duration in minutes e.g. “{ wbe40}”)
- ce (cardio exercise duration in minutes e.g “{ce45}”)
- st (steps from a pedometer e.g “{st1500}”)
- Contact us to discuss the correct measurement format for your device.
- The response to this message should be checked to determine whether future notifications should continue to be sent for this user/device (raz_notification_status).
- The notification message is an OAuth signed request ( URL: https://www.razcode.net/gateway/devicenotification) that includes the following query strings parameters:
- Your website or application can redirect the user to the HealthJibe Configuration endpoint URL whenever the user wishes to modify the device configuration from your website. This OAuth signed request must contain a callback URL query string parameter (raz_callback) so that the user can be returned to your website at the completion of the configuration process.
- Please remember that you do not implement the entire OAuth authorization process as described above on subsequent calls to the Configuration endpoint. The OAuth authorization process is completed only once. Subsequent calls to the Configuration endpoint are used to allow the user to modify the connection he or she has made between the device software and HealthJibe. Simply use the access token you have stored for this user/device to make the OAuth request.
- In addition to the oauth_token query string parameter and the oauth_verifier parameter, HealthJibe will append a query string parameter to the callback request (raz_notification_status) that indicates if future device notifications should continue to be sent for this user/device (false = no longer send notifications).
Contact us for more information or visit the RAZCODE Connected Health Platform website to register your device. We will support your integration effort every step of the way.
