Osiris Multi-tenant RIS Manuals App Book a demo

Turn-key · Multi-tenant · Cloud

One system
from order to
signed report.

OSIRIS is a complete radiology information system that works alongside a DICOM PACS and opens studies in a zero-install browser viewer. It runs the whole study — intake, patient matching, prior authorization, scheduling, DICOM worklist, nursing, acquisition, reading, sign-off and analytics — for many organizations on one deployment, with every request scoped to the signed-in user's organization.

ViewerReconstructing 0 / 40
Hover to magnify · ↑ ↓ scroll slices

The path of a single study

One record from order to signature

Order
placed
Prior
auth
Appointment
booked
Check-in
& MWL
Nursing
clearance
Exam
acquired
Images
to PACS
Report
dictated
Final
signature
304
API endpoints
58
Application screens
8
User roles
5
Role worklists
29
Dashboard indicators
5,826
Automated tests
Workflows

Every path a study can take

One record moves between the people who work it. Authorization, nursing, cancellations, preliminary reads and addenda are not side systems — they are routes through the same record, and every hand-off is logged.

Study in motionSynthetic demonstration—

01Setup

Your whole estate,
modelled properly

An organization is the tenant root. Everything below it — sites, buildings, rooms, scanners, procedures, payers, people — belongs to exactly one organization and is invisible to the rest. Configure once, then add the second and tenth practice without touching the code.

Facility hierarchy

Location → building → floor → room, with room types you define. Every form cascades, so a room can only land somewhere that exists.

Equipment register

Scanners with manufacturer, model, serial, modality, mobile flag and DICOM AE title — the identity the machine uses on the network.

Procedure catalog

Exams defined by modality, body part, laterality, contrast and standard duration, tied to the equipment type that can perform them.

Payers

Carriers with type classification, contacts and addresses, scoped per organization and reused across coverages and authorizations.

Deactivate, not delete

Setup records, patients, coverages and orders are switched off rather than removed, and can be brought back when they are needed again.

Rules in the database

Keys, unique constraints and checks live in the database, not only in application code, so the rules they carry hold for every write.

02Patient identity

One record
per patient

Every patient gets a medical record number that OSIRIS issues itself, unique inside the organization and protected against typing errors. Demographics, contacts, coverages and flags sit on the same record, and the national ID is held encrypted.

MRNs issued, never typed

The server gives every new patient an MRN: the organization's prefix, a running number and a check digit. Nobody types or changes an MRN, and one mistyped digit is caught.

Complete demographics

Legal name with suffix, date of birth, administrative gender and sex at birth kept separately, race, ethnicity and preferred language.

Contact & next of kin

Home, mobile and work numbers, email, full address, plus a named emergency contact and relationship.

Insurance coverages

Primary and secondary policies with payer, policy and group numbers, subscriber details and effective dates that validate against each other.

Confidential and deceased flags

VIP records are marked at the source so downstream screens can treat them differently. Deceased status carries a date.

National ID, encrypted

The full number is stored encrypted, found by an exact search through a keyed hash and masked on every screen. Permitted users can reveal it on request.

03Patient matching (eMPI)

The eMPI is built in.
Nothing extra to buy.

Duplicate patient records split a patient's history and put the wrong prior study in front of the radiologist. The usual answer is a separate enterprise master patient index — another licence, another server and another interface to keep running. OSIRIS matches patients itself, on its own database, in the same step that saves the record. There is no third-party eMPI to buy, host or integrate, and no extra cost for it.

0
eMPI licences to buy
0
Extra servers to run
0
Matching interfaces to maintain

Checked before it is saved

When the front desk registers a patient, OSIRIS compares the new record with the organization's patients first. The closest matches show best first, up to five. Pick one and the existing record opens — no duplicate is made.

Edits are checked too

A change to a name, date of birth, sex or national ID runs the same check, and warns when the edited record now looks like another patient.

Scored field by field

Names are compared with Jaro-Winkler, edit distance and phonetic codes; date of birth, national ID, phone, email and address add to the score. Four search strategies find candidates even when the birth date or the spelling is wrong.

A clear line, no silent links

Every candidate gets a score from 0 to 1. At the review line — 0.70 by default — and above, a person sees the match before anything is saved; below it, the patient is new. Nothing is linked silently at the desk.

A review queue for the doubtful ones

A possible duplicate carries an amber badge and waits in the Review queue. The review puts the records side by side and marks every field that differs; the decision is Same person or Not the same person, with a reason.

Merge many into one

Up to ten records merge into one surviving record in a single transaction. Orders, coverages, allergies and identifiers move across, and every row moved is logged.

Images follow the patient

After a merge, worklist entries are sent again and studies already in the PACS are re-tagged under the surviving patient, in the background, with automatic retries and a Needs attention flag.

Every merge can be undone

The Merge log records who merged what, when and why. Unmerge moves the logged rows back and restores the merged-away record as a patient of its own.

In the right hands

Only clinic administrators review and merge. Platform administrators can read the queue and the log, and never change them.

04Workforce

People, licences
and where they work

Radiologists, technologists, nurses, referring physicians, coders and physicists are all held in one directory, each with credentials and assignments. An assignment records the clinical role a person fills, and the provider pickers across the product read it rather than asking again.

One directory, one record

Demographics, credentials and assignments in a single view, each editable in place without leaving the person's page.

Credential tracking

Licences, certifications and board certifications with issuing body and expiry. Anything expiring inside 90 days surfaces on the dashboard.

Clinical assignments

An assignment binds a person to a clinical role, optionally at one location. Which sites a person can open is set by their sign-in grants — see Access.

Role-aware pickers

Ordering, referring and reading provider fields only offer people who fit that part — no free-text names.

05Order intake

Orders that arrive
complete

The order is where a study begins, so it is where validation belongs. Accession numbers are issued automatically, the patient's active policies are offered for selection, and authorization status travels with the order from the moment it is written until the exam is performed.

Automatic accession numbers

Issued on save, unique per organization, and carried through scheduling, the modality worklist and the final report.

Clinical detail captured up front

Indication, ICD codes, priority from routine through stat, and the ordering, referring and reading providers.

Coverage in context

Selecting the patient offers their active policies, so the coverage on the order is picked from what is on file, not retyped.

A queue you can actually work

Search plus filters on organization, status, priority, modality and date range, with sorting on every column that matters.

Authorization status on the order

Kept in step with the authorization case automatically, so schedulers never have to open a second system to check.

Deactivation is controlled

An order is switched off, never erased, and only a clinic administrator can deactivate it or bring it back.

06Prior authorization

Authorization as
real case management

Most imaging centres run authorizations out of a spreadsheet and a shared inbox. OSIRIS treats each one as a case with a lifecycle, an immutable activity log, attached documents and an appeal path — and writes the outcome straight back onto the order.

A defined lifecycle

Open, in progress, resolved — with resolutions for approved, denied, withdrawn and retro-approved. Only valid transitions are offered.

"Waiting on", with a date

Payer decision, physician letter, peer-to-peer review and the other reasons on the list. A reason and a follow-up date replace a vague blocked flag.

Immutable activity log

Sixteen activity types covering calls, faxes, portal submissions, letters and decisions. Entries cannot be edited or removed once written.

Documents on the record

Denial letters, clinical notes and payer correspondence upload against the activity they belong to and stay with the case.

Appeals keep the history

An appeal reopens the same case rather than starting a new one, so the whole exchange with the payer sits in one place. Appeal count is tracked.

Urgency that sorts itself

Overdue follow-ups, items due today and exams within three days are flagged in the coordinator's worklist without anyone tagging them.

07Scheduling

A board built for
the front desk

Rooms across the top, the day down the side, unscheduled orders one tab away. Drop an order onto a slot and the booking opens already filled in. Occupied and past slots are refused while you drag, not after you save.

Drag to book

Rooms as columns, fifteen-minute rows. The board opens at the current hour so today's work is on screen immediately.

Collisions caught early

Occupied and past slots reject the drop and say why. A technologist or nurse already booked elsewhere is caught when the booking is saved.

Adjust while booking

Override the start time in five-minute steps and the duration when a case needs longer than the catalog default.

Staff on the appointment

Assign the technologist and, where the exam needs one, the nurse at the moment of booking. Both appear on the appointment card.

Cancel and no-show

Both require a reason. A cancelled appointment returns its order to the unscheduled queue.

Availability rules

Weekly patterns per resource, plus date-specific overrides for closures, holidays and extended hours. The board shows closed time, and a booking into it is refused.

08Nursing

Clinical clearance,
enforced not assumed

Nursing runs in parallel with the technologist, but with a gate: an exam requiring assessment cannot be started until nursing has cleared the patient. Allergies, vitals, screening, medications and contrast are captured in one drawer and travel forward to the reading radiologist.

Allergies

Held against the patient, not the visit. Allergen, type, reaction, severity and source, with a reference list of common allergens.

Vitals

Blood pressure, heart rate, respiratory rate, temperature, oxygen saturation, height and weight.

Screening

Pregnancy status and test result, renal function before IV contrast, IV site and gauge, consent, fall risk and isolation precautions.

Medication administration

Drug, dose, route, indication and time, recorded against the visit with the administering nurse attached.

Contrast records

Agent, dose, route, injection method, phase and rate — plus adverse reaction with severity and the treatment given.

Severe allergies stand out

A severe or life-threatening allergy shows as a red alert in the clinical summary the radiologist opens from the report editor.

09Acquisition

The scanner already
knows the patient

Worklist entries are built from the order. The scanner queries the worklist, the technologist picks the patient from the console, and demographics, accession and procedure arrive as the order has them — nothing is retyped at the scanner.

Worklist from the order

Each entry carries the patient's demographics, the accession number and the procedure exactly as they stand on the order.

Study identity

A study instance UID is generated with the worklist entry. The report editor finds the study by that UID, or by accession number when none is on file.

Technologist worklist

Day view per technologist, refreshing every thirty seconds, with single-click check in, start and complete and a colour-coded status strip.

Images in the browser

Studies open in the MedDream viewer directly from the report editor. Nothing to install on the reading workstation.

Modality simulator included

A DICOM device that queries the worklist and sends studies back, so the whole path can be exercised before a scanner is connected.

10Equipment & quality

Every scanner accounted for,
every check on record

Each unit has a responsible person, a service company under contract and a full service history. Quality checks are recorded beside the scanner, against limits you set, and a failed check reaches the people who must act — at once, with the next step one click away.

An equipment manager role

A role for the people who keep equipment running. It opens the equipment screens and no patient or order data. A small clinic can give it to its clinic administrator as well.

Service records

Repair, preventive maintenance and QA / calibration, each with a reason, an expected return, dictated notes and documents. Closing a maintenance record updates the unit's last maintenance date.

Out of service means out of service

While a record is open the unit cannot be booked or checked in. A room with no other working fixed scanner closes too. Appointments already booked are flagged for the scheduler to move, never cancelled silently.

Reported from the console

A technologist takes a failing unit out of service on the spot. The location's equipment managers, the clinic administrator and the unit's responsible person get an email at once.

Contracts and responsibility

Service companies with contacts, a primary contact, a service hotline and their documents. Each unit keeps a dated history of its contracts and of its responsible person — past, current and upcoming.

Overdue alerts

A unit not back by its expected time is flagged overdue: an email at once, then every morning at 07:00 local time while it stays down, and a dashboard tile that opens the overdue list.

Check lists you own

Start from the OSIRIS starter library — seven lists, 72 items for CT, MR, X-ray, portable X-ray, mammography and ultrasound — or build your own. Daily, weekly or monthly, per equipment type, with a layer per manufacturer and model. Every published version is kept.

The Equipment Log

Checks fall due at the times the list sets, in the location's time. Each entry takes numbers against limits, pass / fail, choices, notes and photo evidence. An entry is never edited: a correction is a new entry and the original stays readable. Numbers chart over time against their limits.

The loop after a check

A result that needs attention, or puts the unit out of service, notifies the right people at once. The save screen offers Take out of service now. An equipment manager acknowledges with the action taken, QC lists can require a second person's review, and a missed check sends a reminder.

11Reading & reporting

Read, dictate, sign

The structured report is on screen and the study opens in the viewer in one click. Templates match the modality, each section is saved as you leave it, and the signature is a deliberate act with a proper addendum path afterwards.

Structured templates

Section-based templates per modality, and a template can name a procedure. Reports are stored as structured sections, not one opaque block of text.

Real-time dictation

Speech to text in every report section, with radiology vocabulary loaded. The same dictation works on every notes field in the product.

Drafts kept by section

Each section is saved when you move on from it, so the draft is waiting when you come back to the read.

Preliminary and final

A resident's preliminary read and the attending's final signature are recorded separately, each with the person and the timestamp.

Addenda, not edits

A signed report is never rewritten. An addendum is a new document linked to the original, and both remain readable.

Nursing summary at hand

Allergies, vitals, screening, medications and contrast for the visit open in a drawer beside the report, with severe allergies flagged.

12Analytics

Twenty-nine views of
a working department

One dashboard for the clinic administrator, scoped to the organization, answering the questions a department manager asks every morning — and several they should be asking weekly.

Today at a glance

Exams completed against exams booked, orders waiting to be scheduled, unread studies in the reading backlog, open authorization cases.

Rate indicators

Completion rate, no-show rate, average report turnaround in hours and minutes, and authorization denial rate.

Throughput

Order volume trend, today's appointment status mix, and the reading pipeline from unread to signed.

Resource use

Rooms by bookings and minutes, technologists by exams completed against remaining, radiologists by preliminary against final reads.

Commercial mix

Modality mix, payer mix and authorization outcomes by payer — which carriers deny, and how often.

Demand and risk

Priority mix, top referring physicians, cancellation and no-show trend, nursing workload and patient wait times.

Equipment

Units past their expected return from service, missed checks, open check alerts and checks waiting for review. Each tile opens the list behind the number.

Credentials

Licences and certificates that expire in the next ninety days, and the credentials still waiting for verification, one click from the list.

Locked accounts

User accounts locked after repeated failed sign-ins, counted as they stand now, so nobody waits long for an unlock.

13Access control

Everyone sees
their own job

Access is enforced twice: at the API, where every endpoint declares who may call it, and in the interface, where a screen a person cannot use is not shown. Each role is granted at one location, or at every location of the organization.

Access by role and area
AreaClinic adminSchedulerFront deskTechnologistNurseRadiologistAuth coordinatorEquipment manager
Configuration, facilities & user accountsFull useNo accessNo accessNo accessNo accessNo accessNo accessNo access
Team directoryFull useNo accessNo accessNo accessNo accessNo accessNo accessNo access
Patients & coveragesFull useSome actionsSome actionsRead onlyRead onlyRead onlyRead onlyNo access
Patient matching (MPI)Full useNo accessNo accessNo accessNo accessNo accessNo accessNo access
OrdersFull useSome actionsSome actionsRead onlyRead onlyRead onlyRead onlyNo access
Schedule boardFull useSome actionsSome actionsFull useNo accessNo accessNo accessNo access
AvailabilityFull useSome actionsNo accessNo accessNo accessNo accessNo accessNo access
Technologist worklistFull useNo accessNo accessFull useNo accessNo accessNo accessNo access
Nursing worklistFull useNo accessNo accessNo accessFull useNo accessNo accessNo access
Reading & reportsFull useNo accessNo accessNo accessNo accessFull useNo accessNo access
Prior authorizationFull useNo accessNo accessNo accessNo accessNo accessFull useNo access
Equipment & service recordsFull useNo accessNo accessSome actionsNo accessNo accessNo accessFull use
Service companies & contractsFull useNo accessNo accessNo accessNo accessNo accessNo accessFull use
Check listsFull useNo accessNo accessNo accessNo accessNo accessNo accessFull use
Equipment LogFull useNo accessNo accessSome actionsNo accessNo accessNo accessFull use
DashboardFull useNo accessNo accessNo accessNo accessNo accessNo accessNo access
Full use Some actions Read only No access A super administrator spans every organization.

Session security

Signed tokens in HTTP-only cookies, with expiry and revocation. Browser script never touches the credential.

Account administration

Create an account, link it to a team member, grant roles per location and send an invitation link. The person sets their own password.

Reset closes old sessions

Resetting a password revokes that user's refresh tokens, so no old session can be renewed. One already open lapses within 30 minutes.

14Integration surface

Connects to what
you already run

Every capability in the product is a documented REST endpoint, published as an OpenAPI specification. External services are wired so the workflow keeps working before they are switched on — useful for pilots, demonstrations and staged go-lives.

Watch one study move through these systems, message by message →

Live

Modality worklist

DICOM worklist entries built from the order, so demographics, accession and procedure reach the scanner without retyping.

Live

PACS

Orthanc today. Studies are found over DICOMweb by study instance UID, or by accession number when no UID is on file.

Live

MedDream viewer

Zero-install browser image review, opened in context from the report editor.

Live

Speech to text

Real-time dictation. The vendor key stays on the server; audio streams straight from the browser.

Live

Object storage

Authorization documents and correspondence held in S3, referenced by metadata in the database.

Live

REST & OpenAPI

Every endpoint documented in a machine-readable specification for downstream teams.

Configured

Transactional email

Account invitations and password resets, delivered without blocking the request that triggered them.

Built in

Modality simulator

A DICOM device for testing acquisition end to end without occupying a real scanner.

15Security & architecture

How it is built

What an IT reviewer asks first: how organizations are kept apart, how credentials are held, how the system talks to the rest of the department, and where it runs. Each line below is read from the code and the running service, not from a plan.

Isolation & access
OrganizationsEvery request scoped to the signed-in user's organization
LocationsRoles granted per location
No matching grantNo access — the check fails closed
PasswordsStored as bcrypt hashes only
SessionsAccess tokens expire after 30 minutes
Stored tokensRefresh and password-link tokens kept as SHA-256 digests
Password resetRevokes every refresh token of the account
Data & interfaces
DatabaseRelational, one schema for every organization
QueriesValues passed as parameters, never written into the query text
Interface contractREST, published as an OpenAPI specification
Imaging standardsDICOM modality worklist · DICOMweb
ViewerZero install, in the browser
Request timingEvery request logged with its duration
Automated tests5,826: 5,012 in the server test suite and 814 in the user interface
Hosting & recovery
HostingAWS, US East (Ohio)
Internet-facingHTTPS web front end only; database, PACS and viewer have no public port
Viewer accessOpens only behind an OSIRIS sign‑in
Server loginSSH keys only, password login off
BackupsNightly, copied to a second AWS region; 14 days on the server, 30 off‑site
RestoreProven on every deploy, before any change goes live
UpdatesOperating system security updates applied automatically
Roadmap

Being built now

Listed so anyone evaluating OSIRIS can tell what runs today from what is on the way. Nothing below is claimed in the sections above; when a feature ships, it moves.

Pricing

How pricing works

The price follows the work you do: the exams you complete, not the number of people who sign in. Figures are quoted for your volume.

Sized by volume

Three tiers, set by the number of exams you complete each month.

Monthly fee

A base fee per installation, plus a fee for each completed exam.

Onboarding

A one-time fee when your installation is set up.

Book a demo

See a study go from order to signed report

A demonstration runs the full path on live software with synthetic patients: an order raised, an authorization worked, an appointment booked, the worklist reaching a scanner, the report dictated and signed. Tell us about your department and we will follow your workflow.

You
Your organization
Modalities in use
Current systems
The demo