The composable EHR platform

One record.
Every setting.

Nineteen modules, from the ambulatory clinic to behavioral health, the hospital floor, the emergency department, hospice, assisted living, and the patient's own home. All of them reading and writing one FHIR-native record, with no interfaces between them.

Request Early Access See the nineteen modules

In active development · Every module running against the live record · Early access opening 2026

Built on
  • HL7® FHIR® R4
  • US Core · USCDI v3
  • HIPAA
  • 42 CFR Part 2
  • TEFCA-ready
  • CMS-0057-F payer APIs
19 Composable modules
1 FHIR R4 record
7 CMS eCQMs computed live
0 Interfaces between modules

The problem

Your patient moves.
Your record doesn't.

A patient leaves the clinic for the emergency department, goes upstairs to a bed, comes home with monitoring, and eventually into hospice. In most organizations that is four systems, three interface engines, and a reconciliation problem nobody owns. The seams between systems are where care falls through, and every vendor's answer is to sell you another integration.

OmniEHR's answer is that there is nothing to integrate. Nineteen modules share one FHIR R4 record through OmniCore. Nothing is synced, mapped, or reconciled, because nothing is separate. Adding a care setting is a configuration change, not an implementation project.

What is actually running

Specifics, not a roadmap deck.

OmniEHR is pre-certification and pre-pilot, and we will not pretend otherwise. What we will do is tell you exactly what the system does today, in enough detail that you can check it.

  • Quality measurement

    Seven CMS eCQMs, computed live

    CMS165v11, CMS122v11, CMS130v11, CMS125v11, CMS138v11, CMS147v12 and heart-failure weight monitoring, calculated from the record with the full population flow: initial population, denominator, exclusions, numerator, exceptions. Care gaps drill down to the patient. Certified CQL and QRDA submission needs ONC-certified tooling and full VSAC value sets, which is a roadmap item, not a claim.

  • Behavioral health

    42 CFR Part 2 in the data layer

    Segment-level consent evaluated on every read, with audited break-glass and revocation, on the same record as primary care rather than in a walled-off chart. Nine screening instruments including C-SSRS, PHQ-9, GAD-7, AUDIT-C, CRAFFT, DAST-10 and Vanderbilt are built into the workflow.

  • Hospice

    HOPE, end to end

    Election statements, certification of terminal illness, face-to-face encounters, recertification, notices of election, interdisciplinary group documentation, ESAS, CAHPS and bereavement planning, with HOPE assessment validation, fixed-width export and submission.

  • Medication safety

    PDMP gaps and DEA audit

    Controlled-substance gap enforcement that can require a PDMP check before a prescription proceeds, prescriber flagging, a DEA audit export, formulary checking and medication administration recording.

  • Emergency

    From EMS call to disposition

    Pre-arrival EMS intake, ESI triage with a quick path, zone assignment and capacity, live zone telemetry, provider assignment, protocol ordering, disposition and a structured shift handoff.

  • Governance

    An audit trail that already exists

    Every chart open and every clinical write recorded to FHIR AuditEvent before the first pilot. Chart-level locking with request, grant, deny and audited takeover so two clinicians never silently overwrite each other.

Every module in the clinical application carries its own status label, working, Release 2, or Release 3, visible to the people using it. The system tells you what it is. So do we.

All nineteen modules in depth

Why OmniEHR

Four decisions made at the beginning.

Architecture is the set of choices you cannot retrofit later. These are ours.

  1. 01

    FHIR at write, not as an export

    Most systems store data their own way and translate to FHIR when someone asks. OmniEHR writes the standard from the first keystroke, so exchange, quality measurement, and AI all operate on the real record rather than a copy of it. That is why the eCQMs are computed live instead of assembled in a reporting run.

  2. 02

    Behavioral health as a first-class citizen

    Part 2 consent is enforced where the data lives, segment by segment, on every read, rather than policed by the goodwill of each application screen. Psychiatric and general clinical care share one record without either one leaking into the other.

  3. 03

    Ambient intelligence, human-gated

    Ambient documentation drafts the note while the visit happens and routes it to review and attested signature. Agentic workers chase claims and route tasks. Every AI action is attributed and audit-logged, and nothing enters the legal record without a clinician's sign-off.

  4. 04

    The whole span, or it does not count

    Ambulatory, behavioral health, inpatient, emergency, pharmacy, hospice, assisted living and hospital-at-home are modules on one record, not products in a portfolio. Transitions of care stop being transfers of risk when there is nothing to transfer.

The platform

Nineteen components.
One core. Zero interfaces between them.

Traditional health IT bolts systems together and calls the seams integration. OmniEHR is composed: every module reads and writes the same FHIR-native record through OmniCore.

OmniCore Platform foundation

FHIR-native data core, identity, consent, and event backbone every module shares.

Deploy the modules your organization needs. The rest attach to a record that is already there.

The road

Three releases. One destination.

OmniEHR ships in deliberate stages, each one a complete platform, each one widening the circle of settings the record can follow a patient into.

R1

Foundation & Ambulatory

The FHIR-native core, plus everything an outpatient or behavioral health practice needs to run: charting, scheduling, billing, engagement, interoperability, and security.

  • OmniCore
  • OmniCare
  • OmniMind
  • OmniFlow
  • OmniBill
  • OmniLink
  • OmniReach
  • OmniGuard
R2

Hospital & Intelligence

Inpatient and emergency care on the same record, ambient AI documentation, controlled-substance prescribing, remote monitoring, language access, and public health reporting.

  • OmniHospital
  • OmniED
  • OmniRx
  • OmniScribe
  • OmniSense
  • OmniInterpret
R3

Every Setting

Electronic prior authorization, hospital-at-home, hospice and palliative care, and value-based care analytics, the record follows the patient everywhere care happens.

  • OmniAuth
  • OmniHome
  • OmniHospice
  • OmniLiving
  • OmniValue

Early access

Be first on the record.

We are partnering with a small group of practices, health systems, and investors ahead of launch. Founding customers help decide what hardens first and keep their rate through the early-access window.

  • A working system to evaluate, not a slide deck
  • A direct line to the people building it
  • $249 per provider per month, all-inclusive, locked for your first three months

Questions

Asked, answered.

Is OmniEHR available today?

Not as a generally available product. The platform is built and running: nineteen modules operate against a live FHIR R4 record store, with synthetic data, in a development environment. The early access program opens in 2026, and joining the list puts you in line for it and shapes what hardens first.

Is OmniEHR ONC-certified?

Not yet, and we will not imply otherwise. ONC Health IT certification is a funded milestone on the roadmap, planned and budgeted as part of the development program. Where certification affects a capability, we say so on the page describing it, as with certified eCQM submission.

What does composable actually mean here?

Every module reads and writes the same FHIR-native record through OmniCore. There are no interfaces between modules because there is nothing between them. Adding a care setting later is a licensing and configuration change, not a data migration, because the record it needs already exists.

How does the AI handle clinical responsibility?

Every AI action is human-gated. Ambient drafts are reviewed and signed with attestation, agentic workflows are attributed and audit-logged, and nothing enters the legal record without a clinician's sign-off. The AI does the typing; clinicians stay the authors.

Can OmniEHR exchange data with the systems we already use?

That is OmniLink's job: a live FHIR R4 API with a published capability statement, TEFCA-ready exchange on US Core and USCDI v3, HL7v2 interfaces for labs and devices, and CMS-0057-F payer APIs. Exchange is inspectable in the product rather than asserted in a brochure.

Who is building this?

NorCemic Inc., a health technology company in Phoenix, Arizona, also the maker of SmartCemic health monitoring and PIIRATE privacy protection. Meet the company →

Are you a patient?

View your appointments, medications, allergies, and health issues in the secure OmniEHR patient portal.

Patient portal

One record. Every setting.
Come see it work.

Nineteen modules on one FHIR-native record, at $249 per provider all-inclusive. Tell us your settings and your team, and we will show you the system rather than describe it.

Request Early Access Talk to the team