Thanks for your feedback guys.  I understand David's point because, while I do plan on keeping up on technology trends, I definitely don't see myself spending too much time on the details.

I also agree with Craig in that you have a responsibility to communicate opinions and validate them for the benefit of the project. 

So how do you suggest I approach requriements that I feel have a technical feasibility issue?  For example, on a recent project, the users explained a requirement that involved importing data from a client and updating our systems.  I asked about the format that the data was being sent to us in and how the update was to occur.  They said that the data could be in a variety of formats, with no defined layout (i.e. specific fields, data type, order) and there was not a consistent field in the data on which the file would be matched to our data in order to do the update.  They current do the updates by trial and error.  They look at the data, and mess with it until it works.  I feel that this is a feasibility issue.  I tried to sugest improving their process by standardizing communications with clients, but they do not accept the suggestions. 

How should I approach this?  I don't want to just say it can't be done because I am not the technical expert.  We have an internal IT team, but we are not sure if they are going to do the development or if we are going to outsource.  How should I validate my hunch and communicate back to the business?

Thanks!