Hierarchy

In order to support the dynamic use cases that exist in healthcare, the Lynx platform supports unique and complex client hierarchies. When using the Lynx APIs, it’s important to understand this hierarchical structure, the elements within it, and how preferences and data are related to those different elements.

Actor	Description
Client	A ’client’ is the highest level organizational entity within the Lynx hierarchy. A client defines the base services and preferences for all organizations that fall under it.
Client Organization	A ‘client organization’ is an entity that falls underneath the ‘client’. These can be separate subdivisions or subsidiaries of the parent client. A client organization inherits the configurations of its parent, which can then be further customized as needed. Possible configurations include product functionality, digital content, branding, and even extends to webhooks, events, and API keys. Within our robust client hierarchy architecture, there is no technical limit to the number of client organizations that may be nested, parent-child, to seamlessly support even the most complex company structures.
Member	A ‘member’ is the end user of products and is associated with a client organization. Consumer preferences, accounts, cards, and activity are all determined at an individual member level.
Product	A ‘product’ is the health-fintech offering that determines the accounts, cards, payment, and other financial solutions entitled to a member. Product eligibility is governed by client and client organization program configurations.