Patient profile fields in a file upload
The patient profile fields a file-upload trigger can map columns to, how each value is handled, and why an unusable value is skipped instead of written.
A file-upload trigger can map columns to patient profile fields such as first name, phone, date of birth and address, as well as to the baseline data points the care flow's logic reads. Each row is matched to a patient, and the mapped fields update that patient's profile. This page lists the fields and the rules applied to each value.
Profile mappings are added one field at a time
Patient profile mappings sit under Optional mappings in the trigger's data mapping step, added from Add Patient Profile Data Point. A field that is already mapped drops out of the list, so each one is mapped at most once. Profile mappings are offered for file-upload triggers. Baseline data points are mapped in the same step and reach the care flow's logic rather than the profile.
Each field accepts a particular shape of value
| Mapping | How the value is handled |
|---|---|
| Phone, Mobile Phone | Everything except digits and a leading + is removed, and a + is added if the value has none. The result has to be a valid E.164 number to be written. |
| Date of Birth | YYYY-MM-DD or MM/DD/YYYY. |
| Sex | male, m, female or f, in any capitalization. Any other value records the sex as not known. |
| Patient Code | The organization's own identifier for the patient. See Patient identifiers. |
| Patient Name, First Name, Last Name, Email, Street, City, State, Zip Code, Country, Patient Timezone, Preferred Language | Surrounding whitespace is removed; the value is otherwise used as written. |
The update touches only the mapped fields
The update is a patch against the matched patient. A field with no mapping, and a mapped column that is empty in that row, are both left out of it, so whatever the patient already has on file stays. A trigger that maps only Mobile Phone and City changes those two fields and nothing else.
Unusable values are skipped rather than written
Some values arrive in a form Awell can't use:
- A cell containing only whitespace.
- A phone number that isn't a valid E.164 number after cleanup, such as
not a phone. - A phone value that is only a country calling code, such as
+1or+44. That is what a phone input sends when a country is preselected and no number is typed, so it means no phone rather than a wrong one.
Each of these is left out of the update. A row whose phone column reads +1 leaves a stored
+32475123456 in place, and the rest of the row still applies.
A file upload can't clear a profile field
An empty cell and an unusable value are both skipped, so no value in a file removes data already stored. Change a profile field by editing the patient profile in Awell Care or through the Orchestration API.
An unreadable date fails the record
Date of Birth is the one mapping that can stop a row: a value that reads as neither
YYYY-MM-DD nor MM/DD/YYYY fails the record, and no care flow starts from it. Day-first dates
such as 14/03/2026 read as neither.
Trigger from a file upload covers where
each run's results are reviewed.
Next steps
Next: ADT feeds: how hospital admission and discharge messages enroll patients without a file.