Healthcare
Provider directory
Providers with NPI/GLN/license metadata.
Schema
The canonical field set, printed as it ships.
6 fields with multilingual hints (DE / FR / IT / EN / ES) and field-level validators. Any source column that resolves to one of these is mapped by the cascade — most of them on the deterministic layers, with no LLM call.
provider_directory_v1FHIR · Practitioner- fields
- 6
- required
- 2
- validated
- 2
- hints
- 9
| Canonical column | Type | Required | Validators | Header hints the cascade matches |
|---|---|---|---|---|
first_name | string | yes | — | matched on the column name |
last_name | string | yes | — | matched on the column name |
npi | string | — | npi | npi |
gln | string | — | gln | gln |
license_state | string | — | — | kantoncantonstate |
specialty | string | — | — | fachrichtungspécialitéspecialitàespecialidad |
Read the same definition as JSON at GET /v1/templates/provider_directory_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.
- 6 canonical fields
- 2 required
- 2 validated
- 9 header hints
- Healthcare pack
Try it
A real file, a real call, one template id.
10 rows, format-valid synthetic NPIs and GLNs. Fully synthetic — safe to share, commit, and run in CI.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "file=@provider_directory_sample.csv" \
-F "template=provider_directory_v1"adaptivmapr.match_headers({
template_id: "provider_directory_v1",
headers: ["first_name", "last_name", "npi", "gln"]
})Committed rows can be emitted as FHIR Practitioner resources — a healthcare-vertical feature on a vertical-agnostic engine.
Ready when you are
Put provider directory in production — without shipping raw records.
Schema-only mapping leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.