RAZCODE Integration

HealthJibe Connect makes integrating your Health IT solution to consumer selected health management services as easy as integrating an eCommerce application to the payment card networks. The only requirements are:

  • Ability to implement an OAuth Consumer capability (an open source OAuth library for your development platform is likely to be available).
  • Ability to generate Continuity of Care Records  (CCR) or HL7 CDA Release 2 Continuity of Care Documents  (CCD).

Here’s how it works:

  • Implement an OAuth Consumer capability that adheres to the OAuth core authorization protocol. This capability will be used to authorize your solution to create RAZCODE tokens.
  • The authorization process for your Health IT solution is done in three steps:
    1. Your website obtains an unauthorized Request Token (Endpoint: https://www.razcode.net/request-token.ashx)
    2. Your website redirects to the RAZCODE Platform activation page where the organization authorizes the Request Token by simply entering an email address and password (Endpoint: https://www.razcode.com/platform/activate) that was used to establish an account on the RAZCODE Platform website.
    3. 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 HIT solution sends Stage requests (URL:  http://www.razcode.net/gateway/stage) which are  signed OAuth POST requests
    • The body of the POST request contains the following parameters:
      • her – It is a Health Encounter Record (HER) which is an XML string that adheres to the Continuity of Care Record (CCR) or HL7 CDA Continuity of Care Document (CCD) schemas.
      • user – which is an authorization token (obtained by implementing HealthJibe Connect as described below) for a specific person. By including this parameter HealthJibe provides an additional layer of security that guarantees that only the specific person can use the RAZCODE. This parameter is optional or can be null.
    • The Response will contain two parameters: raz_id — a RAZCODE ID (a character string which is provided to the patient so that they may upload their information via the HealthJibe website or via any mobile web browser via www.healthjibe.mobi), and raz_image — a URI (a pointer to a RAZCODE JPEG image that you can use to provide a high capacity barcode image to the patient).

    • NOTE 1:  If you are interested in using only the RAZCODE ID (and not the bar code image) simply send the same Stage request to http://www.razcode.net/gateway/stage/id and only a RAZCODE ID parameter (raz_id) will be returned. However, you may not use just the bar code image. In order to accommodate those users that do not have access to a supported smartphone with a camera and a data connection, you must include the RAZCODE ID code whenever you present a RAZCODE image to an end user.

    NOTE 2: When displaying a RAZCODE ID and/or image to a user, you are required to include the www.healthjibe.com URL (www.healthjibe.com) near enough to the image so that the user will understand that they can visit this website to take advantage of the RAZCODE. You may add additional explanatory text as you see fit.

    NOTE 3: The RAZCODE image is by default encoded as a Microsoft Tag. However you can use any barcode technology that will allow the encoding of a URI in the barcode, that provides decoding software for a wide range of the most popular smartphones, and that will invoke the URI automatically (e.g. QR-Code, etc.). Just send your stage requests to the following Endpoint: https://www.razcode.net/gateway/stageselftag and the gateway will return a URI string (parameter is raz_uri) that you can encode using your barcode technology.

  • You may implement these functions in any way that is consistent with the overall workflow and user experience of your solution. For example Practice Management and Electronic Medical Record systems may simply email a RAZCODE Image and/or a RAZCODE ID to the patient when billing is complete for the health encounter, or they may output a RAZCODE ID as part of a receipt, discharge document, or account summary provided to the patient at checkout.
  • Now implement HealthJibe Connect to allow your users to create a HealthJibe account directly from your website or application (if they don’t already have an account), which they will need to take advantage of the RAZCODE tokens you provide them.

    • Display the “Connect with HealthJibe” button on your website (download here)
    • Implement the Oauth authorization process (similar to the OAuth activation process described above) with the HealthJibe Connect authorization endpoint (Endpoint: https://www.healthjibe.net/jibe/authorize)
    • Implementing HealthJibe Connect will allow you to obtain an authorization token for the user that you can store for future use with our other integration frameworks, or to use as the “user” parameter with stage requests as described above, in order to provider an additional level of security by ensuring that only a specific person can use the RAZCODE.