Skip to content
IMECore

Referral intake

Turn the referral email into a case without retyping it

Forward the email. IMECore reads the referral, pulls the fields, and holds them for a person to approve.

The problem

The referral lives in someone's inbox

A referral arrives as a long email with a covering letter and a claim number buried in paragraph three. Someone copies it into a spreadsheet, asks by email what the questions are, and waits. The file does not exist until that person has time.

  • You retype name, date of birth, and claim number from the same email twice.
  • The instructing questions hide in the letter and get missed.
  • Two staff open the same referral and create two files.
  • The due date is a phrase like next Friday, not a date.
  • You learn about a follow-up the day after you started the wrong task.

What changes

What IMECore does about it

  • One inbox to forward to

    Send the referral to your intake address. IMECore ingests the message, the attachments, and the thread, and opens a draft case.

  • Fields pulled out, not guessed at

    IMECore reads the body and the covering letter for claimant name, referrer, payer, claim number, exam type, questions, and due date. You see what it found beside the original.

  • A person accepts the case

    The draft sits at needs review until a named coordinator checks the fields, corrects what is wrong, and approves. Nothing is created without that approval.

  • The thread stays on the case

    Every email in the conversation attaches to the case in order. The full thread is visible on the case, not scattered across mailboxes.

  • Duplicate files flagged early

    IMECore matches by claim number and date of birth and surfaces possible duplicates. It suggests a link, it never merges. A person decides.

  • PHI stays in region

    Extraction runs on models pinned to Canadian regions for PHI. IMECore checks residency before the call, and logs who approved what and when.

How it runs

Four steps, start to finish

  1. 1

    Forward the referral

    Send the email to your intake address. Attachments go to Canadian storage and are queued for the next steps.

  2. 2

    Check the draft

    Open the draft. Compare the extracted fields with the original. Fix anything that is off.

  3. 3

    Approve or reject

    Accept the case to move it to open, or reject it with a reason. The audit log records who acted.

  4. 4

    Follow the thread

    Later emails on the same conversation attach to the same case. New fields are flagged for review, not written silently.

FAQ

Questions people ask

Does IMECore decide whether a referral is valid?

No. IMECore extracts what it reads and marks whether it thinks the message is a referral. A person reviews the draft and accepts or rejects the case.

What if the extraction is wrong?

You correct it in the draft. The case is not created until you approve. If you reject the draft, no case is created.

What replaces manual entry?

Forwarding the email and checking the draft. You no longer retype claimant name, date of birth, claim number, or questions from the covering letter.

Can two staff create the same file twice?

IMECore deduplicates on the source message id and surfaces possible claimant matches by claim number and date of birth. It proposes a link for a person to confirm or dismiss.

Where does the data sit?

In Canada, on Cloudflare with Canadian residency for case data, and on model providers pinned to Canada for PHI. Every approval is logged with a person and a time.

See it against one of your own files

Bring a case that keeps getting passed around. We will run it through IMECore on the call.