Create Injury
create_injuryAdd an injury record to an existing incident in Procore. Specify project, incident, and injury details to log workplace injuries.
Instructions
Creates an Injury record. NOTE: The afflictions and affected_body_part keys are deprecated. Please disregard and use the affected_body_parts and affliction_type keys as documented below. Use this to create a new Incidents in Procore. Creates a new Incidents and returns the created object on success (HTTP 201). Required parameters: project_id, incident_id. Procore API: Project Management > Incidents. Endpoint: POST /rest/v1.0/projects/{project_id}/incidents/injuries
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| run_configurable_validations | No | Query string parameter — whether or not Configurable validations from the Injury Configurable Field Set should be run (default: false). See (https://developers.procore.com/reference/configurable-field-sets#list-project-con... | |
| incident_id | Yes | JSON request body field — the ID of the Incident | |
| date_of_death | No | JSON request body field — the date of death for this Incidents operation | |
| description | No | JSON request body field — description of event in Rich Text format | |
| date_returned_to_work | No | JSON request body field — date returned to work | |
| filing_type | No | JSON request body field — filing Type - The 'recordable' filing_type value is deprecated. When a filing type of 'recordable' is provided, the `recordable` attribute of the Injury will instead be set to 'true'. | |
| hospitalized_overnight | No | JSON request body field — represents whether the injured person was hospitalized overnight | |
| recordable | No | JSON request body field — represents whether the Injury record is recordable | |
| treated_in_er | No | JSON request body field — represents whether the injured person was treated in the ER | |
| treatment_facility_address | No | JSON request body field — the street address of the treatment facility | |
| treatment_facility | No | JSON request body field — the name of the treatment facility | |
| treatment_provider | No | JSON request body field — the name of the treatment provider | |
| work_days_absent | No | JSON request body field — the number of days absent from work | |
| work_days_restricted | No | JSON request body field — the number of days on restricted work | |
| work_days_transferred | No | JSON request body field — the number of days transferred | |
| affliction_type_id | No | JSON request body field — the ID of the Affliction Type. This cannot be cleared if there is an affected_body_part. | |
| body_diagram_type | No | JSON request body field — the body diagram type for this Incidents operation | |
| affected_body_parts | No | JSON request body field — dEPRECATED - Use body_part_ids instead. The body parts affected by the affliction. This requires an affliction_type to be set. | |
| affected_person_id | No | JSON request body field — the ID of the Affected Person. This only supports full Users from the Users endpoints. | |
| affected_party_id | No | JSON request body field — the ID of the Affected Person. This supports full and reference Users from the People endpoints. | |
| body_part_ids | No | JSON request body field — the IDs of body parts affected by the affliction. This requires an affliction_type to be set. | |
| harm_source_id | No | JSON request body field — the ID of the Harm Source | |
| affected_company_id | No | JSON request body field — the ID of the Affected Company | |
| managed_equipment_id | No | JSON request body field — the ID of the Managed Equipment | |
| work_activity_id | No | JSON request body field — the ID of the Work Activity | |
| custom_field_%{custom_field_definition_id} | No | JSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ... |