> For the complete documentation index, see [llms.txt](https://docs.lucernahealth.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lucernahealth.com/guide/insights-studio/population-builder/reference-guides/glossary-of-key-terms.md). # Glossary of key terms Terms you'll come across while working in Population Builder. The first table covers the tool itself; the second covers healthcare terms that show up in field names, populations, and quality measures. #### Population Builder terms | Term | Definition | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Block | A reusable set of rules that can be dropped into populations or other blocks. Blocks exist so common logic — like "active roster member" — gets defined once and reused. Unlike populations, blocks don't run on their own; they only take effect as part of something else. | | Catalog | A tag marking a core definition that ships with Population Builder. Catalog populations and blocks are pushed out to all clients and are ready to use immediately. | | Category |

How populations and blocks are grouped for browsing and filtering. Current categories are Engagement, Growth, Medical Cost Management, Operations, Quality & Care Gaps, and Risk Adjustment.
Please note categories for populations and blocks can be different

| | Definition | The query behind a population or block — the actual rules determining who's included. Found on the Definition tab. | | Dependencies | The underlying tables a population draws from, and how they connect. Shown alongside the lineage diagram on the References tab. | | Destination | A place in Leap where a population can be sent to be used. Tagging a population for a destination makes it available there, but each destination has its own admin controls determining what actually appears. | | Exclude | The section that removes members from a population. Include defines who's in; anyone matching an Exclude condition is taken back out, regardless of which group qualified them. | | Fine grain permissions | Team-level permissions controlling specific actions, such as enabling destinations or scheduling populations. Set under Team settings rather than per individual user. | | Funnel breakdown | The panel showing how the member count narrows at each step of a query. Step names match the query builder exactly, so any rule can be traced to its effect on the count. | | Golden table | A curated subset of the full data model covering the most commonly used tables and fields. Golden table results appear first when searching for a field, which is why the top result is usually the right one. | | Group | A set of conditions within a query. Conditions inside a group are joined by AND — all must be true. Conditions across groups are joined by OR — matching any one group is enough. | | Include | The section defining who's in a population. Everything built here forms the base list, which Exclude then filters down. | | Lineage | A diagram showing where the components used to build a population come from and how they connect. Found on the References tab. | | Operator | The comparison used in a rule — equals, not equals, between, contains, is blank, within last X days, and others. Available operators change based on the field type. | | Population | A list of members matching a set of rules you define. Populations can be run on demand or on a schedule, and sent to destinations to be used elsewhere in Leap. | | Population key | A unique identifier generated when a population is created. Used in integrations and API responses. Auto-generated, but editable. | | References | Where a population or block is used by other populations or blocks. Worth checking before editing anything, since changes carry through to everything referencing it. | | Root table | The table a population is built against. It determines what the query returns and is displayed above the query builder. Best left as-is unless the current table doesn't fit your use case. | | Run | Executing a query to produce the member list. Runs happen when someone runs a population manually, or automatically on a schedule. | | Run history | A log of every time a population has run, showing status, row count, timing, and run type. Useful for spotting failed runs or unexpected changes in count. | | Run schedule | The schedule controlling when a population refreshes automatically. Setting one up requires specific permissions. | | Saved view | A set of filters saved for repeated use. Views are public by default and can be made private when saving. | | Simulated root table | The table a count is calculated against while building. It's an estimate meant to help you understand your data as you go, not a live run. Defaults to Dim Consumer and can be changed at any time. | | System managed | A tag marking a population or block maintained by the Lucerna team. These can be viewed in full — logic, count, all details — but not edited, so shared definitions stay consistent for everyone. | | Total population | The member count from the last time a population ran. Not live: if the underlying data has changed since, the count won't reflect it until the next run. | | Version history | A record of every saved edit to a definition. Any previous version can be previewed and restored. | #### Healthcare terms | Term | Definition | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | A1C (HbA1c) | A blood test measuring average blood sugar over roughly three months. Central to diabetes management, and the basis for several quality measures. | | Attribution | The process of formally linking a member to a specific provider — usually a primary care physician — as accountable for their overall care. Typically determined by utilization data, such as which provider the member has seen most often, rather than by member preference alone. | | AWV (Annual Wellness Visit) | A yearly preventive visit covered by Medicare, focused on health risk assessment and planning rather than treating a specific problem. A common quality measure and outreach target. | | Care gap | A recommended service a member is eligible for but hasn't received — a missed screening, an overdue lab, a lapsed medication. Care gaps drive much of the outreach work populations support. | | CHF (Congestive Heart Failure) | A chronic condition where the heart doesn't pump effectively. Common focus for care management given high readmission risk. | | Compliance flag | Indicates whether a member met a given quality measure. A flag of 1 means compliant; 0 means non-compliant, which is what identifies an open care gap. | | Eligible | Whether a member qualifies to be measured for a given quality measure — the denominator. Eligibility rules vary by measure and typically account for age, sex, and condition. | | HCC (Hierarchical Condition Category) | A risk adjustment model that scores members based on documented conditions. Higher scores indicate greater expected cost and clinical complexity. | | HEDIS | A widely used set of standardized healthcare quality measures maintained by NCQA. Most health plans report on HEDIS measures, which is why measure names follow recognizable patterns across organizations. | | Panel | The group of members a provider is responsible for. Populations can be used to filter and segment panels in Provider 360. | | Quality measure | A standardized way of assessing whether recommended care was delivered. Each measure defines who's eligible and what counts as compliant. | | Roster | The list of members currently enrolled or assigned. "Active roster" refers to those currently enrolled, which is the usual starting point for building a population. | | Value-based care (VBC) | A payment model where providers are reimbursed based on outcomes and quality rather than volume of services. VBC is the reason attribution, quality measures, and care gaps matter operationally — they determine how performance is assessed. |