NPI-1 vs NPI-2: which fields to trust for billing vs facility records

NPI-1 identifies a person; NPI-2 identifies an organization. Both return through the same lookup shape, so client code should branch on entity type instead of guessing from the NPI digit pattern alone.

For individuals, the legal name is carried in structured name fields (for example first, last, credential) that maps cleanly to roster and claims-adjacent screens. For organizations, the legal name is represented in the organization name field; treating that as a person name produces the wrong UI and weakens trust with billing partners.

When you normalize once at the API boundary, downstream services—credentialing, billing reconciliation, or facility directories—can share one schema. That reduces duplicate parsing logic and makes regressions easier to catch when upstream fields move.