Introduction

As a business-to-business company, Wellhub only provides its services to employees (and by extension their family members) of subscribing companies, and because of this, all processes begin by establishing and maintaining the eligibility of end-users. Of course, eligibility may change frequently with new people joining the company and others leaving, and because of this, an ongoing process between Wellhub and the company is required to maintain accurate access and use of Wellhub.

The company will generate an Eligibility File (EF) and provide it to Wellhub using a manual upload function available in the Wellhub HR Portal or using SFTP or API for automated transfers. Instead of using W4C, the client will be connected automatically to our systems within a certain frequency (that can be programmed or triggered by the client every time there is a need for an update), eliminating the need for manual work.

For more details on the SFTP option, please see the SFTP section of this website.

For more details on the API option, please see the API section of this website.

Data Privacy and Security

Wellhub takes the privacy and security of the data it processes from its customers very seriously. Wellhub's processing activities are aligned with our PCI-DSS and ISO 27001 certification and aligned with local regulations (eg. GDPR, LGDP). For any detailed questions on our security posture please reach out to your Wellhub Tech Sales representative.

File Exchange Frequency

The first production Eligibility File must be sent to Wellhub at least one week before the date that the Wellhub program will be announced to your company’s employees.

Then, for maintenance purposes, the Eligibility File must be sent to Wellhub at a minimum once a month.
However, when integrating full files we don't recommend sending it more than once a day.

File Format Requirements

• It must include the configured eligible identifiers for the client/company tax id - see further details here
• The header is mandatory, and needs to be in English for all countries
• The column order is not mandatory
• The column titles (attribute names) must be written exactly as indicated on
• Unknown columns will be ignored
• The CSV can use any of the accepted separators, as: comma (,), semicolon ( ; ), tab, and space
• CSV UTF-8 is the format supported
• National ID and Tax ID are validated as a mask. If they are wrong, an error is thrown - see further details here
• Accepted file types: ".xlsx", ".csv" -> for SSH; ".xlsx.pgp", ".xlsx.gpg", ".csv.pgp", ".csv.gpg" -> if PGP is enabled

Note that even though ".csv" is supported, since this file format can be mutable, using ".xlsx" or encrypted files with PGP is highly recommended.

File Naming Convention

For production: your company name_Eligibility_mmddyyyy.csv

For test: your company name_Eligibility_Test_mmddyyyy.csv