About Solutions Your data Your connections How it works Fractional Services Innovation Lab Insights Contact Client Login Start a Conversation
← Back

Everything runs on one connection.

It runs inside the tools you already use. Nothing new to log into.

Member EcosystemMember EcosystemConsentCare planReports to plan, TPA,reinsurerCare NetworkCare NetworkYour practice (DPC)Partner programs: Rx,surgery, imagingClaim coding (PHI)FHIR EngineFHIR EngineReceive: fax, document, 271Convert: FHIR R4Validate and record: audit logYour Team's ViewYour Team's ViewInboxWorklistExceptions and auditrecordDelivery PathsDelivery PathsFHIR gatewayProvider APIPayer API
  1. FHIR Engine
  2. Your Team's View
  3. Delivery Paths
  4. Care Network
  5. Member Ecosystem
Stack layers01Member ecosystem02Care network03FHIR engine04Administrative portal05Delivery paths
1

How we keep it safe.

First, you decide whether your data moves and how. We can work with your data and keep it in your office. If you choose to send it to us, it travels encrypted, is stored encrypted, and is kept apart from everyone else’s. No transfer is ever risk-free, so we reduce it: we have designed our protocols to minimize the opportunity by isolating the data. An air-gapped option is available, and it is encrypted as well, so PHI is limited to only the people working with the data.

We execute Business Associate Agreements (BAAs) with all Covered Entities and Business Associates.

Every action leaves a record in our audit log, kept at least six years. It is ours, not a screen your staff use, but if a question comes up, such as a request you say never arrived, we can show you the entries for your practice.

How the safety works

Where your data goes, and who can see it.

YOUR OFFICE Air-gapped analysis No outside connection. Run by us on site, or run for you. Results stay here. Your records Stay put, or go out encrypted Your staff See only your practice EncryptedSFTP Okta singlesign-on ORION ON AWS Another practicekept apart Another practicekept apart Your practice Your data, in its own lane. Other practices cannot reach it. Your staff see only this lane. Encrypted in transit and at rest. Audit recordEvery action: who, what, when. Kept 6+ years. Out To payers, providersand partners, undera BAA Every send is on the record

Two ways in, your choice: keep the work in your office, or send the data encrypted. Either way, each practice stays in its own lane, and every action is on the record.

2

How we handle your data.

Plain answers to the questions a compliance officer asks first.

What we doWhere it is documented
Who can see it?Each practice’s data is kept apart from every other practice’s. Your staff see only your practice.Separate lane per practice; single sign-on
Access is limited to what each person’s role needs, and reviewed at least quarterly. Administrative access requires multi-factor sign-in.Information Security Policy
How does it move?Encrypted in transit. Encrypted file transfer, or keep the work in your office. An air-gapped option is available, and it is encrypted too.The diagram above
Data goes only where you send it, under a Business Associate Agreement. PHI is never sent as a plain email attachment.BAA
How is it kept?Encrypted at rest. Backups are encrypted and stored apart from production.Business Continuity and Recovery Plan
Our own testing and demonstrations use made-up data.Information Security Policy
What is on the record?Every login, view, change, send and administrative action: who, what, when. Entries cannot be edited or removed, and are kept at least six years. We review the log at least quarterly, and can show you the entries for your practice if a question comes up.The audit log, above
Who else touches it?We execute Business Associate Agreements with all Covered Entities and Business Associates. Every vendor that could touch PHI is listed and reviewed at least annually.Subprocessor list
If something goes wrongStaff report a suspected incident within 24 hours. We assess it against the HIPAA breach standard and notify as the law and your agreement require. The audit record is preserved for the investigation. The plan is tested at least annually.Incident Response Plan
Your practiceOrionVendors that touch PHIBAABAA

Written policies: Information Security · Incident Response · Business Continuity and Recovery · Vendor Management · PHI Access Audit · Acceptable Use · Privacy

3

What it works with.

EHR connections that speak FHIR. Eligibility checks through the Medicare system for fee-for-service, and payer by payer for everyone else (some payer-specific exceptions). Provider and payer connections, including the prior authorization connections CMS requires by January 1, 2027. And when none of that is available, fax and files.

PROVIDER TENANT WALLMEMBER CONSENT WALLPAYER / PLAN WALL COMES IN GOES OUT Fax and PDFRead, and what matters pulled in Web uploadA secure link for your team Files and spreadsheetsLoaded as they are EHR connectionSystems that speak FHIR FHIR conversion engine One place where everything isconverted, checked and written down. Intake Convert to FHIR R4 Output: validated, logged Routing Picks the shortestcompliant path foreach destination Any FHIR gatewayProvider or ACOPayer or plan Standards-basedDirect APIPrior authorizationand provider APIs No single path is a dependency. ACROSS ALL OF IT Your team's viewEvery request in one queue, with one status each. Tenant and sign-onOkta single sign-on. Each party sees only its own.
Full architectureEvery container, wall and path on one page. Click to enlarge.
Underneath

Questions about how we handle your data?

Tell us what your compliance team needs to see, and we will walk through it with you.

Start a Conversation