Workplace Health Achievement Index: Choosing Between Employee Health Data Submission Processes

Workplace Health Achievement Index: Choosing Between Employee Health Data Submission Processes
For Index participants that elect not to use My Life Check®, there are three alternative processes for submitting employee health data based on Life’s Simple 7 (LS7) metrics:

1. 
   Batch Upload
   
2. 
   Application Programming Interface (API)
   
3. 
   Aggregate Report
   

These data are used to calculate an organization’s Heart Health Score, a critical component of the Index program. Without these data, an organization is not eligible for performance metrics points, which currently comprise 40% of the Total Index Score.

What are the Batch Upload, API and Aggregate Report processes?
Organizations participating in the Workplace Health Achievement Index program who are NOT using the My Life Check^® assessment tool can choose to use either the Batch Upload, API or the Aggregate Report process to provide LS7 equivalent data for obtaining an organization/company Heart Health Score as part of the Index program. The advantage of using the Batch Upload, API or the Aggregate Report processes to provide LS7 equivalent employee level data is that each process allows an organization to submit existing health risk assessment (HRA) and biometric data without having to implement the My Life Check^® assessment tool. Through each of these options, the employee HRA and biometric data provided by the organization is uploaded to a secure, HIPAA-compliant database where the organization Heart Health Score (HHS) and data quality measurements are calculated. Successful submission of these LS7 equivalent data automatically make the organization eligible for potentially receiving performance metrics points.
What is the difference?
BATCH: Organizations will need to populate the batch upload data template with their de-identified employee-level LS7 equivalent data in a CSV (comma separated values) file format. The organization will upload the spreadsheet in the admin portal. The data will be validated to ensure it is in the correct format. If any item is in the wrong format, the entire file will be rejected. An email will be sent to the Organization/Company Admin with the row number(s) and column name(s) that are invalid. The organization must correct the errors and upload again. Once a file is validated, it will be stored in a secure, HIPAA-compliant database. The organization can see its results in the Index dashboard.

API: An API (application programming interface) is a set of routines, protocols and tools for building software and applications. An API allows communication of data between an application and database. To utilize an API, the organization will need to write code on their end to be able to send data to the API. LS7 equivalent data is sent through the API one record at a time and there will be a success or reject response for each line of the record. Rejections will be sent with specific error codes to identify the errors and corrections needed. The organization will be able to update the records that were rejected and send them through the API again. For data that is accepted, the data will be stored in a secure, HIPAA-compliant database. The organization can see its results in the Index dashboard.

The organization can choose an API process where data are not recorded (stateless) or recorded (non-stateless):

• 
  Stateless or Recorded API: This type of API process does not record employee-level data (stateless), which means the employee data do not leave the organization environment and the heart health score and data quality calculations are performed within the organization’s data environment. Only the overall health assessment completion rate and the aggregate heart health score come into the environment of the AHA’s third party HIPAA-compliant vendor.
  
• 
  Non-stateless or non-recorded API: This type of API process does record employee-level data (non-stateless), which means the employee data leave the organization environment and comes into the environment of the AHA’s third party HIPAA-compliant vendor where the heart health score and data quality calculations are done and stored.
  

AGGREGATE: Unlike the Batch or API processes, submitting LS7 equivalent data via the Aggregate Report does not require the organization to submit employee level data. Instead, with the Aggregate Report process, the organization provides the number of employees with reported poor, intermediate and ideal health status for each LS7 metric. In addition, the organization reports the Total Eligible Population for providing LS7-equivalent data. Once submitted, these values are used to calculate an organization Heart Health Score using these self-reported aggregate data.
To submit these data, the organization will need to populate the Aggregate Report Template, which is a CSV (comma separated values) file. The organization will then upload the CSV file in the admin portal. The data will be validated to ensure it is in the correct format. If any item is in the wrong format, the entire file will be rejected. An email will be sent to the Organization Admin with the row number(s) and column name(s) that are invalid. The organization must correct the errors and upload again. Once a file is validated, it will be stored in a secure, HIPAA-compliant database. The organization can see its results in the index dashboard.
What is required to qualify for points for a Heart Health Score (HHS) and a Completion Score?
Qualifying for Completion Points (Criteria 1)

“Completion” refers to the percentage of LS7 equivalent employee health data submitted. To receive points for completion, data for at least five of the LS7 metrics must be provided and data must be provided by at least 25% of employees. Organizations that provide employee health data for less than five LS7 metrics or that provide data for less than 25% of employees, will not receive points for completion. For example:

• 
  Organization A provides LS7 equivalent data for five metrics. However, the data were gathered from 20% of employees. Organization A will not receive points for completion.
  
• 
  Organization B provides LS7 equivalent data for four metrics. The data were gathered from 50% of employees. Organization B will not receive points for completion. However, they will qualify for points for the organization HHS (see note below on HHS).
  
• 
  Organization C provides LS7 equivalent data for five metrics. The data were gathered from 50% of employees. Organization C will qualify for points for the organization HHS (see note below on HHS) and will receive points for completion.
  

How can my organization achieve higher points for completion?

Organizations submitting higher percentages of employee data, receive more points. For example, 50% of employee data submitted will receive more completion points compared to 25% of employee data submitted.

Qualifying for Organization Heart Health Score (HHS) Points (Criteria 2)

To qualify for points for an organization HHS, data for at least four of the LS7 metrics must be provided and must be provided by at least 25% of employees. Organizations that provide employee level data for less than four LS7 metrics or that provide data for less than 25% of employees, will not qualify for points for a HHS.

Points are awarded for an organization HHS of 5.2 or higher. An organization HHS of 5.2 represents the median (50^th percentile) score for the US adult population. (Source: National Health and Nutrition Examination Score, CDC, NHANES 1999-2000 to NHANES 2011-2012).

 

For example:

• 
  Organization A provides LS7 equivalent data for four metrics: The data were gathered from 20% of employees. Organization A will not qualify for HHS points.
  
• 
  Organization B provides LS7 equivalent data for only 3 metrics: The data were gathered from 50% of employees. Organization B will not receive a HHS and will not receive HHS points.
  
• 
  Organization C provides LS7 equivalent data for four metrics: The data were gathered from 50% of employees. Organization C will receive a calculated HHS and will receive HHS points if the organization HHS is 5.2 or higher.
  

How can my organization achieve higher points for an organization HHS?

If the data thresholds described above are met, points are awarded for an organization HHS of 5.2 or higher. Higher scores will respectively receive more points. For example, an organization HHS of 6.7 will receive more HHS points compared to an organization HHS of 5.2

BATCH UPLOAD:

PROS		CONS
The data can be uploaded directly through the Index Admin Portal Whenever a new file is uploaded, the previous file data is automatically deleted and replaced with the new file data		Requires manual preparation of the CSV file which may mean compiling data from multiple sources May incur costs if data must be obtained from 3rd party vendors

API – Non-recorded:

PROS		CONS
The organization does not need to prepare a CSV file The API is a more automated process Employee data does not leave the organization’s environment			The organization will need a developer to implement the API solution Prior to sending new data, the organization must submit a request for their existing data to be deleted

API – Recorded:

PROS		CONS
The organization does not need to prepare a CSV file The API is a more automated process			The organization will need a developer to implement the API solution Employee data leaves the organization’s environment Prior to sending new data, the organization must submit a request for their existing data to be deleted

AGGREGATE REPORT:

PROS		CONS
The data can be uploaded directly through the Index Admin Portal Whenever a new file is uploaded, the previous file data is automatically deleted and replaced with the new file data No personal health information is disclosed			Requires manual preparation of the CSV file which may mean compiling data from multiple sources May incur costs if data must be obtained from 3rd party vendors

Directory: idc -> groups
idc -> Arts & crafts : 1850-1900 Protest against the machine aesthetic
idc -> U. S. Department of the interior
idc -> Asymptomatic colonoscopy consults from er that do not meet prereqs
idc -> Enterprise systems Education
groups -> Acute ischemic stroke orders following r-tpa
idc -> Date: 5 Nov 2009 Email This Report