Use this guide alongside the U.S. Pharmacies Database 2.0.0 product page. First decide what your workflow needs to count: pharmacy locations, related provider records, or a transformed view that combines them. The location and companion records describe different things. Their row totals can differ, and a join can expand one location into several rows.

For location analysis, preserve the supplied identifiers, address values, and coordinates in your working copy. Check representative records from multiple regions and compare coordinates to their associated addresses before mapping. If you normalize or geocode data, keep the original values and record the method. Decide whether your geography is a radius, state, county, postal area, or internal territory, then apply the same rule across the analysis.

Companion records may include identifiers, names, network profiles, license references, and historical contacts. Inspect the current schema to find the actual fields and relationship keys. Prefer stable identifiers to name-only joins. If you need one row per location, choose and document how multiple related records will be handled. Keeping companion tables separate can make the relationship easier to audit than flattening values without an explicit rule.

Before choosing a package, read its current contents and license terms on the product page. Inspect the schema and sample for the package you plan to obtain. Check value formats and test a small import using a copy. Keep the original files unchanged and note any filters, joins, deduplication, or enrichment applied later.

Treat indicators such as retail or mail-order as values whose meaning comes from the supplied schema. Do not assume blanks mean “no.” Identifiers or license references can help with matching and review, but their presence does not establish that an operating, licensing, network, or contact detail is current. Verify time-sensitive details from an appropriate current source when your workflow depends on them.

Historical contacts are separate historical information, not current contact records. Retain their dates and status, and do not present them as current without a fresh independent check. Contact information also does not establish permission for every form of outreach. Apply your organization's policies and applicable requirements.

For a repeatable import, record the package, date, schema, counting rule, and validation steps. Label dashboards so users can distinguish locations from companion records and understand the geography and filters applied.

Read the U.S. Pharmacies Database 2.0.0 Journal release guide for a broader look at data relationships and practical validation.