You can have multiple tables that populate data in a details screen, as long as each table has a unique identifier that associates the data in each table to the given row (i.e. a column that contains a rowlink, perhaps in your case an Incident ID or something similar).
This means that when you write data to each of these tables (from your form), you'll want to ensure that you're writing that unique identifier value to the table for each item. This is how your tables would look:
You have your incidents table with data associated to the incident:
Then you have your BodyPart table (or InjuredArea in my example), with a first column that's a rowlink to the Incident table):
And then a InjuryType table, also with a column formatted as a rowlink to the Incidents table:
With this set up, you can set up a details screen that refers to an input row, and each checkbox would refer to the same incident ID to see if it's marked True or False. Here's how I set it up:
I have a data cell at the top which is called
$[InputRow], which is an editable rowlink to the Incidents table:
The first section displays the data from that input row, by referring to the columns:
And the next two sections use FINDROW() to match the toggle to the particular incident ID.
Here's the second second, using FINDROW() in the InjuredArea table:
And the third section using FINDROW() in the InjuryType table:
This is how it looks in action in the app:
Then going back to your lists screen, you would follow the steps I provided in this reply to pass in THISROW() to the details screen.
Hope this example helps!