Free scoping read. A written assessment of your manuscript in two business days, at no cost.

Start one
Contents

Academy · Research Writing · Data Security in Medico-Legal Work

Client Data Handling in Medico-Legal Projects: Security and Privilege Standards

A medico-legal project typically spans two overlapping legal protections: the privacy and security rules of the Health Insurance Portability and Accountability Act (HIPAA) for health information, and the attorney work-product doctrine first recognized in Hickman v. Taylor for litigation materials. Correct handling of the underlying data requires that both be satisfied concurrently, rather than treating one as a substitute for the other.

Pubrica AcademyWritten by a health data compliance analyst Reviewed bya health law reviewer Published10 October 2026 Last checked10 October 2026 Reading time8 minutes Sources10 peer-reviewed

Client data in a medico-legal project typically include protected health information drawn from medical records, communications between counsel and the medico-legal reviewer, and the reviewer's own work product, namely draft analyses, notes and preliminary findings produced in anticipation of litigation. Each of these three categories is governed by a distinct legal framework, and correct handling requires identifying which framework applies to which category, since the rules of the Health Insurance Portability and Accountability Act (HIPAA) on health information and the litigation privileges that protect legal work product address different questions and protect against different risks.

Learning objectives

  • The specific requirements of the HIPAA Privacy, Security and Breach Notification Rules
  • Why attorney work product is protected separately from attorney-client privilege, and the scope of each
  • The position of a medico-legal reviewer’s draft analysis within these protections

Common misconceptions

  • “Attorney-client privilege and the work-product doctrine are the same protection applied to different material.” Hickman v. Taylor (1947) established the work-product doctrine as a distinct protection for materials prepared in anticipation of litigation, separate from attorney-client privilege, which protects confidential communications between a client and their attorney; the draft analysis of a medico-legal reviewer can be protected work product even where no privileged communication is involved.

Definition of client data in a medico-legal project

A medico-legal project generates at least three distinct categories of data, each carrying different legal protections: the underlying protected health information contained in medical records and test results; communications between the client or referring attorney and the medico-legal reviewer about the matter; and the reviewer's own work product (draft reports, research notes and preliminary analyses produced because litigation is anticipated or underway). Treating all three as a single undifferentiated “confidential” category is a common and avoidable error, because the rule governing how each category must be stored, transmitted and disclosed differs, and a safeguard adequate for one category is not necessarily adequate for another.

HIPAA and the handling of health information

The Privacy Rule of the Health Insurance Portability and Accountability Act, administered by the U.S. Department of Health and Human Services (HHS), establishes national standards for protecting individually identifiable health information, specifying when such information may be used or disclosed and the safeguards required1. HHS has published a detailed summary of the requirements of the Privacy Rule, covering permitted uses and disclosures, individual rights and administrative obligations; this summary is the practical reference for confirming that a specific data-handling practice is compliant, rather than relying on a general impression of what HIPAA requires2. A separate, related requirement, the Security Rule, addresses electronic protected health information, setting administrative, physical and technical safeguard standards for the storage and transmission of such data; it is the rule that the IT practices of a medico-legal project concerning medical records must satisfy3. The HHS Breach Notification Rule, in turn, sets out the obligations that follow if protected health information is nonetheless exposed, including notification timelines and required content, a contingency that the data-handling plan of a medico-legal project should address explicitly rather than assuming that a breach will not occur4.

Privilege and work-product protection for the review

Separately from the health-information rules of HIPAA, the reviewer's own analytical work is protected, where applicable, by the work-product doctrine, first recognized by the U.S. Supreme Court in Hickman v. Taylor (1947), which held that materials prepared by or for a party in anticipation of litigation are generally protected from discovery by the opposing side, in order to preserve the reliance of the adversarial process on careful, candid preparation5. This protection was later codified in Federal Rule of Civil Procedure 26(b)(3), which sets out the conditions under which work product may nonetheless be discovered, generally requiring a showing of substantial need and of undue hardship in obtaining the material by other means6. Attorney-client privilege is a distinct protection covering confidential communications between a client and counsel made for the purpose of obtaining legal advice; Upjohn Co. v. United States (1981) extended the practical application of this privilege within an organizational context, clarifying how it applies to communications between the employees of a corporation and its counsel7. A draft analysis prepared by a medico-legal reviewer at the direction of counsel in anticipation of litigation can be protected work product even where it does not itself constitute a privileged communication, which is why the two protections must be tracked separately rather than treated as interchangeable.

Safeguards that satisfy both frameworks

The special publication of the National Institute of Standards and Technology (NIST) on implementing the HIPAA Security Rule provides a detailed, practical resource on the technical and administrative safeguards that the Security Rule requires, covering risk analysis, access controls and encryption practices appropriate to the sensitivity of the health information involved8. Satisfying the HIPAA framework and the litigation-privilege framework simultaneously requires practices that address the specific concern of each: encrypting and access-controlling protected health information to the standard set by the Security Rule and, separately, marking, segregating and limiting the circulation of work-product materials (draft analyses, internal notes and privileged communications). Otherwise, a data-security safeguard designed only for HIPAA compliance may leave work-product materials commingled with, and as exposed as, the underlying medical records, in a manner that could support an argument that the work-product protection was waived9. The recommendations of the International Committee of Medical Journal Editors and the guidance of the Committee on Publication Ethics on confidentiality in research more broadly reinforce the same underlying principle from the perspective of publication ethics: confidentiality obligations are specific to the category of material involved and must be actively maintained, not assumed, throughout the full data lifecycle of a project10.

Common errors in handling medico-legal project data

A frequent error is the application of a single, uniform storage and access policy to an entire case file, including medical records, attorney communications and the reviewer's own draft analyses, treating “confidential” as a single category rather than recognizing that HIPAA governs one part of that file and the work-product doctrine governs a different part under an entirely separate legal test15. A second error is the assumption that the technical safeguards of the Security Rule (encryption, access logging and automatic session timeouts) are optional best practices rather than specific, verifiable requirements with a detailed implementation specification38. A third error is the failure to prepare a breach-notification plan in advance, leaving a project to respond to the specific timelines of the Breach Notification Rule only after an exposure has occurred, rather than having the notification content and timeline already defined4.

Worked example: segregation of work product from the medical record

A hypothetical medico-legal project illustrates the issue: a reviewer's preliminary draft analysis, containing tentative conclusions and candid notes about weaknesses in the claimant's documentation, is stored in the same shared folder as the underlying medical records. Under Hickman v. Taylor and FRCP 26(b)(3), the draft analysis is the type of material prepared in anticipation of litigation that is generally protected from discovery, but commingled storage with limited, undifferentiated access controls makes it more difficult to demonstrate that the material was treated as protected work product rather than as an ordinary business record56. A corrected practice would store the draft analysis in a separately access-controlled location, label it explicitly as prepared at the direction of counsel in anticipation of litigation, and limit its circulation to those within the privilege or work-product protection, while the underlying medical records remain separately secured to the encryption and access-control standard of the Security Rule8.

Good practice across the project lifecycle

Good practice treats data classification as a first step performed before any file is stored or shared, not as a retrospective correction. Every incoming item is classified at intake as protected health information, privileged communication or work product, and the safeguard specific to each category (Security Rule-compliant encryption and access control for health information, and segregated, labelled storage for work product) is applied immediately rather than after a question arises19. A breach-notification plan consistent with the HHS timelines is prepared and reviewed before it is needed, and access to privileged communications is limited on a documented, need-to-know basis consistent with the description in Upjohn Co. v. United States of how privilege operates within an organizational structure47. This discipline at the outset prevents a single data-handling error from becoming a waiver argument or a compliance failure later in the matter, and it is considerably easier to apply consistently when established as the default handling practice of the project from the beginning rather than introduced partway through, once the classification of a specific document is already in dispute.

Key points

Client data in a medico-legal project span protected health information, privileged communications and attorney work product, each governed by a distinct framework: the HIPAA Privacy, Security and Breach Notification Rules on one side and the work-product doctrine from Hickman v. Taylor on the other. Both must be satisfied specifically rather than through a single generic confidentiality practice.

Practical application

  1. Each item of project data should be classified by category before its handling is determined. Protected health information, privileged communications and attorney work product are governed by different rules and require different safeguards rather than a single blanket confidentiality policy.
  2. Electronic health information should be confirmed to meet Security Rule standards specifically. NIST SP 800-66, from the National Institute of Standards and Technology, serves as a practical reference for the administrative, physical and technical safeguards that the HIPAA Security Rule requires.
  3. Work-product materials should be segregated from routine health-record storage. Draft analyses and internal notes prepared in anticipation of litigation should be marked and their circulation limited, so that the work-product protection established in Hickman v. Taylor is not inadvertently weakened by commingled storage.

References

Every source above is a peer-reviewed article, a publisher’s record of one, or a standard issued by the body that owns it. Each carries the date it was last read. Where a standard moves, this article is revised rather than left up with a note.

Pick your referencing style and copy it. Your university or target journal may vary the punctuation — check its guide if it has one.

Pubrica Academy. (2026, October 10). Client Data Handling in Medico-Legal Projects: Security and Privilege Standards. Pubrica. https://pubrica.com/academy/client-data-security-in-medico-legal-projects/

This article is written to be learned from. Cite it if you are referring to what it says; if you are using the evidence behind it, cite the sources listed above instead.

Client Data Classification Checklist

Classify and safeguard medico-legal project data by category before handling begins.

[ ] Classified each data item as protected health information, privileged communication, or work product
[ ] Confirmed electronic health information meets HIPAA Security Rule safeguards (NIST SP 800-66)
[ ] Segregated work-product materials from routine medical-record storage
[ ] Marked draft analyses and notes as prepared in anticipation of litigation where applicable
[ ] Confirmed a breach-notification plan exists consistent with the HIPAA Breach Notification Rule
[ ] Limited circulation of privileged communications to those within the privilege

Pubrica AcademyWritten and maintained by Pubrica’s subject matter experts. Articles are revised when the underlying standards change, and each article states the date on which it was last reviewed.

How Pubrica can help

Pubrica’s medico-legal research team classifies project data by category (health information, privileged communication or work product) and applies the specific HIPAA and litigation-privilege safeguards that each category requires.

Find something else

Search the Pubrica Academy

Access is free and requires no account. Enter a topic, or open the full library to filter by category, sub-topic or resource type.

Classification of medico-legal project data by required protection

A scoping assessment is free and takes two business days. It provides a written assessment of what the work requires and which specialist would undertake it.

Get a free quote

Regulations

Check your project against this rule

  1. 1Your work
  2. 2Your details
  3. 3Send
What do you need?

Material you send is held under signed confidentiality, with access limited to the assigned team and encrypted transfer. It is not used to train anything and is not passed to third-party tools. Ask for the agreement before you send anything you would rather cover first.