Use caseBodily injury claims
An injury claim goes to an IME physician, a defense lawyer and a reinsurer. A zip by email gives all three everything, with no end date.
One pack per recipient, built from a sharing profilePersonal data masked for readers who have no use for itAccess ends when the sharing stage closes
Health data beyond the IME · compliance decides
The IME profile allows 4 document types. The direct deposit form and the adjuster notes stay in the case.
source · 63 typed documents on the claimA year after settlement, the zip is still in the lawyer's inbox. It held the claimant's medical reports, his bank details and the adjuster's notes, because they all sat in one folder, and the reinsurer got the same zip. Shares go out too wide and never close. Today the adjuster sends fast, and compliance finds out later.
Here the role builds the share. Each recipient gets a pack filled from the document types their profile allows, with personal data masked where they have no use for it, read through the partner portal. The adjuster confirms each pack, compliance approves the sensitive ones, and access ends with the sharing stage.
The claim and the masked loss notice show the rule in miniature: each pack is built for one reader, the sensitive ones are approved before they leave, and every share has an end that nobody has to remember. Ryan's three shares follow it below, one decision at a time.
The claim file stays in the case. Each recipient gets a pack built from a profile compliance wrote in advance.
Ryan Caldwell handles claim CL-26-03190: a cyclist, Jason Pruitt, injured by an insured van. He needs an independent medical exam from Dr. Elena Vasquez, a defense opinion from Hartley & Shaw LLP and a loss notice for the reinsurer. At the end of his review step, he launches an external share for each, from the processes he is allowed to start.
Every document on the claim was typed when it arrived. The IME profile allows accident reports, hospital reports, medical reports and correspondence from care providers, so those land in Dr. Vasquez's pack. Ryan checks the list and adds the physical therapist's letter received yesterday.
The reinsurer needs the facts of the loss and the reserve. It has no use for the claimant's identity. In the viewer, the AI flags the personal data in the loss notice and proposes masks on the name, the address and the date of birth. Ryan accepts. He asks the assistant for a short summary of the injuries, each line citing its report, and checks it before it joins the pack.
The lawyer's pack includes the orthopedic report, because the defense will discuss permanent impairment. Health data going to anyone other than the IME physician needs a compliance approval. Denise Holt checks that the report is the only medical document in the pack and approves it.
Each recipient reads their own pack in the partner portal, with the rights their share allows.
The packs are published to the partner portal. Dr. Vasquez can view and print, the lawyer can view only, the reinsurer can view and download the loss notice. Every page carries a watermark with the recipient's name, the date and the claim reference. The source files never leave the company's infrastructure.
Three weeks later Dr. Vasquez uploads her assessment from the same portal page. The portal calls the repository API: the report is filed on the claim, typed as an IME report, and Ryan has a task waiting for him.
A share opens, and a share closes. In between Ryan sees what happened, and afterward Denise can show exactly what left.
Each view, print and download on the portal is recorded with its author and its date. Ryan reads the history of the three shares on the claim, and sees that the reinsurer downloaded its loss notice on Nov 13.
Rights are set by process stage: the recipient can read the pack while the share is at its open stage, and not after. With the IME report filed on Dec 9, Ryan closes Dr. Vasquez's share early. The reinsurer's share reaches its due date and closes. When the claim is settled, any share still open closes with it.
At the quarterly review, Denise searches the shares by profile and by data category. For each one she sees the recipient, the version of each document sent, the masks applied, who approved it and when access ended. The internal auditor asks which outside parties received health data last quarter. She filters and exports the list.
Before a pack goes out, it is held against the recipient's profile. Three outcomes are possible, and only one leaves without a second look.
The documents match the profile, and the masks the AI proposed are approved.
Then: the adjuster publishes the pack to the partner portal.A medical report to a lawyer, bank details to an adjuster. The share says which.
Then: compliance approves or refuses, with a reason on the share.The claimant's identity in a reinsurer's pack. Compliance names the document that blocks.
Then: the pack goes back to the adjuster to mask or remove it.It sends nothing, approves nothing and opens no access. Ryan confirmed every pack and Denise approved the one carrying health data, and the claim records both decisions.
The AI flags personal data, proposes masks and writes the injury summary. The profile sets the limits of each share, so they hold on the busiest day of the year.
Counted on claim CL-26-03190 and its three shares. More recipients per claim means more packs, and still no zip.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
Claim files leave through the adjuster, under rules compliance writes, over a portal IT runs. Three desks, three different worries.
IME physicians and lawyers want the file today, and a clean copy takes an afternoon to build.
You learn what was shared after it has already left.
Every new partner brings one more file transfer tool to run.
With one recipient type. Take the IME physicians, who receive the most sensitive files, and write their profile with compliance. One profile and a few real shares on test data are enough to prove it.
The shares run on top of your claim files and documents, and recipients need nothing more than a browser.
Ready to try
Tell us who your teams send files to and what those files hold. We will set up two or three profiles with your compliance team and run a share on test data.