Webform approach

This is actually how I'm trying to use Field Collections, as a way for a Manager to input information for a form in a nested format (Category, Subcategory, and Detail, all multiples of multiples), which will determine basically the labels for a staff member to input information for. For example, a category of "Vital Signs" has Subcategory "Pulse" (Details of 7am and 7pm), and a staff member must put a number by the Details. This is more complicated than I had originally thought, because as is, my clients use a printed out spreadsheet that the Manager's designed per patient, that each form is for. Every form/sheet is totally different. The staff members squeeze their initials and information into the boxes, very inefficient and icky-looking.

What I've been researching for days, is how to have this functionality of one role of user designing a form for another to input data for, essentially. And no, believe me, I know of Webform, but that doesn't fit because I need views integration at least at some level. Like I said, I've been doing my homework, but nothing seems mature enough (at d7 even) to handle this problem; in my research, I've got Webform, Table Field (where I would do some kind of magic with permissions, or setting the default headers programatically, I have no idea), using a million dynamic select lists, Subform and all that, Dynamic Properties, some views integrated formbuilder UI I have yet to find, CCK Input Field, and a concept idea I read in an issue awhile ago relating subform to views in some way.
I have read that giant issue where many developers went back and forth between combofield, field collection, and flexifield, and I'm keeping up on this idea in multiple module issues.

I could be thinking waaay too hard into my problem, but I'm having trouble. Field Collection seems to be the closest I can get. Bringing myself back to the webform idea, what if, since a field collection is an entity, that another field could be added, such as a textfield, after the field collection has been made. As in this picture: http://drupal.org/files/issues/field-collection.png where the SKU are already labelled, what if that label/field weren't hardcoded but a field of a field collection specifiable by a user. I think this is the basic idea tons of modules are trying to get at.
(apologies for the insanely long comment, I always give too much long-winded information)

You might want to try the Entity Forms module http://drupal.org/project/entityform