Thanks to @pramidat and @santhubairam for presenting the custom IPD features that they have developed for one of their implementation sites.
They use the same version of the Bed Management module, nothing specific has been done on the back-end side. So the bottom line is that changes in the module should not break anything on the vanilla Bahmni IPD app or on their custom IPD app.
Both the vanilla IPD app and their custom IPD app need to know which one is the first layer of admission locations. When this first layer is known, then the whole UI assumes that there is a two-layer system to display.
Otherwise fundamentally there is no limitation as to how many nested layers of admission locations can be. From the admin screens standpoint this is not relevant. It is just that the IPD apps will only handle a two-layer setup, and hence should know where to start. I will create a ticket for this.
In its barest form BAH-313 should bring admin screens that:
- Allow to tag/untag locations as ‘admission locations’.
DONE This can be done through the existing ‘Manage Locations’ admin screen. - Allow to navigate the admission locations only to manage their content (beds basically).
This needs to be done. - Once inside an admission location: allow to add/edit/delete bed for a given admission location.
This needs to be done.
@sudipkoirala @mjsanish does that make sense, can we move forward with 2 & 3?