MTN Guide

An agentic data engineer. It reads your schemas and builds MTN FieldMap, an evidence-backed map of what they mean, then keeps it current as your systems change.

What MTN Guide does

SourcesEHRsBillingSchedulingVendorsClaimsGuideOutputsWarehouseBIAnalyticsAI Agents
A FieldMap in daysChange stays containedAnswers you can check

Live in days.

A new source is mapped against concepts the FieldMap already holds, so each system costs less than the last.

New sourcecustomer_iddobaccount_numpolicy_numvendor_idGuideTarget fieldsclient_idbirth_dateaccount_numberpolicy_numbersupplier_id99%98%97%99%?

Maps fields using values, naming patterns, and standards.

High-confidence matches apply automatically.

Low-confidence cases route to a human, never guesses.

Change stays contained.

Conventional integration maintenance compounds with every new system. Mapping each source into its own layer keeps a change local to the connection it affects.

hrs / wk1 system200+

Self-healing pipelines adapt when sources change, with no manual rework.

Containment doesn't happen by accident.

Three ways a source can move, and what the FieldMap does about each.

customer_idaccount_numpolicy_numcoverage_type+Mapped

New field detected and mapped

AccountNumaccount_number38291, 50412, 77203…38291, 50412, 77203…Values match

Renamed field matched by values

Source sends"01/15/2024"stringTarget expects2024-01-15date

Type conversion applied automatically

Beforeaddressstreet, city, statezipAfterstreet_addresscity, statepostal_codeAudit log updated

Structure adapted with full audit log

Forward-only. Historical data stays stable.

Ready for what you deploy next.

A canonical layer your next model reads from on day one. Claude, GPT, Gemini, or your own.

Canonical LayerPatientEncounterClaimScheduleClaudeGPTGeminiYour own

Every model query lands inside the compliance perimeter

What it does, and what it doesn't.

MTN FieldMap is the layer between your sources and your stack. It doesn't try to be your stack.

It does

  • Read schemas, docs, and API specs, no records required
  • Map fields to shared concepts, with the evidence behind each
  • Re-check only what a schema change actually touched
  • Answer where data lives, for your team, your BI, your agents

It doesn't

  • Replace your warehouse or BI tools
  • Sit in your production data path
  • Require changes to your source systems
  • Hold your records, or return data as results

You find out when something moves.

A schema change re-opens only the mappings it touches, and conflicts surface the moment you ask.

TransmissionSchemaQuality989799962398

A schema change re-opens only the mappings it touches, and conflicts surface the moment you ask.

See how this fits your stack

We'll walk through your sources, your warehouse, and your deployment plans, and show you where the map fits underneath.