Founding Opportunity Brief · Prepared for Ashley
Confidential · July 2026 · ICPO X LLC
Clinical Control Witness
Christopher H. Walling — Founder & CEO, ICPO X LLC
Ashley,
You told me something that stayed with me.
Healthcare demands extraordinary accountability from nurses, while the systems surrounding them often leave everyone reconstructing what actually happened only after something goes wrong.
The fall-risk example made the problem concrete.
A patient is identified as a fall risk. Interventions are ordered. Safeguards are implemented. Nurses are required to observe the patient at defined intervals. Those observations are documented. QA later reviews whether the process occurred.
But there is an important difference between:
evidence that somebody documented an observation
and
evidence supporting that the required control actually occurred.
When nothing goes wrong, that distinction can remain invisible.
When a patient falls, it becomes everything.
Did the nurse perform the round?
Was the documentation contemporaneous?
Was it entered later?
Were the required interventions in place?
Did the patient's condition change?
Do other authorized systems support or conflict with the record?
Was something subsequently corrected?
Did the clinical control fail — or is the available evidence insufficient to establish what happened?
That's when QA becomes archaeology.
Infrastructure I've already built inside ICPO X addresses the evidentiary problem.
What it does not contain — and what I will not manufacture — is your clinical expertise.
That is why I'm writing you.
The Idea
ICPO X already operates the underlying evidence machinery: deterministic evidence manifests, cryptographic artifact fingerprinting, identity-linked records, continuous witness infrastructure, external Arweave records, Bitcoin commitments, correction and supersession lineage, and independent verification surfaces.
I built that infrastructure for provenance problems outside healthcare. The same architecture applies to clinical-control evidence without requiring healthcare to reorganize itself around ICPO X.
The healthcare application is not another documentation system. It is not blockchain medical records. It is not AI deciding whether a nurse did her job.
The System
Clinical Control Witness
A system that evaluates the evidence generated while defined clinical controls are required to operate.
Consider hourly fall-risk observation. The evidence environment can include:
Authenticated clinician identity
Authorized location or proximity signals
EHR event timestamps
Rounding-system events
Bed or chair sensor state
Nurse-call activity
Device or workstation interactions
Required-control attestations
Amendments and corrections
Escalation events
No signal gets to claim more than it establishes.
A badge event does not prove visual assessment.
A sensor does not prove clinical judgment.
An EHR entry does not necessarily prove physical presence.
Missing machine evidence does not prove care wasn't provided.
Evidentiary States
EVIDENCED
Defined requirements satisfied
The available evidence satisfies the defined evidentiary requirements for this control. It does not establish, by itself, that the control was clinically appropriate or adequate for the patient.
INCOMPLETE
One or more required elements missing
The evidence set is incomplete. One or more required evidence elements are absent. Missing machine evidence does not prove care wasn't provided.
CONFLICTING
Available signals disagree
Available signals are in conflict. The system records the conflict and preserves it. It does not resolve it.
INDETERMINATE
Evidence cannot establish the state
The available evidence is insufficient to establish the state of the control. When INDETERMINATE is the only defensible answer, that is what the system records.
Even when a control is classified as EVIDENCED, that establishes only that its defined evidentiary requirements were satisfied. It does not establish, by itself, that the control was clinically appropriate or adequate for the patient. That determination remains a matter of qualified clinical judgment.
That distinction is foundational.
Why This Matters to Nurses
I am not building another system whose primary function is monitoring nurses.
If a nurse performs the required observation
the technology should make establishing that easier — not create another box for her to check.
If evidence is missing
the system preserves the uncertainty rather than manufacturing certainty.
If signals conflict
it records the conflict.
If evidence supports what occurred
that evidence survives subsequent reconstruction.
The machine witnesses.
The nurse provides the care.
QA investigates the exceptions.
That is the division of labor.
What This Is Not
a replacement for clinical judgment
an autonomous disciplinary system
a system that equates missing digital evidence with missing care
indiscriminate workforce surveillance
a replacement for the EHR
a system for publishing PHI to public blockchains
a promise to prevent adverse events
Its purpose is specific
Improve the quality, chronology, integrity, and reconstructability of evidence surrounding consequential clinical controls.
One design requirement is non-negotiable:
The system must protect clinicians from evidentiary ambiguity without becoming an indiscriminate workforce-surveillance system.
I want you defining that boundary with me.
Privacy by Architecture
The architecture separates three distinct planes.
Plane 1
Private Clinical Evidence Plane
PHI, clinical records, workforce information, device data, and clinical mappings remain within appropriately controlled institutional systems.
Plane 2
Institutional Commitment Plane
The institution generates privacy-preserving commitments and provenance records according to the approved clinical, security, privacy, and legal architecture.
Plane 3
External Verification Plane
Only information specifically determined appropriate for external commitment leaves institutional custody.
One rule applies from the beginning
Hashing information does not automatically make PHI de-identified.
Cryptography does not eliminate privacy obligations.
The architecture satisfies the applicable privacy and security requirements first and uses cryptographic provenance within those boundaries.
The Business Case
Healthcare spends enormous amounts of human and financial capital creating, reviewing, reconciling, and defending evidence of work already performed. When something goes wrong, even more capital is spent reconstructing it.
QA labor
Compliance review
Incident investigation
Survey response
Corrective-action programs
Claims management
Legal discovery
Insurance administration
Documentation
Management time
Clinical time diverted from patients
Clinical Control Witness targets that inefficiency. The commercial value is measurable through:
QA reconstruction time · evidence completeness · documentation burden · exception-detection performance · investigation cost · control performance · clinician administrative burden · resolution time · institutional risk
The thesis
If better evidence reduces cost, improves control assurance, protects clinical capacity, or reduces institutional risk by more than the cost of producing it, the architecture creates economic value. That value becomes the basis of the business.
Why You
I build provenance systems, evidence architecture, identity systems, verification infrastructure, automation, and the economic architecture around them. I have not spent your career inside healthcare.
You understand what policies look like after they collide with actual facilities, actual nurses, actual patients, actual QA processes, and actual consequences.
I will not ask an AI model to approximate that expertise for me. I want the healthcare practice designed with somebody who knows. And I don't want you brought in afterward to audit decisions I've already made.
I want your expertise to become infrastructure.
That means helping determine:
What deserves to be witnessed?
What evidence actually matters?
What evidence doesn't prove what engineers assume it proves?
Where does clinical judgment begin?
What should never leave institutional custody?
When does accountability become surveillance?
What evidence genuinely protects a nurse?
What actually helps QA?
What does a CNO require?
What does an auditor challenge?
What creates enough operational value that an institution pays for it?
Those answers become the healthcare control architecture.
The Opportunity
Not an hourly consulting assignment. Not a ceremonial advisory title. Not a request for you to endorse technology you didn't design.
The intent
An ownership and economic-participation opportunity in a healthcare practice that we jointly structure after mutual diligence and validation of the first application.
The commercial thesis: Turn clinical integrity and accountability into measurable operational value — and participate economically in the value we create.
If healthcare exposes a flaw in the architecture, we correct it.
If a control cannot be evidenced responsibly, we don't pretend otherwise.
If the economics don't support deployment, we don't manufacture an ROI case.
If the architecture establishes measurable value, we scale it.
The 90-Day Founding Experiment
We do not begin by asking a healthcare institution to trust an unvalidated system with clinical decisions. We earn our way there.
Phase 1
Find the control
Identify ten clinical controls where the gap between documentation and operational evidence creates meaningful burden or risk
Score against: patient consequence · clinician burden · QA burden · evidence availability · economic consequence · privacy implications · implementation difficulty
Select the first control — falls are an obvious candidate; the scoring determines whether they are the right one
Phase 2
Define reality
Map: requirement → authorized actor → evidence → timing → exceptions → escalation → clinical-judgment boundary
You define what the clinical evidence is permitted to mean
ICPO X defines what the technology can actually establish
The system claims no more than the intersection of those two
Phase 3
Break it
ICPO X builds the synthetic Clinical Control Witness implementation
Test: normal events · missed controls · late documentation · conflicting signals · missing evidence · corrected records · system failures · ambiguous events · false correlations
And cases where the only defensible answer is: INDETERMINATE
Phase 4
Validate
Subject to required approvals: historical/de-identified validation or prospective shadow mode
No autonomous clinical authority. No disciplinary authority.
Measure: QA reconstruction time · evidence completeness · exception precision · false-positive/negative behavior · time to resolution · administrative burden · clinician acceptance · economic value
Disposition at end: BUILD. REVISE. KILL. OR SCALE.
What Success Unlocks
The same evidence model applies wherever healthcare depends upon a consequential control and subsequently needs to establish what happened.
Pressure-injury prevention
Medication workflows
Infection-control procedures
Change-of-condition escalation
MDS provenance
Incident response
Care-plan execution
Corrective actions
Quality measures
Other controls you will identify before I do
I don't want to build twenty unrelated healthcare products. I want us to establish whether one reusable clinical-control evidence architecture sits underneath them.
If it does, we encode your expertise into that architecture. One expert no longer has to personally inspect every event for her knowledge to govern the system.
The result
Machines handle repetition.
Clinical professionals handle judgment.
Exceptions consume expertise instead of every record consuming expertise.
Your knowledge stops being monetized only by the hour.
It becomes infrastructure.
That is leverage. That is the foundation of the healthcare practice.
The First Ask
Bring me the controls you know fail in the real world.
Bring me the assumptions technologists get wrong.
Show me the evidence you trust and the evidence you don't.
Show me where the architecture creates burden instead of eliminating it.
Challenge the surveillance boundary.
Challenge the clinical assumptions.
Challenge the economics.
Challenge whether the evidence actually means what the system says it means.
I don't need you to validate my thesis. I need you to test it against reality.
If the working session establishes a viable clinical control, evidentiary model, and commercial path, we design the 90-day founding experiment together.
You bring
People and clinical reality
I bring
The evidence machinery
Let's determine what they can build together.
Christopher H. Walling
Founder & CEO, ICPO X LLC
July 2026 · Confidential