Building a Malpractice Case and Knowing the Pitfalls
Posted: Wednesday, January 12, 2011
by PRA Law
Pellettieri, Rabstein & Altman
Medical malpractice claims have always created anxiety and some fear in the minds of many attorneys, often with good reason. If properly selected, they are claims usually involving medically sophisticated issues, steps that are necessary to insure the client's story can be told in Court, significant expense, a strong defense bar, and substantial time and financial responsibility for the attorney who is willing to accept them.
This is best done early, even before suit, if possible, to avoid the money pit/trap any poorly selected or poorly prepared medical malpractice case can become. Unlike the more common personal injury claim, experts are needed to prove both liability, damages and the connection between the two. The major investment and hurdle to winning is often in doing what is necessary to clear the liability hurdle and to connect it to the damage obstacle. Since the patient usually comes to medical attention with an injury or illness, the causal connection to the end result is something your client may not easily appreciate as the problem it can often become. It is a hurdle that must be understood and cleared early.
If there is no appreciation for the need to differentiate for the jury the end result from proper treatment versus the malpractice caused outcome, you can find yourself, along with your client, well into the responsibilities, obligations, and financial commitment of the suit, finding out that the clearing the liability/fault hurdle might just have led you to the far more difficult damage causation "jump" you had not anticipated to be so high and wide.
About the Author
Attorney Andrew Rockman is a partner who has been representing injured plaintiffs in medical malpractice cases in New Jersey for more than thirty years. For more information, visit http://www.pralaw.com
This Article has been viewed 135 times. (Not updated in real-time.)
No comments yet.We want your comments! If you can read this, you don't have javascript enabled, so you can't use this comment system. Please enable javascript.