I highly recommend that the Andela team focus only on the specific use case of Drug Order Entry for now, and we keep the UI specific to this (e.g. “Active Prescriptions” is fine). Once that is built and released, we can add Lab Orders, and this may require changing some text labels, or even the whole screen layout. (Full order entry is a huge project, and its size and complexity have the potential to distract…)
That said I agree with Burke’s that you should not use a table with many columns for this, but just write out the whole order text in a single column. This is probably more familiar to doctors, who are used to doing this on paper.
In the existing UI it looks like this:
Bahmni does it similarly:
This will allow both structured and free-text drug orders to be recorded, and it will also pave the way for other types of orders to be listed inline as Burke points out will happen in the future.
FYI the API has a mechanism for different types of dosing instructions to be defined (the main one is SimpleDosingInstructions) and the thing they have in common is that they can all be represented as a string.