{"v":"<h2 id=\"user-content-built-commit-85a2957-not-yet-on-production\" dir=\"auto\">Built (commit 85a2957), not yet on production<\/h2>\n<p dir=\"auto\">Built as proposed above, from a local copy of the national provider registry, not the live API.<\/p>\n<ul dir=\"auto\">\n<li><strong>On the visit screen:<\/strong> &#34;Who is the client&#39;s regular doctor?&#34; now has a <strong>Find the doctor<\/strong> button. Staff type part of the name. Results nearest the client&#39;s ZIP come first, and they can type a different ZIP or city. Each result shows name, specialty, address, phone and fax. Picking one fills the doctor&#39;s name, phone and the PAS service plan&#39;s <strong>Physician Address<\/strong>. Everything stays editable, and &#34;Not listed? Type it in the box above&#34; covers anyone missing.<\/li>\n<li><strong>Who is searched:<\/strong> Texas doctors (MD\/DO), nurse practitioners and physician assistants.<\/li>\n<li><strong>What is kept:<\/strong> the registry entry that was picked is recorded with the visit, encrypted.<\/li>\n<li><strong>Tried on dev<\/strong> with the latest weekly registry file. A pick fills all three boxes and saves.<\/li>\n<\/ul>\n<p dir=\"auto\"><strong>To go live:<\/strong> run the migration, load the registry once (<code>scripts\/import-npi.php --fetch --apply<\/code>, after which a weekly timer keeps it current), then republish SOC\/AO. Production needs outbound HTTPS to download.cms.gov for the import.<\/p>\n<p dir=\"auto\"><strong>Still open:<\/strong> if the customer keeps their own list of doctors, it can be loaded into the same table. Nothing is built for that yet.<\/p>\n"}