Blog
Product and engineering notes
For the API contract, see Documentation and the OpenAPI spec in the repository.
Patient intake often needs a clinician NPI on file. Here is a small HTTP contract you can call from your stack instead of maintaining NPPES parsing in the telehealth path.
Individual and organization records reuse the same envelope in NPPES. If your product shows the wrong legal name, the bug is usually field selection—not the NPI itself.
What “hit”, “miss”, and “stale” mean for your integration—and why they matter during upstream outages.
How monthly entitlements and per-key rate limits work together to protect the registry and your budget.
The public registry is authoritative but noisy. Here is how a thin API layer keeps integrations stable.