{"id":54335,"date":"2026-02-01T13:02:08","date_gmt":"2026-02-01T19:02:08","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/glossary-2\/"},"modified":"2026-03-01T04:05:13","modified_gmt":"2026-03-01T10:05:13","slug":"glossary","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/glossary\/","title":{"rendered":"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/glossary-a1000f3e.png.webp\" alt=\"54334\" \/><\/p>\n<h1>Healthcare recruiting contact data glossary<\/h1>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Calm and simple; every definition leads to a next step.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_65 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\r\n<div class=\"ez-toc-title-container\">\r\n<p class=\"ez-toc-title\" >What&rsquo;s on this page:<\/p>\r\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\r\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Who_this_is_for\" title=\"Who this is for\">Who this is for<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Quick_Answer\" title=\"Quick Answer\">Quick Answer<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Framework_The_%E2%80%9COne-Screen_Glossary%E2%80%9D_Rule_Definition_%E2%86%92_Why_it_matters_%E2%86%92_Next_step\" title=\"Framework: The \u201cOne-Screen Glossary\u201d Rule: Definition \u2192 Why it matters \u2192 Next step\">Framework: The \u201cOne-Screen Glossary\u201d Rule: Definition \u2192 Why it matters \u2192 Next step<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Micro-Asset_Diagnostic_Table\" title=\"Micro-Asset: Diagnostic Table\">Micro-Asset: Diagnostic Table<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Step-by-step_method\" title=\"Step-by-step method\">Step-by-step method<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Weighted_Checklist\" title=\"Weighted Checklist:\">Weighted Checklist:<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Micro-Asset_Outreach_Templates\" title=\"Micro-Asset: Outreach Templates\">Micro-Asset: Outreach Templates<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Email_template_first_touch\" title=\"Email template (first touch)\">Email template (first touch)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Voicemail_template_if_you_reached_voicemail\" title=\"Voicemail template (if you reached voicemail)\">Voicemail template (if you reached voicemail)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Gatekeeper-friendly_script_main_line\" title=\"Gatekeeper-friendly script (main line)\">Gatekeeper-friendly script (main line)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Common_pitfalls\" title=\"Common pitfalls\">Common pitfalls<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#How_to_improve_results\" title=\"How to improve results\">How to improve results<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#1_Use_a_single_scorecard_with_fixed_denominators\" title=\"1) Use a single scorecard with fixed denominators\">1) Use a single scorecard with fixed denominators<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#2_Segment_before_you_%E2%80%9Cfix%E2%80%9D_anything\" title=\"2) Segment before you \u201cfix\u201d anything\">2) Segment before you \u201cfix\u201d anything<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#3_Tie_improvements_to_one_lever_at_a_time\" title=\"3) Tie improvements to one lever at a time\">3) Tie improvements to one lever at a time<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#4_Make_refresh_a_scheduled_step\" title=\"4) Make refresh a scheduled step\">4) Make refresh a scheduled step<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Legal_and_ethical_use\" title=\"Legal and ethical use\">Legal and ethical use<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Evidence_and_trust_notes\" title=\"Evidence and trust notes\">Evidence and trust notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#FAQs\" title=\"FAQs\">FAQs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Whats_the_difference_between_verification_and_data_quality\" title=\"What\u2019s the difference between verification and data quality?\">What\u2019s the difference between verification and data quality?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Which_metrics_should_recruiting_ops_standardize_first\" title=\"Which metrics should recruiting ops standardize first?\">Which metrics should recruiting ops standardize first?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Whats_the_difference_between_opt-out_and_unsubscribe\" title=\"What\u2019s the difference between opt-out and unsubscribe?\">What\u2019s the difference between opt-out and unsubscribe?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#How_should_we_handle_opt-outs_across_multiple_tools\" title=\"How should we handle opt-outs across multiple tools?\">How should we handle opt-outs across multiple tools?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Is_NPI_enough_to_build_outreach_lists\" title=\"Is NPI enough to build outreach lists?\">Is NPI enough to build outreach lists?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Where_do_I_go_next_if_I_need_the_operational_workflow_not_just_definitions\" title=\"Where do I go next if I need the operational workflow, not just definitions?\">Where do I go next if I need the operational workflow, not just definitions?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#Next_steps\" title=\"Next steps\">Next steps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/#About_the_Author\" title=\"About the Author\">About the Author<\/a><\/li><\/ul><\/nav><\/div>\r\n<h2><span class=\"ez-toc-section\" id=\"Who_this_is_for\"><\/span>Who this is for<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This hub is for recruiters and recruiting ops teams who need clean definitions for <strong>provider contact data<\/strong>, <strong>data quality<\/strong>, <strong>consent<\/strong>, <strong>opt-out<\/strong>, and outreach performance\u2014without jargon and without debates.<\/p>\n<p><strong>Tip:<\/strong> Use Ctrl+F (or your browser\u2019s Find) to jump to a term fast. Bookmark this page and link it in your SOP so everyone uses the same language.<\/p>\n<p><strong>Human check (BURNOUT_CHECK):<\/strong> If your team is re-litigating terms in Slack, you\u2019re paying for it in delays, rework, and candidate frustration. Standardize language once, then standardize workflow.<\/p>\n<p><strong>Jump to:<\/strong><\/p>\n<ul>\n<li><a href=\"#quick-answer\">Quick Answer<\/a><\/li>\n<li><a href=\"#diagnostic-table\">Diagnostic Table (one-screen glossary)<\/a><\/li>\n<li><a href=\"#step-by-step-method\">Step-by-step method<\/a><\/li>\n<li><a href=\"#templates\">Outreach templates<\/a><\/li>\n<li><a href=\"#evidence\">Evidence and trust notes<\/a><\/li>\n<\/ul>\n<p><strong>Choose your path:<\/strong><\/p>\n<ul>\n<li><strong>Sourcers:<\/strong> Start with <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/\">provider contact data workflow<\/a>, then use the checklist below to decide what\u2019s outreach-ready.<\/li>\n<li><strong>Recruiters:<\/strong> Use the templates and track the five metrics so you can fix the right bottleneck (deliverability vs connectability vs message fit).<\/li>\n<li><strong>Ops leaders:<\/strong> Standardize definitions and QA gates with <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/\">data quality verification<\/a>, then align handling with <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-compliance\/\">recruiting compliance basics<\/a>.<\/li>\n<\/ul>\n<h2 id=\"quick-answer\"><span class=\"ez-toc-section\" id=\"Quick_Answer\"><\/span>Quick Answer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<dl>\n<dt>Core Answer<\/dt>\n<dd>A practical glossary of healthcare recruiting contact data terms with consistent definitions, why each matters, and the next operational step for recruiters and ops.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Definitions only help if they map to actions: what you verify, what you suppress, and what you measure in outreach.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiters and ops teams who want definitions without jargon.<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; Safety<\/strong><\/p>\n<p>This method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.<\/p>\n<\/blockquote>\n<h2><span class=\"ez-toc-section\" id=\"Framework_The_%E2%80%9COne-Screen_Glossary%E2%80%9D_Rule_Definition_%E2%86%92_Why_it_matters_%E2%86%92_Next_step\"><\/span>Framework: The \u201cOne-Screen Glossary\u201d Rule: Definition \u2192 Why it matters \u2192 Next step<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Every term below follows the same pattern so your team can use it in real workflows:<\/p>\n<ul>\n<li><strong>Definition:<\/strong> what the term means (short and consistent).<\/li>\n<li><strong>Why it matters:<\/strong> how it impacts speed-to-submittal, connectability, deliverability, and workflow fit.<\/li>\n<li><strong>Next step:<\/strong> the operational move (verify, suppress, segment, or escalate).<\/li>\n<\/ul>\n<p>Stable hub principle: fewer concepts, clearer decisions. If a vendor or teammate uses a different definition, you\u2019ll spot the mismatch immediately.<\/p>\n<h2 id=\"diagnostic-table\"><span class=\"ez-toc-section\" id=\"Micro-Asset_Diagnostic_Table\"><\/span>Micro-Asset: Diagnostic Table<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>GLOSSARY_TABLE:<\/strong> term \u2192 why recruiters care \u2192 where it shows up. Use this during list build, outreach setup, and reporting reviews.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Term<\/th>\n<th>Definition<\/th>\n<th>Why recruiters care<\/th>\n<th>Where it shows up<\/th>\n<th>Next step<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Provider contact data<\/td>\n<td>Work-relevant ways to reach a clinician (email, phone, practice line, location context) used for recruiting outreach.<\/td>\n<td>Bad contact data wastes dials, burns sender reputation, and slows submittals.<\/td>\n<td>Sourcing lists, CRM records, outreach tools<\/td>\n<td>Define required fields per channel; verify before scale.<\/td>\n<\/tr>\n<tr>\n<td>Data quality<\/td>\n<td>Fitness of contact data for a specific recruiting workflow (accuracy, completeness, recency, and compliance readiness).<\/td>\n<td>Quality is workflow-specific; \u201cgood\u201d for email may be \u201cbad\u201d for calls.<\/td>\n<td>Dashboards, QA checklists<\/td>\n<td>Set thresholds per channel and role; document them.<\/td>\n<\/tr>\n<tr>\n<td>Verification<\/td>\n<td>Checks that contact details are valid and appropriate for outreach (format, deliverability, ownership signals, and recency).<\/td>\n<td>Verification is the difference between \u201csent\u201d and \u201creached.\u201d<\/td>\n<td>Pre-campaign QA, enrichment steps<\/td>\n<td>Set pass\/fail rules per channel; re-verify before reactivation.<\/td>\n<\/tr>\n<tr>\n<td>Recency<\/td>\n<td>How recently a contact field was last confirmed as usable for outreach.<\/td>\n<td>Older records drive bounces, wrong numbers, and wasted recruiter time.<\/td>\n<td>Record metadata, enrichment logs<\/td>\n<td>Bucket records by last-verified date; refresh before reuse.<\/td>\n<\/tr>\n<tr>\n<td>Enrichment<\/td>\n<td>Adding missing fields to a record (email, phone, location, specialty context) from a data source or workflow step.<\/td>\n<td>Enrichment increases reach, but can add risk if you don\u2019t verify and suppress.<\/td>\n<td>List build, CRM updates<\/td>\n<td>Enrich only the fields you will use; verify and log provenance.<\/td>\n<\/tr>\n<tr>\n<td>De-duplication<\/td>\n<td>Identifying and merging duplicate records that represent the same person.<\/td>\n<td>Duplicates cause double outreach and complaints.<\/td>\n<td>ATS\/CRM merges, list uploads<\/td>\n<td>Use stable identifiers (e.g., NPI) plus name\/location checks; keep merge rules consistent.<\/td>\n<\/tr>\n<tr>\n<td>Source of truth<\/td>\n<td>The system where the \u201cfinal\u201d version of contact preferences and suppressions lives.<\/td>\n<td>If suppressions aren\u2019t centralized, you will re-contact opt-outs.<\/td>\n<td>ATS\/CRM, suppression tool<\/td>\n<td>Pick one owner system; sync outward to email\/dialer\/SMS tools.<\/td>\n<\/tr>\n<tr>\n<td>Sender reputation<\/td>\n<td>How mailbox providers evaluate your sending identity over time based on signals like bounces, complaints, and engagement.<\/td>\n<td>Poor reputation reduces inbox placement and slows every campaign.<\/td>\n<td>Email platform health dashboards<\/td>\n<td>Protect it with verification, suppression, and relevant targeting.<\/td>\n<\/tr>\n<tr>\n<td>Hard bounce<\/td>\n<td>A permanent email delivery failure (e.g., address does not exist).<\/td>\n<td>Hard bounces are a list hygiene problem and can damage sending performance.<\/td>\n<td>Email platform bounce logs<\/td>\n<td>Suppress immediately; don\u2019t resend to hard bounces.<\/td>\n<\/tr>\n<tr>\n<td>Soft bounce<\/td>\n<td>A temporary email delivery failure (e.g., mailbox full or transient server issue).<\/td>\n<td>Repeated soft bounces can become a reputation issue if you keep hammering.<\/td>\n<td>Email platform bounce logs<\/td>\n<td>Retry cautiously per your sending tool rules; suppress if it persists.<\/td>\n<\/tr>\n<tr>\n<td>Call window<\/td>\n<td>The time ranges when a segment is most reachable by phone (by specialty, setting, and local time).<\/td>\n<td>Calling at the wrong time tanks connectability and recruiter morale.<\/td>\n<td>Dialer schedules, recruiter playbooks<\/td>\n<td>Set segment-specific windows; review weekly using call outcomes.<\/td>\n<\/tr>\n<tr>\n<td>Consent<\/td>\n<td>Permission (explicit or implied under applicable rules) to contact someone via a channel for a legitimate purpose.<\/td>\n<td>Consent posture determines channel choice and risk.<\/td>\n<td>Outreach playbooks, policy docs<\/td>\n<td>Document your basis for outreach; keep records of preferences.<\/td>\n<\/tr>\n<tr>\n<td>Opt-out<\/td>\n<td>A recipient\u2019s request not to be contacted (or not via a specific channel).<\/td>\n<td>Ignoring opt-outs creates complaints and deliverability damage.<\/td>\n<td>ATS\/CRM notes, email footer logs, SMS replies<\/td>\n<td>Centralize suppression so it applies across tools and teammates.<\/td>\n<\/tr>\n<tr>\n<td>Suppression list<\/td>\n<td>A list of contacts you must not message (global or channel-specific), including opt-outs and risky addresses.<\/td>\n<td>Prevents repeat mistakes and protects sender reputation.<\/td>\n<td>Email platform, SMS tool, dialer, CRM<\/td>\n<td>Sync suppressions across systems; audit weekly.<\/td>\n<\/tr>\n<tr>\n<td>Unsubscribe<\/td>\n<td>A channel-specific request to stop receiving messages (commonly email; other channels may use different opt-out mechanisms).<\/td>\n<td>Unsubscribes are a clear signal to stop; mishandling them increases complaints.<\/td>\n<td>Email platform events, CRM fields<\/td>\n<td>Auto-suppress immediately for that channel; confirm sync to your source of truth.<\/td>\n<\/tr>\n<tr>\n<td>Do-not-contact (DNC)<\/td>\n<td>An internal operational flag that a person should not be contacted (globally or by channel), including opt-outs and high-risk records.<\/td>\n<td>Prevents repeat outreach to people who asked you to stop.<\/td>\n<td>ATS\/CRM, suppression tooling<\/td>\n<td>Make DNC visible in every tool recruiters use; enforce at send\/dial time.<\/td>\n<\/tr>\n<tr>\n<td>Segmentation<\/td>\n<td>Grouping contacts by attributes (specialty, setting, geography, seniority, channel readiness) to tailor outreach.<\/td>\n<td>Improves relevance and reduces spam complaints.<\/td>\n<td>Campaign setup, CRM views<\/td>\n<td>Segment before you change copy; fix targeting first.<\/td>\n<\/tr>\n<tr>\n<td>Complaint rate<\/td>\n<td>The share of recipients who mark messages as spam or file complaints (tracked by your sending tools).<\/td>\n<td>Complaints can reduce inbox placement and slow the whole team.<\/td>\n<td>Email platform dashboards<\/td>\n<td>Investigate by segment and source; tighten suppression and relevance.<\/td>\n<\/tr>\n<tr>\n<td>Deliverability Rate<\/td>\n<td>Delivered emails \/ sent emails (per 100 sent emails).<\/td>\n<td>Low deliverability means you\u2019re paying for outreach that never lands.<\/td>\n<td>Email reporting<\/td>\n<td>Track by domain and segment; suppress risky addresses and fix hygiene.<\/td>\n<\/tr>\n<tr>\n<td>Bounce Rate<\/td>\n<td>Bounced emails \/ sent emails (per 100 sent emails).<\/td>\n<td>Bounces damage sender reputation and future inbox placement.<\/td>\n<td>Email reporting<\/td>\n<td>Remove hard bounces immediately; re-verify older records before reuse.<\/td>\n<\/tr>\n<tr>\n<td>Reply Rate<\/td>\n<td>Replies \/ delivered emails (per 100 delivered emails).<\/td>\n<td>Separates \u201cinbox placement\u201d from \u201cmessage-market fit.\u201d<\/td>\n<td>Email reporting<\/td>\n<td>Segment by specialty and job type; test subject lines and first lines.<\/td>\n<\/tr>\n<tr>\n<td>Connect Rate<\/td>\n<td>Connected calls \/ total dials (per 100 dials).<\/td>\n<td>Shows whether your numbers and dialing windows are working.<\/td>\n<td>Dialer reporting<\/td>\n<td>Adjust call windows; prioritize higher-quality phone fields.<\/td>\n<\/tr>\n<tr>\n<td>Answer Rate<\/td>\n<td>Human answers \/ connected calls (per 100 connected calls).<\/td>\n<td>Shows whether you\u2019re reaching a person vs voicemail\/IVR.<\/td>\n<td>Dialer reporting<\/td>\n<td>Refine timing and routing; tighten list to direct lines where appropriate.<\/td>\n<\/tr>\n<tr>\n<td>NPI<\/td>\n<td>National Provider Identifier used to identify healthcare providers in U.S. systems.<\/td>\n<td>Useful as a stable identifier for matching and de-duplication.<\/td>\n<td>Matching, enrichment, record merges<\/td>\n<td>Use NPI to reconcile duplicates; don\u2019t assume it includes outreach-ready contact fields.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2 id=\"step-by-step-method\"><span class=\"ez-toc-section\" id=\"Step-by-step_method\"><\/span>Step-by-step method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ol>\n<li>\n<p><strong>Pick the minimum term set your team must share.<\/strong> Start with: provider contact data, verification, data quality, consent, opt-out, suppression list, and the five outreach metrics.<\/p>\n<\/li>\n<li>\n<p><strong>Attach each term to a workflow checkpoint.<\/strong> Example: \u201csuppression list\u201d belongs in list build, pre-send QA, and post-campaign cleanup\u2014not just in policy docs.<\/p>\n<\/li>\n<li>\n<p><strong>Make the glossary enforceable.<\/strong> Add required fields and pass\/fail rules to your list intake form (even if it\u2019s a simple checklist in your CRM).<\/p>\n<\/li>\n<li>\n<p><strong>Standardize metric math across tools.<\/strong> If two dashboards disagree, you don\u2019t have a performance problem\u2014you have a definition problem. Measure this by\u2026 using the denominators in the Diagnostic Table (per 100 dials, per 100 sent emails, per 100 delivered emails).<\/p>\n<\/li>\n<li>\n<p><strong>Turn terms into actions.<\/strong> Every record should end in one of four outcomes: verify, suppress, segment, or escalate for review.<\/p>\n<\/li>\n<\/ol>\n<p>Need the operational workflow behind these terms? Start here: <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/\">provider contact data<\/a>.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Weighted_Checklist\"><\/span>Weighted Checklist:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use this to decide whether a contact record is \u201cready for outreach\u201d or \u201cneeds work.\u201d Score each item 0\u20132 (0 = missing, 1 = partial\/uncertain, 2 = solid). Total possible: 20.<\/p>\n<ul>\n<li><strong>Identity match:<\/strong> name + specialty + location align (0\u20132)<\/li>\n<li><strong>Stable identifier present:<\/strong> NPI or internal ID for de-duplication (0\u20132)<\/li>\n<li><strong>Email readiness:<\/strong> email present and passes your verification rules (0\u20132)<\/li>\n<li><strong>Phone readiness:<\/strong> phone present and tagged (direct vs main line) (0\u20132)<\/li>\n<li><strong>Recency:<\/strong> last verified date is recent enough for your cadence (0\u20132)<\/li>\n<li><strong>Role context:<\/strong> practice owner\/employee\/locums signals captured (0\u20132)<\/li>\n<li><strong>Consent posture documented:<\/strong> channel allowed + rationale recorded (0\u20132)<\/li>\n<li><strong>Opt-out checked:<\/strong> not on suppression list for the channel (0\u20132)<\/li>\n<li><strong>Routing clarity:<\/strong> best time window \/ gatekeeper notes captured (0\u20132)<\/li>\n<li><strong>Next action set:<\/strong> call\/email sequence assigned (0\u20132)<\/li>\n<\/ul>\n<p><strong>Interpretation:<\/strong> 16\u201320 = ready to scale; 11\u201315 = limited test only; \u226410 = fix data before outreach. The trade-off is\u2026 moving fast with partial records versus protecting deliverability and recruiter time.<\/p>\n<h2 id=\"templates\"><span class=\"ez-toc-section\" id=\"Micro-Asset_Outreach_Templates\"><\/span>Micro-Asset: Outreach Templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Short templates that fit real recruiter workflows. Customize to your role, facility, and opportunity. Always honor <strong>consent<\/strong> and <strong>opt-out<\/strong>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Email_template_first_touch\"><\/span>Email template (first touch)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick question about your next role<\/p>\n<p><strong>Body:<\/strong> Hi {FirstName} \u2014 I recruit clinicians for {Org\/Facility}. Are you open to a brief call about {Role} in {Location} (schedule + comp details)? If not, reply \u201cno\u201d and I\u2019ll close the loop.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Voicemail_template_if_you_reached_voicemail\"><\/span>Voicemail template (if you reached voicemail)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi {FirstName}, this is {YourName}. I\u2019m calling about a {Role} opportunity in {Location}. If you\u2019re open to details, call me at {Number}. If not interested, no problem\u2014just reply \u201copt out\u201d and I\u2019ll update our suppression list.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Gatekeeper-friendly_script_main_line\"><\/span>Gatekeeper-friendly script (main line)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi\u2014can you help me route a message to Dr. {LastName}? I\u2019m a recruiter with {Org}. What\u2019s the best way to send a brief opportunity summary\u2014email or a direct line? I\u2019m happy to follow your preferred process.<\/p>\n<p>Want to validate your verification and hygiene steps before you scale outreach? Use: <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/\">data quality verification for recruiting<\/a> and this deeper definition page: <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/what-is-contact-data-accuracy\/\">what contact data accuracy means in recruiting ops<\/a>.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Common_pitfalls\"><\/span>Common pitfalls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>\n<p><strong>Using \u201caccuracy\u201d as a vibe instead of a rule.<\/strong> If your team can\u2019t say what passes\/fails verification, you\u2019ll argue after the campaign instead of before it.<\/p>\n<\/li>\n<li>\n<p><strong>Mixing up deliverability and response.<\/strong> A message can be delivered and still get zero replies. Separate list health (deliverability\/bounce) from offer + copy fit (reply rate).<\/p>\n<\/li>\n<li>\n<p><strong>Not centralizing opt-outs.<\/strong> If opt-outs live in one inbox or one recruiter\u2019s notes, you will re-contact people you shouldn\u2019t.<\/p>\n<\/li>\n<li>\n<p><strong>Letting suppression be email-only.<\/strong> Suppression should be channel-aware (email vs phone vs SMS) and shared across tools.<\/p>\n<\/li>\n<li>\n<p><strong>Over-building the term set.<\/strong> If the glossary grows faster than your workflow, it stops being useful. Keep the smallest set that drives consistent decisions.<\/p>\n<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"How_to_improve_results\"><\/span>How to improve results<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Here\u2019s the measurement plan ops can run weekly without a meeting.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"1_Use_a_single_scorecard_with_fixed_denominators\"><\/span>1) Use a single scorecard with fixed denominators<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Deliverability Rate<\/strong> = delivered emails \/ sent emails (per 100 sent emails)<\/li>\n<li><strong>Bounce Rate<\/strong> = bounced emails \/ sent emails (per 100 sent emails)<\/li>\n<li><strong>Reply Rate<\/strong> = replies \/ delivered emails (per 100 delivered emails)<\/li>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials (per 100 dials)<\/li>\n<li><strong>Answer Rate<\/strong> = human answers \/ connected calls (per 100 connected calls)<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"2_Segment_before_you_%E2%80%9Cfix%E2%80%9D_anything\"><\/span>2) Segment before you \u201cfix\u201d anything<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>By specialty and setting (hospital-employed vs private practice)<\/li>\n<li>By channel (email vs call) and by source<\/li>\n<li>By record age (last verified date buckets)<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"3_Tie_improvements_to_one_lever_at_a_time\"><\/span>3) Tie improvements to one lever at a time<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>If <strong>Deliverability Rate<\/strong> drops: tighten verification rules and suppress risky addresses.<\/li>\n<li>If <strong>Connect Rate<\/strong> drops: adjust call windows and prioritize higher-quality phone fields.<\/li>\n<li>If <strong>Reply Rate<\/strong> drops but deliverability is stable: change message, offer framing, or targeting.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"4_Make_refresh_a_scheduled_step\"><\/span>4) Make refresh a scheduled step<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Contact fields change over time. Build a refresh cadence into your workflow (especially before reactivation campaigns). If you\u2019re evaluating tools, prioritize Access + Refresh + Verification + Suppression over static exports.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Legal_and_ethical_use\"><\/span>Legal and ethical use<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This is operational guidance for legitimate recruiting outreach, not legal advice. Recruiting outreach is appropriate when it\u2019s respectful, relevant, and compliant with applicable rules.<\/p>\n<ul>\n<li><strong>Be transparent:<\/strong> identify yourself and why you\u2019re reaching out.<\/li>\n<li><strong>Honor opt-outs fast:<\/strong> one system of record for suppression.<\/li>\n<li><strong>Minimize data:<\/strong> store only what you need for recruiting workflow.<\/li>\n<li><strong>Document process:<\/strong> who can outreach, on what channels, and how complaints are handled.<\/li>\n<\/ul>\n<p>For a recruiting-focused overview, see: <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-compliance\/\">recruiting compliance basics<\/a>.<\/p>\n<h2 id=\"evidence\"><span class=\"ez-toc-section\" id=\"Evidence_and_trust_notes\"><\/span>Evidence and trust notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This hub is designed to be stable and operational. We update definitions when workflow requirements or regulatory guidance changes, and we keep terms mapped to actions (verify, suppress, segment, escalate).<\/p>\n<ul>\n<li><a href=\"https:\/\/nppes.cms.hhs.gov\/\">NPPES NPI Registry (baseline identifier source)<\/a><\/li>\n<li><a href=\"https:\/\/www.fcc.gov\/general\/telephone-consumer-protection-act-1991-tcpa\">FCC TCPA overview (calling\/texting baseline)<\/a><\/li>\n<li><a href=\"https:\/\/www.ftc.gov\/business-guidance\/resources\/can-spam-act-compliance-guide-business\">FTC CAN-SPAM compliance guide (email baseline)<\/a><\/li>\n<li><a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/\">Heartbeat trust methodology (how we evaluate data quality and claims)<\/a><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"FAQs\"><\/span>FAQs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Whats_the_difference_between_verification_and_data_quality\"><\/span>What\u2019s the difference between verification and data quality?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Verification<\/strong> is the set of checks you run on a field (email\/phone) to decide if it\u2019s usable. <strong>Data quality<\/strong> is whether the whole record is fit for your recruiting workflow (accuracy, completeness, recency, and compliance readiness).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Which_metrics_should_recruiting_ops_standardize_first\"><\/span>Which metrics should recruiting ops standardize first?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Start with Deliverability Rate, Bounce Rate, Reply Rate, Connect Rate, and Answer Rate\u2014using consistent denominators (per 100 sent emails, per 100 delivered emails, per 100 dials, per 100 connected calls).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Whats_the_difference_between_opt-out_and_unsubscribe\"><\/span>What\u2019s the difference between opt-out and unsubscribe?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Opt-out<\/strong> is a request to stop contact (often global or channel-specific). <strong>Unsubscribe<\/strong> is typically an email mechanism and should trigger immediate channel suppression. Treat both as enforceable signals and sync them to your source of truth.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_should_we_handle_opt-outs_across_multiple_tools\"><\/span>How should we handle opt-outs across multiple tools?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use one suppression list as the source of truth, then sync it into your email platform, dialer, SMS tool, and ATS\/CRM. Treat opt-outs as channel-specific when needed, but always honor global do-not-contact requests.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Is_NPI_enough_to_build_outreach_lists\"><\/span>Is NPI enough to build outreach lists?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>NPI is great for matching and de-duplication, but it\u2019s not the same as outreach-ready provider contact data. Use it as an identifier, then apply verification and suppression rules before contacting.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Where_do_I_go_next_if_I_need_the_operational_workflow_not_just_definitions\"><\/span>Where do I go next if I need the operational workflow, not just definitions?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Start with <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/\">provider contact data<\/a>, then layer in <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/\">data quality verification<\/a> so your team can scale outreach without burning time or deliverability.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Next_steps\"><\/span>Next steps<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><strong>Adopt this glossary internally:<\/strong> paste the Diagnostic Table into your ops wiki and make it the standard.<\/li>\n<li><strong>Turn definitions into workflow gates:<\/strong> add the Weighted Checklist to list build and pre-send QA.<\/li>\n<li><strong>Run a small pilot:<\/strong> use the templates and track the five metrics with consistent denominators.<\/li>\n<\/ul>\n<p>If you want to move from definitions to execution, <a href=\"https:\/\/heartbeat.ai\/signup\">start free search &#038; preview data<\/a>.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"About_the_Author\"><\/span><b>About the Author<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\"><span style=\"font-weight: 400;\">Ben Argeband<\/span><\/a><span style=\"font-weight: 400;\"> is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben&#8217;s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on <\/span><a href=\"https:\/\/www.linkedin.com\/in\/ben-m-argeband-2427a8a3\/\"><span style=\"font-weight: 400;\">LinkedIn<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"about\":[{\"@type\":\"Thing\",\"name\":\"Heartbeat.ai\"},{\"@type\":\"Thing\",\"name\":\"glossary\"},{\"@type\":\"Thing\",\"name\":\"provider contact data\"},{\"@type\":\"Thing\",\"name\":\"data quality\"},{\"@type\":\"Thing\",\"name\":\"consent\"},{\"@type\":\"Thing\",\"name\":\"opt-out\"}],\"articleSection\":\"Resources\",\"author\":{\"@type\":\"Person\",\"name\":\"Ben Argeband\"},\"dateModified\":\"2026-01-05\",\"datePublished\":\"2026-01-05\",\"headline\":\"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)\",\"keywords\":[\"healthcare recruiting contact data glossary\",\"contact data glossary\",\"recruiting ops glossary\",\"data quality terms\"],\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/glossary\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Verification is the set of checks you run on a field (email\/phone) to decide if it\u2019s usable. Data quality is whether the whole record is fit for your recruiting workflow (accuracy, completeness, recency, and compliance readiness).\"},\"name\":\"What\u2019s the difference between verification and data quality?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Start with Deliverability Rate, Bounce Rate, Reply Rate, Connect Rate, and Answer Rate\u2014using consistent denominators (per 100 sent emails, per 100 delivered emails, per 100 dials, per 100 connected calls).\"},\"name\":\"Which metrics should recruiting ops standardize first?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Opt-out is a request to stop contact (often global or channel-specific). Unsubscribe is typically an email mechanism and should trigger immediate channel suppression. Treat both as enforceable signals and sync them to your source of truth.\"},\"name\":\"What\u2019s the difference between opt-out and unsubscribe?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use one suppression list as the source of truth, then sync it into your email platform, dialer, SMS tool, and ATS\/CRM. Treat opt-outs as channel-specific when needed, but always honor global do-not-contact requests.\"},\"name\":\"How should we handle opt-outs across multiple tools?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"NPI is great for matching and de-duplication, but it\u2019s not the same as outreach-ready provider contact data. Use it as an identifier, then apply verification and suppression rules before contacting.\"},\"name\":\"Is NPI enough to build outreach lists?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Start with the provider contact data guide, then layer in data quality verification so your team can scale outreach without burning time or deliverability.\"},\"name\":\"Where do I go next if I need the operational workflow, not just definitions?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A one-screen healthcare recruiting contact data glossary: consistent definitions for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics\u2014each with a next step.<\/p>","protected":false},"author":5,"featured_media":54334,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"healthcare recruiting contact data glossary","_yoast_wpseo_title":"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)","_yoast_wpseo_metadesc":"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.","_custom_permalink":"glossary","footnotes":""},"categories":[1],"tags":[],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\r\n<title>Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)<\/title>\r\n<meta name=\"description\" content=\"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.\" \/>\r\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\r\n<link rel=\"canonical\" href=\"http:\/\/heartbeat.ai\/resources\/glossary\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)\" \/>\r\n<meta property=\"og:description\" content=\"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/glossary\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T19:02:08+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-03-01T10:05:13+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png\" \/>\r\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\r\n<meta name=\"author\" content=\"Ben Argeband\" \/>\r\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\r\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ben Argeband\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#article\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)\",\"datePublished\":\"2026-02-01T19:02:08+00:00\",\"dateModified\":\"2026-03-01T10:05:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/\"},\"wordCount\":2583,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/glossary\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/\",\"url\":\"http:\/\/heartbeat.ai\/resources\/glossary\/\",\"name\":\"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png\",\"datePublished\":\"2026-02-01T19:02:08+00:00\",\"dateModified\":\"2026-03-01T10:05:13+00:00\",\"description\":\"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.\",\"breadcrumb\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/glossary\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage\",\"url\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png\",\"contentUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/glossary\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/heartbeat.ai\/healthcare\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#website\",\"url\":\"http:\/\/heartbeat.ai\/resources\/\",\"name\":\"Heartbeat.ai\",\"description\":\"\",\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/heartbeat.ai\/resources\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\",\"name\":\"Heartbeat.ai\",\"url\":\"http:\/\/heartbeat.ai\/resources\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png\",\"contentUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png\",\"width\":704,\"height\":126,\"caption\":\"Heartbeat.ai\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173\",\"name\":\"Ben Argeband\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/image\/\",\"url\":\"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g\",\"contentUrl\":\"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g\",\"caption\":\"Ben Argeband\"},\"url\":\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/\"}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)","description":"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"http:\/\/heartbeat.ai\/resources\/glossary\/","og_locale":"en_US","og_type":"article","og_title":"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)","og_description":"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.","og_url":"http:\/\/heartbeat.ai\/resources\/glossary\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T19:02:08+00:00","article_modified_time":"2026-03-01T10:05:13+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)","datePublished":"2026-02-01T19:02:08+00:00","dateModified":"2026-03-01T10:05:13+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/"},"wordCount":2583,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/glossary\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/glossary\/","url":"http:\/\/heartbeat.ai\/resources\/glossary\/","name":"Healthcare Recruiting Contact Data Glossary (One-Screen + Next Steps)","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png","datePublished":"2026-02-01T19:02:08+00:00","dateModified":"2026-03-01T10:05:13+00:00","description":"Stable glossary for provider contact data, data quality, consent, opt-out, suppression, and outreach metrics. One-screen definitions with why it matters and what to do next.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/glossary\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#primaryimage","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/glossary-a1000f3e.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/glossary\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/healthcare\/"},{"@type":"ListItem","position":2,"name":"Healthcare Recruiting Contact Data Glossary (One-Screen Definitions + Next Steps)"}]},{"@type":"WebSite","@id":"http:\/\/heartbeat.ai\/resources\/#website","url":"http:\/\/heartbeat.ai\/resources\/","name":"Heartbeat.ai","description":"","publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/heartbeat.ai\/resources\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"http:\/\/heartbeat.ai\/resources\/#organization","name":"Heartbeat.ai","url":"http:\/\/heartbeat.ai\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","width":704,"height":126,"caption":"Heartbeat.ai"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173","name":"Ben Argeband","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/image\/","url":"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g","contentUrl":"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g","caption":"Ben Argeband"},"url":"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/"}]}},"_links":{"self":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54335"}],"collection":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/comments?post=54335"}],"version-history":[{"count":1,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54335\/revisions"}],"predecessor-version":[{"id":54576,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54335\/revisions\/54576"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54334"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54335"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}