RAZCODE Integration

HealthJibe Connect makes integrating your Health IT solution to consumer selected health management services simple and fast. 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 a string of Open Mobile Health Exchange (OMHE) commands.

In addition, the RAZCODE Integration framework provides for mobile payments via the HealthJibe Payments capability.

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.
• OPTIONAL: Implement an activation process for your Health IT solution.
  • The activation 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.

• OPTIONAL: Implement a user authorization process for your Health IT solution 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 access token for the user that you can store for future use with our other integration frameworks, and to use as the “user” parameter with stage requests (as described below), in order to provider an additional level of security by ensuring that only a specific person, using a specific mobile device, can use the RAZCODE.

• 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 a string of Open Mobile Health Exchange (OMHE) commands.
    • user – which is an authorization token (obtained by implementing the  user authorization process as described above) for a specific person. By including this parameter HealthJibe provides an additional layer of security that guarantees that only the specific person, using a specific mobile device, can use the RAZCODE.
    • pmt – which is a payment request. A payment request is a formatted JSON string.
  • The Response will contain the following 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)
    • raz_image — a URI (a pointer to a Microsoft Tag JPEG image that you can use to provide a high capacity barcode image to the patient), and pmt — an indication of whether a valid payment request was contained in the API Request (set to valid/invalid).
    • ACK -– set to Success or Failure and indicates whether the operation was successful or not
    • On error conditions the response will contain an error message (errormsg) with more details about the error for debugging purposes.
  • 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 Microsoft Tag 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.

NOTE: 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/stage/url and the gateway will return a URI string (parameter is raz_uri) that you can encode using your barcode technology.

Share

Hide Sites