Private outpatient care
Clinics, medical centers and independent physicians; non-admitted patients.
Healthcare operating platformCUBE OneCare
The deepest product asset in the CUBE portfolio.
CUBE OneCare combines modular clinical and administrative software with AI, communications and payments. A governed creator and provider-commerce ecosystem is a future, gated product direction—not a live marketplace today.
What “outpatient” meansNow Next Later
A focused first setting—not a maturity discount.
Management view: OneCare may be as advanced as—or more advanced than—Atlas. This is a qualitative management assessment, not an independently benchmarked comparison. The first setting avoids inpatient complexity while CUBE proves implementation, workflow value and economics. Hospitalization, Emergency Department, oncology and other complex institutional depth follow by separate clinical, contract, BAA and operational gates.
Institutional modules
Departmental implementation, advanced revenue cycle and deeper integrations.
Complex-care depth
Hospital, inpatient, ED, oncology and enterprise programs only after their control gates.
Economic layersInstitutional Consumption Future · gated
License the institution. Meter usage. Grow a governed ecosystem.
Licenses + implementation
Enterprise and practice software, onboarding, workflow configuration and service.
AI + communications + payments
Usage-based intelligence, APIs, communications and net payment economics. Includes CUBE API (dev.cubeonecare.com) for healthcare SaaS, OpenAPI 3.1 and FHIR R4 integrations. One API for other platforms to reach what OneCare centralizes, with consent and the right agreements (planned).
Modules + formulas + commerce
Clinicians will create modules without code and, later, share or sell them to other providers through a curated exchange, with CUBE taking a platform fee. Planned and gated by clinical-safety, privacy, IP, payout and moderation controls.
Claims boundary: the ecosystem is a product direction with implemented foundations at different levels—not an existing open marketplace, active third-party supply, creator sales, payouts, creator-economy revenue or proof of Epic parity. Clinical efficacy, certifications and hospital readiness are never implied without evidence.
Strategic R&D · inside CUBE OneCareFoundation Endpoint Trust Interoperability Fleet Exchange
CUBE OneCare OS: a trusted healthcare edge layer.
A healthcare-native, Linux-based operating environment, explored as long-term R&D, outside current valuation; the dedicated Linux image is not built and not deployed.
Proven enterprise LTS Linux
Use a maintained upstream distribution and security ecosystem rather than creating a custom kernel.
Resilient edge environment
Encrypted state, transactional updates and rollback are target controls, subject to validation.
Identity + policy + audit
OneCare identity, tenant policy, workload isolation, evidence and bounded clinical-continuity modes.
Standards-first coexistence
Progressively validate FHIR, SMART, DICOM, HL7 and IHE profiles instead of promising universal compatibility.
Hardware and workload control
Publish a tested x86-64 and ARM64 matrix; govern AI, application and device workloads by site and risk.
Curated module distribution
CUBE Assembly is designed to verify modules before they reach the OneCare exchange (planned).
Entry and economics boundary: the first credible step is a bounded ambulatory edge gateway or managed workstation for non-life-critical workflows. Managed endpoints, enterprise support, fleet security, edge AI, device bridges and signed distribution are future business-model hypotheses—not current revenue, ARR, TAM, valuation or first-round launch commitments.
Competitive realitySecurity operations Clinical continuity AI + devices
Coexist with incumbent systems. Earn compatibility.
Epic describes Hyperdrive as a web-based client, while its official documentation also identifies Windows-native plugin infrastructure and integrations that retain Windows dependencies. That mixed environment does not support characterizing Epic as limited to a single client OS. OneCare OS is planned to interoperate through standards-based interfaces and to retain approved remote Windows sessions where a native dependency remains necessary.
Smaller endpoint blast radius
Immutable images, segmentation, inventory and controlled updates can simplify fleet governance, but no system eliminates cyber risk.
Bounded local operation
Design for safe degraded workflows and recoverable updates; every clinical mode requires scenario-based verification.
Governed edge execution
Constrain resource access, provenance and deployment of AI and integration workloads closer to care delivery.
Approved positioning: strategic optionality inside OneCare, built on existing Linux primitives and healthcare standards. It is not a seventh product, an incumbent replacement, a certification claim or a promise of complete compatibility. Primary references: Epic Hyperdrive, HHS Healthcare Cybersecurity Performance Goals, NIST Zero Trust Architecture, NIST Medical Device Interoperability and HL7 SMART App Launch.