Now, when architecting this solution, have to take many factors into consideration:

1) First and foremost, time is of the essence ( literally ) – as many of the organs have as small as a 6 HOUR window of opportunity from surgical “procurement” to transplantation.

2) The UWHealth ITS ( Info Technology Systems ) team generally consists of non-.NET developers who are tasked to maintain and customize purchased products developed from a wide variety of other companies.

This project is a new type of endeavor for the department as a whole – ie. in house ASP.NET development.

So while the development staff and project management team are top notch and extremely knowledgeable about the what the application will need to do – they are relatively new to developing critical ASP.NET core applications.

And most importantly in my decisions, they will need to be able to maintain the developed ASP.NET application once the application is past the development stages.

So…

1) For now, choose to go with an n-tiered implementation (obviously ) -- and based on the experience level of the folks that are going to support it after I depart, going with classic WebForms, not MVC.  

As to MVC, I'm not necessarily sold on the benefits of MVC over WebForms myself yet either – spent time playing with the MVC RC1 from Microsoft that allows for easy setup of MVC – and that works great!, but aside from making TDD a little easier - not sure moving away from WebForms will happen any time soon for most projects.

2) Right now looking at how I want to implement my DAL, looking at Linq to Entity as I haven't used that before and it appears to be the direction Microsoft is going, as opposed to Linq to SQL, etc.