One possible way to achieve your scenario in Prism could be using Regions and
Navigation. A region represents a container that can hold dynamic data that is presented in a UI. It allows the Prism Library to place dynamic content contained in modules in predefined placeholders in a UI container.
As Prism documentation shows: “Navigationis defined as the process by which the application coordinates changes to its UI as a result of the user's interaction with the application or internal application state changes.
UI updates can be accomplished by adding or removing elements from the application's visual tree, or by applying state changes to existing elements within the visual tree. (…)
Prism differentiates between the two styles of navigation described earlier.
Navigation accomplished via state changes to existing controls in the visual tree is referred to as state-based navigation.
Navigation accomplished via the addition or removal of elements from the visual tree is referred to as view-based navigation. Prism provides guidance on implementing both styles of navigation, focusing on the case where the application is using
the Model-View-ViewModel (MVVM) pattern to separate the UI (encapsulated in the view) from the presentation logic and data (encapsulated in the view model).”
You can read the following chapters of Prism documentation where these topics are covered and will help you to achieve your desire scenario:
Additionally you could find the following resources handy:
I hope you find this information useful.