Platform Overview

One platform. Four modules.Every level of care.

eLife is a single, interoperable health platform spanning the entire care continuum. From the individual patient with a QR wristband to the health system running population risk models, every module shares one data layer, one security boundary, and one integration surface.

  • HIPAA
  • HL7 v2
  • FHIR R4
  • SOC 2 Type II

Platform Architecture

How the modules connect

Each module is independently deployable but shares a unified patient identity layer, so data entered at any touchpoint is immediately available at every other.

01eLife Summary

Emergency health profiles, always accessible.

Every patient carries their complete medical identity via NFC wristband and QR code. When seconds matter, emergency responders scan and see allergies, active medications, diagnoses, and advance directives before they reach the hospital. No login required on the responder side — read access is public-key authenticated and time-bound.

Allergy and medication list, updated in real time
Emergency contacts and designated healthcare proxy
Advance directives and DNR status
NFC wristband + QR for dual-mode access
Offline read mode — no network required
Owner-controlled sharing with full audit trail

Individual subscription — consumer tier

Technical specification
Profile delivery< 0.4 s via QR scan
Wristband formatNFC + QR, ISO 15693
Data fieldsAllergies, meds, dx, contacts, directives
Access controlOwner-permissioned, time-bound tokens
Offline modeCached profile, no network required
ComplianceHIPAA Privacy Rule §164.524

02eLife Clinical

Patient context at the point of care.

Before the patient is called back, the provider has a full summary: current medications, recent labs, imaging history, allergies, and the last three chief complaints. Clinical pulls from the patient’s eLife Summary and any connected EHR, presenting a unified view with no extra intake forms. The result is fewer medication errors and faster time to treatment.

Appointment-ready patient snapshots
FHIR R4 pull from connected EHRs
Drug-drug and drug-allergy conflict detection
SAML 2.0 and OAuth 2.0 PKCE single sign-on
Role-based access: physician, NP, MA, front desk
Immutable audit log with 6-year HIPAA retention

Per seat per month — practice tier

Technical specification
Dashboard latency< 200 ms p95
EHR pullFHIR R4 Patient/$everything
Intake reduction~80% fewer manual fields
Session authSAML 2.0 / OAuth 2.0 PKCE
Audit logImmutable, tamper-evident, 6-year retention
ComplianceHIPAA Security Rule §164.312

03eLife Insight

Population analytics at health-system scale.

Insight aggregates de-identified data across the full patient population to surface risk stratification, readmission probability, and outcome trends. Clinical leadership can run ad hoc cohort queries against 10M+ patient-lives in under three seconds. Risk models for readmission (LACE+), sepsis (NEWS2), and falls ship out of the box — plus a model builder for custom protocols.

LACE+ readmission risk, NEWS2 sepsis, and falls models
Near-real-time data refresh (15-minute lag max)
Cohort builder — no SQL required
FHIR Bulk export and Parquet for data warehouse load
CMS quality measure reporting automation
De-identification per HIPAA Safe Harbor §164.514(b)

Enterprise license — per facility or IDN

Technical specification
Cohort sizeUp to 10M patient-lives per query
Query latency< 3 s for 95th pct risk model
Risk modelsReadmission (LACE+), sepsis (NEWS2), falls
Data freshnessNear-real-time, 15-min lag max
Export formatsHL7 FHIR Bulk, CSV, Parquet
ComplianceHIPAA de-identification §164.514(b)

04eLife Connect

HL7 v2, FHIR R4, and bi-directional sync.

Connect is the interoperability backbone for the entire platform. It speaks native HL7 v2 (ADT, ORM, ORU, MDM) for legacy hospital interfaces and SMART on FHIR for modern EHR app frameworks. Certified connectors for Epic and Cerner ship with the platform. All sync is bi-directional and event-driven — when a patient’s medication changes in the EHR, every module sees it within seconds.

HL7 v2.5.1 and v2.8 — ADT, ORM, ORU, MDM message types
FHIR R4 (4.0.1) with SMART on FHIR app authorization
Certified Epic and Cerner connectors in-box
Oracle Health, Meditech, Allscripts in connector library
Bi-directional, event-driven — sub-5-second propagation
99.95% uptime SLA on integration endpoints

Bundled with Clinical and Insight — standalone available

Technical specification
HL7 versionv2.5.1, v2.8, ADT/ORM/ORU/MDM
FHIRR4 (4.0.1), SMART on FHIR
Certified EHRsEpic, Cerner, Oracle Health, Meditech
Sync modeBi-directional, event-driven webhooks
Uptime SLA99.95% at integration endpoint
Compliance21st Century Cures Act info blocking

Compliance

Built to clear healthcare procurement

Every control below is in place today and evidenced in the security packet available to qualified prospects.

Privacy & Security
HIPAA Compliant
Annual third-party audit against HIPAA Security Rule and Privacy Rule. BAA available on all tiers. PHI access is logged, time-bound, and role-scoped.
Trust & Availability
SOC 2 Type II
SOC 2 Type II certification across Security, Availability, and Confidentiality criteria. Reports available under NDA to qualified prospects.
Health Interoperability
HL7 v2 Native
Native HL7 v2.5.1 and v2.8 — ADT, ORM, ORU, MDM message types. Certified integration with major hospital information systems and lab networks.
Modern Standards
FHIR R4 + SMART
Full FHIR R4 (4.0.1) implementation with SMART on FHIR authorization. 21st Century Cures Act information blocking compliance built into every endpoint.
  • HIPAA Privacy Rule
  • HIPAA Security Rule
  • SOC 2 Type II
  • 21st Century Cures Act
  • CMS Interoperability Rule
  • NIST SP 800-53
  • ONC Certified HIT

Ready to deploy?

See the full platform on your own data

Implementation takes days, not months. The existing Emory Healthcare deployment is available as a reference.