Injuries enables a Litify user to quickly and easily record a potential client’s injury details while on the phone, including: the injury status, treatments used, and pain levels experienced. Details are associated to the intake (and converted matter) as an injuries related list item.

This article will offer guidance on how to add, edit, and delete injuries. 

Adding Injuries

There are two ways to add an injury.

Add Injury via Injuries tab

  1. Navigate to Intakes > [Intake Name].
  2. Navigate to the Injuries tab.
  3. Select Add Injury.
    add_injury.jpeg
  4. Complete the following fields:
    • Injured Body Part: Dropdown-select of injured area.
    • Diagnosis: Optional free-form text entry field.
    • Injury Status: Dropdown-select of injury statuses.
    • Injury Status as of: Datepicker field.
  5. Select Save.

Repeat for as many injuries as necessary. Injuries saved in the Injuries tab are also available via Related List Quicklinks.

Add Injury via Quicklinks

  1. Navigate to Intakes > [Intake Name].
  2. Hover over the Injuries (0) Related List Quick Link.
  3. Select New. A modal appears.
  4. Complete the following fields:
    • Area Affected: Define the localization for the injury.
    • Body Part: Define which body parts are affected.
    • Injuries/Symptoms: Choose all presenting symptoms.
    • Diagnoses: Add diagnosis if known.
  5. Save.

The new Injury record is now available from the Intake's related list.

Editing Injuries

You can edit an Injury record from the Intake record. 

  1. Navigate to Intakes > [Intake Name]
  2. Hover over the Injuries (1) Related List Quick Link.
  3. Expand the row Action dropdown > select Edit. A modal appears.
  4. Update fields as needed.
  5. Save.

Delete Injuries

You can delete an Injury record from an intake. 

  1. Navigate to Intakes > [Intake Name].
  2. Select a record.
  3. Hover over the Injuries (1) Related List Quick Link.
  4. Expand the row Action dropdown > select Delete. A modal appears.
  5. Confirm Delete.
Was this article helpful?
0 out of 0 found this helpful