That would depend a lot on three things:
1. How many raster images you've got imported into your set.
2. How many DWG files you've got imported into your set.
3. How much 3D information you've got within your Revit Families within the Project.
The way that Revit works is that individual instances of elements are just references of the same Family Type. Just like Blocks in AutoCAD. So I could have one chair, or a thousand, and my filesize will remain the same. But if I have a thousand different chairs, of different levels of 3D detail, the file would be much, much larger.
So, for example, a shopping mall or warehouse (or office tower) that's 90% repetitive elements could have a much smaller file size than a smaller but way more custom multi-family housing complex where only %20 of it is repetitive, and everything else is custom.
So, in other words, I don't think anyone here will be able to answer your questions. Every time something Revit comes up, you chime in with Hospital questions, and I don't think anyone who's doing that kind of work hangs out here sadly. Maybe you should try a pilot, or try to find a firm doing hospital work and using Revit via a reseller or Autodesk to get better answers to your questions.
But, I've seen models way, way more complex than what can be done in AutoCAD, ADT, or Max done in Revit. Take the same model, export it from Revit to DWG, and it makes the same machine crawl when opened in anything else due to number of faces of elements. I was working on a (really) huge project the other week, where half is in Revit and half is in ADT 2004, and the ADT filesizes were way, way more frightening than the Revit ones (and those ADT models weren't nearly as complex, just walls and windows and such).
A very rough rule of thumb I've found over the last five years or so works well is that whatever DWG's it takes to deliver a project, added all togther, will be about the same to 10% larger than the equivalent Revit file that it would take to deliver the same project. It's a fast-and-dirty rule, so it's not perfect, but it seems to work.
But what seems to add bloat the fastest is importing in raster images and DWG's FYI.