Healthcare

Patient demographics

Patient identity. Emits FHIR Patient.

medium riskFHIR · Patientpatient_demographics_v1

Schema

The canonical field set, printed as it ships.

7 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.

patient_demographics_v1FHIR · Patient
fields
7
required
3
validated
4
hints
35
Canonical columnTypeRequiredValidatorsHeader hints the cascade matches
first_namestringyesvornameprenomprénomgiven namenombre
last_namestringyesnachnamenomcognomefamily nameapellido
date_of_birthdateyesdate_rangegeburtsdatumgebdatumdate de naissancedata di nascitafecha de nacimientodobbirthdaybirth date
genderenummalefemaleotherunknowngeschlechtsexesessosexo
ahv_numberstringregexahvavsnssssn
phonephonephonetelefontéléphonetelefonophonemobile
emailemailemailemaile-mailmailcorreo

Read the same definition as JSON at GET /v1/templates/patient_demographics_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.

  • 7 canonical fields
  • 3 required
  • 4 validated
  • 35 header hints
  • Healthcare pack

Try it

A real file, a real call, one template id.

15 rows, multilingual headers (DE/FR/IT), synthetic AHV. Fully synthetic — safe to share, commit, and run in CI.

bash
curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
  -F "file=@patient_demographics_sample.csv" \
  -F "template=patient_demographics_v1"
→ upload created · mappings ready · confirm before commit
This is a medium-risk template. Its mappings response comes back with requires_hitl: true so you can gate your own commit. Schema-only mode — headers plus at most three sample rows, each clamped to 80 characters — is a data-minimization mode. Full-data routes the metered layer-5 call in-region under a BAA at a 20% uplift, and stays locked until the workspace accepts the BAA/NDA in-app.
mcp
adaptivmapr.match_headers({
  template_id: "patient_demographics_v1",
  headers: ["first_name", "last_name", "date_of_birth", "gender"]
})
schema-only · headers and ≤3 clamped rows only

Committed rows can be emitted as FHIR Patient resources — a healthcare-vertical feature on a vertical-agnostic engine.

Ready when you are

Put patient demographics 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.

No free tier · $10 prepaid wallet to start · every map draws a small flat fee