You are the vice-president of application development for a small, but rapidly growing software company that?

produces patient billing applications for doctors鈥?offices. In working on the next release of you firm鈥檚 one and only software product, a small programming glitch has been uncovered in the current release that, if left uncorrected, poses a security risk to its users. The probability of the problem being uncovered is low, but if exposed, the potential impact on your firm鈥檚 100 or so customers could be substantial-hackers could get access to private patient data and change billing records. The problem will be corrected in the next release, but you are concerned about what should be done for the users of the current release.
The problem has come at the worst possible time. The firm is seeking approval for a $10 million loan to raise enough cash to continue operations until revenue from the sale of its just-released products offsets expenses. In addition, the effort to communicate with users, to develop and distribute the patch, and to deal with any fallout will place a major drain on you

It has to be rolled back to a safe and secure issue, or be well insured.

As for hackers they will always find a way in no place is truly secure, just can be more difficult to get the info.

....and the question is????? Big long narrative but no real question. What do you mean by "patient billing applications" does you company just make forms? or does the company process the applications the doctor's patients fill out in their offices. More info.

I would assume the big danger would be if the doctor's offices were on some grand network because most offices of doctors are local area networks and that would be a local area network security issue not a programming issue.

Work day and night to get the patch working . Prove it works and then distribute it to all customers as soon as possible with the minimum of fuss. Don not tell anyone about the problem apart from your customers and deal with it in a light efficient way. Hopefully it wont impact on future projects and no one will lose confidence in your enterprise . The most important thing is to write the patch as quickly as possible and prove it works . Rigorous testing.