{"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-02-27T13:30:57","modified_gmt":"2026-02-27T19:30:57","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><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png.webp\" alt=\"54220\" \/><\/p>\n<h1>Prescriptive authority data for recruiters<\/h1>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 High-risk topic\u2014keep conservative and source-based.<\/p>\n<p>If you recruit NPs and PAs, \u201ccan they prescribe for this job in this state?\u201d is a gating requirement that can stall submittals and create avoidable risk. Prescriptive authority varies by state and credential, and employer policies can be stricter than state minimums. Treat this as a verification workflow problem: store what you checked, where you checked it, and when.<\/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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Framework_The_%E2%80%9CDont_Guess%E2%80%9D_Rule_verify_requirements_with_the_state_and_the_employer\" title=\"Framework: The \u201cDon\u2019t Guess\u201d Rule: verify requirements with the state and the employer\">Framework: The \u201cDon\u2019t Guess\u201d Rule: verify requirements with the state and the employer<\/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\" title=\"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\" title=\"Step 1: Define what \u201cprescriptive authority\u201d means in your workflow\">Step 1: Define what \u201cprescriptive authority\u201d 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_so_everyone_stores_the_same_truth\" title=\"Step 2: Build a field-level trust dictionary (so everyone stores the same truth)\">Step 2: Build a field-level trust dictionary (so everyone stores the same truth)<\/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_not_assumed\" title=\"Step 3: Store \u201cverified\/unknown\u201d with source and date (not assumed)\">Step 3: Store \u201cverified\/unknown\u201d with source and date (not assumed)<\/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_safe_sources_and_what_to_capture\" title=\"Step 4: Where to verify (safe sources and what to capture)\">Step 4: Where to verify (safe sources 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_so_%E2%80%9Cunknown%E2%80%9D_doesnt_stall_submittals\" title=\"Step 5: Build a verification task path (so \u201cunknown\u201d doesn\u2019t stall submittals)\">Step 5: Build a verification task path (so \u201cunknown\u201d doesn\u2019t stall submittals)<\/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_prescriptive_authority_data_as_a_filter%E2%80%94carefully\" title=\"Step 6: Use prescriptive authority data as a filter\u2014carefully\">Step 6: Use prescriptive authority data as a filter\u2014carefully<\/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\/#Diagnostic_Table\" title=\"Diagnostic Table:\">Diagnostic 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\" 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-13\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Outreach_Templates\" title=\"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\" title=\"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\" title=\"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_neutral_source-based\" title=\"Template 3: Hiring manager handoff note (neutral, source-based)\">Template 3: Hiring manager handoff note (neutral, source-based)<\/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\" 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-18\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-19\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#Define_the_metrics_canonical_definitions\" title=\"Define the metrics (canonical definitions)\">Define the metrics (canonical 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\/#Measurement_instructions_what_to_track_weekly\" title=\"Measurement instructions (what to track weekly)\">Measurement instructions (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_that_usually_move_the_needle\" title=\"Operational improvements that usually move the needle\">Operational improvements that usually move the needle<\/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\" 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-23\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-24\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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-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\" title=\"What should \u201cprescriptive authority\u201d mean in an ATS field?\">What should \u201cprescriptive authority\u201d 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\" title=\"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\" title=\"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\" title=\"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\" title=\"Does Heartbeat.ai 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\" 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-31\" href=\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#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>Recruiters sourcing NPs\/PAs where prescribing is a job requirement\u2014especially when you need to screen quickly without making assumptions from a credential 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>Use prescriptive authority as a verified requirement flag: record state, credential, verification source, and date; never assume from title alone; route \u201cunknown\u201d to verification.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Prescriptive authority is state- and credential-dependent; recruiting systems should store it as verified\/unknown with a source and date, not as an inferred yes\/no.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiters sourcing NPs\/PAs where prescribing is a 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. 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%9CDont_Guess%E2%80%9D_Rule_verify_requirements_with_the_state_and_the_employer\"><\/span>Framework: The \u201cDon\u2019t Guess\u201d Rule: verify requirements with the state and the employer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In recruiting ops, prescriptive authority is a gating requirement, not a debate. The \u201cDon\u2019t Guess\u201d Rule keeps you fast and defensible:<\/p>\n<ul>\n<li><strong>Don\u2019t guess from a credential.<\/strong> NP\/APRN and PA titles don\u2019t automatically map to meeting a prescribing requirement in a specific state.<\/li>\n<li><strong>Verify with board<\/strong> (state board \/ official registry) and confirm the employer\u2019s internal requirement for the role.<\/li>\n<li><strong>Store what you verified.<\/strong> Capture the source, date, and what exactly was checked (license status vs other registrations).<\/li>\n<li><strong>Route \u201cunknown\u201d intentionally.<\/strong> Unknown is a valid state; it triggers a verification task instead of a risky assumption.<\/li>\n<\/ul>\n<p><strong>What this does NOT mean (keep your team out of trouble):<\/strong><\/p>\n<ul>\n<li>It does <strong>not<\/strong> confirm controlled-substance registration or any specific prescribing category unless you explicitly verified that requirement and recorded the source.<\/li>\n<li>It does <strong>not<\/strong> override employer credentialing rules; it only documents whether the candidate meets the job\u2019s stated requirement based on what you verified.<\/li>\n<\/ul>\n<p>Note on terminology: some states use <strong>APRN<\/strong> as an umbrella category that can include <strong>NP<\/strong>; store your internal credential_type consistently and verify against the state board naming.<\/p>\n<p>This is a recruiting verification workflow, not a determination of clinical permissions.<\/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 \u201cprescriptive authority\u201d means in your workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Recruiting teams use \u201cprescriptive authority\u201d as shorthand for multiple checks. Separate them so you verify the right thing and store it cleanly:<\/p>\n<ul>\n<li><strong>Role requirement flag<\/strong>: the employer requires prescribing for this job.<\/li>\n<li><strong>State context<\/strong>: the state where the clinician would practice for this job.<\/li>\n<li><strong>Individual verification state<\/strong>: what you have verified about the clinician for that state and role requirement.<\/li>\n<\/ul>\n<p>The trade-off is\u2026 the more you compress these into one yes\/no field, the faster your filters look\u2014but the more rework and risk you create downstream.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Build_a_field-level_trust_dictionary_so_everyone_stores_the_same_truth\"><\/span>Step 2: Build a field-level trust dictionary (so everyone stores the same truth)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Uniqueness hook: use a field-level \u201ctrust dictionary\u201d for every prescriptive-authority-related field. For each field, document:<\/p>\n<ul>\n<li><strong>Definition<\/strong> (what it is)<\/li>\n<li><strong>What it does NOT mean<\/strong> (what you must not infer)<\/li>\n<li><strong>How recruiters use it<\/strong> (screening, routing, outreach)<\/li>\n<li><strong>Common mistakes<\/strong> (assumptions that cause rejects or compliance issues)<\/li>\n<li><strong>Where it comes from<\/strong> (Identity vs Contact vs Derived)<\/li>\n<\/ul>\n<p><strong>Mini example trust dictionary entry (copy\/paste into your ops doc):<\/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\u2019s prescribing requirement in the target state.<\/li>\n<li><strong>Does NOT mean:<\/strong> A blanket \u201ccan prescribe anywhere,\u201d or that all employer credentialing steps are complete.<\/li>\n<li><strong>Recruiter use:<\/strong> Prioritize submittals; route Unknown to verification queue.<\/li>\n<li><strong>Common mistakes:<\/strong> Setting Verified without a source\/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_not_assumed\"><\/span>Step 3: Store \u201cverified\/unknown\u201d with source and date (not assumed)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>From an ops standpoint, you want a small set of fields that are easy to maintain and audit:<\/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 (your internal category)<\/li>\n<li><strong>prescriptive_authority_verification_source<\/strong>: state board\/official registry link or employer policy reference<\/li>\n<li><strong>prescriptive_authority_verification_date<\/strong>: when it was checked<\/li>\n<\/ul>\n<p>Operational rule: if you can\u2019t cite the source, treat it as Unknown.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Where_to_verify_safe_sources_and_what_to_capture\"><\/span>Step 4: Where to verify (safe sources 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>: confirm identity match and license status for the credential (NP\/APRN\/PA).<\/li>\n<li><strong>Official registries referenced by the state board<\/strong>: if the board points to a registry for authorizations, use that and save the link\/reference.<\/li>\n<li><strong>Employer requirement documentation<\/strong>: the facility\u2019s credentialing checklist or job requirement notes for prescribing in that role.<\/li>\n<\/ul>\n<p><strong>What to capture from the board page (so your \u201cVerified\u201d is auditable):<\/strong><\/p>\n<ul>\n<li>Name match (and any identifier shown, such as license number, if displayed)<\/li>\n<li>License status (as shown)<\/li>\n<li>State and credential type you checked<\/li>\n<li>URL or reference name for the lookup page<\/li>\n<li>Date checked (your verification date)<\/li>\n<\/ul>\n<p>If the employer requires additional items beyond license status, record that as an employer requirement note rather than implying a clinician can or cannot prescribe.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Build_a_verification_task_path_so_%E2%80%9Cunknown%E2%80%9D_doesnt_stall_submittals\"><\/span>Step 5: Build a verification task path (so \u201cunknown\u201d doesn\u2019t stall submittals)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>When a candidate looks strong but prescriptive authority is unknown, route them through a standard task:<\/p>\n<ol>\n<li><strong>Confirm target state<\/strong> for the role (where they will practice).<\/li>\n<li><strong>Confirm credential<\/strong> (NP\/APRN\/PA) and license status via the state board.<\/li>\n<li><strong>Confirm employer requirement<\/strong> (what the facility requires for prescribing in that role).<\/li>\n<li><strong>Log outcome<\/strong> as Verified\/Unknown\/Not verified with source + date.<\/li>\n<\/ol>\n<h3><span class=\"ez-toc-section\" id=\"Step_6_Use_prescriptive_authority_data_as_a_filter%E2%80%94carefully\"><\/span>Step 6: Use prescriptive authority data as a filter\u2014carefully<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use it to prioritize and route, not to \u201cdiagnose\u201d eligibility. Examples:<\/p>\n<ul>\n<li><strong>Routing<\/strong>: send Verified candidates to hiring manager review first; send Unknown to verification queue.<\/li>\n<li><strong>Outreach personalization<\/strong>: ask a neutral verification question instead of asserting they can\/can\u2019t prescribe.<\/li>\n<li><strong>Job matching<\/strong>: only apply the filter when the job truly requires prescribing.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_Table\"><\/span>Diagnostic Table:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>Visual note:<\/strong> Directory-style field table visual: Field name \u2192 Definition \u2192 Example value \u2192 Source type (Identity\/Contact\/Derived) \u2192 Recruiter use \u2192 Common mistakes.<\/p>\n<p><strong>Visual note:<\/strong> Data dictionary navigation (jump links grouped by Identity\/Contact\/Quality\/Compliance) so teams can find the right field fast.<\/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>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\u2019t 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 \u201cactive license\u201d with \u201cmeets prescribing requirement for this job.\u201d<\/td>\n<\/tr>\n<tr>\n<td>prescriptive_authority_status<\/td>\n<td>Recruiting verification state for whether the clinician meets the req\u2019s 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 \u201cYes\u201d 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<p>Entity alignment: this table is designed for Heartbeat.ai workflows and common NP\/APRN\/PA recruiting operations, with verification anchored to the state board and employer requirements.<\/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 to move a candidate forward today while verification is pending. Score each item 0\u20132 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\u2019s license status is confirmed active via the state board.<\/li>\n<li><strong>(2)<\/strong> Candidate confirms they currently meet the prescribing requirement in the target state (yes\/no\/unknown) and will share verification details if needed.<\/li>\n<li><strong>(2)<\/strong> Employer requirement is documented (what they require for prescribing in this role).<\/li>\n<li><strong>(1)<\/strong> Verification source reference is saved and the verification date is recorded.<\/li>\n<li><strong>(1)<\/strong> ATS field uses Verified\/Unknown\/Not verified (not assumed yes\/no).<\/li>\n<li><strong>(0)<\/strong> If anything is unclear, you route to a verification task instead of rejecting.<\/li>\n<\/ul>\n<p><strong>Interpretation:<\/strong><\/p>\n<ul>\n<li><strong>10\u201312<\/strong>: Submit-ready from a recruiting standpoint (still follow your credentialing process).<\/li>\n<li><strong>7\u20139<\/strong>: Move forward, but create a verification task before final interviews.<\/li>\n<li><strong>&lt;7<\/strong>: Verify first or re-scope the req.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_Templates\"><\/span>Outreach Templates:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>These templates keep you neutral and source-based. They reduce drop-off by making the ask specific and easy to answer.<\/p>\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\u2019m 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 prefer we use to verify (state board listing link, registry reference, or employer credentialing contact)?<\/p>\n<p>If it\u2019s unknown, that\u2019s fine\u2014we can route a quick verification step so we don\u2019t waste your time.<\/p>\n<p>If you\u2019d prefer no further outreach, tell me and I\u2019ll 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, you can point me to the state board listing you use so we can verify with board and document it correctly.<\/p>\n<p>If you\u2019d prefer no further outreach, tell me and I\u2019ll update our records.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_Hiring_manager_handoff_note_neutral_source-based\"><\/span>Template 3: Hiring manager handoff note (neutral, source-based)<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> \u201cNP\/APRN\u201d or \u201cPA\u201d 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> If you don\u2019t store source + date, you can\u2019t defend the decision later.<\/li>\n<li><strong>Rejecting \u201cunknown.\u201d<\/strong> Unknown should trigger a verification task, not an auto-disqualify.<\/li>\n<li><strong>Overstating what you verified.<\/strong> Keep notes factual: 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 (submittal \u2192 credentialing \u2192 \u201cdoesn\u2019t meet requirement\u201d). Build a measurement loop around verification and outreach quality.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Define_the_metrics_canonical_definitions\"><\/span>Define the metrics (canonical definitions)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials (e.g., per 100 dials).<\/li>\n<li><strong>Answer Rate<\/strong> = human answers \/ connected calls (e.g., per 100 connected calls).<\/li>\n<li><strong>Deliverability Rate<\/strong> = delivered emails \/ sent emails (e.g., per 100 sent emails).<\/li>\n<li><strong>Bounce Rate<\/strong> = bounced emails \/ sent emails (e.g., per 100 sent emails).<\/li>\n<li><strong>Reply Rate<\/strong> = replies \/ delivered emails (e.g., per 100 delivered emails).<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Measurement_instructions_what_to_track_weekly\"><\/span>Measurement instructions (what to track weekly)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Verification cycle time<\/strong>: time from prescriptive_authority_status = Unknown to Verified\/Not verified (track median and a high-percentile, e.g., 90th).<\/li>\n<li><strong>Reversal rate<\/strong>: percent of candidates advanced who later fail the prescribing requirement during employer review or credentialing.<\/li>\n<li><strong>Outreach efficiency<\/strong>: Connect Rate and Answer Rate on calls; Deliverability Rate, Bounce Rate, and Reply Rate on emails for NP\/PA segments where prescribing is required.<\/li>\n<\/ul>\n<p>Measure this by\u2026 running a weekly report that segments candidates by prescriptive_authority_status (Verified vs Unknown) at time of first outreach, then comparing reversal rate and cycle time.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Operational_improvements_that_usually_move_the_needle\"><\/span>Operational improvements that usually move the needle<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Make \u201csource + date\u201d mandatory<\/strong> when setting Verified.<\/li>\n<li><strong>Use a verification queue<\/strong> owned by Recruiting Ops so it doesn\u2019t get dropped.<\/li>\n<li><strong>Standardize the handoff note<\/strong> (see template) so hiring managers don\u2019t re-ask the same questions.<\/li>\n<li><strong>Link your license lookup SOPs<\/strong> so recruiters can 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 verification steps and sources (state board and employer requirement documentation). Do not 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 board and defer to the employer\u2019s 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>We treat this as a high-risk data area: prescriptive authority varies by state and credential, and policies change. The safest recruiting posture is to store verification state (Verified\/Unknown\/Not verified) with a source and date, and to rely on official sources (state board\/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<li>Structured data reference used for this page\u2019s schema: <a href=\"https:\/\/schema.org\/\">https:\/\/schema.org\/<\/a>.<\/li>\n<li>Implementation reference for structured data types: <a href=\"https:\/\/schema.org\/Article\">https:\/\/schema.org\/Article<\/a> and <a href=\"https:\/\/schema.org\/FAQPage\">https:\/\/schema.org\/FAQPage<\/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 \u201cprescriptive authority\u201d 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 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\/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 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\u2019re 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><\/p>\n<p><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><br \/>\n<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 way to use prescriptive authority as a recruiting requirement filter: define fields, store verified\/unknown with source and date, and verify via state boards and employer requirements.<\/p>","protected":false},"author":5,"featured_media":54220,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"prescriptive authority data for recruiters","_yoast_wpseo_title":"Prescriptive Authority Data for Recruiters (Verified\/Unknown Workflow)","_yoast_wpseo_metadesc":"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.","_custom_permalink":"data-dictionary\/prescriptive-authority-data-for-recruiters","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>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-02-27T19:30:57+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=\"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\/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-02-27T19:30:57+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/\"},\"wordCount\":2607,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/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\":\"https:\/\/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-02-27T19:30:57+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\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png\",\"contentUrl\":\"https:\/\/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\":\"https:\/\/heartbeat.ai\/healthcare\/\"},{\"@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\":\"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":"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-02-27T19:30:57+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":"13 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-02-27T19:30:57+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/"},"wordCount":2607,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/data-dictionary\/prescriptive-authority-data-for-recruiters\/#primaryimage"},"thumbnailUrl":"https:\/\/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":"https:\/\/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-02-27T19:30:57+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":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/prescriptive-authority-data-for-recruiters-272566d5.png","contentUrl":"https:\/\/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":"https:\/\/heartbeat.ai\/healthcare\/"},{"@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":"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\/54221"}],"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":1,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54221\/revisions"}],"predecessor-version":[{"id":54482,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54221\/revisions\/54482"}],"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}]}}