> ## Documentation Index
> Fetch the complete documentation index at: https://www.datalegion.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 1.6.0_2026-11-12

> NPI numbers for US healthcare providers, person lookup by NPI, employer domains that match the employer, and job titles that keep C++, C# and .NET.

## New Features

### NPI for Healthcare Providers

Person records now include two fields for US healthcare providers:

* `npi`: the person's National Provider Identifier, the 10-digit ID every US healthcare provider holds.
* `npi_last_updated`: the date the NPI registry last updated the provider's record (`YYYY-MM-DD`).

A person carries an NPI when their record is linked to an individual provider in the NPI registry. Everyone else has both fields empty.

517,281 people carry an NPI.

Both fields are Premium. See [Person Fields](https://www.datalegion.ai/docs/person-data/fields.md#npi) and [Data Tiers](https://www.datalegion.ai/docs/person-data/tiers.md).

* **Enrich by NPI:** pass `npi` to [Person Enrichment](https://www.datalegion.ai/docs/api-reference/person-enrichment.md) to look a provider up by their NPI. It needs `npi` in your contract, as filtering on it in search does. An NPI with a wrong check digit returns `422`.
* **Search by NPI:** `npi` is a [Person Search](https://www.datalegion.ai/docs/api-reference/person-search.md) column. Use `npi = '1234567893'` for one provider, or `npi IS NOT NULL` with a job title or location for healthcare providers.

**Bulk deliveries:** `npi` and `npi_last_updated` are not added to existing delivery definitions automatically. Contact us to include them in your feed.

## Improvements

### Employer Domains Match the Employer

A person linked to a company now carries that company's domain in `company_domain`, replacing another company's domain, a sub-site of the employer's website, or an outdated one. A domain the person's work email uses stays, as does any other domain the company lists as its own.

* An employer named by its initials is matched to the company its work email belongs to, so those people carry its domain too.
* An email domain that spells the employer's name another way (words run together in any order, a school's or department's subdomain, accents written plainly) counts as the employer's, so more of those addresses are typed as work emails.
* An employer written as a short acronym is no longer matched to a company whose acronym is a letter apart, so those people no longer carry that company's domain or employer details.

423,133 people's `company_domain` changed.

### One Person per LinkedIn Account

Records that belong to the same LinkedIn account, for example after the person changed their profile link, now resolve to one person.

A LinkedIn profile now appears only on the person it belongs to. A record that carried someone else's profile keeps its own name, addresses, phones, and emails, but no longer shows that profile's link, jobs, or headline.

Two different people who share a first name are no longer merged into one person when a record of one of them carries the other's automatically generated LinkedIn link. When the evidence is unclear, the records stay together as before.

**If you store `legion_id`, you will need to reconcile.** Merged records retire all but one `legion_id`, and people separated from a wrong merge can take new ones. Re-resolve stored ids against the current data.

This release records 1,297,393 merges, retiring 1,325,190 `legion_id`s from 1.5.0, and 2,237,894 splits.

### Fewer `legion_id` Changes

A person or company keeps the `legion_id` the previous release published unless it merged with another record, split, or left the data. When a record splits, its `legion_id` stays with the part that holds most of it. A company also keeps its `legion_id` when the data behind it is refreshed, as long as its LinkedIn page is the same.

181,289,911 of 1.5.0's 188,866,145 person `legion_id`s and 71,433,004 of its 71,442,615 company `legion_id`s carry into this release.

### Person Names

Names read the way the person writes them:

* A middle initial is shown as a middle initial, never as a suffix.
* Credentials and other text after the surname are removed (for example a professional designation or "(Ret.)"), unless that text is the whole surname.
* `first_name` is the name the person goes by, without initials in front of it.
* A name repeated across fields appears once.
* Text that is not a name, such as "fname", is no longer shown as one.
* A surname shows in its full form, including every word that belongs to it, however it is spaced or punctuated.
* A record whose last name is only a business word, such as "Consultants", "Technologies" or "Ventures", is a business rather than a person and is no longer delivered as one.

984,664 people's `first_name`, `last_name`, `middle_name` or `suffix` changed.

### Email Validation Status

Each email address carries the result of its most recent validation. When two results share a date, the more cautious one is kept.

### Work Emails

A second work email at a person's employer is removed when it doesn't follow how that employer writes its addresses (a misspelled name or a mixed-up format) and the person's better-supported address there does. The better-supported address stays. Addresses a validation confirmed are always kept. Malformed addresses (with characters such as `/`, `&`, or `{`) are removed as well.

The release carries 137,690,663 work emails (1.5.0: 140,674,205).

### Job Titles and Employers as Written

Job titles (`job_title`, `experience[].title`) keep the person's own wording wherever it had been expanded into a different meaning. "MD" and "PA" in a list of states ("Territory Manager, MD, DE, PA") now read as Maryland and Pennsylvania, and where they name something else (an aircraft model, a hospital's name, a film crew's production assistant) they are no longer expanded into "medical doctor" or "physician assistant".

A job is linked to a company (`company_legion_id`, `experience[].organization`) only when that company is the employer. A job that had been linked to a different company of the same name keeps the employer's name and is no longer linked, so the person no longer counts toward that company.

Job titles keep the punctuation that is part of a word. `job_title` and `experience[].title.cleaned` read "director of children's services", "co-founder", "c++ developer", "c# developer", ".net developer", "node.js engineer" and "24/7 support" rather than "director of children s services", "co founder", "c developer" (for both C++ and C#), "net developer", "node js engineer" and "24 7 support". An `&` inside an acronym stays joined ("at\&t", "r\&d", "fp\&a"); between words it is spaced ("oil & gas"). A C++, C# and C job at the same employer are no longer treated as one job.

Searches and enrichment match a title with or without that punctuation, regular expressions and `SIMILAR TO` included, so saved searches keep working: `co founder` finds "co-founder" and `node js` finds "node.js". A pattern with the punctuation at a word's edge or beside a wildcard (`'%c++%'`, `'%.net%'`) matches the title as written, so `'%c++%'` now finds C++ titles, where before it found none. A few advanced regular expressions also match only the written form (those using `\S`, a bracket class other than letters, digits and their ranges such as `[-]`, `[.]` or `[[:digit:]]`, a lookahead or lookbehind naming a space or punctuation mark, a character code or back-reference such as `\x27` or `\1`, or `(?x)`); allow for both spellings there, for example `co[- ]?founder[.]?`.

### Apostrophes

Job titles, names, cities, cleaned values, and company names, headlines and descriptions now use straight apostrophes and plain hyphens, so "O’Brien" and "O'Brien" are one spelling and match each other. Raw source values stay as the source wrote them, and a search or enrichment that types a curly apostrophe in a job title still matches.

### Current Jobs

A job is current only while the person's most recent employment history still lists it as current. A job that history shows as ended now has `current` set to `false` and no longer appears as `job_title` or `company_name`; the person's current job is the one their history lists, or none if it lists none. When no source gives the end date, `end_date` stays empty and `tenure_months` is null.

A job listed under both an earlier and a current company name now appears once, under the current name.

A job with no dates that repeats a job the person has ended is no longer shown as their current job.

1,096,698 jobs, held by 1,014,603 people, are now marked as ended.

### Job Titles That Are Not Jobs

A job title that describes the person rather than a job is no longer shown as a job: retired, looking for work, at home with family, a school they attended, a city and state, or a salutation such as "Mister". Such a person's `job_title` and `company_name` are empty unless they hold another current job. A retired person is no longer shown as a current employee of the employer they retired from.

A job whose title says it is over ("former", "retired") stays in `experience` with `current` set to `false`.

Email addresses no longer appear in job titles or employer names. The rest of the name stays.

Headlines no longer keep placeholder text such as "none" or "n/a" in place of a title or employer.

### Seniority

`seniority_level` reads a title that names a rank, trade or unit as such: a division, flight or survey party chief, a chief cook or a chief electrician is no longer `c_level`, and a chief's assistant or deputy (an assistant fire chief, a deputy chief of staff) is `director`. Officer titles ("Chief Financial Officer", "Chief of Staff") stay `c_level`.

An assistant, associate or deputy chief officer, such as a deputy chief financial officer, is `vp`: the role reports to that officer. A deputy chief executive stays `c_level`. An executive's assistant is ranked by the assistant's own title, not the executive's. A title that names a practice serving officers ("Senior Manager, CFO Advisory") is ranked by the person's own role there.

A managing director at a company of more than 1,000 people is `vp`, since there the title is a rank below the company's leadership. At a smaller company it stays `c_level`.

If you filter on `seniority_level = 'c_level'`, expect fewer people, mostly at large employers.

319,957 people moved from `c_level` to another level, and 160,526 moved into it.

### Company Headcounts

`legion_employee_count` and the workforce fields built from it no longer count people whose employer is written as a status or placeholder ("self-employed", "retired", "stealth startup", "none"), even when that text was linked to a company. Those people keep the job, with the employer written as they wrote it, but it is no longer linked to that company: `company_legion_id`, `company_domain` and the job's `organization` link stay empty. A company named after such a word keeps its own employees.

They also leave out people who list themselves as the chief executive, another chief officer (finance, operations, technology, information, marketing), or the owner or president of a company of more than 10,000 people when many others list the same title there and nothing else supports the claim, such as a sizable LinkedIn following or a headline naming the hospital, region or division they lead. Those people keep their job and title in their own record.

### Education

Each education entry names the school the person attended. Entries that had named a different school now name the person's own, with that school's profile link where known (`education[].organization`), and the same school listed twice is now one entry. When the person's current professional profile lists their education, a school or a period of study it does not show, with no other source to support it, is removed.

`education[].degree` holds the degree and `education[].field_of_study` the field, for example "Bachelor of Science" and "Advertising" rather than both in the degree. A grade no longer appears as a field of study.

Two separate periods at one school, such as a degree and a certificate years later, are now two entries, each with its own start and end date, where before they could be combined into one entry that ended before it began. Jobs work the same way: a promotion at the same company is its own entry in `experience`, and a certification's dates no longer mix two renewals.

A school the person is still attending now shows `education[].current` as true, where before any entry with an end date read as finished. Where the expected graduation had shown as the start date, it is now the end date, and a year far in the future is no longer shown as a date.

### Street Addresses

A street address now appears only when it can receive mail at a home or business. For a person, a street line without a house number (a street name alone, a city or state, or text that is not an address) and a PO box without a box number are removed; general delivery addresses are kept. For a company, a location whose street line repeats its city, or a PO box without a box number, keeps its city, region, and postal code without the street line.

A street address that many different people share without an apartment or unit number, such as an office tower, a campus, or a company's PO box, is no longer shown as a person's address. Apartment buildings are not affected. Where a street line is removed, the city, state, and postal code stay.

A few street names that showed a word from another language in place of the English one now show the English word.

An address the US Postal Service says a person moved away from is no longer shown as their current location, including when another copy of it is spelled differently.

A company street or city with a missing letter is no longer shown; the rest of the location stays. Some company locations shown under the wrong country now show the country their address names.

126,860,288 people carry a street address (1.5.0: 126,983,928), 103,392,236 of them a current one (1.5.0: 87,613,370).

### City Names

US cities now take one standard spelling, the place name their ZIP codes carry, so one city has one spelling for people and companies alike. "St. Louis" and "St Louis" now read "saint louis", "Winston Salem" reads "winston-salem", and "McLean" reads "mc lean". If you filter or join on a city name, use that spelling.

People whose city was "new york" on a ZIP code that carries another place name now show that name: Brooklyn, the Bronx, Staten Island, a Queens neighborhood such as Flushing or Astoria, or a nearby city such as Yonkers. Manhattan stays "new york". To find everyone in New York City, search the borough and neighborhood names as well.

1,275,517 people's top-level `city` changed spelling, and 214,453 people moved from "new york" to a borough, neighborhood or nearby city.

### Company Type, Size and Industry

A company type written another way is now read as the matching `type` ("Non-profit" as `nonprofit`, "Privately-held" and "Self Employed" as `private`), where before the company had no type. An industry written with different punctuation (a curly apostrophe, "and" for "&", a missing comma) is now read as that `industry`, for companies and for a person's `company_industry` alike.

`size` reads a range by its upper end ("5,001-10,000", "10 to 50"), a count written with thousands separators or a "k" ("1.000", "2.5k") as the number it is, and a count followed by a year ("50 employees in 2023") as the count. A size that is not a headcount ("unknown") is left empty rather than shown as written.

11,992 companies gained an `industry`, 38,787 a `size` and 47 a `type`, and 94,836 companies' `size` changed.

### Faster Past-Title Search

A [Person Search](https://www.datalegion.ai/docs/api-reference/person-search.md) on a past job title (`title` on `experience`), such as everyone who has worked as a nurse, no longer times out when the title is common. This covers `LIKE` and `ILIKE` patterns that match anywhere in the title (`'%nurse%'`) and regular expressions that are not anchored to the start or end of the title.

### Company Websites

A company whose website is a page on a shared site, such as a seller's own page on a direct-sales platform, now shows its own page in `domain` rather than one of that page's product, listing or share pages. Where nothing comes before the product or listing part, `domain` shows the site itself.

### Company Locations

An office listed more than once in a company's `locations` now shows once, including copies that differed only in how the postcode was written (with a house number or floor, with or without its hyphen) or a London district beside "london"; the postcode shown is in the country's format. A location naming only a country no longer appears beside a fuller one there, and a headquarters stays primary when another record from the same month calls it closed.

Spanish postal codes show the five-digit code; a floor or door written in that field ("PTL2", "1-BAJO") is removed. Mexico City is spelled "mexico city" as both city and state.

A location with no country now shows the country its address names: Curaçao, Bonaire and Sint Maarten for the former Netherlands Antilles, Serbia, Montenegro, Kosovo and East Timor for retired codes, and the United Kingdom by its postcode. Countries written in their own language ("Deutschland", "España", "Srbija") or without accents ("Curacao") are recognized.

A location shows as in the United States only when its address supports it, through a US state with one of its towns or ZIP codes, or the United States named. An address abroad that showed as a US location ("Casablanca, Casablanca 20000") and a city written twice with no state or ZIP ("Moscow, Moscow", "Dubai, Dubai") no longer show as US locations. Some US cities written the same way without a state ("Denver, Denver") are affected too.

Company `locations` fell from 87,524,552 entries to 84,113,151, and 3,508,511 companies list fewer.

### Social Profiles

A company's X or Facebook account that appeared on several of its employees' records no longer appears there, unless the account's name matches the person.

### Array Order

Every array in a person or company record now follows one order, the same in API responses, bulk deliveries, Snowflake and the free dataset, and the same each time the record is returned. See [Array Ordering](https://www.datalegion.ai/docs/data-standardization/array-ordering.md) for every rule.

* **Contact arrays** (`phones`, `emails`, `locations` and person `socials`): current entries first, then those whose status is unknown, then those known to have ended; within each, high confidence first, then the most recently seen.
* **Top-level entry first:** `experience[0]` is the job the top-level `job_title` and `company_name` describe, `locations[0]` the place the top-level `city`, `state` and `country_code` describe, and `domains[0]` the company's top-level `domain`.

If you compare arrays between builds or read entries by position, expect many records to list their entries in a new order with the same contents.

42,684,847 people (24% of those in both releases) and 445,819 companies list at least one array in a new order.

### Descriptions and Summaries

Company descriptions and person summaries that were missing their quotation marks or apostrophes now appear with them restored, where before they were left out. Company names and descriptions no longer show HTML codes such as `&rsquo;` or `&bull;`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.