Skip to main content

Import Mappings

The Import Mappings tab provides a read‑only view of how your organization’s source file columns are mapped to FHIR resource fields in CareLaunch. These mappings are learned from completed file imports and help auto‑suggest the correct destinations the next time similar column headers appear.

Use this tab to review what the system has learned about your data and confirm that common fields (like identifiers and demographics) are pointed to the right destinations.

Where to find it​

  • Go to Settings ➜ Import Mappings.

What you’ll see​

A list of previously seen column headers with their mapped destinations:

  • Column Name: The source file’s column header (for example, MRN, Member ID, Date of Birth).
  • Resource Type: The target FHIR resource (for example, Patient, Task, Observation).
  • Destination: The field path within the target resource (for example, BirthDate, Identifier.Value, Name.0.Family).
  • Alias (optional): Alternate names or synonyms recognized for a column header.
  • Description (optional): Notes explaining the intent or usage of the mapping.
  • Ignored: Indicates a column that is intentionally excluded during imports.

Tip: Notes added from the Data Imports screen (via the three‑dots (⋯) menu on each row) appear here in the Description column.

Note: This view is read‑only.

How mappings are created​

Mappings are established during the file import process when you map file columns to destinations. Over time, these selections help the system suggest mappings for similar columns in future imports.

When to use this tab​

  • After completing an import to verify what the system learned.
  • Before a large import to quickly review that important fields (especially identifiers) are mapped to the correct destinations.
  • When onboarding a new data source, to check how its headers line up with your existing mappings.

Tips​

  • Normalize headers upstream when possible (for example, keep “Member ID” consistent across sources).
  • Prioritize identifiers and core demographics so downstream matching and updates are reliable.
  • If a column does not appear here, run an import that includes the column so the system can learn it.