ConXus Profile: Third-Party Data Load

Available: June 15, 2009

The ConXus Profile Third-Party HRA Data Load Process allows historical data from third-party HRAs to be loaded into the ConXus Platform, where it can be compared with current HRA data collected using ConXus Profile.

Organizations currently using a health risk assessment may be reluctant to switch to a new HRA vendor because of the valuable HRA data pool they have accumulated over time. PDHI has developed the ConXus Profile Third-Party HRA Data Load Process to address this issue, allowing an organization to take advantage of the advanced data management facilities provided by the ConXus Platform, whilst retaining the value of historical HRA data.

Once third-party HRA data is loaded into the ConXus Platform, it is merged with current HRA data collected using ConXus Profile to provide:

  • Coach access to longitudinal HRA data for individual participants.
  • Administrator access to consolidated aggregate HRA data for outcome reporting.
  • Participant access to previous and current HRA results within the member report summary table for progress tracking.

Implementation Timeline and Process

The ConXus Profile Third-Party HRA Data Load Process is available from June 15, 2009. Please contact PDHI Client Services to request detailed technical documentation and to discuss your third-party data load project.

Data Load Process

The specific questions and response options included in the HRA questionnaire vary from vendor to vendor. All HRAs, however, use evidence-based guidelines to provide broadly similar assessments derived from question responses and data from other sources (typically laboratory results and biometric measurements). Thus a participant who completes a third-party HRA and is identified as at high risk for eating habits, for example, would likely be assessed at high risk for eating habits were he/she to complete the PDHI HRA, even if the questions and response options differ.

Aggregate reporting and system processes within the ConXus platform are driven from derived assessment values, not individual question responses. The Third-Party HRA Data Load Process supports two options, which can be used independently or in combination.

  1. Where derived assessment values for the third-party HRA are available, the derived values are mapped and loaded directly into the matching ConXus data elements.
  2. Where derived assessment values for the third-party HRA are not available, a mapping process and algorithms are used to generate derived assessment values from selected question responses from a third-party HRA, which are then loaded into the matching ConXus data elements.

If a participant has already accessed the ConXus Platform and created a user account, third-Party HRA data will be loaded into this account. Where a participant account does not exist, the data load process will create a temporary account and load data.

Data Requirements

The Third-Party HRA Data Load Process supports incomplete HRA records; so, in developing the mapping from the third-party HRA to the PDHI format, it is recommended that priority is given to modifiable risk factors – lifestyle behaviors, laboratory results, and biometric measurements.

Third-party HRA data must be identified with the same unique user ID as will be used within the ConXus Platform for participant’s gaining access online. Each HRA record must also be identified with an HRA date.

Additional data requirements, such as User Type and Employer Group, will be agreed with your Client Services representative for each data load project.