Skip to main content

Import Mappings

The Import Mappings page lists how your organization's source-file columns are mapped to CareLaunch fields. Those saved mappings are the defaults the next time a similar column header shows up in an import.

The page is available to Organization Admins and Platform Admins under Settings → Import Mappings. It is not shown on Solo. It reads from your organization's analytics dataset. If no BigQuery destination is configured, the page cannot load — contact CareLaunch to have that destination set up.

What you'll see​

The table columns are:

  • Column Name — the source file's header (for example, MRN, Member ID, Date of Birth).
  • Resource Type — the target record type (for example, Patient, Task, Observation).
  • Destination — the field path on that record (for example, BirthDate, Identifier.Value, Name.0.Family).
  • Alias — alternate names recognized for the same header.
  • Ignore — a check mark when the column is left out of imports.
  • Template — a JSON preview when a resource template is saved for that column.

There is no Description column. This page is read-only.

Notes are entered while a file is being mapped, from the ⋮ menu on a row in the import mapper. They stay with that mapping and are not shown as their own column here.

How mappings are created​

Mappings are saved when columns are mapped during a file import. Later imports use those choices to suggest destinations for the same headers.

When to use this page​

  • After an import, to confirm what was saved.
  • Before a large import, to check that identifiers and demographics point at the right fields.
  • When a new data source arrives, to see how its headers line up with mappings you already have.

Tips​

  • Keep header names consistent across sources (for example, always "Member ID").
  • Map identifiers and core demographics first so matching and updates stay reliable.
  • If a column is missing here, it has not been saved from an import yet.