{"schema_version":1,"research_id":"eoa_inverse_innovation_exp03_external48_20260801","source_assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","cell_id":"layer_decay_and_expiration_management__veterinary_medicine","selection_stratum":"MIDDLE_BAND_AUDIT_Q1","search_queries":["site:avma.org veterinary medical records retention problem list medication reconciliation electronic medical records","veterinary electronic medical records inactive problems medication list reconciliation stale records study","veterinary software \"inactive\" \"problem list\"","veterinary practice management software archive medical record audit trail official","site:vmb.ca.gov veterinary medical records retention record alterations regulations","site:rcvs.org.uk clinical records veterinary retention alteration records","site:idexx.com veterinary software \"Active or Inactive\" problem list","site:vetview.atlassian.net \"Inactive\" medication order problem alert veterinary","veterinary electronic health record usability clinician time burden study","veterinary patient safety medical record errors study wrong history records"],"sources":[{"source_id":"S1","title":"First opinion practice electronic health records are a useful source of descriptions of medication errors","publisher":"Frontiers in Veterinary Science / PubMed Central","url":"https://pmc.ncbi.nlm.nih.gov/articles/PMC12130827/","source_class":"PRIMARY_RESEARCH","publication_date":"2025","accessed_at":"2026-08-02","claims_supported":["A retrospective search of UK first-opinion veterinary EHR narratives found 1,023 confirmed medication-error narratives among 2,847 manually reviewed candidates.","The study used human review because clinical narratives could be ambiguous and used a second reviewer on a subset.","Medication errors documented in veterinary EHRs included administrative errors such as incorrect history and errors across prescribing, dispensing, administration, and monitoring."]},{"source_id":"S2","title":"Medical Errors Cause Harm in Veterinary Hospitals","publisher":"Frontiers in Veterinary Science","url":"https://www.frontiersin.org/journals/veterinary-science/articles/10.3389/fvets.2019.00012/full","source_class":"PRIMARY_RESEARCH","publication_date":"2019-02-05","accessed_at":"2026-08-02","claims_supported":["Across 560 voluntary incident reports from three veterinary hospitals, drug and communication errors were the leading reported categories.","Fifteen percent of reported incidents caused patient harm, although voluntary reporting does not establish population prevalence.","Communication-error definitions included incomplete information, transmission failures, and incorrect interpretation; the authors identify medical-record review as an alternative detection method."]},{"source_id":"S3","title":"Episode Problems and SOAPs in 5.0","publisher":"VetView User Guides","url":"https://vetview.atlassian.net/wiki/spaces/UG/pages/4093935617/Episode+Problems+and+SOAPs+in+5.0","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2025-04-22","accessed_at":"2026-08-02","claims_supported":["VetView already permits veterinary problems to be merged, renamed, inactivated, reactivated, resolved, or marked deleted.","VetView separates an active list from retained history, displays source information, preserves merged and deleted history, and allows inactive or resolved problems to return to active status.","VetView has privilege-based SOAP review and verification, tracks users and timestamps, and provides supervisor-controlled record-maintenance actions."]},{"source_id":"S4","title":"IDEXX Cornerstone Electronic Medical Records and Whiteboard Setup","publisher":"IDEXX Laboratories","url":"https://www.idexx.com/media/filer_public/2b/21/2b21fb9f-1494-4fa2-9b8d-b65af6429d00/cornerstone-coach-electronic-medical-record-and-whiteboard-setup-83.pdf","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2013","accessed_at":"2026-08-02","claims_supported":["Cornerstone supports problem states including active, acute, chronic, resolved, and verified incorrect.","Cornerstone supports active and inactive status for problem-list definitions and diagnostic codes.","The documentation links diagnostic codes with documents and patient-history reporting, demonstrating existing veterinary-record dependencies."]},{"source_id":"S5","title":"Lifecycle","publisher":"Health Level Seven International (HL7), FHIR Release 5","url":"https://www.hl7.org/fhir/R5/lifecycle.html","source_class":"STANDARD","publication_date":"2023-03-26","accessed_at":"2026-08-02","claims_supported":["FHIR defines lifecycle or clinical-status values for medication requests, service requests, diagnostic reports, document references, flags, conditions, and other clinical resources.","FHIR distinguishes current problem and medication lists from encounter and historical resources.","FHIR states that currentness cannot always be inferred from an individual resource and that retrospective alteration may conflict with integrity and digital signatures."]},{"source_id":"S6","title":"13. Clinical and client records","publisher":"Royal College of Veterinary Surgeons","url":"https://www.rcvs.org.uk/veterinary-professionals/conduct-and-guidance/supporting-guidance/13-clinical-and-client-records?print=true","source_class":"OFFICIAL_GUIDANCE","publication_date":"2026-04-24","accessed_at":"2026-08-02","claims_supported":["Veterinary clinical records should provide a complete and relevant history sufficient for continuity of care, including treatments, results, plans, responsible personnel, and client advice.","Amendments should not obscure originals and should identify the date and person making the amendment.","Retention must account for legal and regulatory obligations, while necessary deletion must protect confidentiality and prevent accidental loss or disclosure."]},{"source_id":"S7","title":"California Code of Regulations §2032.3: Record Keeping; Records; Contents; Transfer","publisher":"California Veterinary Medical Board","url":"https://vmb.ca.gov/laws_regs/min_stan_records.pdf","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2026","accessed_at":"2026-08-02","claims_supported":["California veterinarians must create records containing diagnoses, medications, treatment plans, progress, and case disposition.","Covered veterinary records must be retained for at least three years after the animal's last visit.","Clients may request a medical-record summary containing pertinent history, treatment, medication, and disposition information."]},{"source_id":"S8","title":"Survey of electronic veterinary medical record adoption and use by independent small animal veterinary medical practices in Massachusetts","publisher":"Journal of the American Veterinary Medical Association / PubMed","url":"https://pubmed.ncbi.nlm.nih.gov/25029312/","source_class":"PRIMARY_RESEARCH","publication_date":"2014-08-01","accessed_at":"2026-08-02","claims_supported":["In the survey, electronic veterinary records were used alone or with paper in 66 of 82 responding practices.","Common uses included recording medical information, reminders, and tracking patient health.","Reported adoption barriers included technological concerns, time constraints, and cost."]}],"problem_evidence":{"support":"MODERATE","rationale":"The bounded search supports the underlying currentness problem indirectly but does not establish its prevalence as formulated. HL7 identifies the general inability to infer whether individual clinical resources are current, and veterinary products explicitly manage inactive, resolved, duplicate, and historical problems. Veterinary studies establish consequential medication and communication errors and ambiguity in narrative review, but neither study isolates stale active veterinary-record layers as a cause or measures their reconciliation burden.","source_ids":["S1","S2","S3","S4","S5"]},"stakeholder_evidence":{"support":"WEAK","rationale":"Veterinary EHRs are widely used in the surveyed sample, record-related communication and medication errors can harm patients, and time, cost, and technical complexity are recognized barriers. However, no source reports clinic demand, willingness to pay, or willingness to perform continuing adjudication specifically for record-wide lifecycle management.","source_ids":["S2","S8"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"VetView Master Problem List and SOAP lifecycle management","similarity":"Implements active, inactive, resolved, deleted, and reversible states; merges duplicates; separates active display from retained history; records sources and history; and uses privileged review workflows in an actual veterinary record system.","remaining_difference":"The documentation does not describe silent record-wide stale-item detection or ranking across medications, alerts, instructions, results, and attachments, nor retention/dependency gates, quarantine/archive policies, restore drills, or comparative evaluation against ordinary reconciliation.","source_ids":["S3"]},{"name":"IDEXX Cornerstone problem and diagnostic-code states","similarity":"Implements active/inactive and richer clinical states for veterinary problems and diagnoses and supports links between diagnostic codes and documents.","remaining_difference":"The documented states primarily configure problem and diagnostic-code use; no record-wide stale-layer detector, adjudication queue, governed disposition pipeline, or restoration evaluation was found.","source_ids":["S4"]},{"name":"HL7 FHIR lifecycle and current-list model","similarity":"Provides lifecycle/status semantics across conditions, medication requests, service requests, diagnostic reports, document references, and flags while distinguishing current curated lists from retained resources.","remaining_difference":"It is a general interoperability standard rather than a demonstrated veterinary workflow, and it does not itself provide stale-item ranking, clinician adjudication, jurisdictional retention gates, archival testing, or effectiveness evidence.","source_ids":["S5"]}],"distinctive_claim_remaining":"The remaining testable claim is not explicit lifecycle state alone. It is that a silent, record-wide veterinary review process can identify possibly stale items across multiple clinical layer types and, after clinician adjudication plus dependency and retention gates, reduce reconciliation time or improve current-state interpretation without hiding protected/current information or imposing excessive review work.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"VetView demonstrates that reversible problem states, duplicate merging, history retention, provenance display, prioritization, permissions, and supervised verification are technically feasible in veterinary software. FHIR supplies status semantics for the broader resource classes, and official guidance supports audit-preserving amendment. No source demonstrates the complete cross-layer detector, dependency resolver, retention engine, archive/restore workflow, or safe production integration proposed here.","source_ids":["S3","S4","S5","S6"]},"scores":{"meaningful_impact":{"score":3,"rationale":"Veterinary medication and communication errors can cause harm, so better current-state interpretation has plausible value. The contribution of stale active layers to those errors and the frequency of the proposed problem remain unmeasured.","source_ids":["S1","S2"]},"stakeholder_pull":{"score":2,"rationale":"Clinics use electronic records for care and tracking, but no direct demand or purchasing evidence for this intervention was found; continuing review workload may conflict with known time and cost barriers.","source_ids":["S8"]},"incremental_advantage":{"score":2,"rationale":"VetView already provides much of the central problem-list lifecycle, history, merging, prioritization, provenance, and governance functionality. The record-wide detector and retention/dependency controls are incremental but have no comparative benefit evidence.","source_ids":["S3","S4","S5"]},"distinctiveness_plausibility":{"score":2,"rationale":"Substantial veterinary prior art exists for lifecycle states, reversible inactivation, duplicate merging, active-versus-history views, and controlled review. The broader cross-layer governed workflow remains differentiable but is narrower than the original mechanism claim.","source_ids":["S3","S4","S5"]},"technical_implementability":{"score":3,"rationale":"Manual silent review and problem-layer lifecycle management are feasible, but reliable cross-layer identity, provenance, dependencies, protected-record logic, archive retrieval, and heterogeneous-platform integration are unresolved.","source_ids":["S3","S4","S5","S6"]},"adoption_authority_feasibility":{"score":3,"rationale":"Official rules and guidance make treating veterinarians and veterinary practices credible clinical-record authorities, while preserving originals and satisfying retention are mandatory concerns. Destructive authority and applicable record-class rules still require jurisdiction-specific approval.","source_ids":["S6","S7"]},"evidence_readiness":{"score":4,"rationale":"A silent chart review with independent adjudication is methodologically feasible and decision-relevant; veterinary EHR research already uses retrospective searches, manual adjudication, and secondary review of ambiguous narratives. Prespecified sampling and thresholds remain necessary.","source_ids":["S1","S2"]},"safety_net_benefit":{"score":4,"rationale":"Silent mode, retained originals, clinician confirmation, separated destructive authority, audit trails, and restoration testing align with official expectations that amendments preserve originals and records remain available. These controls substantially bound pilot risk.","source_ids":["S3","S6","S7"]},"scalability":{"score":2,"rationale":"Status models can span multiple resource types, but veterinary EHR adoption includes mixed paper/electronic environments and reported technical, time, and cost barriers. Vendor schemas and jurisdictional retention variation limit near-term standardization.","source_ids":["S5","S8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"One-clinic, non-mutating retrospective study of 200 closed encounters, covering secure extraction, stratification, rule-based flag generation, dual-clinician adjudication of a predefined sample, records/compliance coordination, analysis, and reporting; existing computers and record access are assumed.","confidence":"MODERATE","assumptions":["The clinic can authorize secure retrospective access without purchasing a new production interface.","Flagging uses manual rules or a lightweight offline prototype.","Clinician review and disagreement resolution are limited to the predefined sample.","No records are changed, archived, or deleted."],"source_ids":["S1","S2","S7"]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"One-clinic non-destructive prototype covering engineering and data mapping, lifecycle taxonomy, provenance inventory, dependency-rule design, retention and hold matrix, role-based review workflow, privacy/security review, audit logging, test environment, project coordination, and evaluation design.","confidence":"LOW","assumptions":["One principal veterinary-record platform is in scope.","Existing authentication, backup, and storage can be reused.","The prototype makes recommendations only and does not alter clinical state.","Vendor API access and historical data are available on reasonable terms."],"source_ids":["S3","S5","S6","S7","S8"]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Clinician-confirmed production launch for one clinic or small clinic group, including vendor integration, software development, secure infrastructure or equipment, archive and retrieval controls, identity and dependency validation, access control, compliance review, training, workflow redesign, monitoring, restore drills, and comparative evaluation.","confidence":"LOW","assumptions":["No autonomous deletion, diagnosis change, treatment change, or owner-instruction change is enabled.","Existing archival and disaster-recovery services can be extended rather than replaced.","Deployment is limited to one platform and a small number of jurisdictions.","Vendor customization and validation are required but no core-system rebuild is needed."],"source_ids":["S3","S4","S5","S6","S7","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Ongoing software and infrastructure support, clinician and records-staff adjudication, exception and hold handling, policy maintenance, vendor licensing, security monitoring, audits, restore drills, user training, and periodic performance and bias revalidation for a limited deployment.","confidence":"LOW","assumptions":["Review volume remains manageable without a large dedicated team.","The clinic retains final clinical and destructive authority.","Integration and archive services remain stable.","Expansion to additional platforms or jurisdictions is excluded."],"source_ids":["S3","S5","S6","S7","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"UNCERTAIN","reason":"External evidence establishes difficulty distinguishing current from historical resources, existing veterinary lifecycle-management features, and consequential medication and communication errors. It does not measure how often veterinary records contain incorrectly active or ambiguous stale layers or whether they materially impair decisions.","source_ids":["S1","S2","S3","S5"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"Official guidance and regulation place responsibility for accurate, retained, accessible veterinary clinical records with veterinarians and practices, making a treating veterinarian and authorized practice records function credible decision-makers. Local destructive-disposition authority still requires confirmation.","source_ids":["S6","S7"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"Against documented veterinary problem-list lifecycle functions, the incremental claim is explicitly testable: record-wide silent flagging plus dependency and retention gates should improve review time or current-state interpretation without increasing protected-record errors, missed dependencies, or reviewer workload beyond preset limits.","source_ids":["S3","S4","S5"]},"bounded_next_evidence_step":{"status":"YES","reason":"Retrospective veterinary EHR searches with manual and secondary review are demonstrated methods. A 200-encounter silent comparison changes no records and can be stopped on low prevalence, low precision, excessive disagreement, or dependency/protection failures.","source_ids":["S1","S2"]},"no_unresolved_safety_or_authority_stop":{"status":"UNCERTAIN","reason":"Preserving originals, audit trails, access, and mandatory retention is necessary, but the candidate has no specified jurisdiction or validated matrix for medicinal-product records, investigations, consent, legal holds, client data, or destruction. Live disposition cannot proceed on current evidence.","source_ids":["S6","S7"]},"credible_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The bands include labor, software, data, compliance, coordination, infrastructure, and evaluation, but no direct cost study was found and actual costs depend materially on vendor interfaces, mixed paper/electronic records, review volume, archive capabilities, and jurisdiction.","source_ids":["S3","S5","S8"]}},"next_evidence_step":"Run one authorized, non-mutating retrospective study on 200 closed encounters from one clinic. Sample both detector-flagged and randomly selected unflagged records; have two clinicians independently classify each sampled item as current, superseded, inactive, entered-in-error, historical-but-relevant, or indeterminate. Compare against ordinary reconciliation on stale-item prevalence, adjudicated flag precision, false negatives in unflagged records, review time, current-state interpretation accuracy, reviewer disagreement, and missed protected-record or dependency flags. Falsify the problem if ambiguous active layers are rare and add no measurable burden or interpretation error; falsify the intervention if precision or interpretation improvement misses preset thresholds, review time increases materially, or any repeated protected/current-record or dependency failure occurs.","blocking_evidence":["Representative veterinary prevalence and burden data for ambiguous or incorrectly active diagnoses, medications, alerts, instructions, results, and attachments.","Evidence that the cross-layer detector adds benefit beyond lifecycle and history functions already present in systems such as VetView and Cornerstone.","Validated jurisdiction- and record-class-specific retention, consent, investigation, legal-hold, quarantine, destruction, and restoration rules.","Platform evidence for reliable animal and episode identity, provenance, dependency resolution, archive retrieval, audit logs, and rollback.","Adopter evidence concerning acceptable clinician review workload, workflow ownership, and willingness to fund ongoing maintenance."],"research_disposition":"PROBLEM_PREVALENCE_STUDY","world_novelty_boundary":"This bounded search found substantial prior art for veterinary problem-list lifecycle states, reversible inactivation, duplicate merging, history preservation, provenance, prioritization, and privileged review, plus a cross-resource lifecycle standard. It did not find a documented veterinary implementation combining silent record-wide stale-item ranking, clinician adjudication, retention and dependency gates, reversible archive or quarantine, restore drills, and comparative evaluation. That remaining difference is only a bounded-search observation and is not a world-novelty or patentability claim."}