Should I avoid the session with a complex object in asp.net?
===

Here's my issue, we have a large patient object that is used on multiple screens throughout the admin. Each screen contains different information about the same patient. It can't all be on one screen.

The only time I want to persist the patient is when the user clicks save. I need to have an in memory patient somewhere. A user may be in the admin, change patient information on various screens, run validation and decide to not save that patient. This is typical use.

Is it ok to store this patient in the session? Or, is there a better approach to do this? At most this admin would have 20 users with access. 
