Summary

Sam clarified that when a provider is added under Providers Seen, that provider should also be pushed to the Requests tab if possible.

I validated the live Litify model and documented the safest design. The current Matter field Providers_Seen__c is free text, so it is not a reliable automation source by itself. The better source is a structured provider row using litify_pm__Role__c, because it stores the Matter, selected provider Account/Party, Role Category, and Role Sub-Category.

The Requests tab object is litify_pm__Request__c. It can link to the Matter, the selected facility Account through litify_ext__Facility_Party__c, and the provider Role row through litify_pm__Facility__c.

Live evidence

Request fields confirmed usable: litify_pm__Matter__c, litify_ext__Facility_Party__c, litify_pm__Facility__c, litify_pm__Request_Type__c, litify_pm__Date_Requested__c, litify_pm__Comments__c, ordered__c, and cancelled__c.

Active Request validation rules only become restrictive when Date Requested is set, including requiring Request To Place and blocking placeholder request names. Recent live request samples show request rows with selected Facility Party, selected Facility Role, request type, and blank Date Requested. That supports creating draft Requests tab rows without silently marking records as actually requested.

Recommended design

Build the workflow from structured provider Role rows, not the legacy text field.

When a provider Role row is created on a Matter, check that it has a Matter and selected Party, confirm the role/subcategory should generate a medical request, check for an existing non-cancelled request for the same Matter, Facility Party, Facility Role, and request type, then create a draft litify_pm__Request__c row if none exists.

Default fields for the new Request row: Matter, Facility Party, Facility Role, provider name, mapped request type, blank Date Requested, and a short system comment that the row was created from provider entry.

Suggested request mapping

Use existing org request type values. Most treatment providers can map to ARC-Records and Bills or Medical Record and Bill, depending which lane the firm wants to standardize. Radiology/imaging should use ARC-Radiology, Records and Bills; ARC-Radiology Films only when films are specifically needed. Medical-record-only or bill-only providers can map to ARC-Medical Records or ARC-Medical Bills. Priors should not be inferred from a normal provider row unless a separate priors flag or subcategory exists.

Files updated

Reason for ending

This portion ended at live-validated design. I did not make a Litify automation/configuration change because creating automatic Request records is a workflow change that should be approved before deployment.