Actually, as June7 noted, it's not. Lack of normalization is often the cause of your problem and sure, there are work-arounds. What if they come back next month and ask for another measure - add another field and have to modify all your reports/forms/queries? To need to do this is a sure sign of design problems. As a general rule, you should never be in a position where you have to add additional fields of the same attribute (characteristic). I know you've been around here before and hope that I've never answered in a way that made you feel moronic, so at the risk of repeating myself, do you need pointers to entity/relationship topics? Understanding that is is pivotal IMHO.
You probably need a table for visit info (with fields like visit id, location, date etc.) and a table for visit actions/outcomes/plans - whatever you call them. Because this would be a many times an action can be related to many visits, it would be a many to many relationship.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.