When Quilia imports cases from your case management system (CMS), field mapping tells it which of your CMS fields holds which piece of information. A field you map is filled in from your CMS, so your client is not asked for something your firm already has.
There are three places to set mappings. Which ones you see depends on your CMS. All of them are admin-only.
Case fields for each case type
For Clio, Filevine, MyCase, Neos and Salesforce, you map case fields separately for each case type, so each type pulls from the fields it actually uses. MyCase values fill in at the overnight sync, not at import.
- Go to Settings → Case Types and select a case type.
- Open the Integration tab. It only shows when the case type is linked to a case type in your CMS.
- In Case fields from [your CMS case type], choose the CMS field that holds each Quilia field. Select Refresh fields if a field you just added in your CMS is missing.
The Quilia fields you can fill this way are:
- Description of the incident, Where it happened, Date of injury and Time of injury
- Police department and Police report number
- Injuries and Prior injuries and health problems
- Vehicle type, Vehicle year, Vehicle make, Vehicle model, Vehicle mileage, Vehicle color, VIN, License Plate Number and License Plate State
- Minor's name (Filevine only). See Importing Minors and Their Parents.
Each field in the card shows a short note on where it appears in Quilia. For Filevine, the card can also suggest mappings for you to accept.
Fields tab (Filevine)
For Filevine, the CMS integration page also has a Fields tab for the mappings that apply to every project type. Go to Settings → Integrations, select Manage next to Filevine, and open Fields.
- Contact fields: Emergency Contact (who Quilia treats as the client's emergency contact) and Language (the client's preferred language for Quilia messages, which can be read from a field or from hashtags like #spanish on the client).
- Case fields: Office / Location (a project field linking each case to the office it belongs to).
Select Refresh from Filevine if a field you need is not listed.
Case subtypes (Filevine and Neostella)
One project type often covers several kinds of case. A Personal Injury project might be an auto accident, a slip and fall or a dog bite. You can split a project type by one of its dropdown fields, such as Incident Type, and map each value to its own Quilia case type.
- Go to Settings → Integrations, select Manage next to your CMS, and open Case Types.
- Under Case subtype, pick the project type, then the dropdown field to split it by.
- Each value of that field appears in the table under its project type. Map each one to a Quilia case type.
When a case is imported or synced, Quilia uses the mapping for its field value. In Neostella, a case whose value is blank or left unmapped uses the project type's own mapping.
Contact Types tab (Filevine and Neos)
Your CMS uses its own words for the contacts on a case. On the Contact Types tab of the integration page, you tell Quilia which of your contact types mean what. For each kind of contact Quilia knows about, pick the matching types from your CMS:
- Treating providers
- Emergency contacts (Filevine only)
- Medical facilities
- Emergency rooms
- Ambulance services
- Police departments
- Employers
- Insurance companies
- Towing companies
- Vehicle storage
- Body shops
- Rental companies
Each of your contact types can belong to only one of these.