Domain surface · synthetic · client-mimic sandbox

From policy decision to completed human-approved residual

LensDNA executes the browser, document, coordination, and evidence work that remains after Medicaid or commercial coverage decisions make doula care reimbursable. This surface demonstrates one narrow residual loop — credentialing, coverage confirmation, and outcomes documentation — not a general care platform or clinical system.

Trust boundary: Synthetic demonstration only. No real patient, doula, or health-plan data. No endorsement, partnership, integration, or customer relationship with any named organization is claimed or implied. LensDNA does not make clinical determinations. Irreversible actions require explicit human approval. Residual shape is relevant to the 26 states + DC with Medicaid doula reimbursement (as of 2026).

What the residual layer does

Policy and platform layers can open reimbursement. They often leave fragmented operational work: MCO credentialing portals, coverage confirmation, visit documentation, outcomes reporting, and claim-ready packets.

Receive the enrollment / coverage decision and preserve case context
Classify the operational residual required
Navigate the relevant synthetic MCO / plan portal
Stage credentialing fields, coverage confirmation, and documentation
Pause before any irreversible submit or external action
Present the complete action set for human review
Record approved / rejected / amended actions + audit trail

Start synthetic event → Reset session

Primary demonstration (synthetic)

Event: Cascadia Community Doula Collective (fictional) is newly eligible for Medicaid doula reimbursement in a high-band state. Credentialing packet for one MCO is incomplete. Coverage confirmation is still required for a synthetic postpartum client. Outcomes documentation residual remains.

Residual still required: open synthetic MCO credentialing portal → complete fields + attach training packet → stage coverage confirmation → prepare visit / outcomes documentation → human gate before irreversible submit → produce Residual Evidence Artifact (REA).

All names, identifiers, organisations, and outcomes are fictional. No live systems are contacted.

Capabilities made visible

Voice interaction & telephony path
Optic / screen interpretation notes
DOM extraction + deterministic field control
Synthetic portal navigation
Continuous case context

Staged actions (not uncontrolled automation)
Human approval before irreversible steps
Action status: proposed → staged → approved
Audit provenance + dossier generation
Zero-retention / synthetic boundary stated

Install pattern (identical to production client)

<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>

Overlay controls only the origin that embeds it. This surface uses the same production embed path clients use.

Reusable runtime · other domains

The same client-side runtime is intended for HealthAdminDNA residual, Education & Therapy Robotics, Deploy care-setting events, PropTech, industrial claims/permitting, and critical-minerals intelligence. Domain pages define event types, workflow steps, approval rules, synthetic portals, terminology, evidence requirements, and pilot metrics. The execution kernel stays domain-agnostic.

← SensorLens residual practice