{"id":54221,"date":"2026-02-01T12:44:09","date_gmt":"2026-02-01T18:44:09","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/prescriptive-authority-data-for-recruiters\/"},"modified":"2026-08-31T08:46:41","modified_gmt":"2026-08-31T13:46:41","slug":"prescriptive-authority-data-for-recruiters","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/","title":{"rendered":"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use"},"content":{"rendered":"<p class=\"article-last-updated\"><strong>Last updated:<\/strong> August 31, 2026<\/p>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 this is a high-risk topic, so the approach here is deliberately conservative and source-based.<\/p>\n<p>If you recruit NPs and PAs, &#8220;can this person prescribe for this job in this state?&#8221; is often a gating requirement. Get it wrong and you stall submittals, waste a hiring manager&#8217;s time, or create compliance headaches. Prescriptive authority varies by state and by credential, and employer policies can be stricter than whatever the state allows. The fix isn&#8217;t a smarter guess \u2014 it&#8217;s a verification workflow. Record what you checked, where you checked it, and when.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 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\" style=\"cursor:inherit\">What\u2019s 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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#The_%E2%80%9Cdont_guess%E2%80%9D_rule\" >The &#8220;don&#8217;t guess&#8221; rule<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step-by-step_method\" >Step-by-step method<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_1_Define_what_%E2%80%9Cprescriptive_authority%E2%80%9D_means_in_your_workflow\" >Step 1: Define what &#8220;prescriptive authority&#8221; means in your workflow<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_2_Build_a_field-level_trust_dictionary\" >Step 2: Build a field-level trust dictionary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_3_Store_%E2%80%9Cverifiedunknown%E2%80%9D_with_source_and_date\" >Step 3: Store &#8220;verified\/unknown&#8221; with source and date<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_4_Where_to_verify_and_what_to_capture\" >Step 4: Where to verify, and what to capture<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_5_Build_a_verification_task_path\" >Step 5: Build a verification task path<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Step_6_Use_the_data_to_route_not_to_diagnose\" >Step 6: Use the data to route, not to diagnose<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Field_reference_table\" >Field reference table<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-13\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Outreach_templates\" >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-14\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Template_1_First-touch_verification-forward\" >Template 1: First-touch, verification-forward<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Template_2_Follow-up_reduce_friction\" >Template 2: Follow-up, reduce friction<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Template_3_Hiring_manager_handoff_note\" >Template 3: Hiring manager handoff note<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-18\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-19\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Metric_definitions\" >Metric definitions<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#What_to_track_weekly\" >What to track weekly<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Operational_improvements_worth_making\" >Operational improvements worth making<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-23\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-24\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-25\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#What_should_%E2%80%9Cprescriptive_authority%E2%80%9D_mean_in_an_ATS_field\" >What should &#8220;prescriptive authority&#8221; mean in an ATS field?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Can_I_assume_an_NP_or_APRN_meets_a_prescribing_requirement_in_any_state\" >Can I assume an NP or APRN meets a prescribing requirement in any state?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#How_do_I_verify_prescriptive_authority_without_making_legal_determinations\" >How do I verify prescriptive authority without making legal determinations?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#What_do_I_do_when_prescriptive_authority_is_unknown\" >What do I do when prescriptive authority is unknown?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Does_Heartbeatai_provide_prescriptive_authority_determinations\" >Does Heartbeat.ai provide prescriptive authority determinations?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-31\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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>Recruiters sourcing NPs and PAs where prescribing is a stated job requirement, particularly teams that need to screen quickly without assuming eligibility from a credential title alone.<\/p>\n<h2><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>Treat prescriptive authority as a verified requirement flag, not a fact you infer. Record state, credential, verification source, and date. Never assume eligibility from title alone, and route anything unknown into a verification step.<\/dd>\n<dt>Key insight<\/dt>\n<dd>Prescriptive authority is state- and credential-dependent. Your ATS should store it as verified or unknown, with a source and date attached, rather than a simple yes\/no.<\/dd>\n<dt>Best for<\/dt>\n<dd>Recruiters filling NP\/PA roles where prescribing is part of the job requirement.<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; safety<\/strong><\/p>\n<p>This method is for legitimate recruiting outreach only. 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=\"The_%E2%80%9Cdont_guess%E2%80%9D_rule\"><\/span>The &#8220;don&#8217;t guess&#8221; rule<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In recruiting ops, prescriptive authority is a gating requirement, not something to debate. A simple rule keeps you fast and defensible:<\/p>\n<ul>\n<li><strong>Don&#8217;t guess from a credential.<\/strong> NP\/APRN and PA titles don&#8217;t automatically mean someone meets a prescribing requirement in a specific state.<\/li>\n<li><strong>Verify with the board.<\/strong> Check the state board or official registry, and confirm the employer&#8217;s own internal requirement for the role.<\/li>\n<li><strong>Store what you verified.<\/strong> Capture the source, the date, and exactly what was checked \u2014 license status is not the same thing as a controlled-substance registration.<\/li>\n<li><strong>Route &#8220;unknown&#8221; on purpose.<\/strong> Unknown is a legitimate status. It should trigger a verification task, not a rejection or an assumption.<\/li>\n<\/ul>\n<p><strong>What this doesn&#8217;t do:<\/strong> it doesn&#8217;t confirm controlled-substance registration or any specific prescribing category unless you explicitly verified that and recorded the source. It also doesn&#8217;t override the employer&#8217;s own credentialing process \u2014 it only documents whether a candidate meets the job&#8217;s stated requirement based on what you actually checked.<\/p>\n<p>One terminology note: some states use APRN as an umbrella term that can include NP. Keep your internal credential_type field consistent and check it against how the state board actually names things.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-step_method\"><\/span>Step-by-step method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Define_what_%E2%80%9Cprescriptive_authority%E2%80%9D_means_in_your_workflow\"><\/span>Step 1: Define what &#8220;prescriptive authority&#8221; means in your workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Recruiting teams often use &#8220;prescriptive authority&#8221; as shorthand for several different checks bundled together. Separate them so you verify the right thing and store it cleanly:<\/p>\n<ul>\n<li><strong>Role requirement flag<\/strong> \u2014 the employer requires prescribing for this job.<\/li>\n<li><strong>State context<\/strong> \u2014 the state where the clinician would actually practice.<\/li>\n<li><strong>Individual verification state<\/strong> \u2014 what you&#8217;ve confirmed about this specific clinician for that state and role.<\/li>\n<\/ul>\n<p>Compressing all three into a single yes\/no field makes your filters look faster, but it creates rework and risk downstream when someone has to untangle what was actually checked.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Build_a_field-level_trust_dictionary\"><\/span>Step 2: Build a field-level trust dictionary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>For every prescriptive-authority-related field, document five things: the definition, what it does NOT mean, how recruiters should use it, common mistakes that cause rejects or compliance issues, and where the data comes from (identity, contact, or derived).<\/p>\n<p><strong>Example entry you can adapt:<\/strong><\/p>\n<ul>\n<li><strong>Field:<\/strong> prescriptive_authority_status<\/li>\n<li><strong>Definition:<\/strong> Recruiting verification state for whether the clinician meets the job&#8217;s prescribing requirement in the target state.<\/li>\n<li><strong>Does NOT mean:<\/strong> A blanket &#8220;can prescribe anywhere,&#8221; or that all employer credentialing steps are complete.<\/li>\n<li><strong>Recruiter use:<\/strong> Prioritize submittals; route Unknown to a verification queue.<\/li>\n<li><strong>Common mistakes:<\/strong> Setting &#8220;Verified&#8221; without a source or date; treating Unknown as No.<\/li>\n<li><strong>Source type:<\/strong> Derived, from documented verification steps.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Store_%E2%80%9Cverifiedunknown%E2%80%9D_with_source_and_date\"><\/span>Step 3: Store &#8220;verified\/unknown&#8221; with source and date<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Keep the field set small and auditable:<\/p>\n<ul>\n<li><strong>prescriptive_authority_status:<\/strong> Verified \/ Unknown \/ Not verified<\/li>\n<li><strong>prescriptive_authority_verified_state:<\/strong> the state the verification applies to<\/li>\n<li><strong>credential_type:<\/strong> NP\/APRN\/PA<\/li>\n<li><strong>prescriptive_authority_verification_source:<\/strong> state board or registry link, or employer policy reference<\/li>\n<li><strong>prescriptive_authority_verification_date:<\/strong> when it was checked<\/li>\n<\/ul>\n<p>A useful operational rule: if you can&#8217;t cite the source, treat it as Unknown. No exceptions for &#8220;I&#8217;m pretty sure.&#8221;<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Where_to_verify_and_what_to_capture\"><\/span>Step 4: Where to verify, and what to capture<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Keep verification source-based and neutral. Typical sources recruiters can use without making clinical determinations:<\/p>\n<ul>\n<li><strong>State board license lookup<\/strong> \u2014 confirm identity match and license status for the credential.<\/li>\n<li><strong>Official registries the board references<\/strong> \u2014 if the board points elsewhere for authorizations, use that and save the link.<\/li>\n<li><strong>Employer requirement documentation<\/strong> \u2014 the facility&#8217;s own credentialing checklist for prescribing in that role.<\/li>\n<\/ul>\n<p>From the board page, capture the name match, license status as shown, state and credential type checked, the URL or reference name, and the date you checked it. If the employer needs more than license status, log that separately as an employer requirement note rather than implying anything about clinical permission.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Build_a_verification_task_path\"><\/span>Step 5: Build a verification task path<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>When a strong candidate has an unknown status, run a standard task instead of stalling:<\/p>\n<ol>\n<li>Confirm the target state for the role.<\/li>\n<li>Confirm credential and license status via the state board.<\/li>\n<li>Confirm the employer&#8217;s actual requirement for prescribing in that role.<\/li>\n<li>Log the outcome as Verified, Unknown, or Not verified, with source and date.<\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Step_6_Use_the_data_to_route_not_to_diagnose\"><\/span>Step 6: Use the data to route, not to diagnose<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use prescriptive authority status to prioritize, not to decide clinical eligibility. In practice: send Verified candidates to hiring manager review first, send Unknown to the verification queue, ask a neutral verification question in outreach instead of asserting anyone can or can&#8217;t prescribe, and only apply the filter to roles that actually require prescribing.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Field_reference_table\"><\/span>Field reference table<span class=\"ez-toc-section-end\"><\/span><\/h2>\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>Field name<\/th>\n<th>Definition<\/th>\n<th>Example value<\/th>\n<th>Source type<\/th>\n<th>Recruiter use<\/th>\n<th>Common mistakes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>role_requires_prescribing<\/td>\n<td>Employer requirement that the role includes prescribing responsibilities.<\/td>\n<td>true<\/td>\n<td>Derived<\/td>\n<td>Turn on\/off prescriptive authority screening for the req.<\/td>\n<td>Applying the filter to roles that don&#8217;t require prescribing.<\/td>\n<\/tr>\n<tr>\n<td>credential_type<\/td>\n<td>Clinician credential category used for recruiting workflow (e.g., NP\/APRN\/PA).<\/td>\n<td>NP<\/td>\n<td>Identity<\/td>\n<td>Route to the correct verification checklist and outreach template.<\/td>\n<td>Assuming credential implies meeting a prescribing requirement in a given state.<\/td>\n<\/tr>\n<tr>\n<td>license_state<\/td>\n<td>State where the clinician holds an active license relevant to the role.<\/td>\n<td>TX<\/td>\n<td>Identity<\/td>\n<td>Determine which state board to check.<\/td>\n<td>Using a compact license list without confirming active status.<\/td>\n<\/tr>\n<tr>\n<td>license_status<\/td>\n<td>Status returned by the state board lookup (as recorded by your team).<\/td>\n<td>Active<\/td>\n<td>Identity<\/td>\n<td>Basic eligibility screen before deeper checks.<\/td>\n<td>Confusing &#8220;active license&#8221; with &#8220;meets prescribing requirement for this job.&#8221;<\/td>\n<\/tr>\n<tr>\n<td>prescriptive_authority_status<\/td>\n<td>Recruiting verification state for whether the clinician meets the req&#8217;s prescribing requirement in the target state.<\/td>\n<td>Unknown<\/td>\n<td>Derived<\/td>\n<td>Prioritize submittals and trigger verification tasks.<\/td>\n<td>Storing &#8220;Yes&#8221; without source\/date; treating Unknown as No.<\/td>\n<\/tr>\n<tr>\n<td>prescriptive_authority_verified_state<\/td>\n<td>The state the verification applies to.<\/td>\n<td>TX<\/td>\n<td>Derived<\/td>\n<td>Avoid applying a verification from one state to another.<\/td>\n<td>Assuming multi-state equivalence.<\/td>\n<\/tr>\n<tr>\n<td>prescriptive_authority_verification_source<\/td>\n<td>Where the verification came from (state board page, official registry, employer policy reference).<\/td>\n<td>State board license lookup URL<\/td>\n<td>Derived<\/td>\n<td>Audit trail for compliance and internal QA.<\/td>\n<td>Using informal sources; missing the link\/name.<\/td>\n<\/tr>\n<tr>\n<td>prescriptive_authority_verification_date<\/td>\n<td>Date the verification was performed.<\/td>\n<td>[YYYY-MM-DD]<\/td>\n<td>Derived<\/td>\n<td>Know when to re-check due to policy changes or stale data.<\/td>\n<td>Leaving it blank; treating old checks as current.<\/td>\n<\/tr>\n<tr>\n<td>verification_notes<\/td>\n<td>Short, neutral notes about what was checked and what remains unknown.<\/td>\n<td>License active per board; employer requires additional credentialing step\u2014pending.<\/td>\n<td>Derived<\/td>\n<td>Hand-off between sourcing, recruiting, and credentialing.<\/td>\n<td>Writing conclusions about what the clinician may do.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\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 to move a candidate forward today while verification is pending. Score each item and total it.<\/p>\n<ul>\n<li><strong>(2)<\/strong> Role explicitly requires prescribing and the target state is confirmed.<\/li>\n<li><strong>(2)<\/strong> Candidate&#8217;s license status is confirmed active via the state board.<\/li>\n<li><strong>(2)<\/strong> Candidate confirms whether they currently meet the prescribing requirement in the target state and will share verification details if needed.<\/li>\n<li><strong>(2)<\/strong> Employer requirement is documented.<\/li>\n<li><strong>(1)<\/strong> Verification source reference is saved and the date is recorded.<\/li>\n<li><strong>(1)<\/strong> ATS field uses Verified\/Unknown\/Not verified, not an assumed yes\/no.<\/li>\n<\/ul>\n<p><strong>Interpretation:<\/strong> 10\u201312 is submit-ready from a recruiting standpoint, though you still follow your credentialing process. 7\u20139 means move forward but open a verification task before final interviews. Below 7, verify first or re-scope the requirement.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_templates\"><\/span>Outreach templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_First-touch_verification-forward\"><\/span>Template 1: First-touch, verification-forward<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick question on prescribing requirement (NP\/PA role)<\/p>\n<p>Hi [Name] \u2014 I&#8217;m recruiting for a [NP\/PA] role in [State]. Prescribing is a requirement for this position.<\/p>\n<p>Can you confirm whether you currently meet that prescribing requirement in [State], and what you&#8217;d prefer we use to verify \u2014 a state board listing link, registry reference, or employer credentialing contact?<\/p>\n<p>If it&#8217;s unknown, that&#8217;s fine \u2014 we can run a quick verification step so we don&#8217;t waste your time.<\/p>\n<p>If you&#8217;d prefer no further outreach, let me know and I&#8217;ll update our records.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_Follow-up_reduce_friction\"><\/span>Template 2: Follow-up, reduce friction<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi [Name] \u2014 following up. To keep this moving, all I need is:<\/p>\n<ul>\n<li>Target state: [State]<\/li>\n<li>Your credential: [NP\/APRN\/PA]<\/li>\n<li>Whether you currently meet the prescribing requirement in that state (yes\/no\/unknown)<\/li>\n<\/ul>\n<p>If you prefer, point me to the state board listing you use so we can verify and document it correctly.<\/p>\n<p>If you&#8217;d prefer no further outreach, let me know and I&#8217;ll update our records.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_Hiring_manager_handoff_note\"><\/span>Template 3: Hiring manager handoff note<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Candidate: [Name] (NP\/APRN\/PA). Prescribing requirement for req: Yes. Status: [Verified\/Unknown\/Not verified].<\/p>\n<ul>\n<li>Target state: [State]<\/li>\n<li>Verification source: [link or reference]<\/li>\n<li>Verification date: [date]<\/li>\n<li>Notes: [what was checked \/ what remains pending]<\/li>\n<\/ul>\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><strong>Assuming from title.<\/strong> &#8220;NP\/APRN&#8221; or &#8220;PA&#8221; alone is not a safe proxy for meeting a prescribing requirement in a specific state.<\/li>\n<li><strong>Mixing employer requirement with state context.<\/strong> Store the role requirement separately from the verification state.<\/li>\n<li><strong>Storing a permanent yes\/no.<\/strong> Without source and date, you can&#8217;t defend the decision later.<\/li>\n<li><strong>Rejecting &#8220;unknown.&#8221;<\/strong> Unknown should trigger a verification task, not an auto-disqualify.<\/li>\n<li><strong>Overstating what you verified.<\/strong> Keep notes factual \u2014 what you checked, where, and when.<\/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>Improvement here means faster screening with fewer reversals \u2014 the pattern where a candidate makes it through submittal and credentialing only to be found not to meet the requirement. Build a measurement loop around verification and outreach quality.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Metric_definitions\"><\/span>Metric definitions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Connect rate<\/strong> = connected calls \/ total dials.<\/li>\n<li><strong>Answer rate<\/strong> = human answers \/ connected calls.<\/li>\n<li><strong>Deliverability rate<\/strong> = delivered emails \/ sent emails.<\/li>\n<li><strong>Bounce rate<\/strong> = bounced emails \/ sent emails.<\/li>\n<li><strong>Reply rate<\/strong> = replies \/ delivered emails.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"What_to_track_weekly\"><\/span>What to track weekly<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Verification cycle time:<\/strong> time from Unknown status to Verified or Not verified \u2014 track the median and a high percentile like the 90th.<\/li>\n<li><strong>Reversal rate:<\/strong> percent of advanced candidates who later fail the prescribing requirement during employer review or credentialing.<\/li>\n<li><strong>Outreach efficiency:<\/strong> connect and answer rates on calls; deliverability, bounce, and reply rates on emails, segmented by NP\/PA roles where prescribing is required.<\/li>\n<\/ul>\n<p>A simple way to measure this: run a weekly report segmenting candidates by prescriptive_authority_status at first outreach, then compare reversal rate and cycle time between the Verified and Unknown groups.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Operational_improvements_worth_making\"><\/span>Operational improvements worth making<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Make source and date mandatory whenever a record is set to Verified.<\/li>\n<li>Use a verification queue owned by recruiting ops so tasks don&#8217;t get dropped.<\/li>\n<li>Standardize the handoff note so hiring managers stop re-asking the same questions.<\/li>\n<li>Link your license lookup SOPs so recruiters verify quickly without improvising.<\/li>\n<\/ul>\n<p>Helpful internal references for verification workflows: <a href=\"http:\/\/heartbeat.ai\/resources\/state-license-lookups\/nursing-license-lookup\/\">nursing license lookup workflow<\/a> and <a href=\"http:\/\/heartbeat.ai\/resources\/state-license-lookups\/np-license-lookup\/\">NP license lookup workflow<\/a>.<\/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>Use prescriptive authority data only to confirm a legitimate job requirement for a specific role and state, and to document your verification steps and sources. Don&#8217;t represent your internal field as a clinical permission determination.<\/p>\n<ul>\n<li>Respect opt-out requests and suppression lists.<\/li>\n<li>Keep notes factual and source-based.<\/li>\n<li>When in doubt, verify with the board and defer to the employer&#8217;s credentialing process.<\/li>\n<\/ul>\n<h2><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>Treat this as a high-risk data area: prescriptive authority varies by state and credential, and policies change over time. The safest recruiting posture is to store a verification state \u2014 Verified, Unknown, or Not verified \u2014 with a source and date, relying on official sources like state boards and registries plus employer requirements.<\/p>\n<ul>\n<li>How Heartbeat defines and audits data quality metrics: <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/\">Trust Methodology<\/a> and <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\">accuracy and metrics definitions<\/a>.<\/li>\n<\/ul>\n<p>Related operational building blocks: <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/ats-field-schema-for-outreach-metrics\/\">ATS field schema for outreach metrics<\/a> and <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/provider-contact-data-api\/\">provider contact data API overview<\/a>.<\/p>\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=\"What_should_%E2%80%9Cprescriptive_authority%E2%80%9D_mean_in_an_ATS_field\"><\/span>What should &#8220;prescriptive authority&#8221; mean in an ATS field?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Make it a recruiting verification flag tied to a specific state and role requirement. Store Verified\/Unknown\/Not verified plus source and date, rather than assuming a permanent yes\/no.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_I_assume_an_NP_or_APRN_meets_a_prescribing_requirement_in_any_state\"><\/span>Can I assume an NP or APRN meets a prescribing requirement in any state?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. Prescriptive authority varies by state and credential, and employer requirements can be stricter than state minimums. Verify with the board and document the source and date.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_verify_prescriptive_authority_without_making_legal_determinations\"><\/span>How do I verify prescriptive authority without making legal determinations?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Keep it procedural: confirm the target state, check the state board or official registry for license status, confirm employer requirements, and record what you verified with a source and date.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_do_I_do_when_prescriptive_authority_is_unknown\"><\/span>What do I do when prescriptive authority is unknown?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Route it to a verification task instead of rejecting. Unknown is a valid state that prevents bad assumptions and reduces downstream reversals.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Does_Heartbeatai_provide_prescriptive_authority_determinations\"><\/span>Does Heartbeat.ai provide prescriptive authority determinations?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Heartbeat.ai supports recruiting workflows and data handling, but you should verify with the board and employer requirements for any role where prescribing is a condition of hire.<\/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>If you need NP\/PA outreach workflows that fit verification-first recruiting, review: <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/nurse-practitioner-contact-data\/\">nurse practitioner contact data<\/a> and <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-assistant-contact-data\/\">physician assistant contact data<\/a>.<\/li>\n<li>Implement the trust dictionary fields in your ATS\/CRM and align them with your outreach metrics schema.<\/li>\n<li>When you&#8217;re ready to operationalize this with your team, <a href=\"https:\/\/heartbeat.ai\/signup\">create a Heartbeat account<\/a>.<\/li>\n<\/ul>\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><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"about\":[\"prescriptive authority\",\"NP\",\"APRN\",\"PA\",\"state board\"],\"author\":{\"@type\":\"Person\",\"jobTitle\":\"Founder & CEO of Heartbeat.ai\",\"name\":\"Ben Argeband\"},\"headline\":\"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use\",\"isPartOf\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/data-dictionary\/\",\"@type\":\"WebPage\"},\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Make it a recruiting verification flag tied to a specific state and role requirement. Store Verified\/Unknown\/Not verified plus source and date, rather than assuming a permanent yes\/no.\"},\"name\":\"What should \\\"prescriptive authority\\\" mean in an ATS field?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Prescriptive authority varies by state and credential, and employer requirements can be stricter than state minimums. Verify with board and document the source and date.\"},\"name\":\"Can I assume an NP or APRN meets a prescribing requirement in any state?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Keep it procedural: confirm the target state, check the state board\/official registry for license status, confirm employer requirements, and record what you verified with a source and date.\"},\"name\":\"How do I verify prescriptive authority without making legal determinations?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Route it to a verification task instead of rejecting. Unknown is a valid state that prevents bad assumptions and reduces downstream reversals.\"},\"name\":\"What do I do when prescriptive authority is unknown?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Heartbeat.ai supports recruiting workflows and data handling, but you should verify with board and employer requirements for any role where prescribing is a condition of hire.\"},\"name\":\"Does Heartbeat.ai provide prescriptive authority determinations?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A conservative, source-based method for recruiters to verify NP\/PA prescriptive authority: define fields, store verified\/unknown status with source and date.<\/p>","protected":false},"author":5,"featured_media":54220,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_custom_permalink":"data-dictionary\/prescriptive-authority-data-for-recruiters","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54221","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\r\n<title>Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)<\/title>\r\n<meta name=\"description\" content=\"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\/unknown status, source+date logging, and verification steps using state boards and employer requirements.\" \/>\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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)\" \/>\r\n<meta property=\"og:description\" content=\"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\/unknown status, source+date logging, and verification steps using state boards and employer requirements.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:44:09+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-08-31T13:46:41+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.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=\"12 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use\",\"datePublished\":\"2026-02-01T18:44:09+00:00\",\"dateModified\":\"2026-08-31T13:46:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/\"},\"wordCount\":2424,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/prescriptive-authority-data-for-recruiters-272566d5.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/\",\"name\":\"Prescriptive Authority Data for Recruiters (Verified\\\/Unknown Workflow)\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/prescriptive-authority-data-for-recruiters-272566d5.png\",\"datePublished\":\"2026-02-01T18:44:09+00:00\",\"dateModified\":\"2026-08-31T13:46:41+00:00\",\"description\":\"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\\\/unknown status, source+date logging, and verification steps using state boards and employer requirements.\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#primaryimage\",\"url\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/prescriptive-authority-data-for-recruiters-272566d5.png\",\"contentUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/prescriptive-authority-data-for-recruiters-272566d5.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/data-dictionary\\\/prescriptive-authority-data-for-recruiters\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use\"}]},{\"@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\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"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\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?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":"Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)","description":"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\/unknown status, source+date logging, and verification steps using state boards and employer requirements.","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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/","og_locale":"en_US","og_type":"article","og_title":"Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)","og_description":"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\/unknown status, source+date logging, and verification steps using state boards and employer requirements.","og_url":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:44:09+00:00","article_modified_time":"2026-08-31T13:46:41+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use","datePublished":"2026-02-01T18:44:09+00:00","dateModified":"2026-08-31T13:46:41+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/"},"wordCount":2424,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/","url":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/","name":"Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","datePublished":"2026-02-01T18:44:09+00:00","dateModified":"2026-08-31T13:46:41+00:00","description":"How recruiters should use prescriptive authority as a requirement filter: field definitions, verified\/unknown status, source+date logging, and verification steps using state boards and employer requirements.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage","url":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","contentUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/heartbeat.ai\/resources\/"},{"@type":"ListItem","position":2,"name":"Prescriptive Authority Data for Recruiters: Definitions, Verification, and Safe Use"}]},{"@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":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"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":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?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\/54221","targetHints":{"allow":["GET"]}}],"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=54221"}],"version-history":[{"count":2,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54221\/revisions"}],"predecessor-version":[{"id":66200,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54221\/revisions\/66200"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54220"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54221"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54221"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54221"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}