IRIS8 Talk to us

Healthcare

Keep patient data inside your environment

For informatics, revenue cycle and IT leaders: a model for administrative paperwork, trained on your own documents and run in your VPC or on-prem by IRIS8.

How it fits

Where the model sits beside your EHR

It prepares the paperwork from the chart, and your staff review it before anything is sent.

Sample workflow · prior-authorization packsSample workflow
Frontier modelOptionalOff by default for patient data
Yours

Your VPC or data centre

Your people

Clinical staffReview and send
Informatics leadSets the pass mark, approves each version

Your systems

EHR
Revenue cycle system
Document and fax intake
Patient messaging portal
Payer forms and rules library

Added by IRIS8

GatewayMasks, routes and logs
Your modelTuned on your note types and forms

IRIS8 engineerScoped, logged access

Your records

Request logEvery request and response
Model recordData, training runs, scores, approvals
Benchmark reportYour cases, your pass mark

Use cases

Where health systems start

Each of these is administrative work where a pilot can begin.

  • Prior-authorization packs
  • Clinical note summaries
  • Coding and documentation support
  • Patient message triage
  • Referral processing
  • Denials and appeals drafts
  • Policy and formulary questions
View all healthcare use cases
Prior-authorization packsSample data
  1. 01

    Chart notes in

  2. 02

    Request form filled

  3. 03

    Lab result missing, flagged

  4. 04

    Sent to staff for review

For your reviewers

What privacy and security will ask

These are the questions we are asked first, with the answers we give.

  1. 01

    Does the model make clinical or coverage decisions?

    No. It prepares administrative paperwork: forms, summaries, drafts. A member of your staff reviews every output before it is used.

  2. 02

    Where is patient data processed?

    In your VPC, or on-prem as a scoped data-centre install. Notes, claims and messages stay in your environment.

  3. 03

    Does patient data go to a frontier model?

    Only if you set a rule that allows it. The gateway controls every route and logs each one.

  4. 04

    Who at IRIS8 can reach our environment?

    Named engineers with scoped, task-bound access. Every action they take is written to a record you hold.

  5. 05

    Will you sign the agreements our privacy office requires?

    Tell us what your privacy office requires and we will go through it on the first call.

YoursVPC / On-prem, scoped install
EHRYour model

Patient data stays inside this line

Take this with you

Is this workflow ready for a pilot?

Seven checks for an administrative workflow. Five or more ticks is a good candidate.

IRIS8 · Healthcare1 page

Is this workflow ready for a pilot?

  • It is administrative, not a clinical decision
  • Staff do it many times a day
  • A skilled person would agree on the right output
  • You have past examples of the work done well
  • One named person reviews the output today
  • One number would show it works
  • The documents already sit in systems you control

iris8.ai/healthcare.html

Questions

Questions

Talk to us
Q1Which workflow should we start with?

One administrative task with high volume and a named reviewer, such as prior-authorization packs or denial appeals.

Q2Does the model write into the EHR?

In a pilot the model returns its output to your staff for review. Writing back to the EHR is scoped with your IT team.

Q3Do we need our own ML team?

No. Your informatics leaders set the pass mark and review sample outputs. IRIS8 does the rest.

Q4Can it run with no connection to the internet?

Yes, as a scoped on-prem install.

Q5How is the pilot priced?

Fixed price, one use case, credited to year one.

Next step

Bring one administrative workflow