{"schema_version":1,"assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","source_experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__speech_language_pathology","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"speech_language_pathology","title":"Explicit lifecycle management for longitudinal swallowing recommendations","opportunity_summary":"The candidate proposes identity-linking generations of dysphagia guidance, assigning clinician-authorized lifecycle states, and tiering visibility so superseded guidance loses routine authority while remaining recoverable. The safety consequence could be meaningful, but the sealed packet does not establish that active-facing conflicts are prevalent, influence care, or are better addressed by lifecycle management than by a reconciled current-order banner.","adopter_authorizer":"A treating speech-language pathology service and responsible medical team would adopt and authorize clinical-currency decisions, with EHR leadership, health-information-management, privacy, and compliance authorities approving integration, access, retention, and operational controls.","scores":{"meaningful_impact":{"score":4,"rationale":"Following obsolete diet, liquid-consistency, supervision, or aspiration guidance could materially affect patient safety, and preserving lineage also supports accountability; however, the packet supplies no prevalence or effect-size evidence."},"stakeholder_pull":{"score":2,"rationale":"The proposal identifies affected clinicians, caregivers, patients, and governance staff, but contains no interviews, requests, workflow observations, purchasing interest, or other evidence that these stakeholders seek lifecycle management."},"incremental_advantage":{"score":3,"rationale":"Cross-artifact lineage, explicit supersession states, reversible suppression, and auditability could add value beyond manual date comparison or a single current-order banner, but no comparative evidence shows improved selection accuracy, speed, or safety."},"distinctiveness_plausibility":{"score":3,"rationale":"The combination of recommendation identity resolution, authorized lifecycle states, and visibility tiering is structurally distinguishable from the stated banner rival, but prior art is explicitly unsearched and implementation novelty is unmeasured."},"technical_implementability":{"score":3,"rationale":"A read-only shadow review and simulated visibility changes are technically bounded, while production implementation depends on uncertain identity-linking across notes, orders, handoffs, and instructions plus reliable dependency and lineage handling."},"adoption_authority_feasibility":{"score":3,"rationale":"The candidate names the treating SLP and medical team as clinical authorities and records/compliance functions as disposition authorities, but distributed authority and transition workflows may make timely adjudication and governance coordination difficult."},"evidence_readiness":{"score":4,"rationale":"The packet provides a four-week read-only study, blinded expert adjudication, explicit problem and intervention falsifiers, a nearest-rival comparison, exclusions, and halt conditions; representative sampling and outcome measures still require operational definition."},"safety_net_benefit":{"score":4,"rationale":"Reversible suppression, preserved source records, lineage links, audits, dependency checks, restore drills, and explicit halt conditions provide substantial safeguards against concealing current instructions, though their effectiveness is untested."},"scalability":{"score":2,"rationale":"Scaling would require cross-artifact identity resolution, authorized clinical review, EHR-specific display changes, local retention governance, training, and ongoing exception handling; no evidence shows these burdens can be standardized across services or institutions."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"One service, four-week read-only shadow review of closed or clinician-reviewed encounters, including conflict inventory, blinded expert adjudication, simulated lifecycle states, comparison with baseline and the current-order-banner rival, analysis, and governance oversight.","confidence":"MODERATE","assumptions":["Existing records can be accessed under an approved internal review pathway.","No production EHR modification or patient-facing output is required.","Clinical experts and an analyst can perform most identity resolution and adjudication manually.","The review does not require costly vendor customization or extensive data normalization."]},"initial_deployment_startup":{"band_2026_usd":"250K_TO_1M","scope":"Initial production capability for one organization or service, including cross-artifact recommendation registry or indexing, lifecycle-state workflow, visibility controls, lineage, role-based access, dependency checks, audit logging, security review, and validation.","confidence":"LOW","assumptions":["Integration is limited to a bounded set of EHR artifacts and one initial service.","The incumbent EHR permits supported integration and display customization.","Source records remain unchanged and no destruction workflow is built.","Material engineering is needed because identity-linking cannot be assumed to exist."]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Controlled launch in the initial service, including workflow configuration, clinician and governance training, acceptance testing, retrospective safety checks, monitoring, support, and rollback preparation.","confidence":"LOW","assumptions":["The startup capability has already passed technical validation.","Launch remains limited to one service or a small set of connected workflows.","No major redesign is triggered by clinician-comprehension testing.","Clinical and records-governance personnel participate as part of launch work."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Annual operation for the initial deployment, including authorized review labor, exception handling, software maintenance, access and audit review, lineage and restore testing, monitoring, training refreshes, and governance updates.","confidence":"LOW","assumptions":["Recommendation review remains human-authorized rather than automatic.","Volume is manageable within one organization or service.","Existing infrastructure hosts the capability.","Expansion to additional specialties, institutions, or extensive vendor licensing is excluded."]}},"research_burden":"HIGH","earliest_credible_horizon":"0_TO_3_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The packet specifies a recognizable observable conflict and safety mechanism, but supplies no representative audit showing that materially conflicting active-facing generations occur or influence decisions."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"The treating SLP and responsible medical team are identified for clinical currency, while records/compliance authorities govern retention and disposition; an SLP service with its EHR governance partners is an identifiable adoption unit."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal makes a testable claim that lifecycle states, lineage, and tiered visibility improve correct current-guidance selection relative to manual comparison and a single reconciled-order banner."},"bounded_next_evidence_step":{"status":"YES","reason":"A four-week, one-service, read-only shadow review on closed or clinician-reviewed encounters is bounded, uses blinded expert adjudication, simulates rather than applies visibility changes, and has explicit problem and intervention falsifiers."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first step does not change care or source records, reserves currency decisions for authorized clinicians, excludes automatic invalidation and patient-facing advice, and halts for current-guidance demotion, dependency loss, broken lineage, or unauthorized disclosure."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"A broad one-service resource range can be estimated, but production scope is not specified sufficiently to resolve EHR interfaces, artifact volume, vendor constraints, review workload, or governance effort."}},"blocking_evidence":["A representative audit must establish that materially conflicting active-facing swallowing recommendations exist and are not reliably neutralized by the current authoritative-order workflow.","Observed or simulated testing must show that stale artifacts affect correct-guidance selection, selection time, errors, or delays rather than merely coexisting harmlessly.","Reviewers must be able to identity-link recommendation generations and adjudicate currency with acceptable consistency across notes, orders, handoffs, and patient instructions.","Lifecycle flags and tiered displays must outperform or materially complement the simpler current-order-banner rival without increasing missed-current-guidance events or alert burden.","Governance review must confirm that access controls, preservation, simulated demotion, lineage recovery, and applicable retention obligations can be handled safely."],"next_evidence_step":"Conduct the specified four-week read-only shadow review in one service using closed or clinician-reviewed encounters: compare detected conflicts with blinded expert adjudication, and compare simulated lifecycle/tiered presentation with current manual practice and the single current-order-banner rival. Stop or reject the mechanism if material active-facing conflicts are absent, clinicians already select the authoritative guidance reliably, lifecycle handling does not improve correct selection, or any simulated demotion targets current guidance, obscures a dependency, breaks recoverable lineage, or creates unauthorized disclosure.","research_questions":["How often do materially conflicting swallowing recommendations coexist in active-facing artifacts, and in which artifact combinations?","Which artifacts do clinicians and caregivers actually consult, and do conflicts change selection accuracy, time, escalation, or care decisions?","Can recommendation generations be identity-linked across orders, notes, handoffs, and instructions with sufficient reliability for authorized review?","How consistently can treating SLPs and responsible medical teams adjudicate current, superseded, exception-held, and historical states?","Does lifecycle labeling and visibility tiering improve correct current-guidance selection over manual practice and a reconciled current-order banner?","Do the proposed labels increase alert burden, confusion, or missed-current-guidance events?","What EHR integration, privacy, access-control, retention, and recovery constraints determine local deployment feasibility?","What existing clinical reconciliation, copied-forward-text, supersession-display, recommendation-registry, or records-lifecycle approaches overlap with the proposal?","What ongoing review volume and exception rate would be required, and can authorized staff sustain it?","Can lineage, dependency visibility, rollback, and restore behavior be validated without changing or destroying source records?"],"recommendation":"VALIDATE_PROBLEM_FIRST","uncertainty_constraints":["Closed-book assessment: no external evidence was used.","Problem prevalence, realized harm, effect size, stakeholder demand, and market size are unmeasured.","Prior art and world novelty are unsearched and cannot support a novelty claim.","Cost bands are resource-equivalent planning ranges, not quotations or point estimates.","Production feasibility depends on unknown EHR interfaces, data quality, vendor constraints, artifact volume, and reviewer workload.","Applicable retention, privacy, disclosure, and clinical-authority rules are not established by the packet.","The four-week shadow review can provide initial evidence but does not imply live deployment or patient-facing use."],"closed_book_prior_art_boundary":"The sealed candidate supports only structural differentiation from its stated nearest rival. It provides no basis to claim historical novelty, implementation novelty, absence of equivalent EHR functionality, prevalence of competing approaches, or freedom from prior art."}