Device Integration

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.

Here’s how it works (Click here for an overview diagram):

  • Implement an OAUTH Consumer capability that adheres to the OAUTH core authorization protocol as described here.
  • Display a Connect with HealthJibe button on your website or application that invokes the OAUTH process
  • After completing the OAUTH process and receiving an Access Token:
    • 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 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 (true= continue sending notifications and 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  GET 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”
      • Contact us to discuss the correct measurement format  for  your device.
    • The response to this message will include an ACK parameter – set to Success or Failure and indicates whether the operation was successful or not
    • 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).
    • On error conditions the response will contain an error message (errormsg) with more details about the error for debugging purposes.
  • 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(s) 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).