The Clinical Cortex Clip

Clinical intelligence that moves with care.

Cortex Clip is a development-stage AI wearable for clinical documentation. Worn on scrubs, it captures selected clinical encounters or voice notes. Speech is processed locally on the wearable. The dock then transfers reviewable information to the local review application.

Request a Pilot →See the Workflow
On-device processingLocal-first architectureDocked transferClinician review
Blue-and-white sketch close-up of Cortex Clip attached to a clinician's scrubs in a hospital
Clinical Cortex ClipSee the wearable first.A closer product view shows how Cortex Clip is worn during the clinical day.
Wearable by designMade to stay with the clinician.
Local intelligenceRuns core processing on the device.
Controlled data pathMoves retained information through the dock.
Built to validateStart small. Measure results. Expand carefully.
The Cortex Clip workflow

One wearable. Five clear steps from encounter to review.

The clinician workflow stays simple: wear, capture, dock, then review. Cortex Clip handles the processing in between. The technology stays in the background.

Blue clinical sketch of a clinician wearing Cortex Clip during a bedside patient interaction
Bedside captureStay focused on the patient.Capture context without turning the encounter into a screen-first interaction.
01
WearAttach Cortex Clip to scrubs and keep it available throughout the shift.
02
CapturePress REC when you choose to capture an encounter or focused voice note.
03
Process locallyOn-device intelligence turns captured speech into organized clinical context.
04
DockPlace Cortex Clip in its dock to charge. The dock then transfers retained information to the local review application.
05
ReviewReview the transcript and documentation draft. Refine both as needed before using them in the clinical record.
TranscriptA reviewable record of captured speech.
Organized clinical contextRelevant details structured around the encounter.
Documentation draftA structured draft for clinician review and refinement.
Local AI & privacy

Keep sensitive processing close to the point of care.

Cortex Clip is being built around a local-first architecture. The wearable performs primary speech processing on the device. The dock provides a controlled path to the local review application.

EncounterClinician-selected capture at the point of care.
Cortex ClipLocal speech processing and encounter organization.
Cortex DockCharging and controlled local transfer.
Local reviewClinician review, correction, copying, or export of approved information.
Blue sketch of Cortex Clip being placed into its dock beside a local workstation
Controlled transferDock to move from capture to review.The dock connects the wearable to the local review environment.

Privacy by design

The goal is to reduce reliance on continuous cloud connectivity. Sensitive processing stays closer to the point of care.

The wearable does not depend on Wi‑Fi or BluetoothCapture and primary processing are being designed to work without a continuous wireless connection.
Local speech processingSpeech processing and encounter organization are designed to run on the wearable.
Encrypted retained informationRetained transcript and encounter information are intended to remain encrypted.
Docked handoff to reviewThe dock is designed to provide a controlled path from the wearable to the local review application.
Development-stage privacy architectureAudio is intended to be processed locally and then deleted. The encrypted information needed for clinician review is retained. Final behavior remains subject to implementation and validation.
Purpose-built hardware

Simple hardware for a full clinical shift.

The hardware has four core goals: capture clearly, process locally, protect retained information, and dock reliably. Each design choice is being evaluated against the realities of a clinical shift.

Blue-and-white product sketch showing Cortex Clip from the front, side profile with clip, and seated in its dock
Hardware systemCortex Clip + Cortex Dock.Front, side, and docked views show the complete physical system.
Small wearable form factorDesigned to attach securely to scrubs without adding another handheld device.
Simple physical controlsREC, clear status indicators, and simple privacy controls.
MCU-based edge AIDigital microphones, constrained-device processing, and encrypted local storage.
Full-shift directionThe design targets an 8–12-hour clinical workday, followed by dock-based charging and transfer.

Dimensions, battery life, controls, performance, and manufacturing targets remain development-stage specifications. Prototype and clinical validation are still required.

Cortex Clip pilot

Start with one workflow. Learn from real use.

A pilot should answer practical questions first. We want to understand usability, workflow fit, review burden, and time impact before considering broader deployment.

Blue sketch of a small clinical team around a table being introduced to Cortex Clip devices and docks
Pilot deploymentTest the workflow with a real clinical team.Start with a small team. Support the workflow closely, then measure what changes.
01 · Define

Choose the workflow

Choose the clinical team, care setting, and documentation use case to evaluate.

02 · Deploy

Introduce Cortex Clip

Set up the devices and docks. Define training, review, and the approved operating process.

03 · Measure

Evaluate what changes

Track usability, adoption, review burden, workflow fit, and documentation time.

04 · Learn

Decide the next step

Use the findings to improve the product. Then decide whether broader deployment is warranted.

Usability
Workflow fit
Review burden
Time impact
Enterprise scale

Start focused. Scale with control.

The enterprise path begins with a validated clinical workflow. As deployment grows, the enterprise layer can add administration, governance, and support. Those capabilities can extend from a department to a facility, then across a multi-site health system.

Blue-and-white sketch of a hospital operations area with multiple Cortex Clips in docks, clinicians wearing the device, and an administrator at a fleet dashboard
Enterprise deploymentFrom a focused pilot to a managed clinical fleet.Scale should add operational control around the same simple clinician experience.
01

Pilot

One team. One workflow. Clear measures.

Validate
02

Department

Standardize onboarding and device assignment across a larger clinical team.

Repeat
03

Facility

Add fleet operations, support, training, and governance.

Operate
04

Health system

Build toward multi-site administration, reporting, identity, and integrations.

Scale

Role-based administration

Define responsibilities for clinicians, department leaders, IT, and security teams.

Fleet operations

Design for provisioning, assignment, inventory, lifecycle management, and support.

Governance + audit

Provide visibility into access, transfer, policy enforcement, and review activity. Give administrators the controls needed to manage those activities.

Adoption measurement

Track utilization, correction burden, workflow fit, and time impact as deployment expands.

Desktop review

Keep the clinician in control of the final output.

Cortex Clip captures information and organizes it for review. The clinician decides what is ready to use.

  • Review transcript and organized context
  • Correct or refine the output
  • Copy or export through an approved local process
Blue sketch of a clinician docking Cortex Clip at a desktop workstation for local review
Review workflowDock, review, refine.The workstation is where captured information becomes clinician-approved documentation.
Blue-and-white sketch of clinicians caring for a patient in a smaller community hospital room while wearing Cortex Clip
Community + rural careAdvanced clinical AI should be practical in community and rural care.Build for real teams, practical infrastructure, and settings where connectivity may vary.
Why rural + community healthcare

Build for the places where practical deployment matters most.

Community, rural, and critical-access hospitals need technology that fits the resources they actually have. Cortex Clip is being designed for practical IT environments, strong privacy requirements, and settings where connectivity may be limited.

Fit real clinical environmentsFocus on workflows that matter in community hospitals, clinics, regional systems, and critical-access facilities.
Keep the core workflow localReduce dependence on continuous connectivity for capture and primary processing.
Design for practical adoptionKeep deployment, training, support, and daily use manageable for smaller teams.
AssetCoherence platform

Healthcare is the first application of a broader edge-intelligence platform.

AssetCoherence is built around a broader idea: useful AI should operate closer to where physical work happens, even on constrained devices. Cortex Clip is the first application of that approach.

EDGE
INTELLIGENCE

Healthcare wearables

Privacy-sensitive, mobile workflows where local intelligence can support the user.

Industrial systems

Constrained devices that need intelligence closer to the process.

Agricultural sensing

Local intelligence for environments where infrastructure and connectivity may be limited.

Ambient + robotic devices

Small systems that turn physical-world signals into useful local context.

Dallas Johnson

Founder & CEO
Founder spotlight

Building intelligence closer to where the work happens.

AssetCoherence began with a simple idea: useful AI should not require high-cost hardware or a continuous cloud connection. Cortex Clip brings that idea into clinical documentation, where mobility, privacy, constrained hardware, and human review all matter.

Edge AI + hardwareSystems + partnershipsPhysical-world intelligence
Cortex Clip pilots

Bring Cortex Clip into a real clinical workflow.

We are looking for healthcare organizations interested in testing Cortex Clip in a real clinical workflow. A pilot can help evaluate usability, documentation impact, and privacy requirements. It can also show what responsible deployment would require.

Request a Pilot →