What Medical Documents Will I Need to Gather for My Medical Malpractice Case?
Home / Blog / What Medical Documents Will I Need to Gather for My Medical Malpractice Case?
Medical malpractice cases are difficult to process for many reasons. You and your medical malpractice attorney will need to gather many different medical documents while litigating your lawsuit. Your lawsuit could be against a medical provider, a pharmaceutical business, or other medical entity. You could help your case provide proper documentation if you gather the proper letters, records, forms, and data. Careful review of those documents may show that negligence on part of the health care professionals was involved.
What Are the Different Kinds of Documents I Will Need?
Medical records. Most of the time, your medical records will be a huge chunk of evidence for your medical malpractice case. If you do not have any of these records in your possession, you can provide the names and addresses of the medical providers you saw to your attorney. Your attorney can then get the copies of your medical records on your behalf.
Mental health records. If you received treatment from any mental health professionals (psychologists, psychiatrists, or psychotherapists), your attorney will want to review those records in order to determine if your need for treatment was related to your medical condition.
Prescription medicine data. Your attorney will also need to know the names of any prescription medications you take, including the dosage.
Health insurance information. If you have any sort of disability or health insurance, it is crucial that you relay that information to your attorney. Obtain a copy of your health insurance policy or a copy of your certificate of coverage.
Hospital and medical provider bills/invoices. Your attorney will want to know how much you or your insurance company were charged for medical treatment and care. Keep all copies of invoices and bills that you receive from your medical provider.
Documented proof of lost wages. If you lost time from work as a result of your injury or illness, your attorney may be able to help you recover from that loss. Your attorney will need to prove that you suffered a wage loss that was caused by your injury or illness. A common way to do this is to compare your earnings from the periods of time before and after you were sick and/or hospitalized. Obtaining a copy of your attendance record and sick leave from your employer after your hospitalization will assist in determining whether lost wages should become part of your claim.
It’s important to know that a client must not selectively omit some records which may be unflattering to the client. Otherwise, the attorney could be blindsided and the validity of the case weakened when the defense attorney presents records that the client should have revealed.
If you are able to obtain these documents and provide them to your attorney, then your medical malpractice case will have more evidence to present in court. Contact Regan Zambri Long PLLC today if you would like more information on your eligibility for filing a medical malpractice lawsuit.
Share This Article:
About the Author
Patrick M. Regan, Esq.
Patrick Regan is a board certified personal injury lawyer and a founding partner at Regan Zambri Long. His practice is devoted to helping those who suffered catastrophic injuries in car accidents, truck accidents, Metro accidents, and medical malpractice. Over his nearly 40-year career, Patrick has obtained some of the most significant jury verdicts in the history of Washington, DC on behalf of injured victims. Patrick is licensed to practice law in Washington, DC, Virginia, and Maryland. He received his B.A. at Hamilton College and his J.D. at the Columbus School of Law at the Catholic University of America.
Have you or your loved one sustained injuries in Washington DC, Maryland or Virginia? Regan Zambri Long PLLC has the best lawyers in the country to analyze your case and answer the questions you may have.
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Cookie Preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
CleanTalk offers effective spam protection and website security solutions to enhance user experience.
Name
Description
Duration
spbc_is_logged_in
Dashboard. Flag defines if a user was logged in.
Session
ct_
Group of cookies used for storing dynamic variables from browser
Session
ct_sfw_
Group of cookies used for our SpamFireWall technology.
Session
spbc_cookies_test
Cookie to test cookies so we know that everything working properly
Session
spbc_firewall_pass_key
The flag defines if the Security Firewall was passed.
Session
apbct_cookies_test
Сookie to validate other cookies, so they can’t be spoofed.
Session
spbc_timer
Dashboard. Time spent on the page.
Session
spbc_log_id
Dashboard. User identification.
Session
spbc_2fa_passed
Dashboard. Flag defines if Two-Factor Authentication was passed.
Session
apbct_antibot
This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website.
session
ct_check_js
Used in order to detect spam and improve the website's security.
session
ct_fkp_timestamp
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
ct_has_scrolled
This cookie is used to distinguish between humans and bots.
session
ct_pointer_data
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
ct_ps_timestamp
Used in order to detect spam and improve the website's security. Does not store visitor specific data.
session
ct_timezone
Used in order to detect spam and improve the website's security.
Session
apbct_
Group of cookies which are set from backend and contain information about the current user
Session
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Used by the content network, Cloudflare, to identify trusted web traffic.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
Facebook Pixel is a web analytics service that tracks and reports website traffic.
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
cookiePreferences
Registers cookie preferences of a user
2 years
Matomo is an open-source web analytics platform that provides detailed insights into website traffic and user behavior.
This cookie is used to play YouTube videos embedded on the website.
2 years
DEVICE_INFO
Used to detect if the visitor has accepted the marketing category in the cookie banner. This cookie is necessary for GDPR-compliance of the website.
179 days
YSC
Registers a unique ID to keep statistics of what videos from YouTube the user has seen.
Session
PREF
This cookie stores your preferences and other information, in particular preferred language, how many search results you wish to be shown on your page, and whether or not you wish to have Google’s SafeSearch filter turned on.
10 years from set/ update
VISITOR_INFO1_LIVE
Tries to estimate the users' bandwidth on pages with integrated YouTube videos. Also used for marketing
179 days
GPS
Registers a unique ID on mobile devices to enable tracking based on geographical GPS location.