When handling post requests, need to assume or deal with a "parent" param

[blakewest]

Tables may come with params that are nested under some parent param, such as...{patient: {email: "new_email@gmail.com"}}. Currently, such patches will fail, because they don't know to apply only the thing nested under the parent param.

My guess is it should be assumed to use a nested param that matches the name of the resource, unless specified as an option when creating the resource.