Practice residual flow like a client site
Your own pages + one script tag. Domain surfaces demonstrate how LensDNA turns an upstream event into completed, human-gated operational work. Bottom-right pill opens LensDNA overlay (optional WebRTC voice).
Featured · Doula Care Residual
From policy decision to completed human-approved residual. LensDNA executes the credentialing, coverage confirmation, documentation, and evidence work that remains after Medicaid or commercial coverage makes doula care reimbursable (26 states + DC as of 2026).
- Receive enrollment / coverage decision + preserve context
- Stage MCO credentialing fields, coverage confirmation, outcomes docs
- Human gate before irreversible actions
- Residual Evidence Artifact (REA) + qualification path
Synthetic only. No endorsement or integration with any named program or plan is claimed.
Education & Therapy Robotics
From robot event to completed human-approved workflow. LensDNA executes the browser, phone, documentation, coordination, and evidence work that remains after an education or therapy robot creates an event.
HealthAdmin-shaped residual (original practice path)
- Handoff — decision already done; residual still listed for the operator.
- Residual portal — member, auth ref, CPT, attachments, status notes (overlay can read/type).
- Human gate — irreversible submit blocked until explicit approval.
- Status / metrics — practice dossier + local learning log.
- Pilot intake — local parameter form without leaving this origin.
Install under test (identical client pattern)
<script src="https://lensdna.app/embed.js" data-overlay-url="https://lensdna.app/overlay.html" data-tenant-id="sensorlens-sandbox" data-theme="dark" data-position="bottom-right"> </script>
Runtime posture
LensDNA is a domain-agnostic, client-side execution runtime for residual work after an intelligent system, robot, platform, or human operator has created an event. Domain surfaces (Doula Care, Education & Therapy Robotics, HealthAdmin residual, Deploy care-setting, PropTech, industrial) define event types, steps, approval rules, terminology, and pilot metrics. The execution kernel stays reusable.