Healthie supports storing information about users locations, which is a core feature in healthcare applications because of specifics of things like state licensure, but the current connector state does not pull in location data due to Healthie's API behavior. 

From Fivetran support explaining the results of investigating this on a related ticket:

Additionally, we observed that a Location breakout table exists within the Users table, and it contains the same fields. So, instead of implementing a separate child table with user_id filtering, we should consider using this breakout table directly. However, the Location breakout table has not yet been implemented in our Healthie (Lite) connector.

Adding the ability to retrieve location data, which is present in the Healthie application, for a given user is of critical importance and a core use case for users' demographic data. This is important for questions like state-level licensure, zip-level social determinants of health data, information on access/distance to physical healthcare locations, etc.