@ssmusoke, it would take some code to make this happen, but yes, it’s possible, and yes, we generally intend to support this.
Behind the scenes OpenMRS has the idea of a configurable encounter-to-visit-assignment-handler. The EMR API module has an implementation of this that it activates by default.
In the currently implementation, if you create a past encounter that can’t be placed in an existing visit, it just leaves it that way. (I don’t think that implementation has been changed at all from what PIH initially wrote for Mirebalais.)
The change you would need to make is to add behavior like ExistingOrNewVAH from openmrs-core to the end of the EMR API version.
I would welcome you to (a) create a ticket in the EMR API module for this, and propose how you think the behavior should be changed, (b) verify that this won’t break the Reference Application UI, and © implement it. There is definitely room for improvement in the current code.