Argthtjtr

I am currently trying to learn MVVM - this is my first application, apologies if my understanding is poor. I have been tasked with creating a Medical Resource Management System which allows for different disciplines of Doctor e.g. Cardiologist, Pulmonologist, Urologist etc to be registered and deregistered in the system.

These Doctors must hold discipline specific information

All disciplines inherit from an IDoctor interface. Currently I have 10 separate Models - one for each discipline of doctor. These doctors will all interact with similar views i.e register view, deregister view, however, I am unsure how I should approach hooking up each Model to the view via the ViewModel. Should I create separate ViewModels foreach Discipline's interaction with the View or contain all disciplines within one ViewModel?

I have created the following view:

RegistrationView

From here I am unsure if I should create a ViewModel for each specific Discipline of Doctor which interacts with this View or if there is some more practical way to approach this.

Should I create separate ViewModels foreach Discipline's interaction with the View or contain all disciplines within one ViewModel?

A ViewModel is to support a View. So, in your case, first define your view: i.e.: create the labels, lists, buttons etc.

This will give you a better view (excuse the pun) on your ViewModel. Normally the view is to interact, and it doesn't make sense to create 10 different screens for just a different discipline.

in MVVM view and ViewModel are somehow tightly coupled. I would not say to build exactly one VM for each View. Its totaly dependent on view, how It will function. For example You have task to display address of customer such that customer details page can see address in tab control with each and every information, where there is another view where customer address displays only few columns, and another one, where customer can edit his address.
Ideally these 3 view have same business, i.e. show address, but layout is different; also only edit view has extra functionality to edit changes.
In such situation, you don't need to create saperate VM for each view, instead create one VM and use it smartly.

Now Models and ViewModels are loosely coupled, Only models will be part of VM, which is required by View.
In address example I might have Models of CustomerAddress, City, or POBox (which retrieve all information based on PO code).
but I dont need to create VM for Pobox or City; but Address VM need these models.
Hope you got the point