Every field · what it means · what it costs

The data dictionary, written down rather than emailed.

71 fields, grouped so you can find one fast. Each entry says what the field is in a sentence, what it is actually used for, how complete it is where we can measure that, what it costs on your plan, and the three names it travels under - in the API, in an export, and in an append. Where a field exists on one surface and not another, the entry says so, because that is the thing people write in to ask.

See plans What is in the data The same list as JSON

71fields documented here

48returned by the API

36available as export columns

44you can append to your own file

How to read an entry

Five things a reference page usually leaves out.

The examples are invented, and say so

Every example value on this page is fictional - the shape of the value, in obviously made-up data. We do not put a real provider's details on a public page to illustrate a field, and we never dress an invented value up as a real one.

Coverage is live, dated, or it says “not published”

Work email, trusted-tier email, practice phone and practice location are counted by the platform and quoted here from that count. Those counts were last recomputed on 2026-10-05. The two Medicare utilisation fields are counted over ten million procedure lines, which is too slow to do while you wait, so they are read from the platform's own measurement and carry the date it was taken on instead of pretending to be live. Every other field says not published rather than carrying a fill rate nobody measured.

Three names, because there are three surfaces

A field can be on the API, in an export column, in the append catalogue, or in some but not all three. Each entry gives all three names and prints Not exportable or Not appendable where one is missing, so a developer and a buyer can use the same page.

Cost in the plan's own terms

Free and public, included with an account, a metered reveal, or contract only. The plans page is where the numbers behind those words live; this page never restates an allowance, because a figure repeated where nobody is looking is a figure that goes stale.

The band describes the field, not the door. Taking a record out of the platform costs one row against your plan's row allowance whatever its fields cost, in an export and in an API response alike, and a metered reveal costs its reveal on top of that wherever you ask for it.

What they do has limits, and they are on the entries

Published Medicare fee-for-service data for 2024, covering about one in seven clinicians nationally, and more in the specialties that bill it most — not all-payor claims, and low-volume providers are removed before publication. A provider with nothing there has no published Medicare volume — which covers no volume, volume below the publication threshold, and not billing Medicare at all, because the published file does not separate them. One year is held, so nothing supports a trend.

Through the API, one published procedure line and one published prescribing line each count as one row against your plan's row allowance — the same allowance an export spends — so thirty procedure lines for one surgeon are thirty rows. Asking about a provider whose Medicare volume was never published returns nothing and costs no rows, and the procedure and drug pickers cost no rows at all. Reading the detail on screen in the app is included, like search, and filtering a search on a procedure or a drug costs nothing beyond the providers it returns. In a file it is priced differently, because a file carries the summary and not the lines: the claims columns widen a row and never add one, so an export or an append costs exactly the same rows with them as without.

Contents

13 groups.

Identity (6)Name, in one piece and in parts (9)Specialty and taxonomy (5)Practice location (7)Contact (10)Employment and affiliation (6)Licences (2)Standing (4)What they do (4)Organisation and facility (10)Health system (2)Home address and cell phone (4)What every record carries (2)

6 fields

Identity

Who the record is about, and whether it is still live. Every other field on this page hangs off the identifier.

NPI

The ten-digit national identifier a healthcare provider is enumerated under. One provider, one number, for life.

Example: 0000000000
What it is for: The join key for everything. It is what makes a record you hold and a record we hold the same record, so it is the column to keep when you load a file into a CRM and the column to send when you ask us to fill one in. It is also the only identifier here that survives a name change, a move and a change of employer.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: npi
Export column: NPI
Append field: npi
Worth knowing: Every export preset carries it, including the ones named after a CRM, because no CRM has a standard field for it and it is the column that makes the file worth re-loading later.

Type

Whether the record is a person or an organisation.

Example: individual
What it is for: It decides which half of the record is populated: a person has name parts and no organisation name, an organisation is the other way round. Filtering on it is how you stop a list of clinicians filling up with practices, and it is the first thing to check when a mail merge starts writing "Dear NORTHSIDE HOSPITAL".
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: type
Export column: Type
Append field: type

Status

Whether the identifier is still active, or has been retired.

Example: active
What it is for: Suppressing spend. An inactive identifier is a provider who has retired, died or given the number up, and mailing them costs the same as mailing anybody else. Search returns active records unless you ask for the rest, so this is mostly a field you read rather than one you set.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: status
Export column: Status
Append field: status

Credentials

The post-nominal letters the provider filed - MD, DO, NP, RN and the rest - exactly as they filed them.

Example: MD
What it is for: Salutation and segmentation. It is what lets an email open correctly, and it is a rougher but faster cut than specialty when you only need to separate physicians from everybody else. It is filed free-text, so treat it as a label rather than a controlled list: the same qualification appears as MD, M.D. and MD, FACP.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: credentials
Export column: Credentials
Append field: credentials
Worth knowing: Post-nominal qualifications live here. Generational suffixes - JR, SR, III - are a different field, and neither is derived from the other.

Identifier issued

The date the identifier was first issued.

Example: 2011-04-18
What it is for: A proxy for how long somebody has been practising, useful when you are separating a new graduate from a thirty-year practice and have nothing else to go on. It is a floor, not a career start: an identifier is issued when it is first needed.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: enumeration_date
Worth knowing: Appendable and on the record page, but not an export column and not on the v1 search row. Ask for it by appending your own file of identifiers.

Sole proprietor

Whether the provider filed as a sole proprietor.

Example: no
What it is for: A cheap read on practice size when you are separating independents from employed clinicians. It is what the provider filed rather than what an accountant would say today, so it is a hint that pairs with the employer field rather than a fact to route a rep on.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: sole_proprietor
Worth knowing: Blank where nothing was filed, which is not the same as "no".

9 fields

Name, in one piece and in parts

The filed name as one string, and the parts it was filed in. Nothing is ever split to fill a part: where only one string was filed, the parts are empty rather than guessed at.

Name

The whole filed name as one string, inverted for reading.

Example: SAMPLE JR, JORDAN E
What it is for: Reading, matching and display. It is the string to show a human and the string to match against when you are reconciling a list that has names but no identifiers. It is not the string to put in a CRM's surname field - that is what the parts are for.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: name
Export column: Name
Append field: name

First name

The given name, as filed.

Example: JORDAN
What it is for: A mail merge that says "Hi Jordan" rather than "Hi SAMPLE JR, JORDAN E". Pair it with the surname; on its own it is not enough to identify anybody.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: first_name
Export column: First name
Append field: first_name

Middle name

The middle name or initial, as filed.

Example: E
What it is for: Deduplication, almost exclusively. Two records with the same surname, first name and city are one person or two, and the middle initial is usually what decides it. Rarely worth showing a reader.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: middle_name
Export column: Middle name
Append field: middle_name

Last name

The surname, as filed. Empty on an organisation, which has no surname.

Example: SAMPLE
What it is for: The surname field of every CRM, and the strongest half of a name match. An organisation gets an empty cell here on purpose: putting a hospital's name in a surname field is how a merge ends up addressing a building.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: last_name
Export column: Last name
Append field: last_name

Prefix

DR, MR and the like, where one was filed.

Example: DR
What it is for: Formal salutations. It is filed in the register's own spelling, which is upper case and full-stopped, so most importers want it cased before it goes into a picklist.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API and in an export.
API field: name_prefix
Export column: Prefix
Append field: Not appendable
Worth knowing: On the API and in an export, but not an append field. If you need it against your own file, take it from an export keyed on the identifier.

Suffix

A generational suffix - JR, SR, III - where one was filed.

Example: JR
What it is for: Telling a father and a son apart, which matters more than it sounds: they often share a surname, a first name, a speciality and a practice address. Never treat a suffix as a qualification; those are in credentials.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: name_suffix
Export column: Suffix
Append field: suffix

Organisation name

The filed name of an organisation record. Empty on a person.

Example: Example Health Partners
What it is for: The account name. On an organisation record this is the name on the door, and it is what an account-based list is keyed on. A person's record leaves it empty; their employer is a different field.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API and in an export.
API field: organization_name
Export column: Organization name
Append field: Not appendable
Worth knowing: On the API and in an export, but not an append field - an append is keyed on the identifier, and the Name field already carries an organisation's name.

Company

One column that holds the right company whichever kind of record the row is: an organisation's own name, or a person's employer.

Example: Example Health Partners
What it is for: Loading a mixed file into a CRM without a formula. Every importer has one company field and it has to be filled from two different places depending on the row; this does that once, on our side.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an export.
API field: Not on the API
Export column: Company
Append field: Not appendable
Worth knowing: An export column only - it is composed for the file rather than stored, so there is nothing for the API to return. Every CRM preset uses it.

Last name for an importer

The surname a CRM's own Last Name field should be given, with the fallbacks an importer needs so no row arrives nameless.

Example: SAMPLE
What it is for: Getting a file past an importer that refuses a row with an empty Last Name. It is the filed surname where there is one, the whole filed string where the register filed no parts at all, and empty for an organisation, whose name belongs in Company.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an export.
API field: Not on the API
Export column: Last name for an importer
Append field: Not appendable
Worth knowing: An export column only, and the one the CRM presets use in place of the plain surname.

5 fields

Specialty and taxonomy

What the provider practises, as a code and as three levels of plain English. Asking for a classification matches every specialty beneath it.

Specialty

The display name of the provider's primary specialty.

Example: Internal Medicine Physician
What it is for: The single most useful segmentation field on the record, and the one every list is cut by. It is also what the CRM presets map to the Title or Job Title field, because that is the field a rep reads before a call.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: primary_taxonomy.display
Export column: Specialty
Append field: specialty

Taxonomy code

The reference code behind the specialty.

Example: 207R00000X
What it is for: Filtering precisely and reproducibly. Display names change wording between reference releases; the code does not, so a saved segment built on codes still means the same thing a year later. This is the field to store if you are keeping our segment definition in your own system.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API and in an append.
API field: primary_taxonomy.code
Export column: Not exportable
Append field: taxonomy_code
Worth knowing: On the API and appendable, but there is no export column for the raw code - exports carry the display name and the classification instead.

Specialty group

The heading the specialty sits under.

Example: Internal Medicine
What it is for: Sizing a segment at the level a plan is actually written at. "Internal Medicine" is a market; "Internal Medicine, Interventional Cardiology" is a territory. Filtering on the classification matches every specialisation beneath it, so this is the field to use when you do not yet know how far down you want to go.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: primary_taxonomy.classification
Export column: Specialty group
Append field: taxonomy_classification

Specialisation

The narrower specialisation inside the classification, where the provider filed one.

Example: Endocrinology
What it is for: The last cut before a named list. Most providers file no specialisation at all, so a filter on it is a much smaller audience than the classification above it - which is the right answer when the product only fits the sub-specialty, and the wrong one when you wanted the whole field.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: taxonomy_specialization
Worth knowing: Appendable, and on the record page inside the full taxonomy list. Not an export column and not on the v1 search row.

Matched specialty

When a specialty filter matched something other than the primary specialty, the one it actually matched.

Example: Cardiovascular Disease
What it is for: Explaining a result that otherwise looks wrong. A provider whose primary is Internal Medicine and whose second is Cardiovascular Disease is a cardiologist, and will appear in a cardiology search labelled Internal Medicine; this field is the reason. Null when no specialty filter was used, or when the primary is what matched.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account. It is returned by the API and shown on screen; there is no column for it in a file. Available over the API.
API field: matched_taxonomy
Export column: Not exportable
Append field: Not appendable

7 fields

Practice location

Where the provider practises, as filed - not where they live. The home address is a different, contracted product with its own section below.

Practice street

The street line of the practice address.

Example: 100 Sample Way, Suite 4
What it is for: Routing a rep to a door, and collapsing a group practice: eleven clinicians at one suite is eleven letters through one door, which is why an export can cap how many rows it writes per address.
How complete: 9,469,070 of 9,469,127 (100%) of the providers on the published specialty lists carry a practice location. The same count is published per specialty and per state on the list pages.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: address_line
Worth knowing: This is the asymmetry people write in about most. City, state and ZIP are on the API and in every export; the street line is appendable and on the record page, and is in neither the v1 search row nor an export column.

Practice city

The town or city of the practice address.

Example: Anytown
What it is for: Territory lines and metro sizing, and half of the weakest name-match rule the append tool will use. On its own a city is ambiguous - there are towns of the same name in a dozen states - so it is always read with the state.
How complete: 9,469,070 of 9,469,127 (100%) of the providers on the published specialty lists carry a practice location. The same count is published per specialty and per state on the list pages.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: city
Export column: City
Append field: city

Practice state

The two-letter state of the practice address.

Example: ST
What it is for: The first cut on almost every list, the unit most sales territories are drawn in, and the field a licensing question is asked against. Note that it is the practice state, not the licence state, and the two disagree more often than people expect.
How complete: 9,469,070 of 9,469,127 (100%) of the providers on the published specialty lists carry a practice location. The same count is published per specialty and per state on the list pages.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: state
Export column: State
Append field: state

Practice ZIP

The five-digit postal code of the practice address. A nine-digit code is cut to its first five.

Example: 00000
What it is for: Radius search, catchment modelling and the single strongest of the name-based match rules - a surname plus a practice ZIP identifies one provider far more often than a surname plus a state. It is also what a territory is really drawn in once it gets below state level.
How complete: 9,469,070 of 9,469,127 (100%) of the providers on the published specialty lists carry a practice location. The same count is published per specialty and per state on the list pages.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: postal_code
Export column: ZIP
Append field: postal_code

Mailing address

The separate mailing address, where the provider filed one: street, city, state and ZIP.

Example: PO Box 100, Anytown, ST 00000
What it is for: Physical mail that has to arrive. A practice address is where care happens and is frequently a suite in a building with a shared mailroom; the mailing address is where the provider asked to be written to. For anything posted, prefer it and fall back to the practice address.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: mailing_address, mailing_city, mailing_state, mailing_zip
Worth knowing: Four append fields, and on the record page. Not on the API row, and not export columns.

Practice locations

How many practice locations we hold for the record - the main practice address plus every additional location filed under the same identifier.

Example: 3
What it is for: Separating a single-site clinician from one who covers a network, and a good early filter for anything sold by site count. It is a count of what was filed, so a provider who covers four sites and filed one reads as one.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: practice_locations_count

Distance

How far the practice is from the centre of the ZIP you searched around, in miles.

Example: 4.2
What it is for: Ordering a radius search by how close somebody actually is, and defending a territory boundary. It exists only on a search that used a ZIP and a radius; on any other search it is empty.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account. It is computed for the search that asked for it rather than stored, so there is nothing to append. Available over the API and in an export.
API field: distance_miles
Export column: Distance (miles)
Append field: Not appendable

10 fields

Contact

The practice phone is filed on the public record. The work email is not - it has to be confirmed, so it is the one field on the record that carries a measured tier.

Practice phone

The phone number filed against the practice location. A practice line, not a personal one.

Example: (555) 010-0123
What it is for: Calling the practice and reaching whoever answers it. It is the number to give a rep for a first call and the wrong number for anything that has to reach one named person. Paired with a surname it is also one of the stronger rules the append tool matches on.
How complete: 9,467,101 of 9,469,127 (100%) of the providers on the published specialty lists carry a practice phone. The same count is published per specialty and per state on the list pages.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API, in an export and in an append.
API field: phone
Export column: Phone
Append field: phone

Phone source

A short phrase saying where the practice phone came from.

Example: (a short phrase naming the public register the number was filed in)
What it is for: Defending a number to a compliance reviewer who wants to know how you came by it. It is a single fixed phrase rather than a varying label, so it is more useful in an audit file than on a screen.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an export.
API field: Not on the API
Export column: Phone source
Append field: Not appendable
Worth knowing: An export column only.

Work email

The best work email address we hold for the provider.

Example: jordan.sample@example.com
What it is for: Reaching one named person directly, which is the thing a practice phone cannot do. Read it with its trust tier below: the address alone is a string, and the tier is what tells you whether to send to it.
How complete: 4,892,855 of 9,469,127 (52%) of the providers on the published specialty lists carry a work email. The same count is published per specialty and per state on the list pages.
What it costs: Metered reveal A metered reveal on screen: one provider at a time, counted, and free for the rest of the month if the same provider is opened again. In a file or over the API it comes with an account, against your plan's export, append and call allowances. Available over the API, in an export and in an append.
API field: email
Export column: Email
Append field: work_email

Work email trust tier

How much we stand behind an address: trusted, probable, doubtful or rejected - and null when it has not been measured at all.

Example: trusted
What it is for: Deciding what to send and what to sit on. Trusted is safe to send; probable is good enough to tell you where somebody works but not to mail without care; doubtful is kept and shown and never acted on; rejected is not usable. Null is "not measured", which fails every trust filter - it is never treated as fine.
How complete: 3,084,198 of 9,469,127 (33%) of the providers on the published specialty lists carry a work email in the trusted tier. The same count is published per specialty and per state on the list pages.
What it costs: Included with an account Included with an account. There is no tier column in a file; instead a file can be told to write only trusted-tier addresses, and an append does that by default. Available over the API.
API field: email_trust_tier
Export column: Not exportable
Append field: Not appendable
Worth knowing: No column of its own in an export or an append - the switch is a trusted-only option on the job, and the job result counts how many cells it blanked. The tiers are explained on the email trust page.

Work email source

A short phrase saying how the address reached us.

Example: Practice website
What it is for: Two jobs. It is how a compliance reviewer traces an address, and it is how you decide which of several addresses for one provider to prefer when the tiers are equal. An address and its source column always agree: a blanked address never leaves its source behind.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: email_source
Export column: Email source
Append field: work_email_source

Further work emails

The other addresses we hold for the same provider, best first, each with its own source.

Example: j.sample@example.com; jordan.sample@example.org
What it is for: Coverage on a provider who has moved, or who is reachable at two organisations. A second address is the difference between a bounce and a delivery on somebody who changed jobs and kept practising. A file carries up to four further addresses beside the best one.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Metered reveal The same as the work email: a metered reveal on screen, and in a file or over the API against your plan's allowances. Available over the API, in an export and in an append.
API field: emails
Export column: Email 2 … Email 5, with Email 2 source … Email 5 source
Append field: all_emails, all_emails_with_sources

Email count

How many addresses we hold for the provider. Always exact, even where the row lists only the best few.

Example: 2
What it is for: Judging a list before you buy it, and judging a row before you mail it. A count of zero is the honest statement that this provider is not reachable by email through us, and it is the field to filter on when you want a segment that is.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: email_count
Export column: Emails
Append field: email_count

Email domains

The distinct domains of the addresses we hold for the provider.

Example: example.com; example.org
What it is for: Rolling a list of clinicians up to the organisations behind them without a name match. Two providers on the same domain are usually two colleagues, which is the cheapest account grouping there is - and it is a hint rather than a fact, because a domain can be a shared consumer mailbox.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: email_domains

Personal email

A known personal address, where one is on the record and marked as personal rather than work.

Example: j.sample@example.net
What it is for: Recruiting, mostly - the case where a work address is the wrong place to write. It is far thinner than the work address and should never be the only route in a campaign.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Metered reveal A metered reveal on screen, and appendable against your plan's append rows. It is not an export column and not on the v1 search row. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: personal_email

Phones from your own contact files

Numbers your own organisation supplied for a provider in a contact file, given back beside the record.

Example: (555) 010-0124 (office); (555) 010-0125 (cell)
What it is for: Keeping what you already knew. If you have loaded your own numbers, this is how they come back out attached to the identifier rather than to whatever row they arrived on. Empty for an organisation that has loaded none, which is most.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an export.
API field: Not on the API
Export column: Phones from contact files
Append field: Not appendable
Worth knowing: An export column only, and it holds your own data rather than ours. Suppressed numbers are left out of it like any other.

6 fields

Employment and affiliation

Who a provider works for, how that was established, and the systems the practice runs. Everything in this group is worked out rather than filed, so everything in it carries how it was worked out.

Employer

The organisation a provider works for, where one can be justified.

Example: Example Health Partners
What it is for: Rolling clinicians up to the account that signs. It is the field that turns a list of names into a list of opportunities, and the field a territory is really assigned on once a team sells to systems rather than to individuals. Read it with the employer source: an employer nobody can justify is not published.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: employer_name
Export column: Employer
Append field: employer_name

Employer domain

The employer's web domain.

Example: examplehealth.com
What it is for: The account key every CRM already has. Matching a provider to an account by domain is faster and far more reliable than matching by name, which is why the CRM presets map this to the Website field rather than mapping the employer name to it.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: employer_domain
Export column: Employer domain
Append field: employer_domain

Employer source

How the employer was worked out, in plain words.

Example: The provider's own email domain
What it is for: Deciding how much weight to put on the employer. Some routes are a federal filing saying so; others are an inference from colleagues at the same address. The column tells you which, which is what a careful buyer wants before they route an account on it.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: employer_source
Export column: Employer source
Append field: employer_source
Worth knowing: The API returns a short code; an export writes the sentence.

Billing group

The group a provider reassigns their billing to, as named in federal enrolment filings.

Example: Example Health Partners LLC
What it is for: The hardest evidence of employment there is, because it is a filing rather than an inference. It is also frequently a legal entity rather than the name on the door, so it is better as a join key and a corroboration than as something to print in a letter.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: billing_group

Record system

The electronic health record the practice runs, where that is evidenced.

Example: Example EHR
What it is for: Qualifying anything that has to integrate. If your product plugs into two systems and not a third, this field is the difference between a pipeline and a list. It is evidenced rather than surveyed, so absence means "no evidence", not "no system".
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: ehr_system
Export column: EHR system
Append field: ehr_system

Record system source

How the record system was identified, in plain words.

Example: Most colleagues at the same employer
What it is for: The same job the employer source does. Some routes are the practice publishing its own technical endpoint; others are what the majority of colleagues at the same organisation run. Treat the second as a strong hint and the first as a fact.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: ehr_source
Export column: EHR source
Append field: ehr_source

2 fields

Licences

The licence numbers and states filed against the record. A licence is filed by the provider against a specialty, so one record can carry several.

Licence number

The state licence number as filed against the provider's specialty.

Example: A00000
What it is for: Credentialling and verification. It is the number somebody takes to a state board to check standing, and it is the join key when you are reconciling our record against a board's own roster. It is what was filed, so treat it as a lead for verification rather than as verification.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: license_number
Worth knowing: Appendable, and on the record page with the full licence list. Not an export column and not on the v1 search row.

Licence state

The state that issued the licence.

Example: ST
What it is for: Checking that somebody may practise where you want to place them, which is not the same question as where they practise today. A clinician near a state line commonly holds licences on both sides, and only this field shows it.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: license_state

4 fields

Standing

Whether a provider can be billed for at all, and what federal programmes say about them. This is the group that saves money before it is spent.

Programme exclusion

Whether the provider is on a federal exclusion list and has not been reinstated.

Example: no
What it is for: The check before anything else. An excluded provider cannot be billed for, and a contract signed with one is a problem that gets more expensive the longer it runs. It is also a clean reason to drop rows from a campaign before you pay to mail them.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: excluded
Worth knowing: Appendable, and a filter on search. Not an export column and not on the v1 search row.

Opted out

Whether the provider has opted out of the federal programme.

Example: no
What it is for: Reimbursement and eligibility questions. A provider who has opted out is not billing the programme, which changes both what you can sell them and how their patients pay. Often the explanation for a busy clinician with no utilisation figures at all.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: medicare_opted_out

Programme patients

How many programme patients the provider saw, in the latest published year.

Example: 1,240
What it is for: Sizing a practice by what it does rather than by how many people work there. It is a floor rather than a total - small counts are withheld by the publisher and stay withheld here rather than being filled in with a zero - and it says nothing about patients outside the programme.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: medicare_beneficiaries
Worth knowing: Nothing under eleven patients is published, so a blank is not a zero.

Industry payments

Money reported as paid to this provider by industry - consulting, speaking, travel, food - totalled in dollars over the latest year published.

Example: 4,820.00
What it is for: Two very different jobs. It is a conflict-of-interest check for anyone who has to run one, and it is a relationship signal for anyone selling into a speciality where the field already pays for speaking and consulting. Read it as one year's published total rather than a career total: the year moves as new figures are published, and what you get is always the latest one held.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available in an append.
API field: Not on the API
Export column: Not exportable
Append field: industry_payments_total

4 fields

What they do

Not who a provider is but what they actually did: the procedures they billed and the drugs they prescribed, from published Medicare data for one year. This is the group that answers “find me the surgeons who really do this operation” rather than “find me the surgeons”. A provider has many lines and a file has one row per provider, so a file carries a summary of them — the highest-volume few, and the sizes — under headers that name the data year, while the lines themselves stay on their own API call. Those columns widen a row and never add one, so a file costs the same rows with them as without. Read the limits on each entry before you plan around it - it is Medicare fee-for-service only, it covers about one in six clinicians, and low-volume providers are removed from the published file before we receive it, so five rows in six carry “No published volume” rather than a number.

Procedure billed

A procedure the provider billed Medicare for, as its published code with a plain-English description, at each place of service.

Example: 27447 - total knee replacement, office
What it is for: Finding the clinicians who demonstrably perform a procedure, rather than the ones whose specialty suggests they might. It is the difference between a list of orthopaedic surgeons and a list of orthopaedic surgeons who billed knee replacements. You can search by name rather than by code, so “knee replacement” finds the code for you, and the filter works as an exclusion too.
How complete: 1,144,245 of 7,492,373 active individual providers (15%) have a published procedure line, measured 2026-10-05. That is a count of providers, not an estimate, and it is a national one: the share is far higher in the specialties that bill Medicare Part B most, and the data page publishes it per specialty. The rest are blank on these fields, and low-volume providers are removed from the published file before we receive it - so a blank does not mean they do none of it.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: code, description, place_of_service
Export column: Top Medicare procedures
Append field: top_procedures
Worth knowing: Every line has its own API call per provider, because a busy surgeon has dozens of codes and a large group has hundreds. A file has one row per provider, so it carries a summary instead: the three highest-volume procedures in one cell, each as its published code, its description and its volume, separated by “; ” — the same separator the phone and email columns already use. Three, because that is what a cell holds and a person reads, and the same three in an export and in an append. The header carries the data year, so the file says which year the numbers are from. An absence is not a no: low-volume rows are removed before publication, so a provider not shown for a code may still do it for a small number of Medicare patients, or for patients on any other insurance.

Procedure volume

For each procedure: how many services and how many Medicare patients, with the published average submitted charge, allowed amount and payment.

Example: 112 services, 94 patients, 1,480.00 allowed
What it is for: Sizing and ranking. “At least fifty of these last year” is a different and much better target than “does these”, and the published averages tell you what the procedure is worth where they practise, which is what a device or service priced against it needs. Read a volume as Medicare volume, not total volume - the same clinician may do several times as much outside the programme.
How complete: 1,144,245 of 7,492,373 active individual providers (15%) have a published procedure line, measured 2026-10-05. That is a count of providers, not an estimate, and it is a national one: the share is far higher in the specialties that bill Medicare Part B most, and the data page publishes it per specialty. The rest are blank on these fields, and low-volume providers are removed from the published file before we receive it - so a blank does not mean they do none of it.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: beneficiaries, services, avg_submitted_charge, avg_allowed_amount, avg_payment_amount
Export column: Top Medicare procedures, Medicare services, Medicare procedure codes
Append field: top_procedures, procedure_services, procedure_codes
Worth knowing: In a file this is two numbers, plus the volume beside each procedure in the top cell: how many services were published for the provider across every line, and how many distinct codes those lines cover. There is no total-patients column and there will not be one built from these lines — patients are published per line and the same patient appears on as many lines as they had procedures, so adding them up produces a number that counts nobody. The separately published per-provider patient total is its own entry on this page. A provider with nothing published reads “No published volume”, never 0 and never an empty cell: the published data carries no zeros, because a low-volume line is removed rather than published small. Each header carries the data year. One year is held, so there is no previous year to compare with: nothing here supports “rising”, “falling” or “recently started”, and we will not imply otherwise until earlier years are loaded.

Drug prescribed

A drug the provider prescribed under Medicare Part D, by brand name and by generic name.

Example: ELIQUIS (APIXABAN)
What it is for: Reaching prescribers by what they actually write. A generic name means the molecule - every prescription filed under it, whichever brand - so you can target a therapy class or one brand within it, and search by either name without knowing which is which. As an exclusion it is just as useful: leave out everybody already writing a competitor.
How complete: 1,135,392 of 7,492,373 active individual providers (15%) have a published prescribing row, measured 2026-10-05. That is a count of providers, not an estimate, and it is a national one: the share is far higher in the specialties that bill Medicare Part B most, and the data page publishes it per specialty. The rest are blank on these fields, and low-volume providers are removed from the published file before we receive it - so a blank does not mean they do none of it.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: brand_name, generic_name
Export column: Top Part D drugs
Append field: top_drugs
Worth knowing: Part D only: what a prescriber writes for patients with Medicare drug coverage, not what they write for everybody. Every line has its own API call per provider; a file carries the three highest-volume drugs in one cell, separated by “; ”, each written as “BRAND / GENERIC” where the two differ and as the one name where they do not — both, because a search means one or the other depending on who is asking. The header carries the data year.

Prescribing volume

For each drug: claims, patients and total drug cost as published, with the share for patients aged 65 and over.

Example: 412 claims, 96 patients, 184,300.00
What it is for: Ranking prescribers inside a therapy class, which is the whole job for anyone selling against one. “At least four hundred claims” separates the prescribers worth a visit from the ones who wrote it twice, and the cost figure is what a formulary conversation is actually about.
How complete: 1,135,392 of 7,492,373 active individual providers (15%) have a published prescribing row, measured 2026-10-05. That is a count of providers, not an estimate, and it is a national one: the share is far higher in the specialties that bill Medicare Part B most, and the data page publishes it per specialty. The rest are blank on these fields, and low-volume providers are removed from the published file before we receive it - so a blank does not mean they do none of it.
What it costs: Included with an account Included with an account, against your plan's row and call allowances. Available over the API, in an export and in an append.
API field: claims, beneficiaries, drug_cost, claims_65_plus
Export column: Top Part D drugs, Part D claims, Part D drugs
Append field: top_drugs, prescribing_claims, prescribing_drugs
Worth knowing: In a file this is two numbers, plus the volume beside each drug in the top cell: how many claims were published for the prescriber across every drug, and how many drugs they have a published row for, counting one brand-and-generic combination as one drug. A missing count is never a zero, so the cell reads “No published volume” rather than being left blank. The published file leaves out low-volume prescribing entirely rather than flagging it, so a prescriber with nothing here may be below the publication threshold - and we cannot tell you which. Each header carries the data year. One year, so no trend.

10 fields

Organisation and facility

A certified facility carries everything a provider record does, plus what only an organisation has: a certification, a size, an owner, a chain and a leadership team.

Certification number

The number a certified facility is certified under. One number, one certified facility.

Example: 000000
What it is for: The join key for a facility, the way the identifier is for a provider. It is what links a facility to its published ratings, its bed count and its ownership, and it is the key to keep when you load facilities into a CRM as accounts.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the facility pages and over the API. Facility records are their own product and are not columns in a provider export. Available over the API.
API field: ccn
Export column: Not exportable
Append field: Not appendable

Facility family and category

Which kind of certified organisation it is - hospital, nursing home, hospice, home health agency, dialysis centre or another certified type - and the category beneath it.

Example: hospital
What it is for: The first cut on any facility list, and the level at which a product is usually sold. The category beneath it is what separates a critical-access hospital from a general one, which is frequently the difference between a fit and a waste of a call.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: facility_type, category, subtype
Export column: Not exportable
Append field: Not appendable

Certified beds

How many beds the facility is certified for.

Example: 120
What it is for: The size field. Almost everything sold into an inpatient setting is priced or sized on beds, and it is the most reliable proxy for budget on a facility record. Empty on facility families where beds are not the unit - a home health agency has none.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: beds
Export column: Not exportable
Append field: Not appendable

Ownership type

Whether the facility is for-profit, non-profit or government, in the publisher's own words.

Example: Non-profit - Corporation
What it is for: Qualifying how a purchase gets made. A government facility buys on a schedule and a procurement process; a for-profit chain buys centrally; an independent non-profit buys locally. It changes the sales motion more than the size field does.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: ownership_type
Export column: Not exportable
Append field: Not appendable

Chain

The chain the facility reports under, where it reports one.

Example: Example Care Group
What it is for: Finding the buyer above the building. A chain name is how twelve separate facility records become one account, and it is the field to group on before anybody calls, so two reps do not call the same head office.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: chain_organization
Export column: Not exportable
Append field: Not appendable

Published ratings

The facility's published quality ratings - overall, health inspection, staffing and quality measures - as the publisher released them.

Example: 4
What it is for: Prioritising, and qualifying anything sold on quality improvement. A low staffing rating is a live problem somebody is being asked about. The ratings are carried as published: we neither recompute them nor infer anything beneath them.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: overall_rating, health_inspection_rating, staffing_rating, quality_measure_rating
Export column: Not exportable
Append field: Not appendable

Emergency services

Whether the facility offers emergency services.

Example: yes
What it is for: A fast qualifier for anything that only applies to a facility with an emergency department. Empty where the publisher did not say, which is not the same as no.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: emergency_services
Export column: Not exportable
Append field: Not appendable

The facility's billing identifier

The organisation identifier the facility bills under, where the two are linked.

Example: 0000000000
What it is for: Crossing between the two halves of the product. It is what joins a certified facility to the clinicians who bill under it, so an account plan can carry both the building and the people in it. Not every facility is linked to one.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility pages and over the API. Available over the API.
API field: npi
Export column: Not exportable
Append field: Not appendable

Leadership, counted by role

How many named leadership people an organisation has, by role - chief executives, finance, nursing, medical directors, administrators, compliance, board members and owners.

Example: Executive 2 · Finance 1 · Owner 3
What it is for: Sizing the buying committee before you go looking for it, and deciding which accounts are worth the effort. A facility with a named compliance officer and a named chief nursing officer is a different sale from one with neither.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public as counts. The names and titles behind the counts are for signed-in customers. Available over the API.
API field: leadership.total, leadership.by_role
Export column: Not exportable
Append field: Not appendable
Worth knowing: Counts on every public page and over the API. Nobody without an identifier of their own is named in public, anywhere on this site.

Linked providers

The clinicians who bill under the organisation or practise at the facility, counted by specialty.

Example: Internal Medicine 24 · Cardiology 6
What it is for: Reading what a facility actually does, which its type does not tell you. It is also the bridge from an account to the individuals inside it, and the counts are what a territory is sized on before a rep is hired.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the organisation and facility pages and over the API. Available over the API.
API field: affiliated_providers, by_specialty
Export column: Not exportable
Append field: Not appendable

2 fields

Health system

The layer above a facility: the system or chain it belongs to, and what else that system operates.

Health system

The system or chain the facility belongs to, where it belongs to one large enough to publish.

Example: Example Care Group
What it is for: The account, when the account is bigger than a building. This is the level a framework agreement is signed at, and grouping on it is how a list of two hundred facilities becomes a list of twenty conversations.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the facility and system pages and over the API. Available over the API.
API field: system.slug, system.label
Export column: Not exportable
Append field: Not appendable

System footprint

How many certified facilities the system operates, how many beds between them, which states they are in, and how the facilities split by family.

Example: 18 facilities · 2,400 beds · 4 states
What it is for: Deciding whether a system is worth a named account team, and sizing the deal before the first call. The state list is also the fastest way to see whether a system sits inside one territory or crosses several.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public, on the system pages and over the API. Available over the API.
API field: facilities, beds, states, by_type
Export column: Not exportable
Append field: Not appendable
Worth knowing: A system gets a page of its own only above a published floor of active facilities; smaller chains are still named on their facilities.

4 fields

Home address and cell phone

Licensed data, available only under an agreement that names what it may be used for. These are matched to the provider rather than filed by them, which is why each one carries a confidence score - and why they are never in a list and never over the API.

Home address

Where a provider lives, matched to the named provider from a licensed file rather than filed by them.

Example: (not shown here - revealed one provider at a time, under contract)
What it is for: Reaching a clinician who is not reachable at a practice, which is a narrow and genuine need - recruiting, and mail that must not go through a practice mailroom. It is the wrong tool for volume, and it is not sold that way.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Contract only Contract only. It is switched on for an organisation by a person here, after an agreement stating the permissible use; plans that include it are not in online checkout. Revealing it costs more than an ordinary reveal, because the data underneath has a cost. It is in no file and on no API route: it is revealed, or not at all.
API field: Not on the API
Export column: Not exportable
Append field: Not appendable
Worth knowing: There is no home address column in an export on any plan, not even an empty one, and asking for it over the API is refused by name rather than answered with blanks. Only a confirmed match under the current matching model is ever handed over: a probable one, one waiting on review, or one made by an older model is treated exactly as if nothing were on file.

Cell phone

A provider's personal mobile number, matched to the named provider the same way the home address is.

Example: (not shown here - revealed one provider at a time, under contract)
What it is for: The same narrow job as the home address, for a call rather than a letter. Whether to call or text it at all is a decision you make, not one the field makes for you.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Contract only Contract only, revealed one provider at a time and counted, on the same terms as the home address. A key that asks for it is refused by name rather than answered with blanks, because a column of empties looks like poor coverage and a refusal tells the truth. It is in no file and on no API route: it is revealed, or not at all.
API field: Not on the API
Export column: Not exportable
Append field: Not appendable

Match confidence

How well the link between the provider and a person in the licensed file is evidenced, out of a hundred.

Example: 92
What it is for: Knowing what you are holding. The score is built from signals that are each named and weighted - how closely the first name agrees, how rare the name is, how far the home is from the practice, and the middle initial, age, gender and suffix where they are known. Every signal agreeing on a name almost nobody has is a confident match; the same signals agreeing on one of forty people with a common name in one dense metropolitan area is not a match at all, and is not treated as one.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Contract only Contract only. It travels with the value it describes, every time one is revealed. It is in no file and on no API route: it is revealed, or not at all.
API field: Not on the API
Export column: Not exportable
Append field: Not appendable
Worth knowing: Distance from the practice is measured in miles rather than as a state, because roughly one American worker in ten crosses a state line to get to work: matching on state alone both misses real people and invents others.

Do Not Call flag

Whether the records we hold for a revealed cell number carry a Do Not Call flag. It has three states, not two: flagged, not flagged, and unknown.

Example: unknown
What it is for: Not being handed a number blind. Unknown means we could not determine it, and it is never reported as not flagged. The flag decides nothing - it never stops a reveal and never changes what you are charged, and it is looked up after the reveal is settled, so a failed lookup produces unknown rather than a failed reveal.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Contract only Contract only, shown with the cell phone it belongs to, at no extra cost. It is in no file and on no API route: it is revealed, or not at all.
API field: Not on the API
Export column: Not exportable
Append field: Not appendable
Worth knowing: It is not the live national registry, and nothing here may be read as saying a number is safe to call. Whether to call or text a number, flagged or not, is your decision, and compliance with do-not-call and telemarketing rules is yours.

2 fields

What every record carries

The two fields that are about the record rather than about the provider, and that decide how far you can trust the rest of it.

Last confirmed

The date the record was last confirmed against a refresh.

Example: 2026-01-01T00:00:00Z
What it is for: Deciding what is fresh enough for what you are doing. It is not the date the page was built and not the date the record was created; it is when we last saw the values stand up. Groups of fields are refreshed on different schedules, so a record is never uniformly current or stale.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API and in an export.
API field: updated_at
Export column: Updated
Append field: Not appendable

Suppressed fields

The fields on a record that were withheld because somebody asked for them to be, listed by name rather than left silently empty.

Example: phone
What it is for: Telling "withheld" apart from "nothing on file", which are opposite facts and look identical in a blank cell. On a page a withheld value says so; in a file the value is left out and counted in the job result, so the gap is a number you can check rather than one you have to notice.
How complete: Not published. We do not measure a fill rate for this field, so there is not one to quote.
What it costs: Free and public Free and public. It is on the open record pages and in search without an account. Available over the API.
API field: suppressed_fields
Export column: Not exportable
Append field: Not appendable
Worth knowing: Suppression reaches the public pages, the signed-in search, the counts, every export and every appended file, and it keeps applying through later refreshes. A record is never deleted outright, because a deleted record is one the next refresh recreates.

What this page does not answer

The questions a field list cannot settle.

Where does each field come from?

Not published, and deliberately so. Which registries, filings and suppliers a record is assembled from is a competitor's question rather than a customer's, so this site says what a field holds and how current it is and stops there. What we will tell you is how a value was reached in plain words, which is what the source columns on this page are for.

What is the fill rate for a field that says “not published”?

We have not measured it, so we will not quote one. The four figures we do publish - work email, trusted-tier email, practice phone and practice location - are counted per specialty and per state on the list pages, so you can check coverage for your own segment rather than for the database as a whole. If a segment matters enough to buy on, ask and we will count it for you.

How accurate is a field, as opposed to how complete?

This page does not claim an accuracy rate, because a single number for a whole database would not mean anything. What it gives you instead is per-field: the date the record was last confirmed, a measured tier on the one field that has to be confirmed rather than filed, and a plain-words source column on every derived field so you can see how a value was reached before you rely on it. Search is open without an account, so the fastest check is to look up a provider you already know.

Can I get a field that is not on this list?

This is everything the product supplies today. There is no hidden tier of fields and no propensity score, likelihood-to-buy number or invented completeness grade - if it is not here, we do not have it. If something you need is missing, tell us; it is a better use of the conversation than a field we would have to make up.

Which fields can I filter on?

More than can usefully be listed on one page, and the set changes as filters are added. The API reference is the current list for a key, and the search screen is the current list for a person. This page is about what a field is; that one is about what you can ask for.

Check a field against a provider you already know.

Search is open without an account. Look somebody up, see which of these fields we actually hold for them, and judge the reference from that rather than from a page.

Search providers API reference Exports and append