CLINICAL EXECUTION REQUIRES MORE THAN A PROTOCOL.
A protocol, consent record, safety assessment or batch document can establish important domain facts. None of them alone creates an execution right. immo.quick resolves encoded, source-bound conditions before a capability can exist.
One clinical action can depend on several independent states.
The sector surface does not collapse protocol, consent, safety, regulatory and product conditions into one score.
Protocol State
Version, amendment, applicable procedural conditions and protocol-bound dependencies.
Consent & Subject State
Encoded conditions around consent status and other defined subject-bound prerequisites.
Safety State
Adverse-event and safety-reporting facts remain evidence-bearing states.
Regulatory State
Applicable approvals, authorisations, jurisdiction and time-bound regulatory conditions.
Product / Batch State
Where relevant, product, batch, release, serialisation or conformity conditions can enter as dependencies.
Time & Evidence
The resolved state is bound to the relevant point in time and attributable evidence.
Determination first. Execution rights second.
Two sector gates. Different purposes.
Evidence can strengthen accountability. It does not create medical or regulatory authority.
CAN
- Deterministically evaluate encoded, source-bound conditions.
- Bind domain determinations to a defined state.
- Surface missing or conflicting dependencies.
CANNOT
- Create ethics, regulatory or medical authority.
- Replace competent roles.
- Turn a gate result into execution permission by itself.