Use caseBodily injury claims

Injury claim files shared by role

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

Each pack

Health data beyond the IME · compliance decides

Actions on this claim
The sharingPack: Dr. Elena Vasquez

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 claim
01

The starting point

In two paragraphs

A 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.

Claim CL-26-03190Case management
Three readers, three end dates. The claim on the left, one share per recipient with its profile.
Pack: Reinsurer · Loss notice.pdfViewer
What leaves. The reinsurer reads the loss and the reserve. The claimant's identity is masked in its copy.

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.

02

The packs

The claim file stays in the case. Each recipient gets a pack built from a profile compliance wrote in advance.

Step 1Workflow

One share per recipient, started from the claim

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.

IME physician: 45 daysDefense counsel: 90 daysReinsurance notice: 30 days
Claim CL-26-03190Case management
Profiles are written once by compliance. The adjuster picks one and its rules come with it.
Each share is a case of its ownWith its recipient, its profile and its due date. The claim stays whole, and each share can be followed on its own.
Step 2Case

The pack fills from the types the profile allows

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.

Pack: Dr. Elena VasquezCase management
The documents are transferred to the share, and their history stays on the claim.
The bank details never reach the doctorThe selection follows the role. The adjuster adds what is missing, and the rest stays in the case.
Step 3Viewer

Data inside the documents is masked for each reader

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.

Pack: Reinsurer · Loss notice.pdfViewer
The original stays complete in the claim. The masks travel with the copy that is shared.
Each reader gets the facts their job needsThe reinsurer can price the loss without ever learning who the claimant is.
Step 4Workflow

Compliance approves the pack that carries health data

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.

Sharing approvalsCase management
The decision and its reason are written on the share.
The sensitive packs are seen before they leaveCompliance does not audit the shares after the fact. It approves the ones that need it, on the way out.
03

The reading

Each recipient reads their own pack in the partner portal, with the rights their share allows.

Step 5Viewer

Each pack is read with its own rights

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.

Orthopedic report, Oct 2.pdfViewer
The recipient reads a faithful rendition in the browser, with nothing to install.
A printed page still says whose it isThe rights follow the role, and the watermark follows the page.
Step 6Intake

The IME report comes back into the case

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.

IME report: filedTask: read the assessment
Count it in your own claims shop: how many IME reports arrive as email attachments, and how many of those ever reach the claim?
Nothing travels through a mailboxThe report arrives where the claim is, already typed, and the adjuster is told.
04

The end

A share opens, and a share closes. In between Ryan sees what happened, and afterward Denise can show exactly what left.

Step 7History

Every action on the packs is recorded

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.

Claim CL-26-03190 · SharesCase management
The trail is part of each share, readable by whoever opens it next.
The adjuster knows who opened whatWhen the lawyer says the report never arrived, the history answers.
Step 8Workflow

Access ends when the sharing stage closes

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.

SharesCase management
A timer runs on each open share, and the team lead sees the ones that end this week.
Nobody has to remember to cut accessThe end is part of the share from the start. Closing the stage closes the door.
Step 9Reporting

The sharing register answers the audit

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.

Sharing registerCase management
Each share keeps the pack exactly as it was sent, even after access has ended.
Audit questions are answered from the registerWho received what, in which version, approved by whom: the register has held it since each share opened.
05

Where each file lands

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.

Within profile

Only what the role allows

The documents match the profile, and the masks the AI proposed are approved.

Then: the adjuster publishes the pack to the partner portal.
Needs approval

Sensitive data beyond the profile

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.
Refused

The reader has no use for it

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.
What the AI leaves to you

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.

06

The gains

Counted on claim CL-26-03190 and its three shares. More recipients per claim means more packs, and still no zip.

0 zipssent by email. Each recipient reads a pack in the partner portal.
3 packsbuilt for three roles, each with the documents and data that role needs.
0 shareswithout an end date. Access closes with the stage, or with the claim.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

The three principles behind those numbers

Zero oversharingProductivityThe pack fills from the profile. The adjuster adds and confirms, and does not build it by hand.
Zero forgotten accessProcess reliabilityEvery share is a case with a stage and a due date. It closes on its own schedule.
Decision supportA person decidesThe AI proposes masks and summaries. The adjuster confirms, compliance approves.
07

Built for

Claim files leave through the adjuster, under rules compliance writes, over a portal IT runs. Three desks, three different worries.

Business operations

Claims adjusters

IME physicians and lawyers want the file today, and a clean copy takes an afternoon to build.

  • The pack fills from the profile you pick.
  • The AI proposes the masks for each reader.
  • The summary for the reinsurer cites its reports.
  • The IME report comes back into the claim.
Risk and compliance

Compliance officers

You learn what was shared after it has already left.

  • You write the profiles once, per role.
  • Sensitive packs come to you before they go out.
  • Every view, print and download is recorded.
  • The register exports for the auditor.
IT and architecture

CIOs and architects

Every new partner brings one more file transfer tool to run.

  • Recipients read through a portal, in the browser.
  • Source files never leave your infrastructure.
  • Rights and watermarks are set per share.
  • Hosted in your data center or in a cloud tenant, as you prefer.

How to begin

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

Build your first sharing profiles

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.

The screens on this page are drawn to show one step at a time, with example data.

Uxopian Software helps organizations put AI to work across the systems they already run, without giving up control of their data, their infrastructure or their critical processes.