Oriaris Core and Relay, in research and planning
The tools that will catch the gap before your claim leaves
Core will check each claim before submission and hand your coder the missing code, with the chart evidence. Relay will connect it to your hospital's systems. Both come after Academy, Nexus and Horizon.
Oriaris Core, in research
Claims intelligence
When a chart shows a complication the claim omits, the hospital is paid less. Core is being designed to catch that. Beside it is an early prototype, on synthetic cases.
- The rules decide, not a model
- Coding rules are versioned files a physician can open and check. The same claim always gets the same answer.
- A person approves every change
- Core will suggest. A licensed coder approves, edits or rejects, and nothing is ever submitted on its own.
- No patient data kept
- A claim will exist in memory only for the moment it is checked. Nothing identifying is written down.
Outbound claim
OC-0042
Primary A91
Secondary D69.6
7-year-old admitted day 5 of illness with persistent vomiting and abdominal pain. On day 6 developed profound hypotension with narrow pulse pressure of 18 mmHg and cold clammy extremities. Serial hematocrit rose 22 percent with corresponding platelet drop, consistent with plasma leakage. Managed as dengue shock syndrome with crystalloid resuscitation and colloid bolus in the PICU. Circulatory collapse resolved after 14 hours of aggressive fluid management.
Anonymize, encrypt in transit
Extract entities from free text
CURB-65, qSOFA, TIMI
26-MDC rules register
Synthetic cases only · 4 rule packs of 26 MDCs · registry version 1.0.0
Oriaris Relay, later
Integrations
Secure links between hospital, billing, laboratory and payer systems, so Core can read a claim where it lives. Relay comes last because it serves Core's hospitals first.
- Connections to the hospital information systems already in place
- Secure data exchange under each hospital's data-sharing agreement
- Workflow links between clinical, billing and payer systems
Design partners
Help shape Core, then run its first pilots
A small group of design partner hospitals will run Core's first pilots, once it is ready. This is how those pilots will run.
01
Connect
One webhook behind your existing HIS. No schema change, no migration, no new screen.
02
Watch
Run beside your current process for 90 days. We flag, your coder decides.
03
Recover
Approve the flags that are right. You keep the recovery, we take a share.
What would make us tell you not to do this
- Your claims are already clean. If a review of past claims finds almost no gap, we will say so before you have spent anything
- You have no executive sponsor. Unowned projects stall regardless of the technology
- Your system cannot send a claim to an outside address. Without that, Core will have nothing to read
Be first in line when Core is ready
Ten questions and a reply within one business day. Until Core is ready, our free guides explain the same gaps.