Solution to track Engineering velocity, as well as separate requirements validation process?

[Kevin Quinn]

I am working on a highly regulated project. After the normal Engineering Scrum process that includes QA, there is a separate team providing requirements validation and this sometimes does not take place until several sprints after the initial Engineering work is completed.

We would like to keep it simple and make use of the same Issues to track both processes, but maintain the velocity tracking capability of the original sprint. Can cards be later moved from Done on a scrum board, to a new status (like ready for validation) on a different Board (likely a Kanban), without affecting velocity metrics?

Any issues found in Validation would result in Bugs sent back to Engineering, and the original User Stories would remain in Validation until resolved.

Is this a feasible strategy, or is there an easier or better way to do this?