{"v":"

Proposal: use the same NPI download as #82<\/h2>\n

Pharmacies are already in the NPPES file proposed in #82: organisations (entity type 2) with a pharmacy taxonomy (3336*<\/code>). The import keeps them in the same npi_provider<\/code> table, so we need no second source and no second import.<\/p>\n

Where the answer comes from, in order:<\/strong><\/p>\n

    \n
  1. On file.<\/strong> If the client's last visit recorded a pharmacy, start with that one already selected. VESTA as a source is still the open question for the customer.<\/li>\n
  2. Look it up.<\/strong> Staff type part of the name. Results are limited to the client's ZIP or city<\/strong> first, because a name like "Walgreens" or "CVS" matches hundreds of stores and only the location tells them apart. Each match shows the name, street address and phone.<\/li>\n
  3. Staff pick one. Name and phone fill in, and both can still be edited.<\/li>\n<\/ol>\n

    Details:<\/strong><\/p>\n

      \n
    • Also import the NPPES "other name" file, so a store's DBA name (e.g. "CVS Pharmacy #1234") can be searched as well as its legal company name.<\/li>\n
    • Show the pharmacies this agency has picked before at the top of the results. That gives the requested drop-down of known pharmacies with no separate list to maintain.<\/li>\n
    • Store the pharmacy's NPI<\/strong> with the answer, as for the doctor.<\/li>\n
    • The search runs against our own table, so nothing about the client leaves our server.<\/li>\n<\/ul>\n

      Still needed from the customer:<\/strong> does VESTA or their own records already hold each client's pharmacy? If so, we prefill from that and use the lookup only when nothing is on file.<\/p>\n"}