sunsetsystems wrote on Thursday, January 28, 2010:
Regarding Tony’s proposed requirements:
The tables that we developed call for an order to be associated with an encounter. Of course we might plug in an encounter ID of 0 to indicate no association, but is that desirable? Note that any related billing must absolutely be tied to an encounter.
By “order type panel” are you referring to the GUI for maintaining procedure and result types? I do envision that it can be desirable to add new types in the course of placing an order. So my thinking is to enhance this for use as the order type selector when placing an order, in addition to its current functionality of maintaining the types.
I don’t know what a “framework for plugging in new order types” would look like. My style would be to JavaScript the thing to adapt its look according to the order type, but I’m very receptive to other ideas.
Regarding a couple your questions:
(1) If the ordering interface is effectively an encounter form (as in the Phyaura model) then it can be indicated just like other encounter forms in the clinical view of the encounters list.
(4) Automatically creating a charge line item sounds like a nice optional feature. For example some information could be added to the procedure type entry for that.
Finally, I will probably have to write some code for non-electronic order entry and results to meet my client deadlines before we have everything sorted out. This may end up being throw-away code and I’ll keep it out of CVS to the degree we are in limbo, but I hope most of it will be useful.