Full architecture

← Back
C4 — container view
How the pieces fit together
Two independent sides meeting at one boundary. Every transfer in either direction crosses the FHIR conversion engine — nothing moves around it.
Proprietary & Confidential — Orion Health Partners, LLC
Care network container
FHIR enablement container
FHIR engine
Person
External — outside Orion
Trust boundary (visibility wall)
Care network member & care
Member consent wall
Care-delivery wall · clinical data, minimum necessary
Employer Health Plan
[External system]
Sponsors coverage · consumes risk insight
Member
[Person]
Owns consent · requests and receives care
DPC Wellness Gateway
[Container: mobile + wearable]
Telemetry → FHIR Observation
DPC Providers
[Container: clinical app]
Encounters, orders, referrals into the care network
Medical Care Plan
[Container: care service]
CarePlan, Goal, longitudinal member record
Claim Coding / Analytics
[Container: data service]
Codes encounters · reference-price comparison
Specialty Rx
[Vendor service]
MedicationRequest handoff
Outpatient Surgery & Imaging
[Vendor service]
Bundled ServiceRequest
Regional Medical Tourism
[Vendor service]
Episode of care at a regional partner facility
Dividing line
FHIR Conversion Engine
[Container · “FHIR Magic”]
AI fax / document → FHIR R4 US Core. OCR-backed, conversion at the point of ingestion — no intermediary hop.
Bundle validation · audit log
Every data transfer between the two products, in either direction, crosses here.
FHIR enablement administrative portal
Provider tenant wall
Payer / plan wall · tenant-scoped
Intake Channels
[Container: web + fax]
Hosted submission link, upload, inbound fax
Request Inventory
[Container: portal app]
Prior auth, referral, records — one queue, one status
Bundle Validation
[Container: service]
Conformance check before anything leaves
Tenant & Identity
[Container: multi-tenant, SSO]
Scopes what each party can see of another
External Providers
[Person: practice staff]
Independent / rural practices, fax-first
Routing & Delivery
[Container: router]
Picks the shortest compliant path per destination
01
Universal FHIR Gateway
[External · illustrative]
Aggregation into any standards-compliant gateway
02
Direct API — ACO / Provider
[External system]
Point-to-point, mapped to a specialized API
03
Payer / Plan API
[External system]
CMS-0057-F prior auth & provider APIs
Reading the split
The two sides share no database, no session, and no direct call path. The FHIR conversion engine on the split line is the only contract between them — a change, outage, or integration on one side does not touch the other, so your team only ever needs to integrate against the boundary that's relevant to you.
Trust boundaries
Grey blocks are parties outside Orion; everything coloured is Orion-built. Dashed walls mark what one party can see of another: consent gates the member record, the care-delivery wall passes minimum-necessary clinical data to vendors, and the tenant wall keeps every provider’s inventory scoped to itself.
Three outputs
Delivery supports three interchangeable paths — universal FHIR gateway, direct ACO/provider API, or payer/plan API — so integration can match whichever standard your systems already speak. None is a dependency: if one path changes or goes away, the others are unaffected.