ideaman911 wrote on Wednesday, April 01, 2009:
Folks;
There are a few search functions and data entry functions which could go a long way. As background consider that it is helpful for my user to have every new ICD she enters become an entry into the “Issues” listing, which is actually formed in …/custom/clickoptions.txt Her current process is to add the ICD at Superbill, then manually create that Issue for that patient’s encounter. Invariably that leads to transcription errors and omissions. She likes to have the ICD code followed by its description separated by a hyphen with spaces around it. That helps her when she goes to the Fee Sheet to do the Justify and assign the ICD. The search capability there is helpful. Why not use the exact same functionality to allow the search and add in the Encounters - Issue area, which would make the clickoptions insertion unnecessary?
At present I export the ICD list periodically to Excel then do a sort and concatenate build to make the "medical_problem:: 123.45 - This is the ICD problem" line by line for clickoptions.txt. But you can see how tedious that can be, and the list is always lagging her efforts. If we could do per above, that would be immediately available as soon as created in Superbill. Even better would be imports.
BTW, the Superbill search can ONLY look for numbers. Why not text match descriptions as well, since that is the way most users will think?
A potential customer asked about getting the medications info from PDR with a simple click selection to populate the Rx fields. If that could be made to default there, could it not default there for the medications from the Issues as well? Or even better, if a med is selected for Rx, it should post to the encounter issues directly without added effort?
Joe Holzer