HaHafeng
5523ef36ea
Summary: - Implement Prompt management infrastructure and core services - Build admin portal frontend with light theme - Integrate CodeMirror 6 editor for non-technical users Phase 3.5.1: Infrastructure Setup - Create capability_schema for Prompt storage - Add prompt_templates and prompt_versions tables - Add prompt:view/edit/debug/publish permissions - Migrate RVW prompts to database (RVW_EDITORIAL, RVW_METHODOLOGY) Phase 3.5.2: PromptService Core - Implement gray preview logic (DRAFT for debuggers, ACTIVE for users) - Module-level debug control (setDebugMode) - Handlebars template rendering - Variable extraction and validation (extractVariables, validateVariables) - Three-level disaster recovery (database -> cache -> hardcoded fallback) Phase 3.5.3: Management API - 8 RESTful endpoints (/api/admin/prompts/*) - Permission control (PROMPT_ENGINEER can edit, SUPER_ADMIN can publish) Phase 3.5.4: Frontend Management UI - Build admin portal architecture (AdminLayout, OrgLayout) - Add route system (/admin/*, /org/*) - Implement PromptListPage (filter, search, debug switch) - Implement PromptEditor (CodeMirror 6 simplified for clinical users) - Implement PromptEditorPage (edit, save, publish, test, version history) Technical Details: - Backend: 6 files, ~2044 lines (prompt.service.ts 596 lines) - Frontend: 9 files, ~1735 lines (PromptEditorPage.tsx 399 lines) - CodeMirror 6: Line numbers, auto-wrap, variable highlight, search, undo/redo - Chinese-friendly: 15px font, 1.8 line-height, system fonts Next Step: Phase 3.5.5 - Integrate RVW module with PromptService Tested: Backend API tests passed (8/8), Frontend pending user testing Status: Ready for Phase 3.5.5 RVW integration
3913 lines
453 KiB
PL/PgSQL
3913 lines
453 KiB
PL/PgSQL
--
|
||
-- PostgreSQL database dump
|
||
--
|
||
|
||
\restrict vMbzIt5rdhooQQkVIadThqQNeTLSUjU5BIRHdaDmCIx41txnLZ1zV3bBefNanOQ
|
||
|
||
-- Dumped from database version 15.14
|
||
-- Dumped by pg_dump version 15.14
|
||
|
||
SET statement_timeout = 0;
|
||
SET lock_timeout = 0;
|
||
SET idle_in_transaction_session_timeout = 0;
|
||
SET client_encoding = 'UTF8';
|
||
SET standard_conforming_strings = on;
|
||
SELECT pg_catalog.set_config('search_path', '', false);
|
||
SET check_function_bodies = false;
|
||
SET xmloption = content;
|
||
SET client_min_messages = warning;
|
||
SET row_security = off;
|
||
|
||
--
|
||
-- Name: admin_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA admin_schema;
|
||
|
||
|
||
ALTER SCHEMA admin_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: aia_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA aia_schema;
|
||
|
||
|
||
ALTER SCHEMA aia_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: asl_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA asl_schema;
|
||
|
||
|
||
ALTER SCHEMA asl_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: capability_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA capability_schema;
|
||
|
||
|
||
ALTER SCHEMA capability_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: common_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA common_schema;
|
||
|
||
|
||
ALTER SCHEMA common_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA dc_schema;
|
||
|
||
|
||
ALTER SCHEMA dc_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: iit_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA iit_schema;
|
||
|
||
|
||
ALTER SCHEMA iit_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: pkb_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA pkb_schema;
|
||
|
||
|
||
ALTER SCHEMA pkb_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: platform_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA platform_schema;
|
||
|
||
|
||
ALTER SCHEMA platform_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: public; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
-- *not* creating schema, since initdb creates it
|
||
|
||
|
||
ALTER SCHEMA public OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: SCHEMA public; Type: COMMENT; Schema: -; Owner: postgres
|
||
--
|
||
|
||
COMMENT ON SCHEMA public IS '';
|
||
|
||
|
||
--
|
||
-- Name: rvw_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA rvw_schema;
|
||
|
||
|
||
ALTER SCHEMA rvw_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: ssa_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA ssa_schema;
|
||
|
||
|
||
ALTER SCHEMA ssa_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: st_schema; Type: SCHEMA; Schema: -; Owner: postgres
|
||
--
|
||
|
||
CREATE SCHEMA st_schema;
|
||
|
||
|
||
ALTER SCHEMA st_schema OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: PromptStatus; Type: TYPE; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE capability_schema."PromptStatus" AS ENUM (
|
||
'DRAFT',
|
||
'ACTIVE',
|
||
'ARCHIVED'
|
||
);
|
||
|
||
|
||
ALTER TYPE capability_schema."PromptStatus" OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: TenantStatus; Type: TYPE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE platform_schema."TenantStatus" AS ENUM (
|
||
'ACTIVE',
|
||
'SUSPENDED',
|
||
'EXPIRED'
|
||
);
|
||
|
||
|
||
ALTER TYPE platform_schema."TenantStatus" OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: TenantType; Type: TYPE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE platform_schema."TenantType" AS ENUM (
|
||
'HOSPITAL',
|
||
'PHARMA',
|
||
'INTERNAL'
|
||
);
|
||
|
||
|
||
ALTER TYPE platform_schema."TenantType" OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: UserRole; Type: TYPE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE platform_schema."UserRole" AS ENUM (
|
||
'SUPER_ADMIN',
|
||
'PROMPT_ENGINEER',
|
||
'HOSPITAL_ADMIN',
|
||
'PHARMA_ADMIN',
|
||
'DEPARTMENT_ADMIN',
|
||
'USER'
|
||
);
|
||
|
||
|
||
ALTER TYPE platform_schema."UserRole" OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: VerificationType; Type: TYPE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE platform_schema."VerificationType" AS ENUM (
|
||
'LOGIN',
|
||
'RESET_PASSWORD',
|
||
'BIND_PHONE'
|
||
);
|
||
|
||
|
||
ALTER TYPE platform_schema."VerificationType" OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: job_state; Type: TYPE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TYPE platform_schema.job_state AS ENUM (
|
||
'created',
|
||
'retry',
|
||
'active',
|
||
'completed',
|
||
'cancelled',
|
||
'failed'
|
||
);
|
||
|
||
|
||
ALTER TYPE platform_schema.job_state OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: create_queue(text, jsonb); Type: FUNCTION; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE FUNCTION platform_schema.create_queue(queue_name text, options jsonb) RETURNS void
|
||
LANGUAGE plpgsql
|
||
AS $_$
|
||
DECLARE
|
||
tablename varchar := CASE WHEN options->>'partition' = 'true'
|
||
THEN 'j' || encode(sha224(queue_name::bytea), 'hex')
|
||
ELSE 'job_common'
|
||
END;
|
||
queue_created_on timestamptz;
|
||
BEGIN
|
||
|
||
WITH q as (
|
||
INSERT INTO platform_schema.queue (
|
||
name,
|
||
policy,
|
||
retry_limit,
|
||
retry_delay,
|
||
retry_backoff,
|
||
retry_delay_max,
|
||
expire_seconds,
|
||
retention_seconds,
|
||
deletion_seconds,
|
||
warning_queued,
|
||
dead_letter,
|
||
partition,
|
||
table_name
|
||
)
|
||
VALUES (
|
||
queue_name,
|
||
options->>'policy',
|
||
COALESCE((options->>'retryLimit')::int, 2),
|
||
COALESCE((options->>'retryDelay')::int, 0),
|
||
COALESCE((options->>'retryBackoff')::bool, false),
|
||
(options->>'retryDelayMax')::int,
|
||
COALESCE((options->>'expireInSeconds')::int, 900),
|
||
COALESCE((options->>'retentionSeconds')::int, 1209600),
|
||
COALESCE((options->>'deleteAfterSeconds')::int, 604800),
|
||
COALESCE((options->>'warningQueueSize')::int, 0),
|
||
options->>'deadLetter',
|
||
COALESCE((options->>'partition')::bool, false),
|
||
tablename
|
||
)
|
||
ON CONFLICT DO NOTHING
|
||
RETURNING created_on
|
||
)
|
||
SELECT created_on into queue_created_on from q;
|
||
|
||
IF queue_created_on IS NULL OR options->>'partition' IS DISTINCT FROM 'true' THEN
|
||
RETURN;
|
||
END IF;
|
||
|
||
EXECUTE format('CREATE TABLE platform_schema.%I (LIKE platform_schema.job INCLUDING DEFAULTS)', tablename);
|
||
|
||
EXECUTE format('ALTER TABLE platform_schema.%1$I ADD PRIMARY KEY (name, id)', tablename);
|
||
EXECUTE format('ALTER TABLE platform_schema.%1$I ADD CONSTRAINT q_fkey FOREIGN KEY (name) REFERENCES platform_schema.queue (name) ON DELETE RESTRICT DEFERRABLE INITIALLY DEFERRED', tablename);
|
||
EXECUTE format('ALTER TABLE platform_schema.%1$I ADD CONSTRAINT dlq_fkey FOREIGN KEY (dead_letter) REFERENCES platform_schema.queue (name) ON DELETE RESTRICT DEFERRABLE INITIALLY DEFERRED', tablename);
|
||
|
||
EXECUTE format('CREATE INDEX %1$s_i5 ON platform_schema.%1$I (name, start_after) INCLUDE (priority, created_on, id) WHERE state < ''active''', tablename);
|
||
EXECUTE format('CREATE UNIQUE INDEX %1$s_i4 ON platform_schema.%1$I (name, singleton_on, COALESCE(singleton_key, '''')) WHERE state <> ''cancelled'' AND singleton_on IS NOT NULL', tablename);
|
||
|
||
IF options->>'policy' = 'short' THEN
|
||
EXECUTE format('CREATE UNIQUE INDEX %1$s_i1 ON platform_schema.%1$I (name, COALESCE(singleton_key, '''')) WHERE state = ''created'' AND policy = ''short''', tablename);
|
||
ELSIF options->>'policy' = 'singleton' THEN
|
||
EXECUTE format('CREATE UNIQUE INDEX %1$s_i2 ON platform_schema.%1$I (name, COALESCE(singleton_key, '''')) WHERE state = ''active'' AND policy = ''singleton''', tablename);
|
||
ELSIF options->>'policy' = 'stately' THEN
|
||
EXECUTE format('CREATE UNIQUE INDEX %1$s_i3 ON platform_schema.%1$I (name, state, COALESCE(singleton_key, '''')) WHERE state <= ''active'' AND policy = ''stately''', tablename);
|
||
ELSIF options->>'policy' = 'exclusive' THEN
|
||
EXECUTE format('CREATE UNIQUE INDEX %1$s_i6 ON platform_schema.%1$I (name, COALESCE(singleton_key, '''')) WHERE state <= ''active'' AND policy = ''exclusive''', tablename);
|
||
END IF;
|
||
|
||
EXECUTE format('ALTER TABLE platform_schema.%I ADD CONSTRAINT cjc CHECK (name=%L)', tablename, queue_name);
|
||
EXECUTE format('ALTER TABLE platform_schema.job ATTACH PARTITION platform_schema.%I FOR VALUES IN (%L)', tablename, queue_name);
|
||
END;
|
||
$_$;
|
||
|
||
|
||
ALTER FUNCTION platform_schema.create_queue(queue_name text, options jsonb) OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: delete_queue(text); Type: FUNCTION; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE FUNCTION platform_schema.delete_queue(queue_name text) RETURNS void
|
||
LANGUAGE plpgsql
|
||
AS $$
|
||
DECLARE
|
||
v_table varchar;
|
||
v_partition bool;
|
||
BEGIN
|
||
SELECT table_name, partition
|
||
FROM platform_schema.queue
|
||
WHERE name = queue_name
|
||
INTO v_table, v_partition;
|
||
|
||
IF v_partition THEN
|
||
EXECUTE format('DROP TABLE IF EXISTS platform_schema.%I', v_table);
|
||
ELSE
|
||
EXECUTE format('DELETE FROM platform_schema.%I WHERE name = %L', v_table, queue_name);
|
||
END IF;
|
||
|
||
DELETE FROM platform_schema.queue WHERE name = queue_name;
|
||
END;
|
||
$$;
|
||
|
||
|
||
ALTER FUNCTION platform_schema.delete_queue(queue_name text) OWNER TO postgres;
|
||
|
||
SET default_tablespace = '';
|
||
|
||
SET default_table_access_method = heap;
|
||
|
||
--
|
||
-- Name: admin_operation_logs; Type: TABLE; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE admin_schema.admin_operation_logs (
|
||
id integer NOT NULL,
|
||
admin_id text NOT NULL,
|
||
operation_type text NOT NULL,
|
||
target_type text NOT NULL,
|
||
target_id text NOT NULL,
|
||
module text,
|
||
before_data jsonb,
|
||
after_data jsonb,
|
||
ip_address text,
|
||
user_agent text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE admin_schema.admin_operation_logs OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_operation_logs_id_seq; Type: SEQUENCE; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE admin_schema.admin_operation_logs_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE admin_schema.admin_operation_logs_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_operation_logs_id_seq; Type: SEQUENCE OWNED BY; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE admin_schema.admin_operation_logs_id_seq OWNED BY admin_schema.admin_operation_logs.id;
|
||
|
||
|
||
--
|
||
-- Name: conversations; Type: TABLE; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE aia_schema.conversations (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
project_id text,
|
||
agent_id text NOT NULL,
|
||
title text NOT NULL,
|
||
model_name text DEFAULT 'deepseek-v3'::text NOT NULL,
|
||
message_count integer DEFAULT 0 NOT NULL,
|
||
total_tokens integer DEFAULT 0 NOT NULL,
|
||
metadata jsonb,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
deleted_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE aia_schema.conversations OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: general_conversations; Type: TABLE; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE aia_schema.general_conversations (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
title text NOT NULL,
|
||
model_name text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
deleted_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE aia_schema.general_conversations OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: general_messages; Type: TABLE; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE aia_schema.general_messages (
|
||
id text NOT NULL,
|
||
conversation_id text NOT NULL,
|
||
role text NOT NULL,
|
||
content text NOT NULL,
|
||
model text,
|
||
metadata jsonb,
|
||
tokens integer,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE aia_schema.general_messages OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: messages; Type: TABLE; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE aia_schema.messages (
|
||
id text NOT NULL,
|
||
conversation_id text NOT NULL,
|
||
role text NOT NULL,
|
||
content text NOT NULL,
|
||
model text,
|
||
metadata jsonb,
|
||
tokens integer,
|
||
is_pinned boolean DEFAULT false NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE aia_schema.messages OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: projects; Type: TABLE; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE aia_schema.projects (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
name text NOT NULL,
|
||
background text DEFAULT ''::text NOT NULL,
|
||
research_type text DEFAULT 'observational'::text NOT NULL,
|
||
conversation_count integer DEFAULT 0 NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
deleted_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE aia_schema.projects OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: fulltext_screening_results; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.fulltext_screening_results (
|
||
id text NOT NULL,
|
||
task_id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
literature_id text NOT NULL,
|
||
model_a_name text NOT NULL,
|
||
model_a_status text NOT NULL,
|
||
model_a_fields jsonb NOT NULL,
|
||
model_a_overall jsonb NOT NULL,
|
||
model_a_processing_log jsonb,
|
||
model_a_verification jsonb,
|
||
model_a_tokens integer,
|
||
model_a_cost double precision,
|
||
model_a_error text,
|
||
model_b_name text NOT NULL,
|
||
model_b_status text NOT NULL,
|
||
model_b_fields jsonb NOT NULL,
|
||
model_b_overall jsonb NOT NULL,
|
||
model_b_processing_log jsonb,
|
||
model_b_verification jsonb,
|
||
model_b_tokens integer,
|
||
model_b_cost double precision,
|
||
model_b_error text,
|
||
medical_logic_issues jsonb,
|
||
evidence_chain_issues jsonb,
|
||
is_conflict boolean DEFAULT false NOT NULL,
|
||
conflict_severity text,
|
||
conflict_fields text[],
|
||
conflict_details jsonb,
|
||
review_priority integer,
|
||
review_deadline timestamp(3) without time zone,
|
||
final_decision text,
|
||
final_decision_by text,
|
||
final_decision_at timestamp(3) without time zone,
|
||
exclusion_reason text,
|
||
review_notes text,
|
||
processing_status text DEFAULT 'pending'::text NOT NULL,
|
||
is_degraded boolean DEFAULT false NOT NULL,
|
||
degraded_model text,
|
||
processed_at timestamp(3) without time zone,
|
||
prompt_version text DEFAULT 'v1.0.0'::text NOT NULL,
|
||
raw_output_a jsonb,
|
||
raw_output_b jsonb,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.fulltext_screening_results OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: fulltext_screening_tasks; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.fulltext_screening_tasks (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
model_a text NOT NULL,
|
||
model_b text NOT NULL,
|
||
prompt_version text DEFAULT 'v1.0.0'::text NOT NULL,
|
||
status text DEFAULT 'pending'::text NOT NULL,
|
||
total_count integer NOT NULL,
|
||
processed_count integer DEFAULT 0 NOT NULL,
|
||
success_count integer DEFAULT 0 NOT NULL,
|
||
failed_count integer DEFAULT 0 NOT NULL,
|
||
degraded_count integer DEFAULT 0 NOT NULL,
|
||
total_tokens integer DEFAULT 0 NOT NULL,
|
||
total_cost double precision DEFAULT 0 NOT NULL,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone,
|
||
estimated_end_at timestamp(3) without time zone,
|
||
error_message text,
|
||
error_stack text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.fulltext_screening_tasks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: literatures; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.literatures (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
pmid text,
|
||
title text NOT NULL,
|
||
abstract text NOT NULL,
|
||
authors text,
|
||
journal text,
|
||
publication_year integer,
|
||
doi text,
|
||
pdf_url text,
|
||
pdf_oss_key text,
|
||
pdf_file_size integer,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
stage text DEFAULT 'imported'::text NOT NULL,
|
||
has_pdf boolean DEFAULT false NOT NULL,
|
||
pdf_storage_type text,
|
||
pdf_storage_ref text,
|
||
pdf_status text,
|
||
pdf_uploaded_at timestamp(3) without time zone,
|
||
full_text_storage_type text,
|
||
full_text_storage_ref text,
|
||
full_text_url text,
|
||
full_text_format text,
|
||
full_text_source text,
|
||
full_text_token_count integer,
|
||
full_text_extracted_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.literatures OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: screening_projects; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.screening_projects (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
project_name text NOT NULL,
|
||
pico_criteria jsonb NOT NULL,
|
||
inclusion_criteria text NOT NULL,
|
||
exclusion_criteria text NOT NULL,
|
||
status text DEFAULT 'draft'::text NOT NULL,
|
||
screening_config jsonb,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.screening_projects OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: screening_results; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.screening_results (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
literature_id text NOT NULL,
|
||
ds_model_name text NOT NULL,
|
||
ds_p_judgment text,
|
||
ds_i_judgment text,
|
||
ds_c_judgment text,
|
||
ds_s_judgment text,
|
||
ds_conclusion text,
|
||
ds_confidence double precision,
|
||
ds_p_evidence text,
|
||
ds_i_evidence text,
|
||
ds_c_evidence text,
|
||
ds_s_evidence text,
|
||
ds_reason text,
|
||
qwen_model_name text NOT NULL,
|
||
qwen_p_judgment text,
|
||
qwen_i_judgment text,
|
||
qwen_c_judgment text,
|
||
qwen_s_judgment text,
|
||
qwen_conclusion text,
|
||
qwen_confidence double precision,
|
||
qwen_p_evidence text,
|
||
qwen_i_evidence text,
|
||
qwen_c_evidence text,
|
||
qwen_s_evidence text,
|
||
qwen_reason text,
|
||
conflict_status text DEFAULT 'none'::text NOT NULL,
|
||
conflict_fields jsonb,
|
||
final_decision text,
|
||
final_decision_by text,
|
||
final_decision_at timestamp(3) without time zone,
|
||
exclusion_reason text,
|
||
ai_processing_status text DEFAULT 'pending'::text NOT NULL,
|
||
ai_processed_at timestamp(3) without time zone,
|
||
ai_error_message text,
|
||
prompt_version text DEFAULT 'v1.0.0'::text NOT NULL,
|
||
raw_output jsonb,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.screening_results OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: screening_tasks; Type: TABLE; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE asl_schema.screening_tasks (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
task_type text NOT NULL,
|
||
status text DEFAULT 'pending'::text NOT NULL,
|
||
total_items integer NOT NULL,
|
||
processed_items integer DEFAULT 0 NOT NULL,
|
||
success_items integer DEFAULT 0 NOT NULL,
|
||
failed_items integer DEFAULT 0 NOT NULL,
|
||
conflict_items integer DEFAULT 0 NOT NULL,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone,
|
||
estimated_end_at timestamp(3) without time zone,
|
||
error_message text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE asl_schema.screening_tasks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: prompt_templates; Type: TABLE; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE capability_schema.prompt_templates (
|
||
id integer NOT NULL,
|
||
code text NOT NULL,
|
||
name text NOT NULL,
|
||
module text NOT NULL,
|
||
description text,
|
||
variables jsonb,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE capability_schema.prompt_templates OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: prompt_templates_id_seq; Type: SEQUENCE; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE capability_schema.prompt_templates_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE capability_schema.prompt_templates_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: prompt_templates_id_seq; Type: SEQUENCE OWNED BY; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE capability_schema.prompt_templates_id_seq OWNED BY capability_schema.prompt_templates.id;
|
||
|
||
|
||
--
|
||
-- Name: prompt_versions; Type: TABLE; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE capability_schema.prompt_versions (
|
||
id integer NOT NULL,
|
||
template_id integer NOT NULL,
|
||
version integer NOT NULL,
|
||
content text NOT NULL,
|
||
model_config jsonb,
|
||
status capability_schema."PromptStatus" DEFAULT 'DRAFT'::capability_schema."PromptStatus" NOT NULL,
|
||
changelog text,
|
||
created_by text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE capability_schema.prompt_versions OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: prompt_versions_id_seq; Type: SEQUENCE; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE capability_schema.prompt_versions_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE capability_schema.prompt_versions_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: prompt_versions_id_seq; Type: SEQUENCE OWNED BY; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE capability_schema.prompt_versions_id_seq OWNED BY capability_schema.prompt_versions.id;
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_items; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_extraction_items (
|
||
id text NOT NULL,
|
||
task_id text NOT NULL,
|
||
row_index integer NOT NULL,
|
||
original_text text NOT NULL,
|
||
result_a jsonb,
|
||
result_b jsonb,
|
||
status text DEFAULT 'pending'::text NOT NULL,
|
||
conflict_fields text[] DEFAULT ARRAY[]::text[],
|
||
final_result jsonb,
|
||
tokens_a integer DEFAULT 0 NOT NULL,
|
||
tokens_b integer DEFAULT 0 NOT NULL,
|
||
error text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
resolved_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_extraction_items OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_extraction_tasks; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_extraction_tasks (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
project_name text NOT NULL,
|
||
source_file_key text NOT NULL,
|
||
text_column text NOT NULL,
|
||
disease_type text NOT NULL,
|
||
report_type text NOT NULL,
|
||
target_fields jsonb NOT NULL,
|
||
model_a text DEFAULT 'deepseek-v3'::text NOT NULL,
|
||
model_b text DEFAULT 'qwen-max'::text NOT NULL,
|
||
status text DEFAULT 'pending'::text NOT NULL,
|
||
total_count integer DEFAULT 0 NOT NULL,
|
||
processed_count integer DEFAULT 0 NOT NULL,
|
||
clean_count integer DEFAULT 0 NOT NULL,
|
||
conflict_count integer DEFAULT 0 NOT NULL,
|
||
failed_count integer DEFAULT 0 NOT NULL,
|
||
total_tokens integer DEFAULT 0 NOT NULL,
|
||
total_cost double precision DEFAULT 0 NOT NULL,
|
||
error text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_extraction_tasks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_health_checks; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_health_checks (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
file_name text NOT NULL,
|
||
column_name text NOT NULL,
|
||
empty_rate double precision NOT NULL,
|
||
avg_length double precision NOT NULL,
|
||
total_rows integer NOT NULL,
|
||
estimated_tokens integer NOT NULL,
|
||
status text NOT NULL,
|
||
message text NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_health_checks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_templates; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_templates (
|
||
id text NOT NULL,
|
||
disease_type text NOT NULL,
|
||
report_type text NOT NULL,
|
||
display_name text NOT NULL,
|
||
fields jsonb NOT NULL,
|
||
prompt_template text NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_templates OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_tool_c_ai_history; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_tool_c_ai_history (
|
||
id uuid DEFAULT gen_random_uuid() NOT NULL,
|
||
session_id character varying(255) NOT NULL,
|
||
user_id character varying(255) NOT NULL,
|
||
role character varying(50) NOT NULL,
|
||
content text NOT NULL,
|
||
generated_code text,
|
||
code_explanation text,
|
||
execute_status character varying(50),
|
||
execute_result jsonb,
|
||
execute_error text,
|
||
retry_count integer DEFAULT 0,
|
||
model character varying(100),
|
||
created_at timestamp(6) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_tool_c_ai_history OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: dc_tool_c_sessions; Type: TABLE; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE dc_schema.dc_tool_c_sessions (
|
||
id uuid DEFAULT gen_random_uuid() NOT NULL,
|
||
user_id character varying(255) NOT NULL,
|
||
file_name character varying(500) NOT NULL,
|
||
file_key character varying(500) NOT NULL,
|
||
total_rows integer,
|
||
total_cols integer,
|
||
columns jsonb,
|
||
encoding character varying(50),
|
||
file_size integer NOT NULL,
|
||
created_at timestamp(6) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(6) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
expires_at timestamp(6) without time zone NOT NULL,
|
||
data_stats jsonb,
|
||
column_mapping jsonb,
|
||
clean_data_key character varying(1000)
|
||
);
|
||
|
||
|
||
ALTER TABLE dc_schema.dc_tool_c_sessions OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: audit_logs; Type: TABLE; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE iit_schema.audit_logs (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
action_type text NOT NULL,
|
||
entity_type text NOT NULL,
|
||
entity_id text NOT NULL,
|
||
details jsonb,
|
||
trace_id text NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE iit_schema.audit_logs OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: pending_actions; Type: TABLE; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE iit_schema.pending_actions (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
record_id text NOT NULL,
|
||
field_name text NOT NULL,
|
||
current_value jsonb,
|
||
suggested_value jsonb,
|
||
status text NOT NULL,
|
||
agent_type text NOT NULL,
|
||
reasoning text NOT NULL,
|
||
evidence jsonb NOT NULL,
|
||
approved_by text,
|
||
approved_at timestamp(3) without time zone,
|
||
rejection_reason text,
|
||
executed_at timestamp(3) without time zone,
|
||
error_message text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE iit_schema.pending_actions OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: projects; Type: TABLE; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE iit_schema.projects (
|
||
id text NOT NULL,
|
||
name text NOT NULL,
|
||
description text,
|
||
dify_dataset_id text,
|
||
protocol_file_key text,
|
||
cached_rules jsonb,
|
||
field_mappings jsonb NOT NULL,
|
||
redcap_project_id text NOT NULL,
|
||
redcap_api_token text NOT NULL,
|
||
redcap_url text NOT NULL,
|
||
last_sync_at timestamp(3) without time zone,
|
||
status text DEFAULT 'active'::text NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
deleted_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE iit_schema.projects OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: task_runs; Type: TABLE; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE iit_schema.task_runs (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
task_type text NOT NULL,
|
||
job_id text,
|
||
status text NOT NULL,
|
||
total_items integer NOT NULL,
|
||
processed_items integer DEFAULT 0 NOT NULL,
|
||
success_items integer DEFAULT 0 NOT NULL,
|
||
failed_items integer DEFAULT 0 NOT NULL,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone,
|
||
duration integer,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE iit_schema.task_runs OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: user_mappings; Type: TABLE; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE iit_schema.user_mappings (
|
||
id text NOT NULL,
|
||
project_id text NOT NULL,
|
||
system_user_id text NOT NULL,
|
||
redcap_username text NOT NULL,
|
||
wecom_user_id text,
|
||
mini_program_open_id text,
|
||
session_key text,
|
||
role text NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE iit_schema.user_mappings OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: batch_results; Type: TABLE; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE pkb_schema.batch_results (
|
||
id text NOT NULL,
|
||
task_id text NOT NULL,
|
||
document_id text NOT NULL,
|
||
status text NOT NULL,
|
||
data jsonb,
|
||
raw_output text,
|
||
error_message text,
|
||
processing_time_ms integer,
|
||
tokens_used integer,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE pkb_schema.batch_results OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: batch_tasks; Type: TABLE; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE pkb_schema.batch_tasks (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
kb_id text NOT NULL,
|
||
name text NOT NULL,
|
||
template_type text NOT NULL,
|
||
template_id text,
|
||
prompt text NOT NULL,
|
||
status text NOT NULL,
|
||
total_documents integer NOT NULL,
|
||
completed_count integer DEFAULT 0 NOT NULL,
|
||
failed_count integer DEFAULT 0 NOT NULL,
|
||
model_type text NOT NULL,
|
||
concurrency integer DEFAULT 3 NOT NULL,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone,
|
||
duration_seconds integer,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE pkb_schema.batch_tasks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: documents; Type: TABLE; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE pkb_schema.documents (
|
||
id text NOT NULL,
|
||
kb_id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
filename text NOT NULL,
|
||
file_type text NOT NULL,
|
||
file_size_bytes bigint NOT NULL,
|
||
file_url text NOT NULL,
|
||
dify_document_id text NOT NULL,
|
||
status text DEFAULT 'uploading'::text NOT NULL,
|
||
progress integer DEFAULT 0 NOT NULL,
|
||
error_message text,
|
||
segments_count integer,
|
||
tokens_count integer,
|
||
extraction_method text,
|
||
extraction_quality double precision,
|
||
char_count integer,
|
||
language text,
|
||
extracted_text text,
|
||
uploaded_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
processed_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE pkb_schema.documents OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: knowledge_bases; Type: TABLE; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE pkb_schema.knowledge_bases (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
name text NOT NULL,
|
||
description text,
|
||
dify_dataset_id text NOT NULL,
|
||
file_count integer DEFAULT 0 NOT NULL,
|
||
total_size_bytes bigint DEFAULT 0 NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE pkb_schema.knowledge_bases OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: task_templates; Type: TABLE; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE pkb_schema.task_templates (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
name text NOT NULL,
|
||
description text,
|
||
prompt text NOT NULL,
|
||
is_public boolean DEFAULT false NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
"outputFields" jsonb NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE pkb_schema.task_templates OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: app_cache; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.app_cache (
|
||
id integer NOT NULL,
|
||
key character varying(500) NOT NULL,
|
||
value jsonb NOT NULL,
|
||
expires_at timestamp(6) without time zone NOT NULL,
|
||
created_at timestamp(6) without time zone DEFAULT CURRENT_TIMESTAMP
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.app_cache OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: app_cache_id_seq; Type: SEQUENCE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE platform_schema.app_cache_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE platform_schema.app_cache_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: app_cache_id_seq; Type: SEQUENCE OWNED BY; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE platform_schema.app_cache_id_seq OWNED BY platform_schema.app_cache.id;
|
||
|
||
|
||
--
|
||
-- Name: departments; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.departments (
|
||
id text NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
name text NOT NULL,
|
||
parent_id text,
|
||
description text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.departments OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: job; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.job (
|
||
id uuid DEFAULT gen_random_uuid() NOT NULL,
|
||
name text NOT NULL,
|
||
priority integer DEFAULT 0 NOT NULL,
|
||
data jsonb,
|
||
state platform_schema.job_state DEFAULT 'created'::platform_schema.job_state NOT NULL,
|
||
retry_limit integer DEFAULT 2 NOT NULL,
|
||
retry_count integer DEFAULT 0 NOT NULL,
|
||
retry_delay integer DEFAULT 0 NOT NULL,
|
||
retry_backoff boolean DEFAULT false NOT NULL,
|
||
retry_delay_max integer,
|
||
expire_seconds integer DEFAULT 900 NOT NULL,
|
||
deletion_seconds integer DEFAULT 604800 NOT NULL,
|
||
singleton_key text,
|
||
singleton_on timestamp(6) without time zone,
|
||
start_after timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
created_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
started_on timestamp(6) with time zone,
|
||
completed_on timestamp(6) with time zone,
|
||
keep_until timestamp(6) with time zone DEFAULT (now() + '336:00:00'::interval) NOT NULL,
|
||
output jsonb,
|
||
dead_letter text,
|
||
policy text
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.job OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: job_common; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.job_common (
|
||
id uuid DEFAULT gen_random_uuid() NOT NULL,
|
||
name text NOT NULL,
|
||
priority integer DEFAULT 0 NOT NULL,
|
||
data jsonb,
|
||
state platform_schema.job_state DEFAULT 'created'::platform_schema.job_state NOT NULL,
|
||
retry_limit integer DEFAULT 2 NOT NULL,
|
||
retry_count integer DEFAULT 0 NOT NULL,
|
||
retry_delay integer DEFAULT 0 NOT NULL,
|
||
retry_backoff boolean DEFAULT false NOT NULL,
|
||
retry_delay_max integer,
|
||
expire_seconds integer DEFAULT 900 NOT NULL,
|
||
deletion_seconds integer DEFAULT 604800 NOT NULL,
|
||
singleton_key text,
|
||
singleton_on timestamp without time zone,
|
||
start_after timestamp with time zone DEFAULT now() NOT NULL,
|
||
created_on timestamp with time zone DEFAULT now() NOT NULL,
|
||
started_on timestamp with time zone,
|
||
completed_on timestamp with time zone,
|
||
keep_until timestamp with time zone DEFAULT (now() + '336:00:00'::interval) NOT NULL,
|
||
output jsonb,
|
||
dead_letter text,
|
||
policy text
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.job_common OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: permissions; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.permissions (
|
||
id integer NOT NULL,
|
||
code text NOT NULL,
|
||
name text NOT NULL,
|
||
description text,
|
||
module text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.permissions OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: permissions_id_seq; Type: SEQUENCE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE platform_schema.permissions_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE platform_schema.permissions_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: permissions_id_seq; Type: SEQUENCE OWNED BY; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE platform_schema.permissions_id_seq OWNED BY platform_schema.permissions.id;
|
||
|
||
|
||
--
|
||
-- Name: queue; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.queue (
|
||
name text NOT NULL,
|
||
policy text NOT NULL,
|
||
retry_limit integer NOT NULL,
|
||
retry_delay integer NOT NULL,
|
||
retry_backoff boolean NOT NULL,
|
||
retry_delay_max integer,
|
||
expire_seconds integer NOT NULL,
|
||
retention_seconds integer NOT NULL,
|
||
deletion_seconds integer NOT NULL,
|
||
dead_letter text,
|
||
partition boolean NOT NULL,
|
||
table_name text NOT NULL,
|
||
deferred_count integer DEFAULT 0 NOT NULL,
|
||
queued_count integer DEFAULT 0 NOT NULL,
|
||
warning_queued integer DEFAULT 0 NOT NULL,
|
||
active_count integer DEFAULT 0 NOT NULL,
|
||
total_count integer DEFAULT 0 NOT NULL,
|
||
singletons_active text[],
|
||
monitor_on timestamp(6) with time zone,
|
||
maintain_on timestamp(6) with time zone,
|
||
created_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.queue OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: role_permissions; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.role_permissions (
|
||
id integer NOT NULL,
|
||
role platform_schema."UserRole" NOT NULL,
|
||
permission_id integer NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.role_permissions OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: role_permissions_id_seq; Type: SEQUENCE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE platform_schema.role_permissions_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE platform_schema.role_permissions_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: role_permissions_id_seq; Type: SEQUENCE OWNED BY; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE platform_schema.role_permissions_id_seq OWNED BY platform_schema.role_permissions.id;
|
||
|
||
|
||
--
|
||
-- Name: schedule; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.schedule (
|
||
name text NOT NULL,
|
||
key text DEFAULT ''::text NOT NULL,
|
||
cron text NOT NULL,
|
||
timezone text,
|
||
data jsonb,
|
||
options jsonb,
|
||
created_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.schedule OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: subscription; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.subscription (
|
||
event text NOT NULL,
|
||
name text NOT NULL,
|
||
created_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_on timestamp(6) with time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.subscription OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenant_members; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.tenant_members (
|
||
id text NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
role platform_schema."UserRole" NOT NULL,
|
||
joined_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.tenant_members OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenant_modules; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.tenant_modules (
|
||
id text NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
module_code text NOT NULL,
|
||
is_enabled boolean DEFAULT true NOT NULL,
|
||
expires_at timestamp(3) without time zone,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.tenant_modules OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.tenant_quota_allocations (
|
||
id integer NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
target_type text NOT NULL,
|
||
target_key text NOT NULL,
|
||
limit_amount bigint NOT NULL,
|
||
used_amount bigint DEFAULT 0 NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.tenant_quota_allocations OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations_id_seq; Type: SEQUENCE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE platform_schema.tenant_quota_allocations_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE platform_schema.tenant_quota_allocations_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations_id_seq; Type: SEQUENCE OWNED BY; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE platform_schema.tenant_quota_allocations_id_seq OWNED BY platform_schema.tenant_quota_allocations.id;
|
||
|
||
|
||
--
|
||
-- Name: tenant_quotas; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.tenant_quotas (
|
||
id text NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
quota_type text NOT NULL,
|
||
total_amount bigint NOT NULL,
|
||
used_amount bigint DEFAULT 0 NOT NULL,
|
||
reset_period text,
|
||
last_reset_at timestamp(3) without time zone,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.tenant_quotas OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: tenants; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.tenants (
|
||
id text NOT NULL,
|
||
code text NOT NULL,
|
||
name text NOT NULL,
|
||
type platform_schema."TenantType" NOT NULL,
|
||
status platform_schema."TenantStatus" DEFAULT 'ACTIVE'::platform_schema."TenantStatus" NOT NULL,
|
||
config jsonb DEFAULT '{}'::jsonb,
|
||
total_quota bigint DEFAULT 0 NOT NULL,
|
||
used_quota bigint DEFAULT 0 NOT NULL,
|
||
contact_name text,
|
||
contact_phone text,
|
||
contact_email text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL,
|
||
expires_at timestamp(3) without time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.tenants OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: users; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.users (
|
||
id text NOT NULL,
|
||
phone text NOT NULL,
|
||
password text NOT NULL,
|
||
email text,
|
||
is_default_password boolean DEFAULT true NOT NULL,
|
||
password_changed_at timestamp(3) without time zone,
|
||
name text NOT NULL,
|
||
tenant_id text NOT NULL,
|
||
department_id text,
|
||
avatar_url text,
|
||
role platform_schema."UserRole" DEFAULT 'USER'::platform_schema."UserRole" NOT NULL,
|
||
status text DEFAULT 'active'::text NOT NULL,
|
||
kb_quota integer DEFAULT 3 NOT NULL,
|
||
kb_used integer DEFAULT 0 NOT NULL,
|
||
trial_ends_at timestamp(3) without time zone,
|
||
is_trial boolean DEFAULT true NOT NULL,
|
||
last_login_at timestamp(3) without time zone,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.users OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: verification_codes; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.verification_codes (
|
||
id integer NOT NULL,
|
||
phone text NOT NULL,
|
||
code character varying(6) NOT NULL,
|
||
type platform_schema."VerificationType" NOT NULL,
|
||
expires_at timestamp(3) without time zone NOT NULL,
|
||
is_used boolean DEFAULT false NOT NULL,
|
||
attempts integer DEFAULT 0 NOT NULL,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.verification_codes OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: verification_codes_id_seq; Type: SEQUENCE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE platform_schema.verification_codes_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE platform_schema.verification_codes_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: verification_codes_id_seq; Type: SEQUENCE OWNED BY; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE platform_schema.verification_codes_id_seq OWNED BY platform_schema.verification_codes.id;
|
||
|
||
|
||
--
|
||
-- Name: version; Type: TABLE; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE platform_schema.version (
|
||
version integer NOT NULL,
|
||
cron_on timestamp(6) with time zone
|
||
);
|
||
|
||
|
||
ALTER TABLE platform_schema.version OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_logs; Type: TABLE; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE public.admin_logs (
|
||
id integer NOT NULL,
|
||
admin_id text NOT NULL,
|
||
action text NOT NULL,
|
||
resource_type text,
|
||
resource_id text,
|
||
details jsonb,
|
||
ip_address text,
|
||
user_agent text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE public.admin_logs OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_logs_id_seq; Type: SEQUENCE; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE SEQUENCE public.admin_logs_id_seq
|
||
AS integer
|
||
START WITH 1
|
||
INCREMENT BY 1
|
||
NO MINVALUE
|
||
NO MAXVALUE
|
||
CACHE 1;
|
||
|
||
|
||
ALTER TABLE public.admin_logs_id_seq OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_logs_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: postgres
|
||
--
|
||
|
||
ALTER SEQUENCE public.admin_logs_id_seq OWNED BY public.admin_logs.id;
|
||
|
||
|
||
--
|
||
-- Name: users; Type: TABLE; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE public.users (
|
||
id text NOT NULL,
|
||
email text NOT NULL,
|
||
password text NOT NULL,
|
||
name text,
|
||
avatar_url text,
|
||
role text DEFAULT 'user'::text NOT NULL,
|
||
status text DEFAULT 'active'::text NOT NULL,
|
||
kb_quota integer DEFAULT 3 NOT NULL,
|
||
kb_used integer DEFAULT 0 NOT NULL,
|
||
trial_ends_at timestamp(3) without time zone,
|
||
is_trial boolean DEFAULT true NOT NULL,
|
||
last_login_at timestamp(3) without time zone,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE public.users OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: review_tasks; Type: TABLE; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE TABLE rvw_schema.review_tasks (
|
||
id text NOT NULL,
|
||
user_id text NOT NULL,
|
||
file_name text NOT NULL,
|
||
file_size integer NOT NULL,
|
||
file_path text,
|
||
extracted_text text NOT NULL,
|
||
word_count integer,
|
||
status text DEFAULT 'pending'::text NOT NULL,
|
||
selected_agents text[] DEFAULT ARRAY['editorial'::text, 'methodology'::text],
|
||
editorial_review jsonb,
|
||
methodology_review jsonb,
|
||
overall_score double precision,
|
||
editorial_score double precision,
|
||
methodology_score double precision,
|
||
methodology_status text,
|
||
pico_extract jsonb,
|
||
is_archived boolean DEFAULT false NOT NULL,
|
||
archived_at timestamp(3) without time zone,
|
||
model_used text,
|
||
started_at timestamp(3) without time zone,
|
||
completed_at timestamp(3) without time zone,
|
||
duration_seconds integer,
|
||
error_message text,
|
||
created_at timestamp(3) without time zone DEFAULT CURRENT_TIMESTAMP NOT NULL,
|
||
updated_at timestamp(3) without time zone NOT NULL
|
||
);
|
||
|
||
|
||
ALTER TABLE rvw_schema.review_tasks OWNER TO postgres;
|
||
|
||
--
|
||
-- Name: admin_operation_logs id; Type: DEFAULT; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY admin_schema.admin_operation_logs ALTER COLUMN id SET DEFAULT nextval('admin_schema.admin_operation_logs_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: prompt_templates id; Type: DEFAULT; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY capability_schema.prompt_templates ALTER COLUMN id SET DEFAULT nextval('capability_schema.prompt_templates_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: prompt_versions id; Type: DEFAULT; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY capability_schema.prompt_versions ALTER COLUMN id SET DEFAULT nextval('capability_schema.prompt_versions_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: app_cache id; Type: DEFAULT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.app_cache ALTER COLUMN id SET DEFAULT nextval('platform_schema.app_cache_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: permissions id; Type: DEFAULT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.permissions ALTER COLUMN id SET DEFAULT nextval('platform_schema.permissions_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: role_permissions id; Type: DEFAULT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.role_permissions ALTER COLUMN id SET DEFAULT nextval('platform_schema.role_permissions_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations id; Type: DEFAULT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_quota_allocations ALTER COLUMN id SET DEFAULT nextval('platform_schema.tenant_quota_allocations_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: verification_codes id; Type: DEFAULT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.verification_codes ALTER COLUMN id SET DEFAULT nextval('platform_schema.verification_codes_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs id; Type: DEFAULT; Schema: public; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY public.admin_logs ALTER COLUMN id SET DEFAULT nextval('public.admin_logs_id_seq'::regclass);
|
||
|
||
|
||
--
|
||
-- Data for Name: admin_operation_logs; Type: TABLE DATA; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
COPY admin_schema.admin_operation_logs (id, admin_id, operation_type, target_type, target_id, module, before_data, after_data, ip_address, user_agent, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: conversations; Type: TABLE DATA; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
COPY aia_schema.conversations (id, user_id, project_id, agent_id, title, model_name, message_count, total_tokens, metadata, created_at, updated_at, deleted_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: general_conversations; Type: TABLE DATA; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
COPY aia_schema.general_conversations (id, user_id, title, model_name, created_at, updated_at, deleted_at) FROM stdin;
|
||
5c1c1339-f493-42b7-84e8-b7af058745b7 user-mock-001 梳理文档中的主要结局指标 qwen-long 2026-01-11 05:01:54.262 2026-01-11 05:02:07.672 \N
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: general_messages; Type: TABLE DATA; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
COPY aia_schema.general_messages (id, conversation_id, role, content, model, metadata, tokens, created_at) FROM stdin;
|
||
8b0a39d7-f7da-4164-a823-c8b4b00cd955 5c1c1339-f493-42b7-84e8-b7af058745b7 user 梳理文档中的主要结局指标 \N {"knowledgeBaseIds": ["f8cf82ff-9b59-4f0e-babc-55542b33102e"]} \N 2026-01-11 05:01:54.279
|
||
3c74680c-3466-4f10-8ddb-aacf177630ec 5c1c1339-f493-42b7-84e8-b7af058745b7 assistant 根据【文献1】，该研究的主要结局指标（outcome measures）包括以下三项经过验证的临床评估工具，用于评价阿尔茨海默病患者在治疗前后的认知功能、整体病情变化及临床疗效：\n\n1. **简易精神状态检查（Mini-Mental State Examination, MMSE）** \n - 用于评估患者的总体认知功能。纳入标准为基线MMSE得分在13至25分之间，表明为轻度至中度痴呆。 \n - 结果显示：EGb 761组和多奈哌齐（donepezil）组在24周后MMSE评分均有轻微改善，而安慰剂组略有下降，但组内和组间差异均未达到统计学显著性【文献1】。\n\n2. **Syndrom Kurz测试（SKT）** \n - 是一种评估记忆与注意力的心理测验量表，总分范围为1（极好）至27（极差），分数越高表示认知功能越差。 \n - 纳入标准为SKT得分在8–23分之间。 \n - 结果显示：EGb 761组和多奈哌齐组在24周后SKT评分显著改善（分别下降3.3分），且与安慰剂组相比差异具有高度统计学意义（P < 0.001），而两活性药物组之间无显著差异【文献1】。\n\n3. **临床总体印象量表第2项（Clinical Global Impression-2, CGI-2）** \n - 用于评估患者从基线到治疗结束的整体病情变化，评分范围为1（极大改善）至7（极大恶化）。 \n - 结果显示：EGb 761组和多奈哌齐组的CGI评分均显著改善（平均降低0.9分），与安慰剂组相比差异显著（P < 0.001），但两种药物之间无显著差异【文献1】。\n\n综上所述，本研究的主要结局指标为：\n- **MMSE评分的变化**\n- **SKT评分的变化**\n- **CGI-2评分的变化**\n\n其中，SKT和CGI-2的结果显示出EGb 761（银杏叶提取物）与多奈哌齐在治疗轻至中度阿尔茨海默病方面具有相当的临床疗效，而MMSE虽呈现类似趋势，但未达统计学显著性【文献1】。这些结果支持银杏叶提取物EGb 761作为阿尔茨海默病的一种有效且耐受性良好的治疗选择。\n\n---\n\n📚 **参考文献**\n\n<span id="citation-detail-1">[1]</span> 📄 **Ginkgo_biloba_and_donepezil_a_comparison_in_the_treatment_of_Alzheimer's_dementia_in_a_randomized_pl1.pdf** - 第0段 (相关度100%)\n "--- 第 1 页 --- Ginkgo biloba and donepezil: a comparison in the treatment of Alzheimer’s dementia in ..."\n\n qwen-long {"usage": {"totalTokens": 7394, "promptTokens": 6831, "completionTokens": 563}} 7394 2026-01-11 05:02:07.67
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: messages; Type: TABLE DATA; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
COPY aia_schema.messages (id, conversation_id, role, content, model, metadata, tokens, is_pinned, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: projects; Type: TABLE DATA; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
COPY aia_schema.projects (id, user_id, name, background, research_type, conversation_count, created_at, updated_at, deleted_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: fulltext_screening_results; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.fulltext_screening_results (id, task_id, project_id, literature_id, model_a_name, model_a_status, model_a_fields, model_a_overall, model_a_processing_log, model_a_verification, model_a_tokens, model_a_cost, model_a_error, model_b_name, model_b_status, model_b_fields, model_b_overall, model_b_processing_log, model_b_verification, model_b_tokens, model_b_cost, model_b_error, medical_logic_issues, evidence_chain_issues, is_conflict, conflict_severity, conflict_fields, conflict_details, review_priority, review_deadline, final_decision, final_decision_by, final_decision_at, exclusion_reason, review_notes, processing_status, is_degraded, degraded_model, processed_at, prompt_version, raw_output_a, raw_output_b, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: fulltext_screening_tasks; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.fulltext_screening_tasks (id, project_id, model_a, model_b, prompt_version, status, total_count, processed_count, success_count, failed_count, degraded_count, total_tokens, total_cost, started_at, completed_at, estimated_end_at, error_message, error_stack, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: literatures; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.literatures (id, project_id, pmid, title, abstract, authors, journal, publication_year, doi, pdf_url, pdf_oss_key, pdf_file_size, created_at, updated_at, stage, has_pdf, pdf_storage_type, pdf_storage_ref, pdf_status, pdf_uploaded_at, full_text_storage_type, full_text_storage_ref, full_text_url, full_text_format, full_text_source, full_text_token_count, full_text_extracted_at) FROM stdin;
|
||
646ea68a-9b5b-476c-9493-fbf2f60ecc4d f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Efficacy and safety of argatroban in the management of acute ischemic stroke: A systematic literature review and meta-analysis BACKGROUND: Acute ischemic stroke (AIS) is a leading cause of death and disability. AIS is caused by an embolus or thrombus that restricts blood flow to the brain tissue. Despite intravenous thrombolysis and endovascular thrombectomy, a substantial number of patients do not achieve effective reperfusion. Argatroban, a direct thrombin inhibitor, can potentially improve neurological outcomes in AIS patients. However, there are conflicting results in the medical literature regarding the efficacy and safety of argatroban in this context. OBJECTIVE: This study aims to evaluate the efficacy and safety of argatroban as monotherapy or adjunct therapy for acute ischemic stroke. METHODS: Five major databases (PubMed, Embase, Scopus, Web of Science, and Cochrane Library) were searched for randomized controlled trials (RCTs) that compared the efficacy and safety of using argatroban alone or in combination with recombinant tissue plasminogen activator (r-TPA) in the management protocol of the AIS. We used Review Manager Software (RevMan 5.4.1) for data analysis. RESULTS: We included 1393 patients from eight RCTs (of them, 726 were treated with argatroban alone or combined with r-TPA, while 667 received the placebo, standard therapy (standard treatments based on current guidelines including antihypertensive, antiplatelet agents, and statins) or endovascular r-TPA). Neither argatroban vs control nor argatroban with r-TPA vs r-TPA showed significant difference regarding the activity in daily living; (SMD= 1.69, 95% CI [-0.23, 3.61]; p = 0.09), (SMD= 0.99, 95% CI [-0.88, 2.86]; p = 0.30), respectively. Also, there was no significant difference in the National Institutes of Health Stroke Scale (NIHSS) score at seven days, the number of patients achieving modified Rankin Scale (mRS) of 0-1 or 0-2 at 90 days (p > 0.05). Argatroban did not significantly increase the risk of adverse events or symptomatic intracranial hemorrhage (ICH), or major systemic bleeding compared to control or r-TPA (p > 0.05) CONCLUSIONS: Argatroban does not demonstrate superior efficacy compared to placebo or standard therapy in terms of ADL, NIHSS and mRS outcomes. Importantly, argatroban does not significantly increase the incidence of adverse events, including symptomatic ICH and systemic bleeding. Al-Salihi, M. M. and Saha, R. and Ayyad, A. and Al-Jebur, M. S. and Al-Salihi, Y. and Roy, A. and Dalal, S. S. and Rivet, D. and Spiotta, A. M. and Qureshi, A. I. Clinical neurology and neurosurgery 2024 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
4dca5bcb-0f81-4a3a-864d-2fe2277f8d8f f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Intravenous Thrombolysis in Patients With Ischemic Stroke Aged ≥90 Years: A Cohort Study From the TRISP Collaboration BACKGROUND: The probability to receive intravenous thrombolysis (IVT) for treatment of acute ischemic stroke declines with increasing age and is consequently the lowest in very elderly patients. Safety concerns likely influence individual IVT treatment decisions. Using data from a large IVT registry, we aimed to provide more evidence on safety of IVT in the very elderly. METHODS: In this prospective multicenter study from the TRISP (Thrombolysis in Ischemic Stroke Patients) registry, we compared patients ≥90 years with those <90 years using symptomatic intracranial hemorrhage (ECASS [European Cooperative Acute Stroke Study]-II criteria), death, and poor functional outcome in survivors (modified Rankin Scale score 3-5 for patients with prestroke modified Rankin Scale score ≤2 and modified Rankin Scale score 4-5 for patients prestroke modified Rankin Scale ≥3) at 3 months as outcomes. We calculated adjusted odds ratio with 95% CI using logistic regression models. RESULTS: Of 16 974 eligible patients, 976 (5.7%) were ≥90 years. Patients ≥90 years had higher median National Institutes of Health Stroke Scale on admission (12 versus 8) and were more often dependent prior to the index stroke (prestroke modified Rankin Scale score of ≥3; 45.2% versus 7.4%). Occurrence of symptomatic intracranial hemorrhage (5.7% versus 4.4%, odds ratio(adjusted) 1.14 [0.83-1.57]) did not differ significantly between both groups. However, the probability of death (odds ratio(adjusted) 3.77 [3.14-4.53]) and poor functional outcome (odds ratio(adjusted) 2.63 [2.13-3.25]) was higher in patients aged ≥90 years. Results for the sample of centenarians (n=21) were similar. CONCLUSIONS: The probability of symptomatic intracranial hemorrhage after IVT in very elderly patients with stroke did not exceed that of their younger counterparts. The higher probability of death and poor functional outcome during follow-up in the very elderly seems not to be related to IVT treatment. Very high age itself should not be a reason to withhold IVT. Altersberger, V. L. and Rusche, N. and Martinez-Majander, N. and Hametner, C. and Scheitz, J. F. and Henon, H. and Dell'Acqua, M. L. and Strambo, D. and Stolp, J. and Heldner, M. R. and Grisendi, I. and Jovanovic, D. R. and Bejot, Y. and Pezzini, A. and Leker, R. R. and Kägi, G. and Wegener, S. and Cereda, C. W. and Lindgren, E. and Ntaios, G. and Piot, I. and Polymeris, A. A. and Lyrer, P. A. and Räty, S. and Sibolt, G. and Tiainen, M. and Heyse, M. and Erdur, H. and Kaaouana, O. and Padjen, V. and Zedde, M. and Arnold, M. and Nederkoorn, P. J. and Michel, P. and Bigliardi, G. and Zini, A. and Cordonnier, C. and Nolte, C. H. and Ringleb, P. A. and Curtze, S. and Engelter, S. T. and Gensicke, H. Stroke 2022 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
68056539-873f-4582-847b-56a9febf4570 f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Intravenous Thrombolysis 4.5-9 Hours After Stroke Onset: A Cohort Study from the TRISP Collaboration OBJECTIVE: To investigate the safety and effectiveness of intravenous thrombolysis (IVT) >4.5-9 hours after stroke onset, and the relevance of advanced neuroimaging for patient selection. METHODS: Prospective multicenter cohort study from the ThRombolysis in Ischemic Stroke Patients (TRISP) collaboration. Outcomes were symptomatic intracranial hemorrhage, poor 3-month functional outcome (modified Rankin scale 3-6) and mortality. We compared: (i) IVT >4.5-9 hours versus 0-4.5 hours after stroke onset and (ii) within the >4.5-9 hours group baseline advanced neuroimaging (computed tomography perfusion, magnetic resonance perfusion or magnetic resonance diffusion-weighted imaging fluid-attenuated inversion recovery) versus non-advanced neuroimaging. RESULTS: Of 15,827 patients, 663 (4.2%) received IVT >4.5-9 hours and 15,164 (95.8%) within 4.5 hours after stroke onset. The main baseline characteristics were evenly distributed between both groups. Time of stroke onset was known in 74.9% of patients treated between >4.5 and 9 hours. Using propensity score weighted binary logistic regression analysis (onset-to-treatment time >4.5-9 hours vs onset-to-treatment time 0-4.5 hours), the probability of symptomatic intracranial hemorrhage (OR(adjusted) 0.80, 95% CI 0.53-1.17), poor functional outcome (OR(adjusted) 1.01, 95% CI 0.83-1.22), and mortality (OR(adjusted) 0.80, 95% CI 0.61-1.04) did not differ significantly between both groups. In patients treated between >4.5 and 9 hours, the use of advanced neuroimaging was associated with a 50% lower mortality compared with non-advanced imaging only (9.9% vs 19.7%; OR(adjusted) 0.51, 95% CI 0.33-0.79). INTERPRETATION: This study showed no evidence in difference of symptomatic intracranial hemorrhage, poor outcome, and mortality in selected stroke patients treated with IVT between >4.5 and 9 hours after stroke onset compared with those treated within 4.5 hours. Advanced neuroimaging for patient selection was associated with lower mortality. ANN NEUROL 2023;94:309-320. Altersberger, V. L. and Sibolt, G. and Enz, L. S. and Hametner, C. and Scheitz, J. F. and Henon, H. and Bigliardi, G. and Strambo, D. and Martinez-Majander, N. and Stolze, L. J. and Heldner, M. R. and Grisendi, I. and Jovanovic, D. R. and Bejot, Y. and Pezzini, A. and Leker, R. R. and Kägi, G. and Wegener, S. and Cereda, C. W. and Ntaios, G. and De Marchis, G. M. and Bonati, L. H. and Psychogios, M. and Lyrer, P. and Räty, S. and Tiainen, M. and Wouters, A. and Caparros, F. and Heyse, M. and Erdur, H. and Padjen, V. and Zedde, M. and Arnold, M. and Nederkoorn, P. J. and Michel, P. and Zini, A. and Cordonnier, C. and Nolte, C. H. and Ringleb, P. A. and Curtze, S. and Engelter, S. T. and Gensicke, H. Annals of neurology 2023 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
bda7e5dd-287f-4d73-95a8-84cf5532b5d5 f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Characteristics, clinical profiles, and outcomes of patients undergoing endovascular thrombectomy: A retrospective study, Saudi Arabia BACKGROUND: Stroke is a significant contributor to both mortality and compromised physical function. Endovascular thrombectomy (EVT) is now the recognized standard of care for anterior circulation acute ischemic stroke (AIS) with large vessel occlusion (LVO), especially when favorable brain images are evident within 24 h of symptom onset. This study elucidated the characteristics, clinical profiles, and outcomes of patients who underwent EVT for AIS. METHODOLOGY: In this retrospective record-based cohort study, we reviewed the medical records of individuals who underwent EVT for AIS at King Fahad General Hospital in Jeddah, Saudi Arabia. The study, conducted from July 2022 through October 2023, encompassed a comprehensive analysis of clinical, radiological, and time-related factors and diverse outcomes. RESULTS: In a cohort of 117 patients with a mean age of 58.5 years, 81 (69.2%) were male. Hypertension and diabetes mellitus were the most common risk factors, affecting 48.7% and 41% of the cohort, respectively. Approximately half of the patients had a favorable ASPECT Score (7-10), and 45.3% received intravenous tissue plasminogen activator (tPA). Nearly two-thirds achieved a modified thrombolysis in cerebral infarction (mTICI) score of 2b or higher, and 39.3% exhibited M1-middle cerebral artery (MCA) occlusion. The incidence of symptomatic hemorrhagic transformation was about 13%, whereas one-third of the patients attained a favorable mRs outcome (0-2). Factors such as advanced age, higher NIH Stroke Scale (NIHSS) scores, and prolonged hospital stays were associated with poorer outcomes. Conversely, the absence of hypertension and atrial fibrillation, along with higher TICI scores, significantly increased the likelihood of favorable outcomes, with P values of 0.015, 0.0490, and 0.025, respectively. CONCLUSIONS: In our study, the examined patients who underwent EVT were younger in age, with clinical and radiological outcomes showing some degree of comparability to other publications. Notably, the absence of hypertension and atrial fibrillation, combined with a higher TICI score, was associated with an increased likelihood of achieving a favorable outcome. Althobaiti, F. A. and Alqahtani, M. S. and Alharbi, N. F. and Alwadai, M. M. and Alkhatib, A. H. and Asiri, M. A. and Maghrabi, R. I. and Alnahari, E. A. and Alqarni, A. H. and Alzahrani, S. S. Journal of Taibah University Medical Sciences 2024 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
de9db261-92f5-473d-add4-1fb9c3e09fc9 f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Ticagrelor Added to Aspirin in Acute Ischemic Stroke or Transient Ischemic Attack in Prevention of Disabling Stroke: A Randomized Clinical Trial IMPORTANCE: Reduction of subsequent disabling stroke is the main goal of preventive treatment in the acute setting after transient ischemic attack (TIA) or minor ischemic stroke. OBJECTIVE: To evaluate the superiority of ticagrelor added to aspirin in preventing disabling stroke and to understand the factors associated with recurrent disabling stroke. DESIGN, SETTING, AND PARTICIPANTS: The Acute Stroke or Transient Ischemic Attack Treated With Ticagrelor and Aspirin for Prevention of Stroke and Death (THALES) was a randomized clinical trial conducted between January 22, 2018, and December 13, 2019, with a 30-day follow-up, at 414 hospitals in 28 countries. The trial included 11 016 patients with a noncardioembolic, nonsevere ischemic stroke or high-risk TIA, including 10 803 with modified Rankin Scale score (mRS) recorded at 30 days. INTERVENTIONS: Ticagrelor (180-mg loading dose on day 1 followed by 90 mg twice daily for days 2-30) or placebo within 24 hours of symptom onset. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30. MAIN OUTCOMES AND MEASURES: Time to the occurrence of disabling stroke (progression of index event or new stroke) or death within 30 days, as measured by mRS at day 30. Disabling stroke was defined by mRS greater than 1. RESULTS: Among participants with 30-day mRS greater than 1, mean age was 68.1 years, 1098 were female (42.6%), and 2670 had an ischemic stroke (95.8%) as a qualifying event. Among 11 016 patients, a primary end point with mRS greater than 1 at 30 days occurred in 221 of 5511 patients (4.0%) randomized to ticagrelor and in 260 of 5478 patients (4.7%) randomized to placebo (hazard ratio [HR], 0.83; 95% CI, 0.69-0.99, P = .04). A primary end point with mRS 0 or 1 at 30 days occurred in 70 of 5511 patients (1.3%) and 87 of 5478 patients (1.6%) (HR, 0.79; 95% CI, 0.57-1.08; P = .14). The ordinal analysis of mRS in patients with recurrent stroke showed a shift of the disability burden following a recurrent ischemic stroke in favor of ticagrelor (odds ratio, 0.77; 95% CI, 0.65-0.91; P = .002). Factors associated with disability were baseline National Institutes of Health Stroke Scale score 4 to 5, ipsilateral stenosis of at least 30%, Asian race/ethnicity, older age, and higher systolic blood pressure, while treatment with ticagrelor was associated with less disability. CONCLUSIONS AND RELEVANCE: In patients with TIA and minor ischemic stroke, ticagrelor added to aspirin was superior to aspirin alone in preventing disabling stroke or death at 30 days and reduced the total burden of disability owing to ischemic stroke recurrence. TRIAL REGISTRATION: ClinicalTrials.gov Identifier: NCT03354429. Amarenco, P. and Denison, H. and Evans, S. R. and Himmelmann, A. and James, S. and Knutsson, M. and Ladenvall, P. and Molina, C. A. and Wang, Y. and Johnston, S. C. JAMA neurology 2020 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
305fb512-91e2-4def-af45-bb3de70c578e f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Remote ischemic conditioning improves cerebral hemodynamics in symptomatic intracranial atherosclerosis: A PET/CT-guided randomized controlled study Patients with symptomatic intracranial arterial stenosis (sICAS) suffer embarrassed hemodynamic status and acute ischemic stroke (AIS) recurrence. We aimed to assess the efficacy of remote ischemic conditioning (RIC) on improving this status by evaluating cerebral blood flow (CBF) and cerebral glucose metabolism (CGM) via PET/CT. Adult patients with unilateral sICAS in middle cerebral artery and/or intracranial segment of internal carotid artery-related AIS or transient ischemic attack within 6 months prior to randomization were enrolled. Individuals who received intravenous thrombolysis or endovascular treatment, or sICAS caused by cardiac embolism, small vessel occlusion, or other determined causes were excluded. Twenty-three eligible patients were randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13). The RIC protocol consisted of 5 cycles, each for 5-min bilateral upper limb ischemia and 5-min reperfusion period, twice a day, with a total duration of 3 months. Ten healthy volunteers were enrolled as healthy control group. We tested CBF and CGM at the rest stage and the methazolamide-induced stress stage. All patients received PET/CT at baseline and three-month followup. Both CBF and CGM in ipsilateral hemisphere of sICAS patients were significantly decreased at the rest stage and the stress stage (p < .05), which were improved by three-month RIC (p < .05). The lesions decreased notably in RIC group compared to SMT group (p < .05). RIC ameliorated the hemodynamic status and glucose metabolism in regions at high risk of infarction, which might improve the resistance capacity towards ischemic load in sICAS patients. An, H. and Ma, H. and Wu, C. and Cui, C. and Wu, L. and Zhao, W. and Cui, B. and Li, S. and Wu, D. and Hu, W. and Ji, X. Journal of neuroscience research 2024 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
26f8af79-1536-4a6d-8338-dc74d78786b2 f0d3c742-fa2e-487a-a6d0-6b544df396ba \N Blood pressure reduction and outcome after endovascular therapy with successful reperfusion: a multicenter study BACKGROUND: Elevated systolic blood pressure (SBP) after mechanical thrombectomy (MT) correlates with worse outcome. However, the association between SBP reduction (SBPr) and outcome after successful reperfusion with MT is not well established. OBJECTIVE: To investigate the association between SBPr in the first 24 hours after successful reperfusion and the functional and safety outcomes of MT. METHODS: A multicenter retrospective study, which included 10 comprehensive stroke centers, was carried out. Patients with acute ischemic stroke and anterior circulation large vessel occlusions who achieved successful reperfusion via MT were included. SBPr was calculated using the formula 100×([admission SBP-mean SBP]/admission SBP). Poor outcome was defined as a modified Rankin Scale (mRS) score of 3-6 at 90 days. Safety endpoints included symptomatic intracerebral hemorrhage, mortality, and requirement for hemicraniectomy during admission. A generalized mixed linear model was used to study the association between SBPr and outcomes. RESULTS: A total of 1361 patients were included in the final analysis. SBPr as a continuous variable was inversely associated with poor outcome (OR=0.97; 95% CI 0.95 to 0.98; p<0.001) but not with the safety outcomes. Subanalysis based on reperfusion status showed that SBPr was associated with lower odds of poor outcome only in patients with complete reperfusion (modified Thrombolysis in Cerebral Infarction (mTICI 3)) but not in patients with incomplete reperfusion (mTICI 2b). When SBPr was divided into categories (<1%, 1%-10%, 11%-20%, >20%), the rate of poor outcome was highest in the first group. CONCLUSION: SBPr in the first 24 hours after successful reperfusion was inversely associated with poor outcome. No association between SBPr and safety outcome was found. Anadani, M. and Arthur, A. S. and Alawieh, A. and Orabi, Y. and Alexandrov, A. and Goyal, N. and Psychogios, M. N. and Maier, I. and Kim, J. T. and Keyrouz, S. G. and de Havenon, A. and Petersen, N. H. and Pandhi, A. and Swisher, C. B. and Inamullah, O. and Liman, J. and Kodali, S. and Giles, J. A. and Allen, M. and Wolfe, S. Q. and Tsivgoulis, G. and Cagle, B. A. and Oravec, C. S. and Gory, B. and De Marini, P. and Kan, P. and Rahman, S. and Richard, S. and Nascimento, F. A. and Spiotta, A. Journal of neurointerventional surgery 2020 \N \N \N \N 2026-01-11 05:06:30.054 2026-01-11 05:06:30.054 imported f \N \N \N \N \N \N \N \N \N \N \N
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: screening_projects; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.screening_projects (id, user_id, project_name, pico_criteria, inclusion_criteria, exclusion_criteria, status, screening_config, created_at, updated_at) FROM stdin;
|
||
f0d3c742-fa2e-487a-a6d0-6b544df396ba asl-test-user-001 标题摘要初筛 - 2026/1/11 {"C": "骨质疏松", "I": "骨质疏松", "O": "骨质疏松", "P": "骨质疏松", "S": "真实世界研究"} 骨质疏松 心衰 draft {"style": "standard", "models": ["DeepSeek-V3", "Qwen-Max"]} 2026-01-11 05:06:30.031 2026-01-11 05:06:30.031
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: screening_results; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.screening_results (id, project_id, literature_id, ds_model_name, ds_p_judgment, ds_i_judgment, ds_c_judgment, ds_s_judgment, ds_conclusion, ds_confidence, ds_p_evidence, ds_i_evidence, ds_c_evidence, ds_s_evidence, ds_reason, qwen_model_name, qwen_p_judgment, qwen_i_judgment, qwen_c_judgment, qwen_s_judgment, qwen_conclusion, qwen_confidence, qwen_p_evidence, qwen_i_evidence, qwen_c_evidence, qwen_s_evidence, qwen_reason, conflict_status, conflict_fields, final_decision, final_decision_by, final_decision_at, exclusion_reason, ai_processing_status, ai_processed_at, ai_error_message, prompt_version, raw_output, created_at, updated_at) FROM stdin;
|
||
a347c958-e97f-4442-a21e-c2095db2ce25 f0d3c742-fa2e-487a-a6d0-6b544df396ba 646ea68a-9b5b-476c-9493-fbf2f60ecc4d deepseek-chat mismatch mismatch mismatch match exclude 0.95 Acute ischemic stroke (AIS) patients Argatroban, a direct thrombin inhibitor placebo, standard therapy (standard treatments based on current guidelines including antihypertensive, antiplatelet agents, and statins) or endovascular r-TPA randomized controlled trials (RCTs) 该文献应被排除。首先,研究人群（P）为急性缺血性卒中患者,与纳入标准“骨质疏松”完全不匹配。其次,干预措施（I）为直接凝血酶抑制剂阿加曲班,用于治疗卒中,与骨质疏松的干预无关。对照（C）为安慰剂、标准疗法或血管内r-TPA,也与骨质疏松研究无关。研究设计（S）为随机对照试验,虽然匹配,但其他核心PICO维度均不匹配。此外,文献未提及骨质疏松,也未触发排除标准“心衰”。因此,该文献与研究方案的主题完全无关,应直接排除。 qwen-max mismatch mismatch mismatch match exclude 0.95 研究人群为急性缺血性卒中（AIS）患者:"Acute ischemic stroke (AIS) is a leading cause of death and disability. AIS is caused by an embolus or thrombus that restricts blood flow to the brain tissue." 干预措施为阿加曲班单独使用或与重组组织型纤溶酶原激活剂（r-TPA）联合使用:"This study aims to evaluate the efficacy and safety of argatroban as monotherapy or adjunct therapy for acute ischemic stroke." 对照组为安慰剂、标准治疗（包括抗高血压药物、抗血小板药物和他汀类药物）或血管内r-TPA:"We included 1393 patients from eight RCTs (of them, 726 were treated with argatroban alone or combined with r-TPA, while 667 received the placebo, standard therapy (standard treatments based on current guidelines including antihypertensive, antiplatelet agents, and statins) or endovascular r-TPA)." 研究设计为系统综述和Meta分析:"Efficacy and safety of argatroban in the management of acute ischemic stroke: A systematic literature review and meta-analysis" 该文献的研究人群为急性缺血性卒中患者,而非骨质疏松患者；干预措施为阿加曲班及其与r-TPA的联合使用,与方案中的干预措施不匹配；对照组为安慰剂、标准治疗或血管内r-TPA,与方案中的对照标准不符。此外,该文献为系统综述和Meta分析,通常情况下这类文献会被排除。因此,根据PICO标准及纳排标准,该文献应被排除。 none \N exclude \N \N \N completed 2026-01-11 05:06:45.801 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究人群为急性缺血性卒中患者,而非骨质疏松患者；干预措施为阿加曲班及其与r-TPA的联合使用,与方案中的干预措施不匹配；对照组为安慰剂、标准治疗或血管内r-TPA,与方案中的对照标准不符。此外,该文献为系统综述和Meta分析,通常情况下这类文献会被排除。因此,根据PICO标准及纳排标准,该文献应被排除。", "evidence": {"C": "对照组为安慰剂、标准治疗（包括抗高血压药物、抗血小板药物和他汀类药物）或血管内r-TPA:\\"We included 1393 patients from eight RCTs (of them, 726 were treated with argatroban alone or combined with r-TPA, while 667 received the placebo, standard therapy (standard treatments based on current guidelines including antihypertensive, antiplatelet agents, and statins) or endovascular r-TPA).\\"", "I": "干预措施为阿加曲班单独使用或与重组组织型纤溶酶原激活剂（r-TPA）联合使用:\\"This study aims to evaluate the efficacy and safety of argatroban as monotherapy or adjunct therapy for acute ischemic stroke.\\"", "P": "研究人群为急性缺血性卒中（AIS）患者:\\"Acute ischemic stroke (AIS) is a leading cause of death and disability. AIS is caused by an embolus or thrombus that restricts blood flow to the brain tissue.\\"", "S": "研究设计为系统综述和Meta分析:\\"Efficacy and safety of argatroban in the management of acute ischemic stroke: A systematic literature review and meta-analysis\\""}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.95}, "deepseek": {"reason": "该文献应被排除。首先,研究人群（P）为急性缺血性卒中患者,与纳入标准“骨质疏松”完全不匹配。其次,干预措施（I）为直接凝血酶抑制剂阿加曲班,用于治疗卒中,与骨质疏松的干预无关。对照（C）为安慰剂、标准疗法或血管内r-TPA,也与骨质疏松研究无关。研究设计（S）为随机对照试验,虽然匹配,但其他核心PICO维度均不匹配。此外,文献未提及骨质疏松,也未触发排除标准“心衰”。因此,该文献与研究方案的主题完全无关,应直接排除。", "evidence": {"C": "placebo, standard therapy (standard treatments based on current guidelines including antihypertensive, antiplatelet agents, and statins) or endovascular r-TPA", "I": "Argatroban, a direct thrombin inhibitor", "P": "Acute ischemic stroke (AIS) patients", "S": "randomized controlled trials (RCTs)"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:06:45.804 2026-01-11 05:06:45.804
|
||
b2f164de-5774-4922-8661-1027beab9f3d f0d3c742-fa2e-487a-a6d0-6b544df396ba 4dca5bcb-0f81-4a3a-864d-2fe2277f8d8f deepseek-chat mismatch mismatch mismatch mismatch exclude 0.95 patients with ischemic stroke intravenous thrombolysis (IVT) for treatment of acute ischemic stroke compared patients ≥90 years with those <90 years cohort study 这篇文献应被排除。首先,PICO标准完全未定义,无法进行有效匹配。其次,文献的研究人群（P）是缺血性卒中患者,干预措施（I）是静脉溶栓,对照（C）是不同年龄组的比较,研究设计（S）是队列研究。这些内容与给定的纳入标准“骨质疏松”完全无关,属于明确的不匹配。同时,文献主题（卒中）与排除标准“心衰”也无直接关联,但鉴于研究主题与纳入标准完全不符,无需进一步考虑排除标准。因此,基于PICO的全面不匹配,做出排除决策。 qwen-max mismatch mismatch mismatch partial exclude 0.9 Of 16 974 eligible patients, 976 (5.7%) were ≥90 years. Patients ≥90 years had higher median National Institutes of Health Stroke Scale on admission (12 versus 8) and were more often dependent prior to the index stroke (prestroke modified Rankin Scale score of ≥3; 45.2% versus 7.4%). The probability to receive intravenous thrombolysis (IVT) for treatment of acute ischemic stroke declines with increasing age and is consequently the lowest in very elderly patients. We compared patients ≥90 years with those <90 years using symptomatic intracranial hemorrhage (ECASS [European Cooperative Acute Stroke Study]-II criteria), death, and poor functional outcome in survivors (modified Rankin Scale score 3-5 for patients with prestroke modified Rankin Scale score ≤2 and modified Rankin Scale score 4-5 for patients prestroke modified Rankin Scale ≥3) at 3 months as outcomes. In this prospective multicenter study from the TRISP (Thrombolysis in Ischemic Stroke Patients) registry, we compared patients ≥90 years with those <90 years. 该文献的研究人群为≥90岁的急性缺血性脑卒中患者,不符合方案中的研究人群（未定义但应关注骨质疏松患者）。干预措施为静脉溶栓治疗,与方案中的干预措施不匹配。对照组为<90岁的患者,也不符合方案中的对照标准。虽然研究设计为前瞻性多中心队列研究,但其他PICO标准均不匹配,因此排除该文献。 none \N exclude \N \N \N completed 2026-01-11 05:07:01.278 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究人群为≥90岁的急性缺血性脑卒中患者,不符合方案中的研究人群（未定义但应关注骨质疏松患者）。干预措施为静脉溶栓治疗,与方案中的干预措施不匹配。对照组为<90岁的患者,也不符合方案中的对照标准。虽然研究设计为前瞻性多中心队列研究,但其他PICO标准均不匹配,因此排除该文献。", "evidence": {"C": "We compared patients ≥90 years with those <90 years using symptomatic intracranial hemorrhage (ECASS [European Cooperative Acute Stroke Study]-II criteria), death, and poor functional outcome in survivors (modified Rankin Scale score 3-5 for patients with prestroke modified Rankin Scale score ≤2 and modified Rankin Scale score 4-5 for patients prestroke modified Rankin Scale ≥3) at 3 months as outcomes.", "I": "The probability to receive intravenous thrombolysis (IVT) for treatment of acute ischemic stroke declines with increasing age and is consequently the lowest in very elderly patients.", "P": "Of 16 974 eligible patients, 976 (5.7%) were ≥90 years. Patients ≥90 years had higher median National Institutes of Health Stroke Scale on admission (12 versus 8) and were more often dependent prior to the index stroke (prestroke modified Rankin Scale score of ≥3; 45.2% versus 7.4%).", "S": "In this prospective multicenter study from the TRISP (Thrombolysis in Ischemic Stroke Patients) registry, we compared patients ≥90 years with those <90 years."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "partial"}, "conclusion": "exclude", "confidence": 0.9}, "deepseek": {"reason": "这篇文献应被排除。首先,PICO标准完全未定义,无法进行有效匹配。其次,文献的研究人群（P）是缺血性卒中患者,干预措施（I）是静脉溶栓,对照（C）是不同年龄组的比较,研究设计（S）是队列研究。这些内容与给定的纳入标准“骨质疏松”完全无关,属于明确的不匹配。同时,文献主题（卒中）与排除标准“心衰”也无直接关联,但鉴于研究主题与纳入标准完全不符,无需进一步考虑排除标准。因此,基于PICO的全面不匹配,做出排除决策。", "evidence": {"C": "compared patients ≥90 years with those <90 years", "I": "intravenous thrombolysis (IVT) for treatment of acute ischemic stroke", "P": "patients with ischemic stroke", "S": "cohort study"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:07:01.281 2026-01-11 05:07:01.281
|
||
4bb4fcbd-7ccb-4fa1-a4b5-58ccb56ff968 f0d3c742-fa2e-487a-a6d0-6b544df396ba 68056539-873f-4582-847b-56a9febf4570 deepseek-chat mismatch mismatch mismatch match exclude 0.95 selected stroke patients intravenous thrombolysis (IVT) IVT >4.5-9 hours versus 0-4.5 hours after stroke onset Prospective multicenter cohort study 这篇文献应被排除。首先,研究人群（P）是卒中患者（"selected stroke patients"）,与纳入标准"骨质疏松"完全不匹配。其次,干预措施（I）是静脉溶栓治疗卒中（"intravenous thrombolysis (IVT)"）,与骨质疏松的干预无关。对照（C）是不同时间窗的溶栓治疗,也与骨质疏松无关。研究设计（S）是前瞻性多中心队列研究,符合系统综述对观察性研究的常见纳入范围,但这是唯一匹配的维度。文献未提及心衰,因此未触发排除标准。由于文献的研究主题（卒中溶栓）与纳入标准（骨质疏松）在疾病领域上完全不同,所有核心PICO维度均不匹配,因此明确排除。 qwen-max mismatch mismatch mismatch mismatch exclude 0.95 研究人群为缺血性卒中患者:Of 15,827 patients, 663 (4.2%) received IVT >4.5-9 hours and 15,164 (95.8%) within 4.5 hours after stroke onset. 干预措施为静脉溶栓治疗:To investigate the safety and effectiveness of intravenous thrombolysis (IVT) >4.5-9 hours after stroke onset, and the relevance of advanced neuroimaging for patient selection. 对照组为在0-4.5小时内接受静脉溶栓治疗的患者:(i) IVT >4.5-9 hours versus 0-4.5 hours after stroke onset. 结局指标为症状性颅内出血、3个月功能预后不良和死亡率:Outcomes were symptomatic intracranial hemorrhage, poor 3-month functional outcome (modified Rankin scale 3-6) and mortality. 该文献的研究对象为缺血性卒中患者,与骨质疏松无关。干预措施是静脉溶栓治疗,而不是针对骨质疏松的干预。结局指标关注的是症状性颅内出血、3个月功能预后不良和死亡率,与骨质疏松的结局指标不符。因此,该文献不符合PICO标准,并且不涉及骨质疏松,应排除。 none \N exclude \N \N \N completed 2026-01-11 05:07:14.866 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究对象为缺血性卒中患者,与骨质疏松无关。干预措施是静脉溶栓治疗,而不是针对骨质疏松的干预。结局指标关注的是症状性颅内出血、3个月功能预后不良和死亡率,与骨质疏松的结局指标不符。因此,该文献不符合PICO标准,并且不涉及骨质疏松,应排除。", "evidence": {"C": "对照组为在0-4.5小时内接受静脉溶栓治疗的患者:(i) IVT >4.5-9 hours versus 0-4.5 hours after stroke onset.", "I": "干预措施为静脉溶栓治疗:To investigate the safety and effectiveness of intravenous thrombolysis (IVT) >4.5-9 hours after stroke onset, and the relevance of advanced neuroimaging for patient selection.", "P": "研究人群为缺血性卒中患者:Of 15,827 patients, 663 (4.2%) received IVT >4.5-9 hours and 15,164 (95.8%) within 4.5 hours after stroke onset.", "S": "结局指标为症状性颅内出血、3个月功能预后不良和死亡率:Outcomes were symptomatic intracranial hemorrhage, poor 3-month functional outcome (modified Rankin scale 3-6) and mortality."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.95}, "deepseek": {"reason": "这篇文献应被排除。首先,研究人群（P）是卒中患者（\\"selected stroke patients\\"）,与纳入标准\\"骨质疏松\\"完全不匹配。其次,干预措施（I）是静脉溶栓治疗卒中（\\"intravenous thrombolysis (IVT)\\"）,与骨质疏松的干预无关。对照（C）是不同时间窗的溶栓治疗,也与骨质疏松无关。研究设计（S）是前瞻性多中心队列研究,符合系统综述对观察性研究的常见纳入范围,但这是唯一匹配的维度。文献未提及心衰,因此未触发排除标准。由于文献的研究主题（卒中溶栓）与纳入标准（骨质疏松）在疾病领域上完全不同,所有核心PICO维度均不匹配,因此明确排除。", "evidence": {"C": "IVT >4.5-9 hours versus 0-4.5 hours after stroke onset", "I": "intravenous thrombolysis (IVT)", "P": "selected stroke patients", "S": "Prospective multicenter cohort study"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:07:14.869 2026-01-11 05:07:14.869
|
||
45f94570-4f08-483a-849a-accd361896be f0d3c742-fa2e-487a-a6d0-6b544df396ba bda7e5dd-287f-4d73-95a8-84cf5532b5d5 deepseek-chat mismatch mismatch mismatch mismatch exclude 0.95 patients who underwent endovascular thrombectomy (EVT) for anterior circulation acute ischemic stroke (AIS) with large vessel occlusion (LVO) endovascular thrombectomy (EVT) The study is a retrospective cohort analysis of patients who underwent EVT. There is no mention of a specific control group (e.g., standard medical therapy, alternative intervention) for comparison. retrospective record-based cohort study 该文献应被排除。理由如下:(1) 研究人群(P)为接受血管内血栓切除术治疗前循环大血管闭塞性急性缺血性卒中的患者,与纳入标准“骨质疏松”完全不符,属于明确不匹配。(2) 干预措施(I)为血管内血栓切除术,与骨质疏松的干预措施无关。(3) 研究设计(S)为回顾性队列研究,但鉴于PICO所有核心维度均不匹配,研究设计是否匹配已无关紧要。(4) 文献未提及“骨质疏松”或“心衰”,因此不触发纳入标准,也未触发排除标准。排除的根本原因是研究主题（卒中血管内治疗）与系统综述方案的核心主题（骨质疏松）完全不同,属于根本性不相关。 qwen-max mismatch mismatch mismatch mismatch exclude 0.9 In a cohort of 117 patients with a mean age of 58.5 years, 81 (69.2%) were male. Hypertension and diabetes mellitus were the most common risk factors, affecting 48.7% and 41% of the cohort, respectively. Endovascular thrombectomy (EVT) is now the recognized standard of care for anterior circulation acute ischemic stroke (AIS) with large vessel occlusion (LVO). The study does not mention any specific control group or comparator intervention. This study elucidated the characteristics, clinical profiles, and outcomes of patients who underwent EVT for AIS. The study, conducted from July 2022 through October 2023, encompassed a comprehensive analysis of clinical, radiological, and time-related factors and diverse outcomes. 该文献研究的是接受血管内取栓术的急性缺血性脑卒中患者,不符合未定义的PICO标准。此外,研究人群、干预措施、对照组和结局指标均与给定的PICO标准不匹配。尽管研究设计为回顾性队列研究,但其主题与骨质疏松无关,并且未提及心衰作为排除标准的一部分。因此,该文献应被排除。 none \N exclude \N \N \N completed 2026-01-11 05:07:26.528 \N v1.0.0-mvp {"qwen": {"reason": "该文献研究的是接受血管内取栓术的急性缺血性脑卒中患者,不符合未定义的PICO标准。此外,研究人群、干预措施、对照组和结局指标均与给定的PICO标准不匹配。尽管研究设计为回顾性队列研究,但其主题与骨质疏松无关,并且未提及心衰作为排除标准的一部分。因此,该文献应被排除。", "evidence": {"C": "The study does not mention any specific control group or comparator intervention.", "I": "Endovascular thrombectomy (EVT) is now the recognized standard of care for anterior circulation acute ischemic stroke (AIS) with large vessel occlusion (LVO).", "P": "In a cohort of 117 patients with a mean age of 58.5 years, 81 (69.2%) were male. Hypertension and diabetes mellitus were the most common risk factors, affecting 48.7% and 41% of the cohort, respectively.", "S": "This study elucidated the characteristics, clinical profiles, and outcomes of patients who underwent EVT for AIS. The study, conducted from July 2022 through October 2023, encompassed a comprehensive analysis of clinical, radiological, and time-related factors and diverse outcomes."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.9}, "deepseek": {"reason": "该文献应被排除。理由如下:(1) 研究人群(P)为接受血管内血栓切除术治疗前循环大血管闭塞性急性缺血性卒中的患者,与纳入标准“骨质疏松”完全不符,属于明确不匹配。(2) 干预措施(I)为血管内血栓切除术,与骨质疏松的干预措施无关。(3) 研究设计(S)为回顾性队列研究,但鉴于PICO所有核心维度均不匹配,研究设计是否匹配已无关紧要。(4) 文献未提及“骨质疏松”或“心衰”,因此不触发纳入标准,也未触发排除标准。排除的根本原因是研究主题（卒中血管内治疗）与系统综述方案的核心主题（骨质疏松）完全不同,属于根本性不相关。", "evidence": {"C": "The study is a retrospective cohort analysis of patients who underwent EVT. There is no mention of a specific control group (e.g., standard medical therapy, alternative intervention) for comparison.", "I": "endovascular thrombectomy (EVT)", "P": "patients who underwent endovascular thrombectomy (EVT) for anterior circulation acute ischemic stroke (AIS) with large vessel occlusion (LVO)", "S": "retrospective record-based cohort study"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:07:26.531 2026-01-11 05:07:26.531
|
||
abeb3627-faa4-469f-8aba-adf46a08bc33 f0d3c742-fa2e-487a-a6d0-6b544df396ba de9db261-92f5-473d-add4-1fb9c3e09fc9 deepseek-chat mismatch mismatch mismatch match exclude 0.95 The trial included 11 016 patients with a noncardioembolic, nonsevere ischemic stroke or high-risk TIA Ticagrelor (180-mg loading dose on day 1 followed by 90 mg twice daily for days 2-30) or placebo within 24 hours of symptom onset. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30. Ticagrelor...or placebo...All patients received aspirin The Acute Stroke or Transient Ischemic Attack Treated With Ticagrelor and Aspirin for Prevention of Stroke and Death (THALES) was a randomized clinical trial 该文献应被排除。理由如下:(1) 研究人群(P)为急性缺血性卒中或高危TIA患者,与纳入标准“骨质疏松”完全不匹配,属于明确不匹配。(2) 干预措施(I)为替格瑞洛联合阿司匹林,对照(C)为安慰剂联合阿司匹林,均与骨质疏松的干预或对照无关,属于不匹配。(3) 研究设计(S)为随机临床试验,符合系统综述对高质量证据的偏好,但此单一匹配不足以纳入。(4) 文献内容主要关注卒中预防,未提及骨质疏松,也未触发排除标准“心衰”。因此,基于PICO的全面不匹配,该文献与研究主题无关,应直接排除。 qwen-max mismatch mismatch mismatch match exclude 0.9 The trial included 11 016 patients with a noncardioembolic, nonsevere ischemic stroke or high-risk TIA, including 10 803 with modified Rankin Scale score (mRS) recorded at 30 days. Ticagrelor (180-mg loading dose on day 1 followed by 90 mg twice daily for days 2-30) or placebo within 24 hours of symptom onset. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30. The Acute Stroke or Transient Ischemic Attack Treated With Ticagrelor and Aspirin for Prevention of Stroke and Death (THALES) was a randomized clinical trial. 该文献的研究人群是急性缺血性卒中或短暂性脑缺血发作的患者,干预措施是替格瑞洛加阿司匹林,对照组是单用阿司匹林。这些都不符合我们设定的PICO标准。此外,文献中没有提到骨质疏松症的相关信息,因此不符合纳入标准。虽然研究设计是随机对照试验,但研究内容与我们的筛选目标不符,因此排除。 none \N exclude \N \N \N completed 2026-01-11 05:07:39.87 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究人群是急性缺血性卒中或短暂性脑缺血发作的患者,干预措施是替格瑞洛加阿司匹林,对照组是单用阿司匹林。这些都不符合我们设定的PICO标准。此外,文献中没有提到骨质疏松症的相关信息,因此不符合纳入标准。虽然研究设计是随机对照试验,但研究内容与我们的筛选目标不符,因此排除。", "evidence": {"C": "All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30.", "I": "Ticagrelor (180-mg loading dose on day 1 followed by 90 mg twice daily for days 2-30) or placebo within 24 hours of symptom onset. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30.", "P": "The trial included 11 016 patients with a noncardioembolic, nonsevere ischemic stroke or high-risk TIA, including 10 803 with modified Rankin Scale score (mRS) recorded at 30 days.", "S": "The Acute Stroke or Transient Ischemic Attack Treated With Ticagrelor and Aspirin for Prevention of Stroke and Death (THALES) was a randomized clinical trial."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.9}, "deepseek": {"reason": "该文献应被排除。理由如下:(1) 研究人群(P)为急性缺血性卒中或高危TIA患者,与纳入标准“骨质疏松”完全不匹配,属于明确不匹配。(2) 干预措施(I)为替格瑞洛联合阿司匹林,对照(C)为安慰剂联合阿司匹林,均与骨质疏松的干预或对照无关,属于不匹配。(3) 研究设计(S)为随机临床试验,符合系统综述对高质量证据的偏好,但此单一匹配不足以纳入。(4) 文献内容主要关注卒中预防,未提及骨质疏松,也未触发排除标准“心衰”。因此,基于PICO的全面不匹配,该文献与研究主题无关,应直接排除。", "evidence": {"C": "Ticagrelor...or placebo...All patients received aspirin", "I": "Ticagrelor (180-mg loading dose on day 1 followed by 90 mg twice daily for days 2-30) or placebo within 24 hours of symptom onset. All patients received aspirin, 300 to 325 mg on day 1 followed by 75 to 100 mg daily for days 2 to 30.", "P": "The trial included 11 016 patients with a noncardioembolic, nonsevere ischemic stroke or high-risk TIA", "S": "The Acute Stroke or Transient Ischemic Attack Treated With Ticagrelor and Aspirin for Prevention of Stroke and Death (THALES) was a randomized clinical trial"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:07:39.874 2026-01-11 05:07:39.874
|
||
26323f79-7cc5-4ce7-bd99-b120a8e4667e f0d3c742-fa2e-487a-a6d0-6b544df396ba 305fb512-91e2-4def-af45-bb3de70c578e deepseek-chat mismatch mismatch mismatch match exclude 0.95 Adult patients with unilateral sICAS in middle cerebral artery and/or intracranial segment of internal carotid artery-related AIS or transient ischemic attack within 6 months prior to randomization were enrolled. The RIC protocol consisted of 5 cycles, each for 5-min bilateral upper limb ischemia and 5-min reperfusion period, twice a day, with a total duration of 3 months. Twenty-three eligible patients were randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13). randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13). 文献被明确排除。理由如下:(1) 研究人群(P)不匹配:文献研究的是症状性颅内动脉狭窄(sICAS)相关的急性缺血性卒中或短暂性脑缺血发作患者,而纳入标准为“骨质疏松”,两者是完全不同的疾病领域。(2) 干预措施(I)不匹配:文献干预为远程缺血预适应(RIC),而研究方案中干预措施未定义,无法判断是否匹配,但鉴于人群已完全不匹配,此点已不重要。(3) 对照(C)不匹配:文献对照为标准药物治疗(SMT),与研究方案中未定义的对照标准无法匹配。(4) 研究设计(S)匹配:文献为随机对照试验(RCT)。(5) 排除标准:文献未提及“心衰”,不触发排除标准。综上,文献的研究人群与纳入标准“骨质疏松”完全不符,是排除该文献的充分且明确的理由。 qwen-max mismatch mismatch mismatch mismatch exclude 0.9 Adult patients with unilateral sICAS in middle cerebral artery and/or intracranial segment of internal carotid artery-related AIS or transient ischemic attack within 6 months prior to randomization were enrolled. The RIC protocol consisted of 5 cycles, each for 5-min bilateral upper limb ischemia and 5-min reperfusion period, twice a day, with a total duration of 3 months. Twenty-three eligible patients were randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13). We aimed to assess the efficacy of remote ischemic conditioning (RIC) on improving this status by evaluating cerebral blood flow (CBF) and cerebral glucose metabolism (CGM) via PET/CT. 该文献的研究人群是患有单侧症状性颅内动脉狭窄的成人患者,干预措施为远程缺血预处理,对照组为标准医学治疗,研究设计为随机对照试验。然而,根据提供的PICO标准和纳入排除标准,本文献的研究对象不符合骨质疏松症患者的标准,并且没有提到心衰作为排除条件。因此,该文献应被排除。 none \N exclude \N \N \N completed 2026-01-11 05:07:53.866 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究人群是患有单侧症状性颅内动脉狭窄的成人患者,干预措施为远程缺血预处理,对照组为标准医学治疗,研究设计为随机对照试验。然而,根据提供的PICO标准和纳入排除标准,本文献的研究对象不符合骨质疏松症患者的标准,并且没有提到心衰作为排除条件。因此,该文献应被排除。", "evidence": {"C": "Twenty-three eligible patients were randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13).", "I": "The RIC protocol consisted of 5 cycles, each for 5-min bilateral upper limb ischemia and 5-min reperfusion period, twice a day, with a total duration of 3 months.", "P": "Adult patients with unilateral sICAS in middle cerebral artery and/or intracranial segment of internal carotid artery-related AIS or transient ischemic attack within 6 months prior to randomization were enrolled.", "S": "We aimed to assess the efficacy of remote ischemic conditioning (RIC) on improving this status by evaluating cerebral blood flow (CBF) and cerebral glucose metabolism (CGM) via PET/CT."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.9}, "deepseek": {"reason": "文献被明确排除。理由如下:(1) 研究人群(P)不匹配:文献研究的是症状性颅内动脉狭窄(sICAS)相关的急性缺血性卒中或短暂性脑缺血发作患者,而纳入标准为“骨质疏松”,两者是完全不同的疾病领域。(2) 干预措施(I)不匹配:文献干预为远程缺血预适应(RIC),而研究方案中干预措施未定义,无法判断是否匹配,但鉴于人群已完全不匹配,此点已不重要。(3) 对照(C)不匹配:文献对照为标准药物治疗(SMT),与研究方案中未定义的对照标准无法匹配。(4) 研究设计(S)匹配:文献为随机对照试验(RCT)。(5) 排除标准:文献未提及“心衰”,不触发排除标准。综上,文献的研究人群与纳入标准“骨质疏松”完全不符,是排除该文献的充分且明确的理由。", "evidence": {"C": "Twenty-three eligible patients were randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13).", "I": "The RIC protocol consisted of 5 cycles, each for 5-min bilateral upper limb ischemia and 5-min reperfusion period, twice a day, with a total duration of 3 months.", "P": "Adult patients with unilateral sICAS in middle cerebral artery and/or intracranial segment of internal carotid artery-related AIS or transient ischemic attack within 6 months prior to randomization were enrolled.", "S": "randomly assigned to standard medical treatment (SMT) (n = 10) or RIC group (n = 13)."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "match"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:07:53.869 2026-01-11 05:07:53.869
|
||
cdb7dec8-dba7-4862-a57e-559509756cb4 f0d3c742-fa2e-487a-a6d0-6b544df396ba 26f8af79-1536-4a6d-8338-dc74d78786b2 deepseek-chat mismatch mismatch mismatch mismatch exclude 0.95 Patients with acute ischemic stroke and anterior circulation large vessel occlusions who achieved successful reperfusion via MT SBP reduction (SBPr) in the first 24 hours after successful reperfusion Subanalysis based on reperfusion status showed that SBPr was associated with lower odds of poor outcome only in patients with complete reperfusion (modified Thrombolysis in Cerebral Infarction (mTICI 3)) but not in patients with incomplete reperfusion (mTICI 2b). A multicenter retrospective study 该文献应被排除。首先,研究人群（P）为急性缺血性卒中伴前循环大血管闭塞且成功再通的患者,与纳入标准“骨质疏松”完全不匹配。其次,干预措施（I）为成功再通后24小时内的收缩压降低,对照（C）为不同再通状态（mTICI 3 vs 2b）的亚组比较,研究设计（S）为多中心回顾性研究,均与未定义的PICO标准无法匹配。此外,文献未提及“骨质疏松”,也未触发排除标准“心衰”。因此,该文献的研究主题（卒中血管内治疗后的血压管理）与方案关注的“骨质疏松”领域完全无关,明确不相关,应予以排除。 qwen-max mismatch mismatch mismatch mismatch exclude 0.95 Patients with acute ischemic stroke and anterior circulation large vessel occlusions who achieved successful reperfusion via MT were included. SBPr was calculated using the formula 100×([admission SBP-mean SBP]/admission SBP). No specific control group is mentioned, but the study focuses on the association between SBPr and outcomes. A multicenter retrospective study, which included 10 comprehensive stroke centers, was carried out. 该文献的研究人群为急性缺血性脑卒中患者,干预措施是机械取栓后的收缩压降低情况,对照组不明确,研究设计为多中心回顾性研究。这些都不符合本研究方案中的PICO标准（未定义具体的人群、干预措施、对照和结局指标）,并且研究主题与骨质疏松无关。此外,文献没有提及任何关于心衰的内容,因此排除标准也不适用。综合考虑,该文献不符合纳入标准,故排除。 none \N exclude \N \N \N completed 2026-01-11 05:08:11.425 \N v1.0.0-mvp {"qwen": {"reason": "该文献的研究人群为急性缺血性脑卒中患者,干预措施是机械取栓后的收缩压降低情况,对照组不明确,研究设计为多中心回顾性研究。这些都不符合本研究方案中的PICO标准（未定义具体的人群、干预措施、对照和结局指标）,并且研究主题与骨质疏松无关。此外,文献没有提及任何关于心衰的内容,因此排除标准也不适用。综合考虑,该文献不符合纳入标准,故排除。", "evidence": {"C": "No specific control group is mentioned, but the study focuses on the association between SBPr and outcomes.", "I": "SBPr was calculated using the formula 100×([admission SBP-mean SBP]/admission SBP).", "P": "Patients with acute ischemic stroke and anterior circulation large vessel occlusions who achieved successful reperfusion via MT were included.", "S": "A multicenter retrospective study, which included 10 comprehensive stroke centers, was carried out."}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.95}, "deepseek": {"reason": "该文献应被排除。首先,研究人群（P）为急性缺血性卒中伴前循环大血管闭塞且成功再通的患者,与纳入标准“骨质疏松”完全不匹配。其次,干预措施（I）为成功再通后24小时内的收缩压降低,对照（C）为不同再通状态（mTICI 3 vs 2b）的亚组比较,研究设计（S）为多中心回顾性研究,均与未定义的PICO标准无法匹配。此外,文献未提及“骨质疏松”,也未触发排除标准“心衰”。因此,该文献的研究主题（卒中血管内治疗后的血压管理）与方案关注的“骨质疏松”领域完全无关,明确不相关,应予以排除。", "evidence": {"C": "Subanalysis based on reperfusion status showed that SBPr was associated with lower odds of poor outcome only in patients with complete reperfusion (modified Thrombolysis in Cerebral Infarction (mTICI 3)) but not in patients with incomplete reperfusion (mTICI 2b).", "I": "SBP reduction (SBPr) in the first 24 hours after successful reperfusion", "P": "Patients with acute ischemic stroke and anterior circulation large vessel occlusions who achieved successful reperfusion via MT", "S": "A multicenter retrospective study"}, "judgment": {"C": "mismatch", "I": "mismatch", "P": "mismatch", "S": "mismatch"}, "conclusion": "exclude", "confidence": 0.95}} 2026-01-11 05:08:11.429 2026-01-11 05:08:11.429
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: screening_tasks; Type: TABLE DATA; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
COPY asl_schema.screening_tasks (id, project_id, task_type, status, total_items, processed_items, success_items, failed_items, conflict_items, started_at, completed_at, estimated_end_at, error_message, created_at, updated_at) FROM stdin;
|
||
93d5d9c5-cf30-4b0c-b337-4caf0d70e3ad f0d3c742-fa2e-487a-a6d0-6b544df396ba title_abstract completed 7 7 7 0 0 2026-01-11 05:06:30.073 2026-01-11 05:08:11.436 \N \N 2026-01-11 05:06:30.075 2026-01-11 05:08:11.439
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: prompt_templates; Type: TABLE DATA; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
COPY capability_schema.prompt_templates (id, code, name, module, description, variables, created_at, updated_at) FROM stdin;
|
||
1 ASL_SCREENING_TitleAbstract ASL标题摘要初筛 ASL 用于AI智能文献的标题摘要初筛，判断文献是否符合纳入/排除标准 ["title", "abstract", "inclusionCriteria", "exclusionCriteria"] 2026-01-11 03:16:02.67 2026-01-11 03:16:02.67
|
||
2 DC_TOOLB_Extraction DC病历结构化提取 DC 用于Tool B从病历文本中提取结构化数据 ["text", "targetFields"] 2026-01-11 03:16:02.688 2026-01-11 03:16:02.688
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: prompt_versions; Type: TABLE DATA; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
COPY capability_schema.prompt_versions (id, template_id, version, content, model_config, status, changelog, created_by, created_at) FROM stdin;
|
||
1 1 1 你是一个专业的医学文献筛选专家。请根据以下纳入/排除标准，判断这篇文献是否应该纳入系统评价。\n\n## 文献信息\n- 标题：{{title}}\n- 摘要：{{abstract}}\n\n## 筛选标准\n- 纳入标准：{{inclusionCriteria}}\n- 排除标准：{{exclusionCriteria}}\n\n## 输出要求\n请以JSON格式输出你的判断结果：\n{\n "decision": "INCLUDE" | "EXCLUDE" | "UNCERTAIN",\n "confidence": 0.0-1.0,\n "reason": "判断理由"\n} {"model": "deepseek-v3", "temperature": 0.1} ACTIVE 初始版本 6a1ba974-cf74-4d69-801b-9bc1923bfb80 2026-01-11 03:16:02.678
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_extraction_items; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_extraction_items (id, task_id, row_index, original_text, result_a, result_b, status, conflict_fields, final_result, tokens_a, tokens_b, error, created_at, resolved_at) FROM stdin;
|
||
8d4a4b74-5ebf-4536-8944-88bcaa9784d7 2bb18945-29fe-4714-b01c-a3c09a684437 1 【右肺下叶】\n 浸润性腺癌 \n 腺泡型（80%） 乳头型（20%） \n 肿瘤体积2.8cm*2.2cm*1.5cm\n 脉管及神经未见明确癌浸润\n 脏层胸膜及小支气管壁可见癌侵及 \n 支气管切缘及血管切缘未见癌\n 支气管旁淋巴结未见癌转移（0/5）\n 分送各组淋巴结未见癌转移\n 第4组（0/5） 第7组（0/3） 第11组（0/3）\n pTNM:T2aN0 病理分期：ⅠB期（AJCC 8th，2017）\n \n免疫组化结果显示:CK20(－),CK7(+),Ki-67(+5%),Napsin A(+),TTF-1(+)。\n注：免疫组化支持原发性肺癌，相关指南建议非小细胞肺癌做EGFR/ALK/ROS1等基因检测，预测对靶向药物的疗效，以指导临床用药。如需检测，请与病理科联系。 {"免疫组化": "CK20(-), CK7(+), Ki-67(+5%), Napsin A(+), TTF-1(+)", "分化程度": "未提及", "病理类型": "浸润性腺癌（腺泡型80%，乳头型20%）", "肿瘤大小": "2.8cm", "淋巴结转移": "无（支气管旁淋巴结0/5，第4组0/5，第7组0/3，第11组0/3）"} {"免疫组化": "CK20(－),CK7(+),Ki-67(+5%),Napsin A(+),TTF-1(+)", "分化程度": "未提及", "病理类型": "浸润性腺癌", "肿瘤大小": "2.8cm*2.2cm*1.5cm", "淋巴结转移": "无（支气管旁淋巴结0/5，第4组0/5，第7组0/3，第11组0/3）"} conflict {} null 549 623 \N 2026-01-11 03:49:26.901 \N
|
||
1dfdcc36-2866-4765-b313-86eb991cdfb9 2bb18945-29fe-4714-b01c-a3c09a684437 2 【右肺上叶】\n 浸润性腺癌 \n 腺泡型（60%） 贴壁型（40%） \n 肿瘤体积2.5cm*2cm*1cm\n 脉管及神经未见明确癌浸润\n 脏层胸膜及小支气管壁未见癌浸润\n 支气管切缘及血管切缘未见癌\n 支气管旁淋巴结未见癌转移（0/3）\n 分送（第11组）淋巴结未见癌转移（0/5) \n pTNM:T1cN0 病理分期：ⅠA3期 (AJCC 2017)\n\n免疫组化：Ki-67(+10%),TTF-1(+),Napsin A(+),CK7(+),CK20(-),CK5/6(-),CDX-2(-)。 {"免疫组化": "Ki-67(+10%), TTF-1(+), Napsin A(+), CK7(+), CK20(-), CK5/6(-), CDX-2(-)", "分化程度": "未提及", "病理类型": "浸润性腺癌（腺泡型60%，贴壁型40%）", "肿瘤大小": "2.5cm", "淋巴结转移": "无（支气管旁淋巴结0/3，第11组淋巴结0/5）"} {"免疫组化": "Ki-67(+10%),TTF-1(+),Napsin A(+),CK7(+),CK20(-),CK5/6(-),CDX-2(-)", "分化程度": "未提及", "病理类型": "浸润性腺癌", "肿瘤大小": "2.5cm", "淋巴结转移": "无，支气管旁淋巴结及第11组淋巴结均未见癌转移"} conflict {} null 486 547 \N 2026-01-11 03:49:26.901 \N
|
||
4d7032ba-baf1-4ab4-b2ae-ed556c46961d 2bb18945-29fe-4714-b01c-a3c09a684437 3 【右肺上叶】\n 浸润性腺癌 \n 腺泡型（60%） 贴壁型（40%） \n 肿瘤体积2.5cm*2cm*1cm\n 脉管及神经未见明确癌浸润\n 脏层胸膜及小支气管壁未见癌浸润\n 支气管切缘及血管切缘未见癌\n 支气管旁淋巴结未见癌转移（0/3）\n 分送（第11组）淋巴结未见癌转移（0/5) \n pTNM:T1cN0 病理分期：ⅠA3期 (AJCC 2017)\n\n免疫组化：Ki-67(+10%),TTF-1(+),Napsin A(+),CK7(+),CK20(-),CK5/6(-),CDX-2(-)。 {"免疫组化": "Ki-67(+10%), TTF-1(+), Napsin A(+), CK7(+), CK20(-), CK5/6(-), CDX-2(-)", "分化程度": "未提及", "病理类型": "浸润性腺癌（腺泡型60%，贴壁型40%）", "肿瘤大小": "2.5cm", "淋巴结转移": "无（支气管旁淋巴结0/3，第11组淋巴结0/5）"} {"免疫组化": "Ki-67(+10%),TTF-1(+),Napsin A(+),CK7(+),CK20(-),CK5/6(-),CDX-2(-)", "分化程度": "未提及", "病理类型": "浸润性腺癌", "肿瘤大小": "2.5cm", "淋巴结转移": "无，支气管旁淋巴结（0/3），第11组淋巴结（0/5）"} conflict {} null 486 551 \N 2026-01-11 03:49:26.901 \N
|
||
c8170f36-882d-4e1b-b218-a2a5cc006498 2bb18945-29fe-4714-b01c-a3c09a684437 4 【鞍区】\n 垂体腺瘤 符合零细胞腺瘤\n \n免疫组化:Ki-67(+2%),P53(－),Syn(+),CgA(+),GH(－),PRL(－),ACTH(－),LH(－),TSH(－),FSH(－),PIT-1(－),SF-1(－),SSTR2(－),T-PIT(－),CAM5.2(+),ER(+)。 {"免疫组化": "Ki-67(+2%), P53(-), Syn(+), CgA(+), GH(-), PRL(-), ACTH(-), LH(-), TSH(-), FSH(-), PIT-1(-), SF-1(-), SSTR2(-), T-PIT(-), CAM5.2(+), ER(+)", "分化程度": "未提及", "病理类型": "未提及", "肿瘤大小": "未提及", "淋巴结转移": "未提及"} {"免疫组化": "Ki-67(+2%),P53(－),Syn(+),CgA(+),GH(－),PRL(－),ACTH(－),LH(－),TSH(－),FSH(－),PIT-1(－),SF-1(－),SSTR2(－),T-PIT(－),CAM5.2(+),ER(+)", "分化程度": "未提及", "病理类型": "未提及", "肿瘤大小": "未提及", "淋巴结转移": "未提及"} conflict {} null 417 461 \N 2026-01-11 03:49:26.901 \N
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_extraction_tasks; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_extraction_tasks (id, user_id, project_name, source_file_key, text_column, disease_type, report_type, target_fields, model_a, model_b, status, total_count, processed_count, clean_count, conflict_count, failed_count, total_tokens, total_cost, error, created_at, started_at, completed_at) FROM stdin;
|
||
2bb18945-29fe-4714-b01c-a3c09a684437 default-user 5例-病理数据-测试数据1203.xlsx_提取任务 dc/tool-b/default-user/1768103357661_5例-病理数据-测试数据1203.xlsx 诊断 lung_cancer pathology [{"desc": "如：浸润性腺癌、鳞状细胞癌", "name": "病理类型", "width": "w-40"}, {"desc": "高/中/低分化", "name": "分化程度", "width": "w-32"}, {"desc": "最大径，单位cm", "name": "肿瘤大小", "width": "w-32"}, {"desc": "有/无及具体组别", "name": "淋巴结转移", "width": "w-48"}, {"desc": "关键指标", "name": "免疫组化", "width": "w-56"}] deepseek-v3 qwen-max completed 4 4 0 4 0 4120 0 \N 2026-01-11 03:49:26.893 2026-01-11 03:49:26.914 2026-01-11 03:49:44.453
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_health_checks; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_health_checks (id, user_id, file_name, column_name, empty_rate, avg_length, total_rows, estimated_tokens, status, message, created_at) FROM stdin;
|
||
c18d4678-f83f-4fdf-9b7c-a67babdbea09 default-user 1768103357661_5例-病理数据-测试数据1203.xlsx 诊断 0 326.25 4 783 good 健康度良好，预计消耗约 0.8k Token（双模型约 1.6k Token） 2026-01-11 03:49:20.115
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_templates; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_templates (id, disease_type, report_type, display_name, fields, prompt_template, created_at, updated_at) FROM stdin;
|
||
7b8ec46d-6aa2-4d20-a26d-a43dcd00fb0a diabetes admission 糖尿病入院记录 [{"desc": "患者入院的主要症状", "name": "主诉", "width": "w-48"}, {"desc": "发病过程", "name": "现病史", "width": "w-64"}, {"desc": "糖尿病病史年限", "name": "既往史", "width": "w-40"}, {"desc": "单位mmol/L", "name": "空腹血糖", "width": "w-32"}, {"desc": "单位%", "name": "糖化血红蛋白", "width": "w-32"}] 你是一名内分泌科专家。请从以下糖尿病患者入院记录中提取关键信息。\n\n提取字段（必须返回以下所有字段）：\n- 主诉：患者入院时的主要症状\n- 现病史：本次发病的过程和表现\n- 既往史：糖尿病病史年限\n- 空腹血糖：最近的空腹血糖值（单位mmol/L）\n- 糖化血红蛋白：最近的HbA1c值（单位%）\n\n**输出格式：严格的JSON格式：**\n```json\n{\n "主诉": "...",\n "现病史": "...",\n "既往史": "...",\n "空腹血糖": "...",\n "糖化血红蛋白": "..."\n}\n```\n\n如果某个信息未在记录中提及，请填写"未提及"。 2026-01-11 03:25:23.331 2026-01-11 03:48:05.705
|
||
0c6b0ec6-3375-4125-a975-64f6b2573e2c hypertension outpatient 高血压门诊病历 [{"desc": "单位mmHg", "name": "血压值", "width": "w-32"}, {"desc": "单位次/分", "name": "心率", "width": "w-24"}, {"desc": "高血压药物", "name": "当前用药", "width": "w-56"}, {"desc": "心/脑/肾", "name": "靶器官损害", "width": "w-40"}, {"desc": "低/中/高/极高危", "name": "危险分层", "width": "w-32"}] 你是一名心内科专家。请从以下高血压患者门诊病历中提取关键信息。\n\n提取字段（必须返回以下所有字段）：\n- 血压值：收缩压/舒张压（单位mmHg）\n- 心率：心率（单位次/分）\n- 当前用药：患者当前服用的高血压药物\n- 靶器官损害：心脏、脑、肾脏等靶器官损害情况\n- 危险分层：心血管风险分层（低危、中危、高危、极高危）\n\n**输出格式：严格的JSON格式：**\n```json\n{\n "血压值": "...",\n "心率": "...",\n "当前用药": "...",\n "靶器官损害": "...",\n "危险分层": "..."\n}\n```\n\n如果某个信息未在病历中提及，请填写"未提及"。 2026-01-11 03:25:23.337 2026-01-11 03:48:05.708
|
||
e8a09b74-e881-47d1-a994-0e9d3a363f13 lung_cancer pathology 肺癌病理报告 [{"desc": "如：浸润性腺癌、鳞状细胞癌", "name": "病理类型", "width": "w-40"}, {"desc": "高/中/低分化", "name": "分化程度", "width": "w-32"}, {"desc": "最大径，单位cm", "name": "肿瘤大小", "width": "w-32"}, {"desc": "有/无及具体组别", "name": "淋巴结转移", "width": "w-48"}, {"desc": "关键指标", "name": "免疫组化", "width": "w-56"}] 你是一名病理学专家。请从以下肺癌病理报告中提取关键信息。\n\n提取字段（必须返回以下所有字段）：\n- 病理类型：病理诊断类型（如浸润性腺癌、鳞状细胞癌）\n- 分化程度：分化等级（高分化、中分化、低分化、未提及）\n- 肿瘤大小：肿瘤最大径，单位cm\n- 淋巴结转移：淋巴结转移情况（有/无及具体组别）\n- 免疫组化：关键免疫组化指标\n\n**输出格式：严格的JSON格式（不要有任何额外文本）：**\n```json\n{\n "病理类型": "...",\n "分化程度": "...",\n "肿瘤大小": "...",\n "淋巴结转移": "...",\n "免疫组化": "..."\n}\n```\n\n如果某个信息未在报告中提及，请填写"未提及"。 2026-01-11 03:25:23.324 2026-01-11 03:48:05.699
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_tool_c_ai_history; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_tool_c_ai_history (id, session_id, user_id, role, content, generated_code, code_explanation, execute_status, execute_result, execute_error, retry_count, model, created_at) FROM stdin;
|
||
d689a0df-5976-4f73-84c2-6a05fa9d4191 9ae56d64-70db-49e4-9dcc-4a09241d3533 test-user-001 system [功能按钮] 数值映射 操作类型: recode\n参数: {\n "column": "性别",\n "mapping": {\n "女": "1",\n "男": "2"\n },\n "createNewColumn": true,\n "newColumnName": "性别_编码",\n "naHandling": "keep"\n} 用户通过功能按钮执行了数值映射操作（预写函数） success {"output": "📊 NA处理：保持为NA（3个）\\n映射完成: 93 个值成功映射\\n警告: 3 个值未找到对应映射\\n未映射的值: [None]\\n映射成功率: 96.9%\\n", "affectedRows": 96, "executionTime": 0.01748371124267578} \N 0 prewritten-function 2026-01-11 03:48:59.723
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: dc_tool_c_sessions; Type: TABLE DATA; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
COPY dc_schema.dc_tool_c_sessions (id, user_id, file_name, file_key, total_rows, total_cols, columns, encoding, file_size, created_at, updated_at, expires_at, data_stats, column_mapping, clean_data_key) FROM stdin;
|
||
9ae56d64-70db-49e4-9dcc-4a09241d3533 test-user-001 G鼓膜穿孔数据-缺失.xlsx dc/tool-c/sessions/test-user-001/1768103324515-G鼓膜穿孔数据-缺失.xlsx 96 15 ["序号", "年龄", "性别", "性别_编码", "身高 ", "职业（非体力=1，体力=2，退休=3，无业=4）", "体重", "耳聋类型", "术前听力损失分级", "鼓膜修补术", "术中出血量", "手术时长", "疼痛评分", "鼓膜愈合情况", "听力改善情况"] utf-8 16814 2026-01-11 03:48:44.527 2026-01-11 03:48:59.708 2026-01-11 03:58:44.518 {"totalRows": 96, "columnStats": [{"mean": 48.5, "name": "序号", "median": 48.5, "dataType": "numeric", "missingRate": 0, "uniqueCount": 96, "missingCount": 0}, {"mean": 37, "name": "年龄", "median": 36, "dataType": "numeric", "missingRate": 0, "uniqueCount": 27, "missingCount": 0}, {"mean": null, "name": "性别", "median": null, "dataType": "categorical", "missingRate": 3.1, "uniqueCount": 2, "missingCount": 3}, {"mean": 169.15, "name": "身高 ", "median": 174, "dataType": "numeric", "missingRate": 42.7, "uniqueCount": 14, "missingCount": 41}, {"mean": 2.59, "name": "职业（非体力=1，体力=2，退休=3，无业=4）", "median": 3, "dataType": "numeric", "missingRate": 46.9, "uniqueCount": 4, "missingCount": 45}, {"mean": 63.98, "name": "体重", "median": 70, "dataType": "numeric", "missingRate": 42.7, "uniqueCount": 13, "missingCount": 41}, {"mean": 1.16, "name": "耳聋类型", "median": 1, "dataType": "numeric", "missingRate": 15.6, "uniqueCount": 2, "missingCount": 15}, {"mean": 2.47, "name": "术前听力损失分级", "median": 2, "dataType": "numeric", "missingRate": 1, "uniqueCount": 2, "missingCount": 1}, {"mean": 0.51, "name": "鼓膜修补术", "median": 1, "dataType": "numeric", "missingRate": 1, "uniqueCount": 2, "missingCount": 1}, {"mean": 13.57, "name": "术中出血量", "median": 10.02, "dataType": "numeric", "missingRate": 30.2, "uniqueCount": 62, "missingCount": 29}, {"mean": 77.57, "name": "手术时长", "median": 64, "dataType": "numeric", "missingRate": 14.6, "uniqueCount": 43, "missingCount": 14}, {"mean": 3.29, "name": "疼痛评分", "median": 3, "dataType": "numeric", "missingRate": 2.1, "uniqueCount": 9, "missingCount": 2}, {"mean": 0.89, "name": "鼓膜愈合情况", "median": 1, "dataType": "numeric", "missingRate": 1, "uniqueCount": 2, "missingCount": 1}, {"mean": 0.75, "name": "听力改善情况", "median": 1, "dataType": "numeric", "missingRate": 1, "uniqueCount": 2, "missingCount": 1}]} [{"safeName": "col_0", "displayName": "序号", "originalName": "序号"}, {"safeName": "col_1", "displayName": "年龄", "originalName": "年龄"}, {"safeName": "col_2", "displayName": "性别", "originalName": "性别"}, {"safeName": "col_3", "displayName": "性别_编码", "originalName": "性别_编码"}, {"safeName": "col_4", "displayName": "身高 ", "originalName": "身高 "}, {"safeName": "col_5", "displayName": "职业（非体力=1，体力=2，退休=3，无业=4）", "originalName": "职业（非体力=1，体力=2，退休=3，无业=4）"}, {"safeName": "col_6", "displayName": "体重", "originalName": "体重"}, {"safeName": "col_7", "displayName": "耳聋类型", "originalName": "耳聋类型"}, {"safeName": "col_8", "displayName": "术前听力损失分级", "originalName": "术前听力损失分级"}, {"safeName": "col_9", "displayName": "鼓膜修补术", "originalName": "鼓膜修补术"}, {"safeName": "col_10", "displayName": "术中出血量", "originalName": "术中出血量"}, {"safeName": "col_11", "displayName": "手术时长", "originalName": "手术时长"}, {"safeName": "col_12", "displayName": "疼痛评分", "originalName": "疼痛评分"}, {"safeName": "col_13", "displayName": "鼓膜愈合情况", "originalName": "鼓膜愈合情况"}, {"safeName": "col_14", "displayName": "听力改善情况", "originalName": "听力改善情况"}] dc/tool-c/sessions/test-user-001/1768103324515-G鼓膜穿孔数据-缺失.xlsx_clean.json
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: audit_logs; Type: TABLE DATA; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
COPY iit_schema.audit_logs (id, project_id, user_id, action_type, entity_type, entity_id, details, trace_id, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: pending_actions; Type: TABLE DATA; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
COPY iit_schema.pending_actions (id, project_id, record_id, field_name, current_value, suggested_value, status, agent_type, reasoning, evidence, approved_by, approved_at, rejection_reason, executed_at, error_message, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: projects; Type: TABLE DATA; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
COPY iit_schema.projects (id, name, description, dify_dataset_id, protocol_file_key, cached_rules, field_mappings, redcap_project_id, redcap_api_token, redcap_url, last_sync_at, status, created_at, updated_at, deleted_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: task_runs; Type: TABLE DATA; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
COPY iit_schema.task_runs (id, project_id, task_type, job_id, status, total_items, processed_items, success_items, failed_items, started_at, completed_at, duration, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: user_mappings; Type: TABLE DATA; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
COPY iit_schema.user_mappings (id, project_id, system_user_id, redcap_username, wecom_user_id, mini_program_open_id, session_key, role, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: batch_results; Type: TABLE DATA; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
COPY pkb_schema.batch_results (id, task_id, document_id, status, data, raw_output, error_message, processing_time_ms, tokens_used, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: batch_tasks; Type: TABLE DATA; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
COPY pkb_schema.batch_tasks (id, user_id, kb_id, name, template_type, template_id, prompt, status, total_documents, completed_count, failed_count, model_type, concurrency, started_at, completed_at, duration_seconds, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: documents; Type: TABLE DATA; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
COPY pkb_schema.documents (id, kb_id, user_id, filename, file_type, file_size_bytes, file_url, dify_document_id, status, progress, error_message, segments_count, tokens_count, extraction_method, extraction_quality, char_count, language, extracted_text, uploaded_at, processed_at) FROM stdin;
|
||
45f79cd7-61af-471c-95eb-399a5e868fed f8cf82ff-9b59-4f0e-babc-55542b33102e user-mock-001 Ginkgo_biloba_and_donepezil_a_comparison_in_the_treatment_of_Alzheimer's_dementia_in_a_randomized_pl1.pdf application/pdf 192179 855dada7-0fca-4ebd-b57d-5729ed26b925 completed 100 \N \N 6262 pymupdf \N 21059 \N \n\n--- 第 1 页 ---\n\nGinkgo biloba and donepezil: a comparison in the treatment of Alzheimer’s\ndementia in a randomized placebo-controlled double-blind study\nM. Mazzaa, A. Capuanob, P. Briaa and S. Mazzab\nDepartments of aPsychiatry and bNeurology, Catholic University of Sacred Heart, Rome, Italy\nKeywords:\nAlzheimer, dementia,\ndonepezil, EGb 761,\nGinkgo biloba, random-\nized controlled trial\nReceived 21 July 2005\nAccepted 3 October 2005\nThe Ginkgo biloba special extract EGb 761 seems to produce neuroprotective effects\nin neurodegenerative diseases of multifactorial origin. There is still debate about the\nefficacy of Ginkgo biloba special extract EGb 761 compared with second-generation\ncholinesterase inhibitors in the treatment of mild to moderate Alzheimer’s dementia.\nOur aim is to assess the efficacy of the Ginkgo biloba special extract E.S. in patients\nwith dementia of the Alzheimer type in slowing down the disease’s degenerative\nprogression and the patients’ cognitive impairment compared with donepezil and\nplacebo. The trial was designed as a 24-week randomized, placebo-controlled, double-\nblind study. Patients aged 50–80 years, suffering from mild to moderate dementia,\nwere allocated into one of the three treatments: Ginkgo biloba (160 mg daily dose),\ndonepezil (5 mg daily dose), or placebo group. The degree of severity of dementia was\nassessed by the Syndrom Kurz test and the Mini-Mental State Examination. Clinical\nGlobal Impression score was recorded to assess the change in the patients conditions\nand the therapeutic efficacy of tested medications. Our results confirm the clinical\nefficacy of Ginkgo biloba E.S. (Flavogin) in the dementia of the Alzheimer type,\ncomparable with donepezil clinical efficacy. There are few published trials that have\ndirectly compared a cholinesterase inhibitor with Ginkgo for dementia. This study\ndirectly compares a cholinesterase inhibitor with Ginkgo biloba for dementia of the\nAlzheimer type and could be a valid contribution in this debate. Our study suggests\nthat there is no evidence of relevant differences in the efficacy of EGb 761 and\ndonepezil in the treatment of mild to moderate Alzheimer’s dementia, so the use of\nboth substances can be justified. In addition, this study contributes to establish the\nefficacy and tolerability of the Ginkgo biloba special extract E.S. in the dementia of the\nAlzheimer type with special respect to moderately severe stages.\nIntroduction\nThe Ginkgo biloba special extract EGb 761 seems to\nproduce neuroprotective effects in neurodegenerative\ndiseases of multifactorial origin [1]. EGb 761 has been\nlicensed for many years and has been investigated in\nvarious clinical studies with different target variables. In\nparticular, substantial evidence suggests that EGb 761\nprotects hippocampal neurons against cell death in-\nduced by b-amyloid [2]. Evidences for the pharmaco-\nlogical actions of Ginkgo biloba extract stem from\nclinical studies in humans, pharmacological trials in\nanimals and in vitro studies. The main effects of Ginkgo\nbiloba extract in the central nervous system seem to be\nrelated to its antioxidant properties, which require the\nsynergistic action of the flavonoids, the terpenoids\n(ginkgolides, bilobalide), and the organic acids. These\ncompounds to varying degrees act as scavengers for free\nradicals, which have been considered the mediators of\nthe\nexcessive\nlipid\nperoxidation\nand\ncell\ndamage\nobserved in Alzheimer’s disease [3]. In brief, several\nmechanisms of action have been described to explain\nthe nootropic properties of Ginkgo biloba: increased\ntolerance to hypoxia; improvement of blood rheology\nand vasoregulating capacity, resulting in increased\nblood flow; prevention of post-traumatic or toxin-in-\nduced brain edema; platelet activating factor inhibition;\nneuroprotective action by direct or by indirect influen-\nces on the nervous system [4].\nSome clinical trials in the last years showed how\nGinkgo could be effective as a treatment for older\npeople with mild to moderate dementia, considering\nthat there were significant differences in response rates\nbetween active substance and placebo. Therefore, there\nis still debate about the efficacy of Ginkgo biloba spe-\ncial extract EGb 761 compared with second-generation\ncholinesterase inhibitors (donepezil, rivastigmine, met-\nrifonate) in the treatment of mild to moderate Alzhei-\nmer’s dementia [4,5].\nCorrespondence: Marianna Mazza, MD, PhD, Department of Psy-\nchiatry, Catholic University of Sacred Heart, Rome, Via Ugo De\nCarolis 48, 00136 Rome, Italy (tel.: 39-06-35348285; fax: 39-06-\n35501909; e-mail: mariannamazza@hotmail.com or marianna.\nmazza@rm.unicatt.it).\n 2006 EFNS\n981\nEuropean Journal of Neurology 2006, 13: 981–985\ndoi:10.1111/j.1468-1331.2006.01409.x\n\n\n--- 第 2 页 ---\n\nThe aim of this study was to assess the efficacy of the\nGinkgo biloba special extract E.S. in patients with\ndementia of the Alzheimer type in slowing down the\ndisease’s degenerative progression and the patient’s\ncognitive impairment.\nMethods\nThe trial was designed as a randomized, placebo-con-\ntrolled, double-blind study. Patients aged 50–80 years,\nsuffering from mild to moderate dementia, were allo-\ncated into one of the three treatments: Ginkgo biloba\n(160 mg daily dose), donepezil (5 mg daily dose), or\nplacebo group. All participants received a diagnosis of\nprimary degenerative dementia of the Alzheimer type\naccording to the criteria of DSM-IV [6]. Inclusion cri-\nteria were: (i) a mean score of 3–5 on the Brief Cognitive\nRating Scale [7], a Hachinski Ischemic Score [8] of <4\nand the presence of an adequate level of premorbid\nintelligence (IQ > 80, global assessment).\nPatients were excluded if they had dementia of other\netiology, severe organic diseases (tumors, severe infec-\ntious diseases, brain trauma, epilepsy, cerebrovascular\nmalformations, alcohol or drug abuse), pseudodemen-\ntia or a history of schizophrenic or affective psychoses\n(Geriatric Depression Scale, 15-item version, total score\n<11) [9].\nThe degree of severity of dementia had to be mild to\nmoderate as assessed by a score between 8 and 23 on the\nSyndrom Kurz test (SKT) [10], a psychometric test\nbattery for the assessment of memory and attention.\nThe SKT consists of nine 1-min subtests that are partly\nspeed-oriented and partly span-oriented: scaled subtest\nscores are aggregated to an SKT total status score\nranging from 1 (very good) to 27 (very poor). Clinical\nGlobal Impression (CGI) score was recorded at base-\nline and at monthly intervals to assess the change in the\npatients condition and the therapeutic efficacy of tested\nmedications. In particular, psychopathology over time\nwas assessed by the CGI item 2 (CGI-2): this rating\ninstrument expresses the global change in observable\ncognitive functioning directly on a transitional scale\nranging from 1 (very much improved) to 7 (very much\ndeteriorated) [4]. Another baseline and outcome meas-\nure was Mini-Mental State Examination (MMSE):\nsubjects who reached a score of at least 13 but no more\nthan 25 on the MMSE were considered for study par-\nticipation.\nFor randomization procedure we used a computer-\ngenerated random sample set. From March 2003 to\nMarch\n2004,\n150\noutpatients\nwere\nscreened\nfor\ndementia according to the above criteria; 117 patients\nwere enrolled in the study, 41 were excluded and 76\nwere randomly allocated (1:1:1). A trial design is shown\nin Fig. 1. Laboratory tests and computed tomographic\nscans were performed routinely. A single-blind placebo\n4-week run-in period was included to exclude placebo-\nresponders. Demographic and baseline characteristics\nare shown in Table 1. The duration of the study was\n24 weeks. The subjects were informed about the pro-\ncedures and aims of the study, its characteristics, and\npossible side effects of the drug and gave their approval\nthrough informed consent. The study was approved by\nthe local ethics committee.\nThe researchers who provided the pills to the study\nparticipants were different from those who conducted\nthe neuropsychological evaluations, in order to guar-\nantee the blinding.\nVasoactive drugs, nootropics and long-term treat-\nment with other drugs were proscribed during the\nstudy, with the exception of low doses of benzodiaze-\npines and neuroleptics in the treatment of behavioral\ndisturbances.\nStatistical analysis\nStatistical analysis was performed with SPSS software\n(v.12.0; SPSS Inc., Chicago, IL, USA); t-test for paired\nsamples was used to compare each group from baseline\nto 24 weeks of treatment. An analysis of variance\n(ANOVA) was performed to detect difference between\ngroups. Age, gender, and severity of cognitive impair-\nment at baseline were factors of ANOVA model. All data\nare\nshowed\nas\nmean ± standard\ndeviation\n(SD),\ninterval of confidence was at 95%.\nResults\nAt the end of the study, after 24 weeks of treatment\nperiod, 60 patients completed the trial. Of 76 subjects\nrandomized for the study, 15 withdrawn: five patients in\nthe EGb group (20%), four patients in donepezil group\n(16%), and six in placebo group (23%). Causes of drop-\nout are shown in Fig. 2. In particular, in the treatment\ngroup (EGb and donepezil) the major cause of with-\ndrawal was lost at follow-up and in one case in Ginkgo\ngroup was a caregiver request. In placebo group loss of\nefficacy was the first cause for withdrawal.\nOutcome measures\nAll data are resumed in Table 2. Data are showed as\nresult of an intent-to-treat analysis. All values are\nexpressed as mean change from baseline with CI at\n95%, considering the end of 24 weeks of treatment as\nthe\nfinal\ntime\nend-point.\nRegarding\nMMSE,\nwe\nobserved an improvement of MMSE scores in the EGb\nand donepezil groups and a slight worsening in placebo\n982\nM. Mazza et al.\n 2006 EFNS European Journal of Neurology 13, 981–985\n\n\n--- 第 3 页 ---\n\ngroup: mean value was from 18.80 ± 3.622 (SD) at\nbaseline to 19.40 ± 3.485 (SD) at 24 weeks period for\nEGb group, from 18.55 ± 3.47 (SD) to 19.75 ± 3.160\n(SD) for donepezil, and from 18.80 ± 3.636 (SD) to\n18.55 ± 3.663 (SD) for placebo. No significant change\nwas observed for each group (t-test analysis and 95%\nCI), and ANOVA for treatment difference shows no sig-\nnificance for both EGb group and donepezil group\n(Fig. 2).\nAs regard SKT we observed an improvement of SKT\nscores in the EGb and donepezil group: mean values\npassed\nfrom\n15.90 ± 3.86\n(SD)\nat\nbaseline\nto\n16.90 ± 3.9 (SD)\nat\n24 weeks\nfor\nplacebo;\nfrom\n16.45 ± 3.05 (SD) to 13.15 ± 2.9 (SD) for EGb group,\nfrom\n15.15 ± 3.48(SD)\nto\n11.85 ± 2.9\n(SD)\nfor\ndonepezil. A statistical significance was observed for\nEGb and donepezil group in a t-test comparison, both\ngroups show also a significant difference when com-\npared with placebo group in an ANOVA. Placebo group\nshows a statistically significant worsening (P ¼ 0.01).\nNo difference was found in comparison between\ndonepezil and EGb. Data are disposed in Fig. 3.\nThere was a significant difference in CGI scores\nchanges for donepezil and EGb group from baseline to\nthe end of 24 weeks of treatment. Mean values passed\nfrom 5.05 ± 0.99 (SD) at baseline to 5.2 ± 0.95 (SD)\nat 24 weeks for placebo; from 4.65 ± 0.87 (SD) to\n3.75 ± 0.96 (SD) for EGb group, from 4.5 ± 0.76\n(SD) to 3.6 ± 0.94 (SD) for donepezil. These data are\nalso confirmed when both groups are compared with\nplacebo. No difference was found between donepezil\nand EGb groups (Fig. 4).\nDiscussion and conclusions\nOur randomized placebo-controlled double-blind study\ncompared the efficacy and tolerability of the EGb 761\nto donepezil in the treatment of mild to moderate\nTable 1 Demographic and baseline characteristics of patients included\nin the study\nAll\nEGb\nDonepezil\nPlacebo\nNumber\nof patients\n76\n25\n25\n26\nMale\n35 (46)\n12 (48)\n13 (52)\n10 (39)\nFemale\n41 (54)\n13 (52)\n12 (48)\n16 (61)\nAge (years)\n68.5 ± 5\n66.2 ± 6\n64.5 ± 6\n69.8 ± 3\nMMSE\n18.71 ± 3.51 18.80 ± 3.62 18.55 ± 3.47 18.80 ± 3.63\nSKT\n14.73 ± 3.46 16.45 ± 3.05 15.15 ± 3.48 15.9 ± 3.86\nCGI (item 2) 4.73 ± 0.89\n4.65 ± 0.87\n4.5 ± 0.76\n5.05 ± 0.99\nValues represent mean ± standard deviation and\nnumber (%) of patients.\nFigure 1 Design of the study.\nGinkgo versus donepezil in Alzheimer’s dementia\n983\n 2006 EFNS European Journal of Neurology 13, 981–985\n\n\n--- 第 4 页 ---\n\nAlzheimer’s dementia. One of the most important\nparameters in demonstrating the clinical efficacy of an\nantidementia drug is the improvement in cognitive\nperformance. MMSE, SKT, and CGI are some of the\nmost common instruments used in clinical evaluation of\ncognitive impairment. Our results confirm the clinical\nefficacy of Ginkgo biloba E.S. in the dementia of the\nAlzheimer type, comparable with donepezil clinical\nefficacy. The SKT has been largely used by other studies\nand has proved useful for this purpose [11,12]. Com-\npared with the donepezil-treated group, the patients\nattention, memory and cognitive performance after\n6 months of treatment as measured by the SKT test had\nshown a comparable important improvement. There-\nfore, the effectiveness of Ginkgo biloba E.S. can be\nconfirmed by considering the significant group differ-\nences in SKT score changes from the baseline to the\nfinal results.\nWe can also notice a significant improvement in CGI\nscores after 6 months in patients treated with Ginkgo\nbiloba\nE.S.,\ncomparable\nwith\nthe\nimprovement\nobtained by the donepezil sample. These data contrib-\nute to stress the efficacy of the Ginkgo biloba E.S. in\nchanging the patients condition during treatment.\nIt is important to underline that the effect of Ginkgo\nbiloba special extract was large enough to reach clinical\nsignificance, even with such relatively small samples of\npatients. Our results agree with those showed by previ-\nous studies in the literature in which identical or similar\ngeriatric scales were used and evaluated. Concrete evi-\ndence of the efficacy of Ginkgo biloba E.S. can be clearly\nseen by considering the change in the patient’s clinical\nconditions during treatment: for example, the patients\nattention and memory performance after 6 months of\ntreatment as measured by the SKT had shown significant\nimprovement, comparable with the results obtained by\npatients treated with donepezil.\nThere were five (20%) drop-outs in the Ginkgo bi-\nloba group and four (16%) drop-outs in the donepezil\ngroup.\nConsidering\nthe\nlimited\nsample\nevaluated,\nGinkgo biloba group shows a small dropout rate, which\nindicates that it has a good side effect profile. The drop-\nouts in the donepezil group were due to adverse events\nTable 2 Outcome measures: intent to treat analysis*\nGroup\nMean change from baseline (95% CI)\nMMSE\nSKT\nCGI (item 2)\nPlacebo\n)0.25 ()2.17 to 2.67)\n0.9 ()1.3 to )0.4), P ¼ 0.01\n0.15 ()0.3 to 0.02)\nEGb group\n0.6 ()3 to 1.8)\n)3.3 (2.3 to 4.27)*, P < 0.001\n)0.9 (0.5 to1.2)*, P < 0.001\nDonepezil group\n1.2 () 3.6 to 1.2)\n)3.3 (2.3 to 4.29)*, P < 0.001\n)0.9 (0.5 to1.2)*, P < 0.001\nTreatment difference\nfor EGb group\n)0.85 ()3.27 to 1.5), P ¼ 0.1 (ns)\n) 3.65 (1.04 to 6.2)*, P < 0.001\n)1.35 (0.6 to 2.0)*, P < 0.001\nTreatment difference\nfor donepezil group\n)1.2 ()3.6 to 1.2), P ¼ 0.06 (ns)\n) 5.7 (2.3–7.5)*, P < 0.001\n)1.6 (0.9 to 2.2)*, P < 0.001\n*Significance at 95% CI. MMSE, Mini Mental State Examination; SKT, Syndrom Kurz test; CGI (item 2), Clinical Global Impression. No\nstatistical significance for donepezil versus EGb (data not shown).\n12.5\n13\n13.5\n14\n14.5\n15\n15.5\n16\n16.5\n Placebo Ginkgo Donepezil \n Placebo Ginkgo Donepezil \n24 weeks\n*\n*\nBaseline\nFigure 3 SKT scores at baseline and after 24 weeks. Ginkgo and\ndonepezil groups show a statistically significant difference com-\npared with placebo (*P ¼ 0.01).\n Baseline\n24 weeks\n17.8\n18\n18.2\n18.4\n18.6\n18.8\n19\n19.2\n19.4\n19.6\n19.8\n20\n Placebo \n Ginkgo Donepezil \n Placebo \n Ginkgo Donepezil \nFigure 2 MMSE scores at baseline and after 24 weeks.\n0\n1\n2\n3\n4\n5\n6\n Placebo Ginkgo Donepezil \n Placebo Ginkgo \n24 weeks\nBaseline\n*\n*\nDonepezil \nFigure 4 CGI scores at baseline and after 24 weeks. Ginkgo and\ndonepezil groups show a statistically significant difference com-\npared with placebo (*P ¼ 0.01).\n984\nM. Mazza et al.\n 2006 EFNS European Journal of Neurology 13, 981–985\n\n\n--- 第 5 页 ---\n\n(diarrhea, nausea, vomiting and restlessness), the same\nobserved in other studies [13]. On the contrary, the\ndrop-outs in the Ginkgo biloba group were not\nimputable to adverse events, so that the Ginkgo biloba\nE.S. has demonstrated a confirmed good tolerability\n(Table 3).\nA\nrecent\nstudy\n[14]\nreported\nthat\n6 weeks\nof\ntreatment with Ginkgo biloba failed to improve per-\nformance on standardized neuropsychological tests of\nlearning, memory, attention and verbal ability in\nhealthy elderly adults without cognitive impairment.\nWe agree with Nathan [15, 16] in suggesting that\nGinkgo’s effects may be explained by its modulatory\ninfluence\non\nthe\nhuman\ncholinergic\nsystem.\nThe\nmechanisms of action are thought to reflect the\nsynergistic action of several components of the extract\nand include increasing blood supply by dilating blood\nvessels,\nreducing\nblood\nviscosity,\nmodification\nof\nneurotransmitter systems, and reducing the density of\noxygen-free radicals.\nThere are few published trials that have directly\ncompared a cholinesterase inhibitor with Ginkgo for\ndementia. This study directly compares a cholinesterase\ninhibitor with Ginkgo biloba for dementia of the Alz-\nheimer type and could be a valid contribution in this\ndebate.\nNowadays the costs of the drugs used for Alzheimer\ndisease are very high, especially if compared with the\nclinical benefits. In such perspective it results useful to\nlook for cheaper, effective and well-tolerated alternative\ndrugs such as Ginkgo biloba.\nLarger samples of patients should be considered\nindeed to confirm these results. Our study suggests that\nthere is no evidence of relevant differences in the effic-\nacy of EGb 761 and donepezil in the treatment of mild\nto moderate Alzheimer’s dementia, so the use of both\nsubstances can be justified. In addition, this study\ncontributes to establish the efficacy and tolerability of\nthe Ginkgo biloba special extract E.S. in the dementia\nof the Alzheimer type with special respect to moderately\nsevere stages.\nReferences\n1. Ahlemeyer B, Krieglstein J. Pharmacological studies\nsupporting the therapeutic use of Ginkgo biloba extract\nfor\nAlzheimer’s\ndisease.\nPharmacopsychiatry\n2003;\n36(Suppl. 1): S8–S14.\n2. Bastianetto S, Ramassamy C, Dore´ S, Christen Y, Poirier\nJ, Quirion R. The ginkgo biloba extract (EGb 761) pro-\ntects hippocampal neurons against cell death induced by\nb-amyloid. European Journal of Neuroscience 2000; 12:\n1882–1893.\n3. Le Bars PL, Katz MM, Berman N, Itil TM, Freedman\nAM, Schatzberg AF. A placebo-controlled, double-blind,\nrandomized trial of an extract of Ginkgo Biloba for\ndementia. JAMA 1997; 278: 1327–1332.\n4. van Dongen M, van Rossum E, Kessels A, Sielhorst H,\nKnipschild P. Ginkgo for elderly people with dementia\nand age-associated memory impairment: a randomized\nclinical trial. Journal of Clinical Epidemiology 2003; 56:\n367–376.\n5. Maurer K, Ihl R, Dierks T, Frolich L. Clinical efficacy of\nGinkgo Biloba special extract EGb 761 in dementia of the\nAlzheimer type. Journal of Psychiatric Research 1997; 31:\n645–655.\n6. American Psychiatric Association. Diagnostic and Statis-\ntical Manual of Mental Disorders, DSM-IV, 4th edn.\nWashington,\nDC:\nAmerican\nPsychiatric\nAssociation,\n1994.\n7. Reisberg B, Ferris SH. Brief Cognitive Rating Scale\n(BCRS). Psychopharmacology Bulletin 1988; 24: 629–636.\n8. Hachinski VC, Iliff LD, Chiak E, et al. Cerebral blood\nflow in dementia. Archives of Neurology 1975; 32: 632–\n637.\n9. Sheik JI, Yesavage JA. Geriatric Depression Scale (GDS):\nrecent evidence and development of a shorter version. In:\nBrink TL, ed. Clinical Gerontology: a Guide to Assessment\nand Intervention. New York: Hawthorn Press, 1986.\n10. Overall JE, Schaltenbrand R. The SKT neuropsycholog-\nical test battery. Journal of Geriatric Psychiatry and\nNeurology 1992; 5: 220–227.\n11. Boles Ponto L, Schultz SK. Ginkgo Biloba extract: review\nof CNS effects. Annals of Clinical Psychiatry 2003; 15:\n109–119.\n12. Kanowski S, Hoerr R. Ginkgo Biloba extract EGb 761 in\ndementia: intent-to-treat analyses of a 24-week, multi-\ncenter,\ndouble-blind,\nplacebo-controlled,\nrandomized\ntrial. Pharmacopsychiatry 2003; 36: 297–303.\n13. Klinger T, Ibach B, Schoenknecht P, et al. Effect of\ndonepezil in patients with Alzheimer’s disease previously\nuntreated or treated with memantine or nootropic agents\nin Germany: an observational study. Current Medical\nResearch and Opinion 2005; 21: 723–732.\n14. Solomon PR, Adams F, Silver A, Zimmer J, De Veaux R.\nGinkgo for Memory Enhancement: a randomized con-\ntrolled trial. JAMA 2002; 288: 835–840.\n15. Nathan PJ. Can the cognitive enhancing effects of Ginkgo\nBiloba\nbe\nexplained\nby\nits\npharmacology?\nMedical\nHypotheses 2000; 55: 491–493.\n16. Nathan PJ. Ginkgo and Memory. JAMA 2003; 289: 546.\nTable 3 Drop-out: number (%) of patients\nEGb\nDonepezil\nPlacebo\nTotal\n5/25 (20)\n4/25 (16)\n6/26 (23)\nLoss of efficacy\n0\n0\n4 (15.4)\nLoss of follow-up\n3 (12)\n0\n2 (7.6)\nCaregiver request\n2 (8)\n0\n0\nAdverse event\n0\n4 (16)\n0\nGinkgo versus donepezil in Alzheimer’s dementia\n985\n 2006 EFNS European Journal of Neurology 13, 981–985\n 2026-01-11 04:59:38.881 2026-01-11 05:00:24.106
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: knowledge_bases; Type: TABLE DATA; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
COPY pkb_schema.knowledge_bases (id, user_id, name, description, dify_dataset_id, file_count, total_size_bytes, created_at, updated_at) FROM stdin;
|
||
f8cf82ff-9b59-4f0e-babc-55542b33102e user-mock-001 阿尔兹海默症 Neurology 6341bd96-d6ab-4c2b-922e-b9acd7ce0d47 1 192179 2026-01-11 04:59:12.374 2026-01-11 05:00:24.115
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: task_templates; Type: TABLE DATA; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
COPY pkb_schema.task_templates (id, user_id, name, description, prompt, is_public, created_at, updated_at, "outputFields") FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: app_cache; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.app_cache (id, key, value, expires_at, created_at) FROM stdin;
|
||
1 dc:health:dc/tool-b/default-user/1768103357661_5例-病理数据-测试数据1203.xlsx:诊断 {"status": "good", "message": "健康度良好，预计消耗约 0.8k Token（双模型约 1.6k Token）", "avgLength": 326.25, "emptyRate": 0, "totalRows": 4, "estimatedTokens": 783} 2026-01-12 03:49:20.121 2026-01-11 03:49:20.122
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: departments; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.departments (id, tenant_id, name, parent_id, description, created_at, updated_at) FROM stdin;
|
||
dept-cardiology 47ed1c35-b33d-47cd-b1b8-e95df8694e03 心内科 \N 心血管内科 2026-01-11 03:16:02.364 2026-01-11 03:16:02.364
|
||
dept-neurology 47ed1c35-b33d-47cd-b1b8-e95df8694e03 神经内科 \N 神经内科 2026-01-11 03:16:02.376 2026-01-11 03:16:02.376
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: job; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.job (id, name, priority, data, state, retry_limit, retry_count, retry_delay, retry_backoff, retry_delay_max, expire_seconds, deletion_seconds, singleton_key, singleton_on, start_after, created_on, started_on, completed_on, keep_until, output, dead_letter, policy) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: job_common; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.job_common (id, name, priority, data, state, retry_limit, retry_count, retry_delay, retry_backoff, retry_delay_max, expire_seconds, deletion_seconds, singleton_key, singleton_on, start_after, created_on, started_on, completed_on, keep_until, output, dead_letter, policy) FROM stdin;
|
||
186080da-3f5a-44b6-9097-a724fa36db94 dc_toolc_parse_excel 0 {"userId": "test-user-001", "__jobId": "14a76fc6-43d5-4a97-bf68-8c0506063eee", "fileKey": "dc/tool-c/sessions/test-user-001/1768103324515-G鼓膜穿孔数据-缺失.xlsx", "fileName": "G鼓膜穿孔数据-缺失.xlsx", "sessionId": "9ae56d64-70db-49e4-9dcc-4a09241d3533", "__createdAt": "2026-01-11T03:48:44.526Z"} completed 3 0 60 f \N 21600 604800 \N \N 2026-01-11 03:48:44.871543+00 2026-01-11 03:48:44.871543+00 2026-01-11 03:48:45.325529+00 2026-01-11 03:48:45.444479+00 2026-01-25 03:48:44.871543+00 {"success": true, "sessionId": "9ae56d64-70db-49e4-9dcc-4a09241d3533", "totalCols": 14, "totalRows": 96} \N standard
|
||
718e6c56-4642-46b6-8cd5-0587364d149e rvw_review_task 0 {"agents": ["editorial"], "taskId": "7065bce9-d192-46df-84fa-d842513e0f8e", "userId": "user-mock-001", "__jobId": "cb238d79-9a44-4977-9941-476f4b0f381e", "modelType": "deepseek-v3", "__createdAt": "2026-01-11T03:57:00.391Z", "extractedText": "骶骨瘤患者围术期大量输血的术前危险因素分析\\n\\n吴桂玉 刘英 冯晓敏 王超 徐东江（首都医科大学附属北京积水潭医院输血科）\\n\\n摘要：目的 研究骶骨瘤围术期大量输血的术前危险因素。方法 回顾性分析本院2021年9月~ 2024年9月的33例骶骨瘤手术患者临床资料(基本资料、基础病史)、术前相关实验室检查(全血细胞计数、凝血 5 项、肝功能)和术中、术后 24h 内血液制品种类及用量等指标。根据术中或术后24h红细胞输注量将患者分为大量输血组和非大量输血组,对两组患者的临床资料和术前相关实验室检查进行单因素分析,最后对经过单因素分析有统计学意义的变量做多因素logistic回归分析。 结果 单因素分析发现两组患者之间的纤维蛋白原（FIB）、凝血酶原时间(PT)、活化部分凝血酶原时间（APTT）,丙氨酸氨基转移酶酶(ALT)、手术时长（h），手术部位，手术体位的差异具有统计学意义（P＜0.05）。回归分析手术部位（1）、手术体位（1）、手术时长(1)的值差异显著（P＜0.005）。结论 手术部位为骶尾部、手术体位为俯卧位以及手术时长为3~4h在本研究中具有统计学显著性，且是骶骨瘤患者围术期大量输血的术前危险因素。 \\n\\n关键词：骶骨肿瘤手术；围术期血液管理；大量输血：输血影响因素 \\n\\nPreoperative Risk Factors Associated with Massive Blood Transfusion in Patients with Sacral Tumors During the Perioperative Period\\n\\nWu Guiyu, Liu Ying, Feng Xiaomin, WangChao, Xu Dongjiang (Department of Blood Transfusion, Beijing Jishuitan Hospital, Capital Medical University)\\n\\nAbstract: Objective: To investigate the preoperative risk factors associated with massive blood transfusion during the perioperative period of sacral tumor surgery. Methods: This retrospective study analyzed clinical data, including basic information and medical history, preoperative laboratory tests (complete blood count, coagulation function, liver function), and blood product types and quantities administered intraoperatively and within 24 hours postoperatively for 33 patients who underwent sacral tumor surgery at our hospital from September 2021 to September 2024. Patients were categorized into two groups based on the volume of red blood cell transfusions received during or within 24 hours after surgery: the massive transfusion group and the non-massive transfusion group. Univariate analysis was conducted on clinical data and preoperative laboratory tests, followed by multivariate logistic regression analysis for variables that showed statistical significance in univariate analysis. Results: Univariate analysis revealed statistically significant differences between the two groups in fibrinogen (FIB), prothrombin time (PT), activated partial thromboplastin time (APTT), alanine aminotransferase (ALT), operation duration, surgical site, and surgical position (P < 0.05). Multivariate regression analysis identified significant differences in surgical site, surgical position, and operation duration (P < 0.005). Conclusion: The findings indicate that a surgical site at the sacrococcygeal region, a prone surgical position, and an operation duration of 3-4 hours are statistically significant preoperative risk factors for massive blood transfusion in patients undergoing sacral tumor surgery.\\n\\nKey words: sacral tumor surgery; Perioperative blood management; Massive blood transfusion: influencing factors of blood transfusion\\n\\n 骶骨区域常见的良性肿瘤类型包括骨母细胞瘤、骨巨细胞瘤以及动脉瘤样骨囊肿等，而恶性肿瘤则主要有脊索瘤、软骨瘤等。对于骶骨脊索瘤的治疗，广泛切除以确保安全的外科边界是当前的主流方法。然而，由于对肿瘤边界认知的不足、局部解剖结构的复杂性以及术中可能的大量失血等多重因素，骶骨肿瘤切除手术的精确性往往会受到一定程度的影响[1]。此外，骶骨肿瘤在早期阶段往往难以察觉，其侵袭性强、解剖位置复杂且血运丰富，这些因素共同导致了手术难度的大幅增加[2]。目前，国内外关于骶骨肿瘤用血分析的相关报道仍较为罕见。本文基于33例骶骨瘤患者的临床资料，结合术前相关实验室检查及围手术期输血量的统计数据，进行了深入的分析，旨在筛选出骶骨瘤患者围手术期大量输血的术前危险因素。这不仅有助于临床医生识别出可能需要大量输血的高危患者，还为麻醉科医生制定输血策略及实施积极干预提供了有力的依据。\\n\\n1 材料与方法\\n\\n一般资料\\n\\n收集2021年9月~ 2024年9月的骶骨瘤手术33例骶骨瘤手术患者临床资料。纳入标准:诊断为骶骨瘤并行开放性手术患者;排除标准:(1)术中、术后不能统计血液制品使用情况的患者;(2)资料收集不完全的患者。\\n\\n1.2方法 统计患者性别，年龄，术前血红蛋白（Hb）(g/L),术前红细胞压积（Hct）(%),凝血酶原时间(PT)、活化部分凝血酶原时间（APTT）,丙氨酸氨基转移酶酶(ALT)，术前纤维蛋白原（FIB）(mg/dL)、发病位置、肿瘤类型、是否有其他高危因素，手术体位，手术部位，手术方式、手术分级、麻醉分级、手术时长(h)、术中出血量(mL)等。对所有数据进行整理分析，根据术中，术后红细胞输注量对研究对象进行分组，以术中红细胞输注量≥4U（200mL红细胞为1U）或术后24h红细胞输注量≥5U为标准，分为大量输血组（Massive Blood Transfusion Group 简称MBT组）和红细胞注量＜4U分为非大量输血组（Non- Massive Blood Transfusion Group简称NMBT组）。\\n\\n1.3 采用 SPSS20.0 软件进行数据统计,符合正态分布的计量资料以 x ±s 表示,采用 t 检验;不符合正态分布的计量资料以 M (Q 1 ,Q 3 )表示,采用秩和检验。 计数资料以例数或百分比表示,采用 X2 检验。首先用单因素分析对各观察项目(自变量)进行统计分析, 后对有统计学意义的变量及相关因素进行多因素 logistic 回归分析。以（P＜0.05）为差异有统计学意义\\n\\n2 结果\\n\\n2.1 一般资料\\n\\n 51例诊断为骶骨瘤行手术的患者，排除不能统计的血液制品使用情况和资料收集不完全者1例，剩余33例。将33例患者分为MBT组（n=20）和NMBT组（n=13）。具体内容见表1.\\n\\n2.2单因素分析\\n\\n2.2.1 连续性变量\\n\\n 两组患者的纤维蛋白原（FIB）、凝血酶原时间（PT）、活化部分凝血酶原时间（APTT）、 丙氨酸氨基转移酶酶(ALT)、手术时长差的异有统计学意义（P＜0.05），见表1。\\n\\n表1 两组患者连续性变量的比较\\n\\n\\n\\nNMBT\\n\\nMBT\\n\\n\\n\\n项目\\n\\n（n=13)\\n\\n(n=20)\\n\\nP\\n\\n年龄（岁）a\\n\\n45.00(31.00,58.50)\\n\\n39.5(32.5,65.0)\\n\\n0.976\\n\\nRBC(×1012/L)a\\n\\n4.82(4.62,5.23)\\n\\n4.86(4.15,5.26)\\n\\n0.748\\n\\nHct(%)a\\n\\n42.30(40.60,45.30)\\n\\n41.00(38.45,46.45)\\n\\n0.804\\n\\nHb(g/L)a\\n\\n143.00(137.00,153.50)\\n\\n139(120.75,157.00)\\n\\n0.206\\n\\nPT(s) *\\n\\n12.64±0.53\\n\\n13.25±1.27\\n\\n0.002*\\n\\nAPTT(s) a *\\n\\n34.90(32.25,36.45)\\n\\n36.45(33.65,39.75)\\n\\n0.013*\\n\\nFIB(x±s,g/L) *\\n\\n317.77±67.05\\n\\n327.30±114.40\\n\\n0.001*\\n\\nALT(x±s,U/L) *\\n\\n29.92±11.00\\n\\n21.8±13.04\\n\\n0.001*\\n\\n手术时间(x±s,h) *\\n\\n2.743±0.822\\n\\n4.140±1.618\\n\\n0.001*\\n\\nRBC:红细胞计数；Hct:血细胞比容；Hb:血红蛋白; PT:凝血酶时间; APTT:活化部分凝血活酶时间;FIB:纤维蛋白原;ALT:丙氨酸氨基转移酶;a:M(Q 1 ,Q 3 )。\\n\\n2.2.2 分类变量\\n\\n 对于分类变量采取x2检验，结果显示两组患者手术部位，手术体位的差异有统计学意义（P＜0.05），见表2。\\n\\n表2 两组患者分类变量的比较（n）\\n\\n \\n\\n \\n\\nNMBT\\n\\nMBT\\n\\n \\n\\n \\n\\n \\n\\n \\n\\n（n=13)\\n\\n(n=20)\\n\\nx2\\n\\np\\n\\n性别\\n\\n男\\n\\n7\\n\\n11\\n\\n0.004 \\n\\n0.948 \\n\\n女\\n\\n6\\n\\n9\\n\\n手术部位*\\n\\n骶尾部\\n\\n6\\n\\n16\\n\\n4.062 \\n\\n0.044 *\\n\\n其他\\n\\n7\\n\\n4\\n\\n手术体位*\\n\\n俯卧位\\n\\n9\\n\\n19\\n\\n4.070 \\n\\n0.044 *\\n\\n其他\\n\\n4\\n\\n1\\n\\n麻醉分级\\n\\nⅠ~Ⅱ\\n\\n11\\n\\n18\\n\\n0.214 \\n\\n0.643 \\n\\nⅢ~Ⅳ\\n\\n2\\n\\n2\\n\\n肿瘤分类\\n\\n良性\\n\\n7\\n\\n12\\n\\n0.122 \\n\\n0.727 \\n\\n恶性 \\n\\n6\\n\\n8\\n\\n是否有计算机导航\\n\\n有\\n\\n4\\n\\n8\\n\\n0.290 \\n\\n0.590 \\n\\n无\\n\\n9\\n\\n12\\n\\n手术方式\\n\\n切除\\n\\n12\\n\\n18\\n\\n0.510 \\n\\n0.822 \\n\\n其他\\n\\n1\\n\\n2\\n\\n高危因素\\n\\n有\\n\\n0\\n\\n4\\n\\n2.959 \\n\\n0.085 \\n\\n \\n\\n无\\n\\n13\\n\\n16\\n\\n2.3 多因素分析结果\\n\\n 我们对单因素分析中具有统计意义的自变量进行了logistic回归分析，结果显示：手术部位（1）、手术体位（1）、手术时长(1)的值差异显著（P＜0.005）。这意味着，术前评估时手术部位为骶尾部、手术体位为俯卧位、手术时长3~4小时是危险因素，患者术后需要大量输血的可能性就越大。具体数据请见表3。\\n\\n表3 两组患者多因素logistic回归分析结果\\n\\n \\n\\nB\\n\\nS.E.\\n\\nWald\\n\\nP\\n\\nOR\\n\\n95% C.I.\\n\\n手术部位(1) *\\n\\n-3.30\\n\\n1.49\\n\\n4.91\\n\\n0.027 *\\n\\n0.04\\n\\n0.00\\n\\n0.68\\n\\n手术体位(1) *\\n\\n3.90\\n\\n1.71\\n\\n5.21\\n\\n0.022 *\\n\\n49.23\\n\\n1.74\\n\\n1395.27\\n\\n手术时长(1) *\\n\\n3.39\\n\\n1.46\\n\\n5.44\\n\\n0.020 *\\n\\n29.73\\n\\n1.72\\n\\n514.72\\n\\n手术时长(3)\\n\\n-1.14\\n\\n1.67\\n\\n0.46\\n\\n0.496\\n\\n0.32\\n\\n0.01\\n\\n8.50\\n\\n性别(1)\\n\\n1.24\\n\\n1.32\\n\\n0.88\\n\\n0.349\\n\\n3.45\\n\\n0.26\\n\\n46.07\\n\\n年龄(1)\\n\\n23.38\\n\\n6878.97\\n\\n0.00\\n\\n0.997\\n\\n14297314107.83\\n\\n0.00\\n\\n.\\n\\nPT\\n\\n\\n\\n\\n\\n0.00\\n\\n1.000\\n\\n\\n\\n\\n\\n\\n\\nPT(1)\\n\\n18.45\\n\\n29235.68\\n\\n0.00\\n\\n0.999\\n\\n102688179.44\\n\\n0.00\\n\\n.\\n\\nPT(2)\\n\\n-29.79\\n\\n37330.28\\n\\n0.00\\n\\n0.999\\n\\n0.00\\n\\n0.00\\n\\n.\\n\\nAPTT(1)\\n\\n25.95\\n\\n6878.97\\n\\n0.00\\n\\n0.997\\n\\n186231435743.80\\n\\n0.00\\n\\n.\\n\\nFIB(1)\\n\\n-1.16\\n\\n1.22\\n\\n0.90\\n\\n0.343\\n\\n0.31\\n\\n0.03\\n\\n3.45\\n\\nALT(1)\\n\\n-2.60\\n\\n1.39\\n\\n3.52\\n\\n0.061\\n\\n0.07\\n\\n0.01\\n\\n1.13\\n\\n常量\\n\\n-44.00\\n\\n31570.34\\n\\n0.00\\n\\n0.999\\n\\n0.00\\n\\n\\n\\n\\n\\n\\n\\n3.讨论\\n\\n我院计算机导航辅助骨科手术导航技术已经广泛应用于脊柱和骨关节等临床骨科手术，近年来也逐渐应用于骨肿瘤的外科治疗，包括各类骶骨瘤的手术切除 [1] 。根据临床病例分析，对于确诊为骶骨瘤的患者，其适应症明确指向手术干预能够有效切除病灶。相比之下，非手术方式无法达到去除病灶的目的。手术不仅能够精准地去除肿瘤病灶，解除因肿瘤造成的压迫，还能通过彻底切除肿瘤来显著缓解疼痛等症状。因此，综合考虑手术与非手术治疗的效果，手术被确立为治疗骶骨瘤的最佳方案。\\n\\n手术时间的延长通常会导致术中失血增加和感染等风险，根范围据文献报道骶骨脊索切除术平均用时大多超过5h，失血量多在3000~5000mL[1]。骶骨作为骨盆后壁的重要组成部分，其供血极为丰富，因此在进行该区域的手术时，往往面临出血多且止血困难的挑战，使得手术难度大大增加。对于骶骨瘤的手术而言，主要采用边缘性切除或刮除的方法。然而，要确保手术真正达到安全有效的肿瘤治疗切除边界，不仅需要严谨精细的术前研究计划安排，还离不开医生丰富的手术操作经验。这两者是确保手术成功不可或缺的关键因素。\\n\\n手术是一个复杂的过程，需要多科室的紧密协作才能完成。自身输血作为减少异体血输入、避免传染病传播及异体抗原反应的最有效手段，一直受到输血界的广泛提倡。然而，由于自身输血具有严格的适应症，它仅是解决血液库存紧张、血液疾病及疑难血型问题的有效手段之一[15]。在骶骨瘤手术中，大多数情况下仍需依赖异体输血，这进一步体现了术前备血的重要性。为了确保骶骨瘤手术的顺利进行，临床医生在确定手术日期后，应提前与输血科沟通，并送检血样进行血型鉴定和不规则抗体筛查。\\n\\n本研究结果表明，在骶骨瘤手术患者的单因素分析中，纤维蛋白原（FIB）、凝血酶原时间（PT）、活化部分凝血酶原时间（APTT）以及丙氨酸氨基转移酶（ALT）的水平，以及手术时长的差异，均呈现出统计学上的显著性（p＜0.005），显示出一定的影响趋势。然而，这些因素并非骶骨瘤围手术期大量输血的直接术前决定性因素。此外，本研究还发现，血红蛋白（Hb）水平、全血红细胞计数（RBC）、血细胞比容（Hct）、肿瘤的分类、麻醉分级、患者是否存在基础疾病、手术是否采用计算机导航辅助，以及具体的手术方式等，均未被证实为骶骨瘤围手术期大量输血的高危因素。上述结论均基于严谨的数据分析和充分的案例支持，确保了研究的客观性和权威性。\\n\\n我们对影响骶骨瘤手术大量输血的因素进行了logistic回归分析，结果显示：手术部位为骶尾部时输血风险降低4%（p＜0.005），手术体位为俯卧位时输血风险增加近50倍（p＜0.005），手术时长3~4小时时输血风险增加30倍（p＜0.005）。性别、年龄、全血细胞计数、凝血、肝功能等不是术前大量输血的危险因素。临床医生应关注手术位置和体位，以及手术时间长短。\\n\\n综上所述，在临床实践中，医生应针对这些高风险因素制定更为详尽的术前准备和术中管理计划，以降低输血风险。基于这些统计学显著性变量，医生可以对患者进行更为精准的术前评估和风险分层，从而制定个性化的输血管理策略。这有助于优化血液资源的使用，同时提高患者的手术安全性和满意度。通过定期回顾和分析输血病例，发现潜在的风险因素并采取相应措施进行干预，以不断提高输血管理的质量和效率。\\n\\n 参 考 文 献\\n\\n［１］\\t杨勇昆 李远 张清 牛晓辉.计算机导航辅助骶骨脊索瘤的精确切除的手术效果和安全性研究. 中国骨与关节杂志 2021 年 3 月第 10 卷第 3 期 Chinese Journal of Bone and Joint, March 2021, Vol 10, No.3.228-234.\\n\\n［２］\\t战春1，徐林2.手术治疗8例巨大骶骨瘤.中国中西医结合外科杂志2009年4月第15卷第2期。130-131\\n\\n［３］\\t陈元利1 ,傅 洪1 △ ,周润芳1 ,朱厚伟1 ,张 星1 ,孔令文2 ,廖 群，A型主动脉夹层患者围术期大量输血的术前危险因素分析.重庆医学.2023,52（24）；3775-3784.\\n\\n［４］\\t邵方真1 ，闫优萍1 ，朱俊2 ，常圣雅3 ，钟丽慧.血栓弹力图与FIB联合预测普外科患者围术期大量输血的效能评价.河南医学2024年5月第35卷第10期.1436-1439.\\n\\n［５］\\t辛宏杰 .大量输血患者用血情况及检验结果的回顾性分析.临床研究2020年04月第28卷第04期：31-32\\n\\n［６］\\t郭卫，李大森，唐顺，姬涛.骶骨肿瘤的类型和临床特点. 中国脊柱脊髓杂志2010年第20卷第5期.380-381. \\n\\n［７］\\t胡海，杨惠林，王根椿.骶骨肿瘤手术失血量新统计方法初步探索. 实用骨科杂志第17卷，第4期，2011年4月.319-320. \\n\\n［８］\\t王默然,王峻,李星晨,刘浩,葛艳玲.原发性恶性骨肉瘤术中输血影响因素的回顾性研究. 中国输血杂志２０２２年１月第３５卷第１期.35-38.\\n\\n［９］\\t谭刘欣，牛梦林，孙巍．腹膜后肿瘤患者术中输血影响因素及预后分析．中国输血杂志，２０１９，３２（３）：２５７⁃２５９．\\n\\n［１０］\\tKlimo P，Rao G．Schmidt RH．et a1．Nerve sheath tumors involving the sacrum：ease report and classification sehemo[J1.Neurosurg Focus。2003，15(2)：I-6．\\n\\n［１１］\\tarner MA, Shore-Lesserson L, Shander A, et al. Perioperative anemia: prevention, diagnosis,and management throughout the spectrum of perioperative care [J]. Anesth Analg, 2020, 130(5): 1364-1380. \\n\\n［１２］\\tThiele T, Greinacher A. Platelet Transfusion in Perioperative Medicine [J]. Semin Thromb Hemost, 2020, 46(1): 50-61. \\n\\n［１３］\\tLin JY, Liu ZQ, Hu JC, et al. Factors affecting the adverse reactions to blood transfusion during orthopedic surgery and prediction model development [J]. Chin J Mod Med, 2023, 33(4): 71-77. \\n\\n［１４］\\t林娇雅, 刘自强, 胡建超, 等. 骨科手术输血后不良反应的影响因素及预测模型构建与分析[J]. 中国现代医学杂志, 2023, 33(4): 71-77. \\n\\n［１５］\\t刘英，王峻，葛艳玲，疑难交叉配配血成因与交叉配血策略的分析.中国输血杂志，2020，32（2），152-154.\\n\\n"} completed 3 0 60 f \N 21600 604800 \N \N 2026-01-11 03:57:00.652527+00 2026-01-11 03:57:00.652527+00 2026-01-11 03:57:01.516566+00 2026-01-11 03:58:10.98643+00 2026-01-25 03:57:00.652527+00 {"taskId": "7065bce9-d192-46df-84fa-d842513e0f8e", "success": true, "overallScore": 72, "editorialScore": 72, "durationSeconds": 69, "methodologyScore": null} \N standard
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: permissions; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.permissions (id, code, name, description, module, created_at) FROM stdin;
|
||
1 prompt:view 查看Prompt 查看Prompt列表和历史版本 prompt 2026-01-11 03:16:02.425
|
||
2 prompt:edit 编辑Prompt 创建/修改DRAFT版本 prompt 2026-01-11 03:16:02.433
|
||
3 prompt:debug 调试Prompt 开启调试模式（核心权限） prompt 2026-01-11 03:16:02.439
|
||
4 prompt:publish 发布Prompt 发布DRAFT为ACTIVE prompt 2026-01-11 03:16:02.445
|
||
5 tenant:view 查看租户 查看租户列表 tenant 2026-01-11 03:16:02.453
|
||
6 tenant:create 创建租户 创建新租户 tenant 2026-01-11 03:16:02.464
|
||
7 tenant:edit 编辑租户 编辑租户信息 tenant 2026-01-11 03:16:02.471
|
||
8 tenant:delete 删除租户 删除租户 tenant 2026-01-11 03:16:02.481
|
||
9 user:view 查看用户 查看用户列表 user 2026-01-11 03:16:02.49
|
||
10 user:create 创建用户 创建新用户 user 2026-01-11 03:16:02.499
|
||
11 user:edit 编辑用户 编辑用户信息 user 2026-01-11 03:16:02.508
|
||
12 user:delete 删除用户 删除用户 user 2026-01-11 03:16:02.519
|
||
13 quota:view 查看配额 查看配额使用情况 quota 2026-01-11 03:16:02.527
|
||
14 quota:allocate 分配配额 分配配额给科室/用户 quota 2026-01-11 03:16:02.535
|
||
15 audit:view 查看审计日志 查看操作审计日志 audit 2026-01-11 03:16:02.541
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: queue; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.queue (name, policy, retry_limit, retry_delay, retry_backoff, retry_delay_max, expire_seconds, retention_seconds, deletion_seconds, dead_letter, partition, table_name, deferred_count, queued_count, warning_queued, active_count, total_count, singletons_active, monitor_on, maintain_on, created_on, updated_on) FROM stdin;
|
||
rvw_review_task standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 1 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.516991+00 2026-01-11 03:48:02.516991+00
|
||
dc_toolc_parse_excel standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 1 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.517336+00 2026-01-11 03:48:02.517336+00
|
||
dc_extraction_batch standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 0 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.517069+00 2026-01-11 03:48:02.517069+00
|
||
asl_screening_batch standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 0 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.516914+00 2026-01-11 03:48:02.516914+00
|
||
__pgboss__send-it standard 2 0 f \N 900 1209600 604800 \N f job_common 0 0 0 0 0 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.51928+00 2026-01-11 03:48:02.51928+00
|
||
iit_redcap_poll standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 0 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.520764+00 2026-01-11 03:48:02.520764+00
|
||
iit_quality_check standard 3 60 f \N 21600 1209600 604800 \N f job_common 0 0 0 0 0 \N 2026-01-11 05:15:03.356689+00 2026-01-11 05:12:03.323539+00 2026-01-11 03:48:02.522191+00 2026-01-11 03:48:02.522191+00
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: role_permissions; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.role_permissions (id, role, permission_id, created_at) FROM stdin;
|
||
1 SUPER_ADMIN 1 2026-01-11 03:16:02.55
|
||
2 SUPER_ADMIN 2 2026-01-11 03:16:02.561
|
||
3 SUPER_ADMIN 3 2026-01-11 03:16:02.567
|
||
4 SUPER_ADMIN 4 2026-01-11 03:16:02.572
|
||
5 SUPER_ADMIN 5 2026-01-11 03:16:02.577
|
||
6 SUPER_ADMIN 6 2026-01-11 03:16:02.582
|
||
7 SUPER_ADMIN 7 2026-01-11 03:16:02.586
|
||
8 SUPER_ADMIN 8 2026-01-11 03:16:02.59
|
||
9 SUPER_ADMIN 9 2026-01-11 03:16:02.595
|
||
10 SUPER_ADMIN 10 2026-01-11 03:16:02.599
|
||
11 SUPER_ADMIN 11 2026-01-11 03:16:02.604
|
||
12 SUPER_ADMIN 12 2026-01-11 03:16:02.608
|
||
13 SUPER_ADMIN 13 2026-01-11 03:16:02.612
|
||
14 SUPER_ADMIN 14 2026-01-11 03:16:02.616
|
||
15 SUPER_ADMIN 15 2026-01-11 03:16:02.621
|
||
16 PROMPT_ENGINEER 1 2026-01-11 03:16:02.624
|
||
17 PROMPT_ENGINEER 2 2026-01-11 03:16:02.629
|
||
18 PROMPT_ENGINEER 3 2026-01-11 03:16:02.633
|
||
19 PROMPT_ENGINEER 4 2026-01-11 03:16:02.637
|
||
20 HOSPITAL_ADMIN 9 2026-01-11 03:16:02.641
|
||
21 HOSPITAL_ADMIN 10 2026-01-11 03:16:02.646
|
||
22 HOSPITAL_ADMIN 11 2026-01-11 03:16:02.649
|
||
23 HOSPITAL_ADMIN 13 2026-01-11 03:16:02.654
|
||
24 HOSPITAL_ADMIN 14 2026-01-11 03:16:02.659
|
||
25 HOSPITAL_ADMIN 15 2026-01-11 03:16:02.664
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: schedule; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.schedule (name, key, cron, timezone, data, options, created_on, updated_on) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: subscription; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.subscription (event, name, created_on, updated_on) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: tenant_members; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.tenant_members (id, tenant_id, user_id, role, joined_at) FROM stdin;
|
||
f40eddb7-ca75-4937-9618-2036f4552e8e 47ed1c35-b33d-47cd-b1b8-e95df8694e03 91b5c88c-2aee-42b1-be91-cdf2f14648c0 HOSPITAL_ADMIN 2026-01-11 03:16:02.398
|
||
5aac6905-1d4b-41e3-8558-a974886e34a5 47ed1c35-b33d-47cd-b1b8-e95df8694e03 52033431-55f4-4fe2-b749-c6c497912152 USER 2026-01-11 03:16:02.42
|
||
6c902bce-4e3f-4dca-8882-47305d7abced 47ed1c35-b33d-47cd-b1b8-e95df8694e03 1a247c4a-842e-4bd0-96e9-020fded33107 USER 2026-01-11 03:16:02.42
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: tenant_modules; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.tenant_modules (id, tenant_id, module_code, is_enabled, expires_at, created_at) FROM stdin;
|
||
9ed62fa9-942b-4b5a-8a65-e21be9f328ea 47ed1c35-b33d-47cd-b1b8-e95df8694e03 ASL t \N 2026-01-11 03:16:02.694
|
||
28199b15-3bde-4f7a-b49a-8f1ab6beb455 47ed1c35-b33d-47cd-b1b8-e95df8694e03 DC t \N 2026-01-11 03:16:02.703
|
||
b66daeee-294c-4db0-846b-16d2edcf5a99 47ed1c35-b33d-47cd-b1b8-e95df8694e03 PKB t \N 2026-01-11 03:16:02.708
|
||
d150d16c-d7ec-402f-ad4a-85cd18a58a4a 47ed1c35-b33d-47cd-b1b8-e95df8694e03 AIA t \N 2026-01-11 03:16:02.714
|
||
fecc53f4-9fc0-4be9-aefe-146689c0c902 47ed1c35-b33d-47cd-b1b8-e95df8694e03 RVW t \N 2026-01-11 03:16:02.719
|
||
5b6057a0-ac72-4862-be8d-a81a2f80975d c4a00ba6-26a9-4ac7-b8f9-1f71a65edd05 IIT t \N 2026-01-11 03:16:02.725
|
||
d2bc8bc4-4549-48dd-b42b-4fe4bdc97d87 c4a00ba6-26a9-4ac7-b8f9-1f71a65edd05 DC t \N 2026-01-11 03:16:02.731
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: tenant_quota_allocations; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.tenant_quota_allocations (id, tenant_id, target_type, target_key, limit_amount, used_amount, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: tenant_quotas; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.tenant_quotas (id, tenant_id, quota_type, total_amount, used_amount, reset_period, last_reset_at, created_at, updated_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: tenants; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.tenants (id, code, name, type, status, config, total_quota, used_quota, contact_name, contact_phone, contact_email, created_at, updated_at, expires_at) FROM stdin;
|
||
eb4e93b7-0210-4bf5-b853-cbea49cdadf8 yizhengxun 医证讯科技 INTERNAL ACTIVE {"logo": null, "systemName": "AI临床研究平台 - 运营管理端", "primaryColor": "#1890ff", "backgroundImage": null} 999999999 0 \N \N \N 2026-01-11 03:16:02.321 2026-01-11 03:16:02.321 \N
|
||
47ed1c35-b33d-47cd-b1b8-e95df8694e03 demo-hospital 示范医院 HOSPITAL ACTIVE {"logo": null, "systemName": "示范医院临床研究平台", "primaryColor": "#1890ff", "backgroundImage": null} 1000000 0 张主任 13800138000 zhang@demo-hospital.com 2026-01-11 03:16:02.354 2026-01-11 03:16:02.354 \N
|
||
c4a00ba6-26a9-4ac7-b8f9-1f71a65edd05 demo-pharma 示范药企 PHARMA ACTIVE {"logo": null, "systemName": "示范药企IIT管理平台", "primaryColor": "#52c41a", "backgroundImage": null} 2000000 0 李经理 13900139000 li@demo-pharma.com 2026-01-11 03:16:02.383 2026-01-11 03:16:02.383 \N
|
||
tenant-mock-001 mock-tenant 测试租户 INTERNAL ACTIVE {} 0 0 \N \N \N 2026-01-11 04:56:51.805 2026-01-11 04:56:51.805 \N
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: users; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.users (id, phone, password, email, is_default_password, password_changed_at, name, tenant_id, department_id, avatar_url, role, status, kb_quota, kb_used, trial_ends_at, is_trial, last_login_at, created_at, updated_at) FROM stdin;
|
||
6a1ba974-cf74-4d69-801b-9bc1923bfb80 13800000001 $2a$10$gakiN/CxLYf137J4aG1n1eApNePLBn8rfXzwoXahPhqMKRJMg1lbe \N f \N 超级管理员 eb4e93b7-0210-4bf5-b853-cbea49cdadf8 \N \N SUPER_ADMIN active 3 0 \N f \N 2026-01-11 03:16:02.334 2026-01-11 03:16:02.334
|
||
ec92bd43-7352-445c-bcb1-5e8f64af6c95 13800000002 $2a$10$gakiN/CxLYf137J4aG1n1eApNePLBn8rfXzwoXahPhqMKRJMg1lbe \N f \N Prompt工程师 eb4e93b7-0210-4bf5-b853-cbea49cdadf8 \N \N PROMPT_ENGINEER active 3 0 \N f \N 2026-01-11 03:16:02.344 2026-01-11 03:16:02.344
|
||
91b5c88c-2aee-42b1-be91-cdf2f14648c0 13800138001 $2a$10$gakiN/CxLYf137J4aG1n1eApNePLBn8rfXzwoXahPhqMKRJMg1lbe \N t \N 张主任 47ed1c35-b33d-47cd-b1b8-e95df8694e03 dept-cardiology \N HOSPITAL_ADMIN active 3 0 \N f \N 2026-01-11 03:16:02.39 2026-01-11 03:16:02.39
|
||
52033431-55f4-4fe2-b749-c6c497912152 13800138002 $2a$10$gakiN/CxLYf137J4aG1n1eApNePLBn8rfXzwoXahPhqMKRJMg1lbe \N t \N 李医生 47ed1c35-b33d-47cd-b1b8-e95df8694e03 dept-cardiology \N USER active 3 0 \N f \N 2026-01-11 03:16:02.407 2026-01-11 03:16:02.407
|
||
1a247c4a-842e-4bd0-96e9-020fded33107 13800138003 $2a$10$gakiN/CxLYf137J4aG1n1eApNePLBn8rfXzwoXahPhqMKRJMg1lbe \N t \N 王医生 47ed1c35-b33d-47cd-b1b8-e95df8694e03 dept-neurology \N USER active 3 0 \N f \N 2026-01-11 03:16:02.413 2026-01-11 03:16:02.413
|
||
user-mock-001 13800000000 $2b$10$mockhashedpassword123456789 mock@test.com t \N 测试用户 tenant-mock-001 \N \N USER active 3 1 \N f \N 2026-01-11 04:56:51.805 2026-01-11 04:59:12.379
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: verification_codes; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.verification_codes (id, phone, code, type, expires_at, is_used, attempts, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: version; Type: TABLE DATA; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
COPY platform_schema.version (version, cron_on) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: admin_logs; Type: TABLE DATA; Schema: public; Owner: postgres
|
||
--
|
||
|
||
COPY public.admin_logs (id, admin_id, action, resource_type, resource_id, details, ip_address, user_agent, created_at) FROM stdin;
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: users; Type: TABLE DATA; Schema: public; Owner: postgres
|
||
--
|
||
|
||
COPY public.users (id, email, password, name, avatar_url, role, status, kb_quota, kb_used, trial_ends_at, is_trial, last_login_at, created_at, updated_at) FROM stdin;
|
||
user-mock-001 mock@test.com $2b$10$mockhashedpassword123456789 测试用户 \N user active 3 0 \N f \N 2026-01-11 03:55:37.57 2026-01-11 03:55:37.57
|
||
\.
|
||
|
||
|
||
--
|
||
-- Data for Name: review_tasks; Type: TABLE DATA; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
COPY rvw_schema.review_tasks (id, user_id, file_name, file_size, file_path, extracted_text, word_count, status, selected_agents, editorial_review, methodology_review, overall_score, editorial_score, methodology_score, methodology_status, pico_extract, is_archived, archived_at, model_used, started_at, completed_at, duration_seconds, error_message, created_at, updated_at) FROM stdin;
|
||
7065bce9-d192-46df-84fa-d842513e0f8e user-mock-001 骶骨瘤患者围术期大量输血的术前危险因素分析及输血策略2月27.docx 35843 \N 骶骨瘤患者围术期大量输血的术前危险因素分析\n\n吴桂玉 刘英 冯晓敏 王超 徐东江（首都医科大学附属北京积水潭医院输血科）\n\n摘要：目的 研究骶骨瘤围术期大量输血的术前危险因素。方法 回顾性分析本院2021年9月~ 2024年9月的33例骶骨瘤手术患者临床资料(基本资料、基础病史)、术前相关实验室检查(全血细胞计数、凝血 5 项、肝功能)和术中、术后 24h 内血液制品种类及用量等指标。根据术中或术后24h红细胞输注量将患者分为大量输血组和非大量输血组,对两组患者的临床资料和术前相关实验室检查进行单因素分析,最后对经过单因素分析有统计学意义的变量做多因素logistic回归分析。 结果 单因素分析发现两组患者之间的纤维蛋白原（FIB）、凝血酶原时间(PT)、活化部分凝血酶原时间（APTT）,丙氨酸氨基转移酶酶(ALT)、手术时长（h），手术部位，手术体位的差异具有统计学意义（P＜0.05）。回归分析手术部位（1）、手术体位（1）、手术时长(1)的值差异显著（P＜0.005）。结论 手术部位为骶尾部、手术体位为俯卧位以及手术时长为3~4h在本研究中具有统计学显著性，且是骶骨瘤患者围术期大量输血的术前危险因素。 \n\n关键词：骶骨肿瘤手术；围术期血液管理；大量输血：输血影响因素 \n\nPreoperative Risk Factors Associated with Massive Blood Transfusion in Patients with Sacral Tumors During the Perioperative Period\n\nWu Guiyu, Liu Ying, Feng Xiaomin, WangChao, Xu Dongjiang (Department of Blood Transfusion, Beijing Jishuitan Hospital, Capital Medical University)\n\nAbstract: Objective: To investigate the preoperative risk factors associated with massive blood transfusion during the perioperative period of sacral tumor surgery. Methods: This retrospective study analyzed clinical data, including basic information and medical history, preoperative laboratory tests (complete blood count, coagulation function, liver function), and blood product types and quantities administered intraoperatively and within 24 hours postoperatively for 33 patients who underwent sacral tumor surgery at our hospital from September 2021 to September 2024. Patients were categorized into two groups based on the volume of red blood cell transfusions received during or within 24 hours after surgery: the massive transfusion group and the non-massive transfusion group. Univariate analysis was conducted on clinical data and preoperative laboratory tests, followed by multivariate logistic regression analysis for variables that showed statistical significance in univariate analysis. Results: Univariate analysis revealed statistically significant differences between the two groups in fibrinogen (FIB), prothrombin time (PT), activated partial thromboplastin time (APTT), alanine aminotransferase (ALT), operation duration, surgical site, and surgical position (P < 0.05). Multivariate regression analysis identified significant differences in surgical site, surgical position, and operation duration (P < 0.005). Conclusion: The findings indicate that a surgical site at the sacrococcygeal region, a prone surgical position, and an operation duration of 3-4 hours are statistically significant preoperative risk factors for massive blood transfusion in patients undergoing sacral tumor surgery.\n\nKey words: sacral tumor surgery; Perioperative blood management; Massive blood transfusion: influencing factors of blood transfusion\n\n 骶骨区域常见的良性肿瘤类型包括骨母细胞瘤、骨巨细胞瘤以及动脉瘤样骨囊肿等，而恶性肿瘤则主要有脊索瘤、软骨瘤等。对于骶骨脊索瘤的治疗，广泛切除以确保安全的外科边界是当前的主流方法。然而，由于对肿瘤边界认知的不足、局部解剖结构的复杂性以及术中可能的大量失血等多重因素，骶骨肿瘤切除手术的精确性往往会受到一定程度的影响[1]。此外，骶骨肿瘤在早期阶段往往难以察觉，其侵袭性强、解剖位置复杂且血运丰富，这些因素共同导致了手术难度的大幅增加[2]。目前，国内外关于骶骨肿瘤用血分析的相关报道仍较为罕见。本文基于33例骶骨瘤患者的临床资料，结合术前相关实验室检查及围手术期输血量的统计数据，进行了深入的分析，旨在筛选出骶骨瘤患者围手术期大量输血的术前危险因素。这不仅有助于临床医生识别出可能需要大量输血的高危患者，还为麻醉科医生制定输血策略及实施积极干预提供了有力的依据。\n\n1 材料与方法\n\n一般资料\n\n收集2021年9月~ 2024年9月的骶骨瘤手术33例骶骨瘤手术患者临床资料。纳入标准:诊断为骶骨瘤并行开放性手术患者;排除标准:(1)术中、术后不能统计血液制品使用情况的患者;(2)资料收集不完全的患者。\n\n1.2方法 统计患者性别，年龄，术前血红蛋白（Hb）(g/L),术前红细胞压积（Hct）(%),凝血酶原时间(PT)、活化部分凝血酶原时间（APTT）,丙氨酸氨基转移酶酶(ALT)，术前纤维蛋白原（FIB）(mg/dL)、发病位置、肿瘤类型、是否有其他高危因素，手术体位，手术部位，手术方式、手术分级、麻醉分级、手术时长(h)、术中出血量(mL)等。对所有数据进行整理分析，根据术中，术后红细胞输注量对研究对象进行分组，以术中红细胞输注量≥4U（200mL红细胞为1U）或术后24h红细胞输注量≥5U为标准，分为大量输血组（Massive Blood Transfusion Group 简称MBT组）和红细胞注量＜4U分为非大量输血组（Non- Massive Blood Transfusion Group简称NMBT组）。\n\n1.3 采用 SPSS20.0 软件进行数据统计,符合正态分布的计量资料以 x ±s 表示,采用 t 检验;不符合正态分布的计量资料以 M (Q 1 ,Q 3 )表示,采用秩和检验。 计数资料以例数或百分比表示,采用 X2 检验。首先用单因素分析对各观察项目(自变量)进行统计分析, 后对有统计学意义的变量及相关因素进行多因素 logistic 回归分析。以（P＜0.05）为差异有统计学意义\n\n2 结果\n\n2.1 一般资料\n\n 51例诊断为骶骨瘤行手术的患者，排除不能统计的血液制品使用情况和资料收集不完全者1例，剩余33例。将33例患者分为MBT组（n=20）和NMBT组（n=13）。具体内容见表1.\n\n2.2单因素分析\n\n2.2.1 连续性变量\n\n 两组患者的纤维蛋白原（FIB）、凝血酶原时间（PT）、活化部分凝血酶原时间（APTT）、 丙氨酸氨基转移酶酶(ALT)、手术时长差的异有统计学意义（P＜0.05），见表1。\n\n表1 两组患者连续性变量的比较\n\n\n\nNMBT\n\nMBT\n\n\n\n项目\n\n（n=13)\n\n(n=20)\n\nP\n\n年龄（岁）a\n\n45.00(31.00,58.50)\n\n39.5(32.5,65.0)\n\n0.976\n\nRBC(×1012/L)a\n\n4.82(4.62,5.23)\n\n4.86(4.15,5.26)\n\n0.748\n\nHct(%)a\n\n42.30(40.60,45.30)\n\n41.00(38.45,46.45)\n\n0.804\n\nHb(g/L)a\n\n143.00(137.00,153.50)\n\n139(120.75,157.00)\n\n0.206\n\nPT(s) *\n\n12.64±0.53\n\n13.25±1.27\n\n0.002*\n\nAPTT(s) a *\n\n34.90(32.25,36.45)\n\n36.45(33.65,39.75)\n\n0.013*\n\nFIB(x±s,g/L) *\n\n317.77±67.05\n\n327.30±114.40\n\n0.001*\n\nALT(x±s,U/L) *\n\n29.92±11.00\n\n21.8±13.04\n\n0.001*\n\n手术时间(x±s,h) *\n\n2.743±0.822\n\n4.140±1.618\n\n0.001*\n\nRBC:红细胞计数；Hct:血细胞比容；Hb:血红蛋白; PT:凝血酶时间; APTT:活化部分凝血活酶时间;FIB:纤维蛋白原;ALT:丙氨酸氨基转移酶;a:M(Q 1 ,Q 3 )。\n\n2.2.2 分类变量\n\n 对于分类变量采取x2检验，结果显示两组患者手术部位，手术体位的差异有统计学意义（P＜0.05），见表2。\n\n表2 两组患者分类变量的比较（n）\n\n \n\n \n\nNMBT\n\nMBT\n\n \n\n \n\n \n\n \n\n（n=13)\n\n(n=20)\n\nx2\n\np\n\n性别\n\n男\n\n7\n\n11\n\n0.004 \n\n0.948 \n\n女\n\n6\n\n9\n\n手术部位*\n\n骶尾部\n\n6\n\n16\n\n4.062 \n\n0.044 *\n\n其他\n\n7\n\n4\n\n手术体位*\n\n俯卧位\n\n9\n\n19\n\n4.070 \n\n0.044 *\n\n其他\n\n4\n\n1\n\n麻醉分级\n\nⅠ~Ⅱ\n\n11\n\n18\n\n0.214 \n\n0.643 \n\nⅢ~Ⅳ\n\n2\n\n2\n\n肿瘤分类\n\n良性\n\n7\n\n12\n\n0.122 \n\n0.727 \n\n恶性 \n\n6\n\n8\n\n是否有计算机导航\n\n有\n\n4\n\n8\n\n0.290 \n\n0.590 \n\n无\n\n9\n\n12\n\n手术方式\n\n切除\n\n12\n\n18\n\n0.510 \n\n0.822 \n\n其他\n\n1\n\n2\n\n高危因素\n\n有\n\n0\n\n4\n\n2.959 \n\n0.085 \n\n \n\n无\n\n13\n\n16\n\n2.3 多因素分析结果\n\n 我们对单因素分析中具有统计意义的自变量进行了logistic回归分析，结果显示：手术部位（1）、手术体位（1）、手术时长(1)的值差异显著（P＜0.005）。这意味着，术前评估时手术部位为骶尾部、手术体位为俯卧位、手术时长3~4小时是危险因素，患者术后需要大量输血的可能性就越大。具体数据请见表3。\n\n表3 两组患者多因素logistic回归分析结果\n\n \n\nB\n\nS.E.\n\nWald\n\nP\n\nOR\n\n95% C.I.\n\n手术部位(1) *\n\n-3.30\n\n1.49\n\n4.91\n\n0.027 *\n\n0.04\n\n0.00\n\n0.68\n\n手术体位(1) *\n\n3.90\n\n1.71\n\n5.21\n\n0.022 *\n\n49.23\n\n1.74\n\n1395.27\n\n手术时长(1) *\n\n3.39\n\n1.46\n\n5.44\n\n0.020 *\n\n29.73\n\n1.72\n\n514.72\n\n手术时长(3)\n\n-1.14\n\n1.67\n\n0.46\n\n0.496\n\n0.32\n\n0.01\n\n8.50\n\n性别(1)\n\n1.24\n\n1.32\n\n0.88\n\n0.349\n\n3.45\n\n0.26\n\n46.07\n\n年龄(1)\n\n23.38\n\n6878.97\n\n0.00\n\n0.997\n\n14297314107.83\n\n0.00\n\n.\n\nPT\n\n\n\n\n\n0.00\n\n1.000\n\n\n\n\n\n\n\nPT(1)\n\n18.45\n\n29235.68\n\n0.00\n\n0.999\n\n102688179.44\n\n0.00\n\n.\n\nPT(2)\n\n-29.79\n\n37330.28\n\n0.00\n\n0.999\n\n0.00\n\n0.00\n\n.\n\nAPTT(1)\n\n25.95\n\n6878.97\n\n0.00\n\n0.997\n\n186231435743.80\n\n0.00\n\n.\n\nFIB(1)\n\n-1.16\n\n1.22\n\n0.90\n\n0.343\n\n0.31\n\n0.03\n\n3.45\n\nALT(1)\n\n-2.60\n\n1.39\n\n3.52\n\n0.061\n\n0.07\n\n0.01\n\n1.13\n\n常量\n\n-44.00\n\n31570.34\n\n0.00\n\n0.999\n\n0.00\n\n\n\n\n\n\n\n3.讨论\n\n我院计算机导航辅助骨科手术导航技术已经广泛应用于脊柱和骨关节等临床骨科手术，近年来也逐渐应用于骨肿瘤的外科治疗，包括各类骶骨瘤的手术切除 [1] 。根据临床病例分析，对于确诊为骶骨瘤的患者，其适应症明确指向手术干预能够有效切除病灶。相比之下，非手术方式无法达到去除病灶的目的。手术不仅能够精准地去除肿瘤病灶，解除因肿瘤造成的压迫，还能通过彻底切除肿瘤来显著缓解疼痛等症状。因此，综合考虑手术与非手术治疗的效果，手术被确立为治疗骶骨瘤的最佳方案。\n\n手术时间的延长通常会导致术中失血增加和感染等风险，根范围据文献报道骶骨脊索切除术平均用时大多超过5h，失血量多在3000~5000mL[1]。骶骨作为骨盆后壁的重要组成部分，其供血极为丰富，因此在进行该区域的手术时，往往面临出血多且止血困难的挑战，使得手术难度大大增加。对于骶骨瘤的手术而言，主要采用边缘性切除或刮除的方法。然而，要确保手术真正达到安全有效的肿瘤治疗切除边界，不仅需要严谨精细的术前研究计划安排，还离不开医生丰富的手术操作经验。这两者是确保手术成功不可或缺的关键因素。\n\n手术是一个复杂的过程，需要多科室的紧密协作才能完成。自身输血作为减少异体血输入、避免传染病传播及异体抗原反应的最有效手段，一直受到输血界的广泛提倡。然而，由于自身输血具有严格的适应症，它仅是解决血液库存紧张、血液疾病及疑难血型问题的有效手段之一[15]。在骶骨瘤手术中，大多数情况下仍需依赖异体输血，这进一步体现了术前备血的重要性。为了确保骶骨瘤手术的顺利进行，临床医生在确定手术日期后，应提前与输血科沟通，并送检血样进行血型鉴定和不规则抗体筛查。\n\n本研究结果表明，在骶骨瘤手术患者的单因素分析中，纤维蛋白原（FIB）、凝血酶原时间（PT）、活化部分凝血酶原时间（APTT）以及丙氨酸氨基转移酶（ALT）的水平，以及手术时长的差异，均呈现出统计学上的显著性（p＜0.005），显示出一定的影响趋势。然而，这些因素并非骶骨瘤围手术期大量输血的直接术前决定性因素。此外，本研究还发现，血红蛋白（Hb）水平、全血红细胞计数（RBC）、血细胞比容（Hct）、肿瘤的分类、麻醉分级、患者是否存在基础疾病、手术是否采用计算机导航辅助，以及具体的手术方式等，均未被证实为骶骨瘤围手术期大量输血的高危因素。上述结论均基于严谨的数据分析和充分的案例支持，确保了研究的客观性和权威性。\n\n我们对影响骶骨瘤手术大量输血的因素进行了logistic回归分析，结果显示：手术部位为骶尾部时输血风险降低4%（p＜0.005），手术体位为俯卧位时输血风险增加近50倍（p＜0.005），手术时长3~4小时时输血风险增加30倍（p＜0.005）。性别、年龄、全血细胞计数、凝血、肝功能等不是术前大量输血的危险因素。临床医生应关注手术位置和体位，以及手术时间长短。\n\n综上所述，在临床实践中，医生应针对这些高风险因素制定更为详尽的术前准备和术中管理计划，以降低输血风险。基于这些统计学显著性变量，医生可以对患者进行更为精准的术前评估和风险分层，从而制定个性化的输血管理策略。这有助于优化血液资源的使用，同时提高患者的手术安全性和满意度。通过定期回顾和分析输血病例，发现潜在的风险因素并采取相应措施进行干预，以不断提高输血管理的质量和效率。\n\n 参 考 文 献\n\n［１］\t杨勇昆 李远 张清 牛晓辉.计算机导航辅助骶骨脊索瘤的精确切除的手术效果和安全性研究. 中国骨与关节杂志 2021 年 3 月第 10 卷第 3 期 Chinese Journal of Bone and Joint, March 2021, Vol 10, No.3.228-234.\n\n［２］\t战春1，徐林2.手术治疗8例巨大骶骨瘤.中国中西医结合外科杂志2009年4月第15卷第2期。130-131\n\n［３］\t陈元利1 ,傅 洪1 △ ,周润芳1 ,朱厚伟1 ,张 星1 ,孔令文2 ,廖 群，A型主动脉夹层患者围术期大量输血的术前危险因素分析.重庆医学.2023,52（24）；3775-3784.\n\n［４］\t邵方真1 ，闫优萍1 ，朱俊2 ，常圣雅3 ，钟丽慧.血栓弹力图与FIB联合预测普外科患者围术期大量输血的效能评价.河南医学2024年5月第35卷第10期.1436-1439.\n\n［５］\t辛宏杰 .大量输血患者用血情况及检验结果的回顾性分析.临床研究2020年04月第28卷第04期：31-32\n\n［６］\t郭卫，李大森，唐顺，姬涛.骶骨肿瘤的类型和临床特点. 中国脊柱脊髓杂志2010年第20卷第5期.380-381. \n\n［７］\t胡海，杨惠林，王根椿.骶骨肿瘤手术失血量新统计方法初步探索. 实用骨科杂志第17卷，第4期，2011年4月.319-320. \n\n［８］\t王默然,王峻,李星晨,刘浩,葛艳玲.原发性恶性骨肉瘤术中输血影响因素的回顾性研究. 中国输血杂志２０２２年１月第３５卷第１期.35-38.\n\n［９］\t谭刘欣，牛梦林，孙巍．腹膜后肿瘤患者术中输血影响因素及预后分析．中国输血杂志，２０１９，３２（３）：２５７⁃２５９．\n\n［１０］\tKlimo P，Rao G．Schmidt RH．et a1．Nerve sheath tumors involving the sacrum：ease report and classification sehemo[J1.Neurosurg Focus。2003，15(2)：I-6．\n\n［１１］\tarner MA, Shore-Lesserson L, Shander A, et al. Perioperative anemia: prevention, diagnosis,and management throughout the spectrum of perioperative care [J]. Anesth Analg, 2020, 130(5): 1364-1380. \n\n［１２］\tThiele T, Greinacher A. Platelet Transfusion in Perioperative Medicine [J]. Semin Thromb Hemost, 2020, 46(1): 50-61. \n\n［１３］\tLin JY, Liu ZQ, Hu JC, et al. Factors affecting the adverse reactions to blood transfusion during orthopedic surgery and prediction model development [J]. Chin J Mod Med, 2023, 33(4): 71-77. \n\n［１４］\t林娇雅, 刘自强, 胡建超, 等. 骨科手术输血后不良反应的影响因素及预测模型构建与分析[J]. 中国现代医学杂志, 2023, 33(4): 71-77. \n\n［１５］\t刘英，王峻，葛艳玲，疑难交叉配配血成因与交叉配血策略的分析.中国输血杂志，2020，32（2），152-154.\n\n 8964 completed {editorial} {"items": [{"score": 75, "issues": ["未提及研究是否获得伦理委员会批准及受试者知情同意情况。", "稿件为回顾性研究，但未说明数据收集和分析过程是否符合伦理规范。", "论著性文章字数需控制在5000字以内，本文需核实字数。"], "status": "warning", "criterion": "文稿科学性与实用性", "suggestions": ["在“材料与方法”部分开头或文末添加伦理声明，例如：“本研究经XX医院伦理委员会批准（批件号：XXX），所有患者均签署知情同意书。”", "明确说明本研究为回顾性分析，数据使用已获得相关授权或豁免。", "检查全文总字数，确保论著性文章不超过5000字。"]}, {"score": 95, "issues": [], "status": "pass", "criterion": "文题", "suggestions": []}, {"score": 80, "issues": ["作者单位信息未按“邮政编码、所在省市县、单位全称、具体科室”的完整格式列出。", "英文摘要中作者单位格式不完整，缺少城市和邮政编码。"], "status": "warning", "criterion": "作者格式", "suggestions": ["在文题页左下方补充完整的作者单位信息，格式应为：“100035 北京市，首都医科大学附属北京积水潭医院输血科”。", "在英文摘要中补充作者单位的城市和邮政编码，格式应为：“Department of Blood Transfusion, Beijing Jishuitan Hospital, Capital Medical University, Beijing 100035, China”。"]}, {"score": 65, "issues": ["中文摘要未按“目的、方法、结果、结论”四部分结构撰写，未冠以相应标题。", "结果部分未列出主要的具体数据（如OR值、具体P值等），仅有定性描述。", "英文摘要中作者姓名拼音格式不规范（如“WangChao”应分开为“Wang Chao”）。", "英文摘要中作者单位信息不完整。"], "status": "fail", "criterion": "摘要", "suggestions": ["重写中文摘要，明确分为【目的】、【方法】、【结果】、【结论】四个部分，并冠以标题。", "在【结果】部分补充关键数据，例如：“多因素分析显示，手术部位（OR=0.04, P=0.027）、手术体位（OR=49.23, P=0.022）、手术时长（OR=29.73, P=0.020）是独立危险因素。”", "修正英文作者姓名拼音，确保姓和名分开，且首字母大写，如：“Wang Chao”。", "补充英文摘要的作者单位完整信息（城市、邮编、国名）。"]}, {"score": 60, "issues": ["中文关键词之间使用了错误的标点“：”，应为分号“；”。", "关键词“大量输血：输血影响因素”疑似为一个关键词，不符合规范。", "英文关键词首字母未全部大写。", "关键词数量可能不足（中文显示为3组，但格式错误）。", "未说明是否参考了MeSH主题词表。"], "status": "fail", "criterion": "关键词", "suggestions": ["将中文关键词分隔符统一改为分号“；”，例如：“骶骨肿瘤手术；围术期血液管理；大量输血；危险因素”。", "确保中、英文关键词均为2-5个独立的词或短语。", "英文关键词每个单词首字母大写，如：“Sacral Tumor Surgery; Perioperative Blood Management; Massive Blood Transfusion; Risk Factors”。", "在投稿时说明关键词选取依据，尽量使用MeSH主题词。"]}, {"score": 90, "issues": [], "status": "pass", "criterion": "医学名词和药物名称", "suggestions": []}, {"score": 85, "issues": ["文中使用了较多缩略语（如FIB、PT、APTT、ALT、MBT等），虽在首次出现时给出了全称，但建议尽量减少使用。"], "status": "pass", "criterion": "缩略语", "suggestions": ["在非表格、图表等必要场合，可考虑使用中文全称，以增强文章可读性。"]}, {"score": 80, "issues": ["纤维蛋白原（FIB）单位使用了“mg/dL”和“g/L”，在文中不统一。表1中单位为g/L，但正文1.2方法中描述为mg/dL。", "部分量的符号未使用斜体（虽在纯文本中难以体现，但需在排版时注意）。"], "status": "warning", "criterion": "计量单位", "suggestions": ["统一纤维蛋白原的单位，建议使用“g/L”作为标准单位。修改正文1.2方法中的描述。", "在稿件排版时，确保所有量的符号（如t值、P值中的P）使用斜体。"]}, {"score": 70, "issues": ["稿件中提及表1、表2、表3，但未提供独立的图表文件，且文中表格格式为文字描述，非规范表格。", "表1和表2的“注”中包含了大量缩略语解释，这些解释应移至表题下方或正文中首次出现处。", "表1中使用了“*”标注P值，但未在表注中说明“*”的含义。", "未提及是否有病理图片或大体标本图片，若有，需按规范标注。"], "status": "warning", "criterion": "图片格式", "suggestions": ["将文中的表格（表1、2、3）重新制作为规范的三线表，并单独附页。", "将表格内的缩略语解释移至表题下方，作为表注。例如，在表题下添加：“注：RBC：红细胞计数；Hct：血细胞比容；Hb：血红蛋白；PT：凝血酶原时间；APTT：活化部分凝血活酶时间；FIB：纤维蛋白原；ALT：丙氨酸氨基转移酶。”", "在表注中明确统计符号的含义，如：“* P < 0.05”。", "若研究中包含影像学或病理图片，需按规范提供，并注明染色方法、放大倍数等。"]}, {"score": 100, "issues": [], "status": "pass", "criterion": "动态图像", "suggestions": []}, {"score": 50, "issues": ["参考文献著录格式严重不符合GB/T 7714-2015标准。", "中文文献未标注文献类型标识（如[J]）。", "作者著录不规范，未遵循“3名以上只列前3名，后加‘,等’”的规则（如参考文献[1]列出了全部5名作者）。", "期刊名称著录不规范，中文期刊应写全名，但部分条目卷期页码格式混乱（如参考文献[1]、[2]）。", "外文文献（如参考文献[10]）期刊名称未使用标准缩写，且页码著录不规范（“I-6”应为“E1-E6”或具体页码）。", "参考文献[14]与[13]为同一文献的中英文版本，著录方式不规范。", "正文引用标注为上标方括号格式，但部分地方格式不统一。"], "status": "fail", "criterion": "参考文献", "suggestions": ["彻底重写参考文献列表，严格按照GB/T 7714-2015顺序编码制著录。", "为每条参考文献添加文献类型标识，如期刊文章[J]，专著[M]。", "作者超过3人时，只列前3位，后加“，等”。例如，参考文献[1]应改为：“杨勇昆，李远，张清，等.计算机导航辅助骶骨脊索瘤的精确切除的手术效果和安全性研究[J].中国骨与关节杂志，2021, 10(3): 228-234.”", "统一中文期刊的著录格式：刊名全称，年，卷(期): 起页-止页。", "核查外文文献，使用《Index Medicus》标准缩写刊名，并规范页码著录。", "同一文献不重复著录中英文版本，选择一种即可，或在一条文献中注明双语信息（但非标准做法，建议只保留中文版）。", "检查正文，确保所有参考文献引用标号均为上标方括号格式，如[1]。"]}], "summary": "该稿件为回顾性研究，选题具有临床意义，但规范性存在较多问题，需进行较大修改。主要问题包括：1) 摘要格式不规范，缺少结构标题和具体数据；2) 关键词格式错误且数量不足；3) 未提及伦理审批和知情同意；4) 参考文献格式严重不规范；5) 图表格式和标注不完整。建议作者严格按照稿约要求逐项修改。", "overall_score": 72} null 72 72 \N \N \N f \N deepseek-v3 2026-01-11 03:57:00.386 2026-01-11 03:58:10.951 69 \N 2026-01-11 03:56:54.38 2026-01-11 03:58:10.956
|
||
\.
|
||
|
||
|
||
--
|
||
-- Name: admin_operation_logs_id_seq; Type: SEQUENCE SET; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('admin_schema.admin_operation_logs_id_seq', 1, false);
|
||
|
||
|
||
--
|
||
-- Name: prompt_templates_id_seq; Type: SEQUENCE SET; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('capability_schema.prompt_templates_id_seq', 2, true);
|
||
|
||
|
||
--
|
||
-- Name: prompt_versions_id_seq; Type: SEQUENCE SET; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('capability_schema.prompt_versions_id_seq', 1, true);
|
||
|
||
|
||
--
|
||
-- Name: app_cache_id_seq; Type: SEQUENCE SET; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('platform_schema.app_cache_id_seq', 1, true);
|
||
|
||
|
||
--
|
||
-- Name: permissions_id_seq; Type: SEQUENCE SET; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('platform_schema.permissions_id_seq', 15, true);
|
||
|
||
|
||
--
|
||
-- Name: role_permissions_id_seq; Type: SEQUENCE SET; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('platform_schema.role_permissions_id_seq', 25, true);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations_id_seq; Type: SEQUENCE SET; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('platform_schema.tenant_quota_allocations_id_seq', 1, false);
|
||
|
||
|
||
--
|
||
-- Name: verification_codes_id_seq; Type: SEQUENCE SET; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('platform_schema.verification_codes_id_seq', 1, false);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs_id_seq; Type: SEQUENCE SET; Schema: public; Owner: postgres
|
||
--
|
||
|
||
SELECT pg_catalog.setval('public.admin_logs_id_seq', 1, false);
|
||
|
||
|
||
--
|
||
-- Name: admin_operation_logs admin_operation_logs_pkey; Type: CONSTRAINT; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY admin_schema.admin_operation_logs
|
||
ADD CONSTRAINT admin_operation_logs_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: conversations conversations_pkey; Type: CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.conversations
|
||
ADD CONSTRAINT conversations_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: general_conversations general_conversations_pkey; Type: CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.general_conversations
|
||
ADD CONSTRAINT general_conversations_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: general_messages general_messages_pkey; Type: CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.general_messages
|
||
ADD CONSTRAINT general_messages_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: messages messages_pkey; Type: CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.messages
|
||
ADD CONSTRAINT messages_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: projects projects_pkey; Type: CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.projects
|
||
ADD CONSTRAINT projects_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_results fulltext_screening_results_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_results
|
||
ADD CONSTRAINT fulltext_screening_results_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_tasks fulltext_screening_tasks_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_tasks
|
||
ADD CONSTRAINT fulltext_screening_tasks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: literatures literatures_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.literatures
|
||
ADD CONSTRAINT literatures_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: screening_projects screening_projects_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_projects
|
||
ADD CONSTRAINT screening_projects_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: screening_results screening_results_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_results
|
||
ADD CONSTRAINT screening_results_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: screening_tasks screening_tasks_pkey; Type: CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_tasks
|
||
ADD CONSTRAINT screening_tasks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: prompt_templates prompt_templates_pkey; Type: CONSTRAINT; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY capability_schema.prompt_templates
|
||
ADD CONSTRAINT prompt_templates_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: prompt_versions prompt_versions_pkey; Type: CONSTRAINT; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY capability_schema.prompt_versions
|
||
ADD CONSTRAINT prompt_versions_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_items dc_extraction_items_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_extraction_items
|
||
ADD CONSTRAINT dc_extraction_items_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_tasks dc_extraction_tasks_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_extraction_tasks
|
||
ADD CONSTRAINT dc_extraction_tasks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_health_checks dc_health_checks_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_health_checks
|
||
ADD CONSTRAINT dc_health_checks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_templates dc_templates_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_templates
|
||
ADD CONSTRAINT dc_templates_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_tool_c_ai_history dc_tool_c_ai_history_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_tool_c_ai_history
|
||
ADD CONSTRAINT dc_tool_c_ai_history_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: dc_tool_c_sessions dc_tool_c_sessions_pkey; Type: CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_tool_c_sessions
|
||
ADD CONSTRAINT dc_tool_c_sessions_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: audit_logs audit_logs_pkey; Type: CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.audit_logs
|
||
ADD CONSTRAINT audit_logs_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: pending_actions pending_actions_pkey; Type: CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.pending_actions
|
||
ADD CONSTRAINT pending_actions_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: projects projects_pkey; Type: CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.projects
|
||
ADD CONSTRAINT projects_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: task_runs task_runs_pkey; Type: CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.task_runs
|
||
ADD CONSTRAINT task_runs_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings user_mappings_pkey; Type: CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.user_mappings
|
||
ADD CONSTRAINT user_mappings_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: batch_results batch_results_pkey; Type: CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.batch_results
|
||
ADD CONSTRAINT batch_results_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: batch_tasks batch_tasks_pkey; Type: CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.batch_tasks
|
||
ADD CONSTRAINT batch_tasks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: documents documents_pkey; Type: CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.documents
|
||
ADD CONSTRAINT documents_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: knowledge_bases knowledge_bases_pkey; Type: CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.knowledge_bases
|
||
ADD CONSTRAINT knowledge_bases_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: task_templates task_templates_pkey; Type: CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.task_templates
|
||
ADD CONSTRAINT task_templates_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: app_cache app_cache_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.app_cache
|
||
ADD CONSTRAINT app_cache_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: departments departments_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.departments
|
||
ADD CONSTRAINT departments_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: job job_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.job
|
||
ADD CONSTRAINT job_pkey PRIMARY KEY (name, id);
|
||
|
||
|
||
--
|
||
-- Name: permissions permissions_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.permissions
|
||
ADD CONSTRAINT permissions_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: queue queue_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.queue
|
||
ADD CONSTRAINT queue_pkey PRIMARY KEY (name);
|
||
|
||
|
||
--
|
||
-- Name: role_permissions role_permissions_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.role_permissions
|
||
ADD CONSTRAINT role_permissions_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: schedule schedule_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.schedule
|
||
ADD CONSTRAINT schedule_pkey PRIMARY KEY (name, key);
|
||
|
||
|
||
--
|
||
-- Name: subscription subscription_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.subscription
|
||
ADD CONSTRAINT subscription_pkey PRIMARY KEY (event, name);
|
||
|
||
|
||
--
|
||
-- Name: tenant_members tenant_members_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_members
|
||
ADD CONSTRAINT tenant_members_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: tenant_modules tenant_modules_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_modules
|
||
ADD CONSTRAINT tenant_modules_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations tenant_quota_allocations_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_quota_allocations
|
||
ADD CONSTRAINT tenant_quota_allocations_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quotas tenant_quotas_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_quotas
|
||
ADD CONSTRAINT tenant_quotas_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: tenants tenants_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenants
|
||
ADD CONSTRAINT tenants_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: users users_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.users
|
||
ADD CONSTRAINT users_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: verification_codes verification_codes_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.verification_codes
|
||
ADD CONSTRAINT verification_codes_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: version version_pkey; Type: CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.version
|
||
ADD CONSTRAINT version_pkey PRIMARY KEY (version);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs admin_logs_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY public.admin_logs
|
||
ADD CONSTRAINT admin_logs_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: users users_pkey; Type: CONSTRAINT; Schema: public; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY public.users
|
||
ADD CONSTRAINT users_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: review_tasks review_tasks_pkey; Type: CONSTRAINT; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY rvw_schema.review_tasks
|
||
ADD CONSTRAINT review_tasks_pkey PRIMARY KEY (id);
|
||
|
||
|
||
--
|
||
-- Name: idx_admin_logs_admin_id; Type: INDEX; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_admin_logs_admin_id ON admin_schema.admin_operation_logs USING btree (admin_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_admin_logs_created_at; Type: INDEX; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_admin_logs_created_at ON admin_schema.admin_operation_logs USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_admin_logs_module; Type: INDEX; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_admin_logs_module ON admin_schema.admin_operation_logs USING btree (module);
|
||
|
||
|
||
--
|
||
-- Name: idx_admin_logs_operation_type; Type: INDEX; Schema: admin_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_admin_logs_operation_type ON admin_schema.admin_operation_logs USING btree (operation_type);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_conversations_agent_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_conversations_agent_id ON aia_schema.conversations USING btree (agent_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_conversations_created_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_conversations_created_at ON aia_schema.conversations USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_conversations_deleted_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_conversations_deleted_at ON aia_schema.conversations USING btree (deleted_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_conversations_project_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_conversations_project_id ON aia_schema.conversations USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_conversations_user_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_conversations_user_id ON aia_schema.conversations USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_general_conversations_created_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_general_conversations_created_at ON aia_schema.general_conversations USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_general_conversations_updated_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_general_conversations_updated_at ON aia_schema.general_conversations USING btree (updated_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_general_conversations_user_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_general_conversations_user_id ON aia_schema.general_conversations USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_general_messages_conversation_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_general_messages_conversation_id ON aia_schema.general_messages USING btree (conversation_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_general_messages_created_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_general_messages_created_at ON aia_schema.general_messages USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_messages_conversation_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_messages_conversation_id ON aia_schema.messages USING btree (conversation_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_messages_created_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_messages_created_at ON aia_schema.messages USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_messages_is_pinned; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_messages_is_pinned ON aia_schema.messages USING btree (is_pinned);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_projects_created_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_projects_created_at ON aia_schema.projects USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_projects_deleted_at; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_projects_deleted_at ON aia_schema.projects USING btree (deleted_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_aia_projects_user_id; Type: INDEX; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_aia_projects_user_id ON aia_schema.projects USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_final_decision; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_final_decision ON asl_schema.fulltext_screening_results USING btree (final_decision);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_is_conflict; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_is_conflict ON asl_schema.fulltext_screening_results USING btree (is_conflict);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_literature_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_literature_id ON asl_schema.fulltext_screening_results USING btree (literature_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_project_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_project_id ON asl_schema.fulltext_screening_results USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_review_priority; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_review_priority ON asl_schema.fulltext_screening_results USING btree (review_priority);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_results_task_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_results_task_id ON asl_schema.fulltext_screening_results USING btree (task_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_tasks_created_at; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_tasks_created_at ON asl_schema.fulltext_screening_tasks USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_tasks_project_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_tasks_project_id ON asl_schema.fulltext_screening_tasks USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_fulltext_tasks_status; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_fulltext_tasks_status ON asl_schema.fulltext_screening_tasks USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_literatures_doi; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_literatures_doi ON asl_schema.literatures USING btree (doi);
|
||
|
||
|
||
--
|
||
-- Name: idx_literatures_has_pdf; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_literatures_has_pdf ON asl_schema.literatures USING btree (has_pdf);
|
||
|
||
|
||
--
|
||
-- Name: idx_literatures_pdf_status; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_literatures_pdf_status ON asl_schema.literatures USING btree (pdf_status);
|
||
|
||
|
||
--
|
||
-- Name: idx_literatures_project_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_literatures_project_id ON asl_schema.literatures USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_literatures_stage; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_literatures_stage ON asl_schema.literatures USING btree (stage);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_projects_status; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_projects_status ON asl_schema.screening_projects USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_projects_user_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_projects_user_id ON asl_schema.screening_projects USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_results_conflict_status; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_results_conflict_status ON asl_schema.screening_results USING btree (conflict_status);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_results_final_decision; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_results_final_decision ON asl_schema.screening_results USING btree (final_decision);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_results_literature_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_results_literature_id ON asl_schema.screening_results USING btree (literature_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_results_project_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_results_project_id ON asl_schema.screening_results USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_tasks_project_id; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_tasks_project_id ON asl_schema.screening_tasks USING btree (project_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_screening_tasks_status; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_screening_tasks_status ON asl_schema.screening_tasks USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: unique_project_literature; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX unique_project_literature ON asl_schema.screening_results USING btree (project_id, literature_id);
|
||
|
||
|
||
--
|
||
-- Name: unique_project_literature_fulltext; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX unique_project_literature_fulltext ON asl_schema.fulltext_screening_results USING btree (project_id, literature_id);
|
||
|
||
|
||
--
|
||
-- Name: unique_project_pmid; Type: INDEX; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX unique_project_pmid ON asl_schema.literatures USING btree (project_id, pmid);
|
||
|
||
|
||
--
|
||
-- Name: idx_prompt_templates_module; Type: INDEX; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_prompt_templates_module ON capability_schema.prompt_templates USING btree (module);
|
||
|
||
|
||
--
|
||
-- Name: idx_prompt_versions_template_status; Type: INDEX; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_prompt_versions_template_status ON capability_schema.prompt_versions USING btree (template_id, status);
|
||
|
||
|
||
--
|
||
-- Name: prompt_templates_code_key; Type: INDEX; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX prompt_templates_code_key ON capability_schema.prompt_templates USING btree (code);
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_items_task_id_status_idx; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX dc_extraction_items_task_id_status_idx ON dc_schema.dc_extraction_items USING btree (task_id, status);
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_tasks_user_id_status_idx; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX dc_extraction_tasks_user_id_status_idx ON dc_schema.dc_extraction_tasks USING btree (user_id, status);
|
||
|
||
|
||
--
|
||
-- Name: dc_health_checks_user_id_file_name_idx; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX dc_health_checks_user_id_file_name_idx ON dc_schema.dc_health_checks USING btree (user_id, file_name);
|
||
|
||
|
||
--
|
||
-- Name: dc_templates_disease_type_report_type_key; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX dc_templates_disease_type_report_type_key ON dc_schema.dc_templates USING btree (disease_type, report_type);
|
||
|
||
|
||
--
|
||
-- Name: idx_dc_tool_c_ai_history_created_at; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_dc_tool_c_ai_history_created_at ON dc_schema.dc_tool_c_ai_history USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_dc_tool_c_ai_history_session_id; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_dc_tool_c_ai_history_session_id ON dc_schema.dc_tool_c_ai_history USING btree (session_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_dc_tool_c_ai_history_user_id; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_dc_tool_c_ai_history_user_id ON dc_schema.dc_tool_c_ai_history USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_dc_tool_c_sessions_expires_at; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_dc_tool_c_sessions_expires_at ON dc_schema.dc_tool_c_sessions USING btree (expires_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_dc_tool_c_sessions_user_id; Type: INDEX; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_dc_tool_c_sessions_user_id ON dc_schema.dc_tool_c_sessions USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: audit_logs_action_type_created_at_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX audit_logs_action_type_created_at_idx ON iit_schema.audit_logs USING btree (action_type, created_at);
|
||
|
||
|
||
--
|
||
-- Name: audit_logs_project_id_created_at_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX audit_logs_project_id_created_at_idx ON iit_schema.audit_logs USING btree (project_id, created_at);
|
||
|
||
|
||
--
|
||
-- Name: audit_logs_trace_id_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX audit_logs_trace_id_idx ON iit_schema.audit_logs USING btree (trace_id);
|
||
|
||
|
||
--
|
||
-- Name: audit_logs_user_id_created_at_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX audit_logs_user_id_created_at_idx ON iit_schema.audit_logs USING btree (user_id, created_at);
|
||
|
||
|
||
--
|
||
-- Name: pending_actions_project_id_record_id_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX pending_actions_project_id_record_id_idx ON iit_schema.pending_actions USING btree (project_id, record_id);
|
||
|
||
|
||
--
|
||
-- Name: pending_actions_project_id_status_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX pending_actions_project_id_status_idx ON iit_schema.pending_actions USING btree (project_id, status);
|
||
|
||
|
||
--
|
||
-- Name: pending_actions_status_created_at_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX pending_actions_status_created_at_idx ON iit_schema.pending_actions USING btree (status, created_at);
|
||
|
||
|
||
--
|
||
-- Name: projects_dify_dataset_id_key; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX projects_dify_dataset_id_key ON iit_schema.projects USING btree (dify_dataset_id);
|
||
|
||
|
||
--
|
||
-- Name: projects_status_deleted_at_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX projects_status_deleted_at_idx ON iit_schema.projects USING btree (status, deleted_at);
|
||
|
||
|
||
--
|
||
-- Name: task_runs_job_id_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX task_runs_job_id_idx ON iit_schema.task_runs USING btree (job_id);
|
||
|
||
|
||
--
|
||
-- Name: task_runs_job_id_key; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX task_runs_job_id_key ON iit_schema.task_runs USING btree (job_id);
|
||
|
||
|
||
--
|
||
-- Name: task_runs_project_id_task_type_status_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX task_runs_project_id_task_type_status_idx ON iit_schema.task_runs USING btree (project_id, task_type, status);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings_mini_program_open_id_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX user_mappings_mini_program_open_id_idx ON iit_schema.user_mappings USING btree (mini_program_open_id);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings_mini_program_open_id_key; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX user_mappings_mini_program_open_id_key ON iit_schema.user_mappings USING btree (mini_program_open_id);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings_project_id_redcap_username_key; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX user_mappings_project_id_redcap_username_key ON iit_schema.user_mappings USING btree (project_id, redcap_username);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings_project_id_system_user_id_key; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX user_mappings_project_id_system_user_id_key ON iit_schema.user_mappings USING btree (project_id, system_user_id);
|
||
|
||
|
||
--
|
||
-- Name: user_mappings_wecom_user_id_idx; Type: INDEX; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX user_mappings_wecom_user_id_idx ON iit_schema.user_mappings USING btree (wecom_user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_results_document_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_results_document_id ON pkb_schema.batch_results USING btree (document_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_results_status; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_results_status ON pkb_schema.batch_results USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_results_task_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_results_task_id ON pkb_schema.batch_results USING btree (task_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_tasks_created_at; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_tasks_created_at ON pkb_schema.batch_tasks USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_tasks_kb_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_tasks_kb_id ON pkb_schema.batch_tasks USING btree (kb_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_tasks_status; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_tasks_status ON pkb_schema.batch_tasks USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_batch_tasks_user_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_batch_tasks_user_id ON pkb_schema.batch_tasks USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_documents_dify_document_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_documents_dify_document_id ON pkb_schema.documents USING btree (dify_document_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_documents_extraction_method; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_documents_extraction_method ON pkb_schema.documents USING btree (extraction_method);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_documents_kb_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_documents_kb_id ON pkb_schema.documents USING btree (kb_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_documents_status; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_documents_status ON pkb_schema.documents USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_documents_user_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_documents_user_id ON pkb_schema.documents USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_knowledge_bases_dify_dataset_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_knowledge_bases_dify_dataset_id ON pkb_schema.knowledge_bases USING btree (dify_dataset_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_knowledge_bases_user_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_knowledge_bases_user_id ON pkb_schema.knowledge_bases USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_pkb_task_templates_user_id; Type: INDEX; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_pkb_task_templates_user_id ON pkb_schema.task_templates USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: app_cache_key_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX app_cache_key_key ON platform_schema.app_cache USING btree (key);
|
||
|
||
|
||
--
|
||
-- Name: idx_app_cache_expires; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_app_cache_expires ON platform_schema.app_cache USING btree (expires_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_app_cache_key_expires; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_app_cache_key_expires ON platform_schema.app_cache USING btree (key, expires_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_departments_parent_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_departments_parent_id ON platform_schema.departments USING btree (parent_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_departments_tenant_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_departments_tenant_id ON platform_schema.departments USING btree (tenant_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_platform_users_created_at; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_platform_users_created_at ON platform_schema.users USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_platform_users_email; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_platform_users_email ON platform_schema.users USING btree (email);
|
||
|
||
|
||
--
|
||
-- Name: idx_platform_users_phone; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_platform_users_phone ON platform_schema.users USING btree (phone);
|
||
|
||
|
||
--
|
||
-- Name: idx_platform_users_status; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_platform_users_status ON platform_schema.users USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_platform_users_tenant_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_platform_users_tenant_id ON platform_schema.users USING btree (tenant_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_quota_allocations_tenant_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_quota_allocations_tenant_id ON platform_schema.tenant_quota_allocations USING btree (tenant_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_tenant_members_tenant_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_tenant_members_tenant_id ON platform_schema.tenant_members USING btree (tenant_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_tenant_members_user_id; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_tenant_members_user_id ON platform_schema.tenant_members USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: idx_tenants_code; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_tenants_code ON platform_schema.tenants USING btree (code);
|
||
|
||
|
||
--
|
||
-- Name: idx_tenants_status; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_tenants_status ON platform_schema.tenants USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: idx_tenants_type; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_tenants_type ON platform_schema.tenants USING btree (type);
|
||
|
||
|
||
--
|
||
-- Name: idx_verification_codes_expires; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_verification_codes_expires ON platform_schema.verification_codes USING btree (expires_at);
|
||
|
||
|
||
--
|
||
-- Name: idx_verification_codes_phone_type; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX idx_verification_codes_phone_type ON platform_schema.verification_codes USING btree (phone, type, is_used);
|
||
|
||
|
||
--
|
||
-- Name: permissions_code_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX permissions_code_key ON platform_schema.permissions USING btree (code);
|
||
|
||
|
||
--
|
||
-- Name: role_permissions_role_permission_id_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX role_permissions_role_permission_id_key ON platform_schema.role_permissions USING btree (role, permission_id);
|
||
|
||
|
||
--
|
||
-- Name: tenant_members_tenant_id_user_id_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX tenant_members_tenant_id_user_id_key ON platform_schema.tenant_members USING btree (tenant_id, user_id);
|
||
|
||
|
||
--
|
||
-- Name: tenant_modules_tenant_id_module_code_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX tenant_modules_tenant_id_module_code_key ON platform_schema.tenant_modules USING btree (tenant_id, module_code);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations_tenant_id_target_type_target_key_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX tenant_quota_allocations_tenant_id_target_type_target_key_key ON platform_schema.tenant_quota_allocations USING btree (tenant_id, target_type, target_key);
|
||
|
||
|
||
--
|
||
-- Name: tenant_quotas_tenant_id_quota_type_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX tenant_quotas_tenant_id_quota_type_key ON platform_schema.tenant_quotas USING btree (tenant_id, quota_type);
|
||
|
||
|
||
--
|
||
-- Name: tenants_code_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX tenants_code_key ON platform_schema.tenants USING btree (code);
|
||
|
||
|
||
--
|
||
-- Name: users_email_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX users_email_key ON platform_schema.users USING btree (email);
|
||
|
||
|
||
--
|
||
-- Name: users_phone_key; Type: INDEX; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX users_phone_key ON platform_schema.users USING btree (phone);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs_action_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX admin_logs_action_idx ON public.admin_logs USING btree (action);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs_admin_id_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX admin_logs_admin_id_idx ON public.admin_logs USING btree (admin_id);
|
||
|
||
|
||
--
|
||
-- Name: admin_logs_created_at_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX admin_logs_created_at_idx ON public.admin_logs USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: users_created_at_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX users_created_at_idx ON public.users USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: users_email_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX users_email_idx ON public.users USING btree (email);
|
||
|
||
|
||
--
|
||
-- Name: users_email_key; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE UNIQUE INDEX users_email_key ON public.users USING btree (email);
|
||
|
||
|
||
--
|
||
-- Name: users_status_idx; Type: INDEX; Schema: public; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX users_status_idx ON public.users USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: review_tasks_created_at_idx; Type: INDEX; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX review_tasks_created_at_idx ON rvw_schema.review_tasks USING btree (created_at);
|
||
|
||
|
||
--
|
||
-- Name: review_tasks_is_archived_idx; Type: INDEX; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX review_tasks_is_archived_idx ON rvw_schema.review_tasks USING btree (is_archived);
|
||
|
||
|
||
--
|
||
-- Name: review_tasks_status_idx; Type: INDEX; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX review_tasks_status_idx ON rvw_schema.review_tasks USING btree (status);
|
||
|
||
|
||
--
|
||
-- Name: review_tasks_user_id_idx; Type: INDEX; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
CREATE INDEX review_tasks_user_id_idx ON rvw_schema.review_tasks USING btree (user_id);
|
||
|
||
|
||
--
|
||
-- Name: conversations conversations_project_id_fkey; Type: FK CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.conversations
|
||
ADD CONSTRAINT conversations_project_id_fkey FOREIGN KEY (project_id) REFERENCES aia_schema.projects(id) ON UPDATE CASCADE ON DELETE SET NULL;
|
||
|
||
|
||
--
|
||
-- Name: messages messages_conversation_id_fkey; Type: FK CONSTRAINT; Schema: aia_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY aia_schema.messages
|
||
ADD CONSTRAINT messages_conversation_id_fkey FOREIGN KEY (conversation_id) REFERENCES aia_schema.conversations(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_results fulltext_screening_results_literature_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_results
|
||
ADD CONSTRAINT fulltext_screening_results_literature_id_fkey FOREIGN KEY (literature_id) REFERENCES asl_schema.literatures(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_results fulltext_screening_results_project_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_results
|
||
ADD CONSTRAINT fulltext_screening_results_project_id_fkey FOREIGN KEY (project_id) REFERENCES asl_schema.screening_projects(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_results fulltext_screening_results_task_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_results
|
||
ADD CONSTRAINT fulltext_screening_results_task_id_fkey FOREIGN KEY (task_id) REFERENCES asl_schema.fulltext_screening_tasks(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: fulltext_screening_tasks fulltext_screening_tasks_project_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.fulltext_screening_tasks
|
||
ADD CONSTRAINT fulltext_screening_tasks_project_id_fkey FOREIGN KEY (project_id) REFERENCES asl_schema.screening_projects(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: literatures literatures_project_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.literatures
|
||
ADD CONSTRAINT literatures_project_id_fkey FOREIGN KEY (project_id) REFERENCES asl_schema.screening_projects(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: screening_results screening_results_literature_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_results
|
||
ADD CONSTRAINT screening_results_literature_id_fkey FOREIGN KEY (literature_id) REFERENCES asl_schema.literatures(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: screening_results screening_results_project_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_results
|
||
ADD CONSTRAINT screening_results_project_id_fkey FOREIGN KEY (project_id) REFERENCES asl_schema.screening_projects(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: screening_tasks screening_tasks_project_id_fkey; Type: FK CONSTRAINT; Schema: asl_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY asl_schema.screening_tasks
|
||
ADD CONSTRAINT screening_tasks_project_id_fkey FOREIGN KEY (project_id) REFERENCES asl_schema.screening_projects(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: prompt_versions prompt_versions_template_id_fkey; Type: FK CONSTRAINT; Schema: capability_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY capability_schema.prompt_versions
|
||
ADD CONSTRAINT prompt_versions_template_id_fkey FOREIGN KEY (template_id) REFERENCES capability_schema.prompt_templates(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: dc_extraction_items dc_extraction_items_task_id_fkey; Type: FK CONSTRAINT; Schema: dc_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY dc_schema.dc_extraction_items
|
||
ADD CONSTRAINT dc_extraction_items_task_id_fkey FOREIGN KEY (task_id) REFERENCES dc_schema.dc_extraction_tasks(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: audit_logs audit_logs_project_id_fkey; Type: FK CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.audit_logs
|
||
ADD CONSTRAINT audit_logs_project_id_fkey FOREIGN KEY (project_id) REFERENCES iit_schema.projects(id) ON UPDATE CASCADE ON DELETE RESTRICT;
|
||
|
||
|
||
--
|
||
-- Name: pending_actions pending_actions_project_id_fkey; Type: FK CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.pending_actions
|
||
ADD CONSTRAINT pending_actions_project_id_fkey FOREIGN KEY (project_id) REFERENCES iit_schema.projects(id) ON UPDATE CASCADE ON DELETE RESTRICT;
|
||
|
||
|
||
--
|
||
-- Name: task_runs task_runs_project_id_fkey; Type: FK CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.task_runs
|
||
ADD CONSTRAINT task_runs_project_id_fkey FOREIGN KEY (project_id) REFERENCES iit_schema.projects(id) ON UPDATE CASCADE ON DELETE RESTRICT;
|
||
|
||
|
||
--
|
||
-- Name: user_mappings user_mappings_project_id_fkey; Type: FK CONSTRAINT; Schema: iit_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY iit_schema.user_mappings
|
||
ADD CONSTRAINT user_mappings_project_id_fkey FOREIGN KEY (project_id) REFERENCES iit_schema.projects(id) ON UPDATE CASCADE ON DELETE RESTRICT;
|
||
|
||
|
||
--
|
||
-- Name: batch_results batch_results_document_id_fkey; Type: FK CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.batch_results
|
||
ADD CONSTRAINT batch_results_document_id_fkey FOREIGN KEY (document_id) REFERENCES pkb_schema.documents(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: batch_results batch_results_task_id_fkey; Type: FK CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.batch_results
|
||
ADD CONSTRAINT batch_results_task_id_fkey FOREIGN KEY (task_id) REFERENCES pkb_schema.batch_tasks(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: batch_tasks batch_tasks_kb_id_fkey; Type: FK CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.batch_tasks
|
||
ADD CONSTRAINT batch_tasks_kb_id_fkey FOREIGN KEY (kb_id) REFERENCES pkb_schema.knowledge_bases(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: documents documents_kb_id_fkey; Type: FK CONSTRAINT; Schema: pkb_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY pkb_schema.documents
|
||
ADD CONSTRAINT documents_kb_id_fkey FOREIGN KEY (kb_id) REFERENCES pkb_schema.knowledge_bases(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: departments departments_parent_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.departments
|
||
ADD CONSTRAINT departments_parent_id_fkey FOREIGN KEY (parent_id) REFERENCES platform_schema.departments(id) ON UPDATE CASCADE ON DELETE SET NULL;
|
||
|
||
|
||
--
|
||
-- Name: departments departments_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.departments
|
||
ADD CONSTRAINT departments_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: queue queue_dead_letter_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.queue
|
||
ADD CONSTRAINT queue_dead_letter_fkey FOREIGN KEY (dead_letter) REFERENCES platform_schema.queue(name);
|
||
|
||
|
||
--
|
||
-- Name: role_permissions role_permissions_permission_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.role_permissions
|
||
ADD CONSTRAINT role_permissions_permission_id_fkey FOREIGN KEY (permission_id) REFERENCES platform_schema.permissions(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: schedule schedule_name_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.schedule
|
||
ADD CONSTRAINT schedule_name_fkey FOREIGN KEY (name) REFERENCES platform_schema.queue(name) ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: subscription subscription_name_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.subscription
|
||
ADD CONSTRAINT subscription_name_fkey FOREIGN KEY (name) REFERENCES platform_schema.queue(name) ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: tenant_members tenant_members_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_members
|
||
ADD CONSTRAINT tenant_members_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: tenant_members tenant_members_user_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_members
|
||
ADD CONSTRAINT tenant_members_user_id_fkey FOREIGN KEY (user_id) REFERENCES platform_schema.users(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: tenant_modules tenant_modules_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_modules
|
||
ADD CONSTRAINT tenant_modules_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: tenant_quota_allocations tenant_quota_allocations_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_quota_allocations
|
||
ADD CONSTRAINT tenant_quota_allocations_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: tenant_quotas tenant_quotas_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.tenant_quotas
|
||
ADD CONSTRAINT tenant_quotas_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: users users_department_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.users
|
||
ADD CONSTRAINT users_department_id_fkey FOREIGN KEY (department_id) REFERENCES platform_schema.departments(id) ON UPDATE CASCADE ON DELETE SET NULL;
|
||
|
||
|
||
--
|
||
-- Name: users users_tenant_id_fkey; Type: FK CONSTRAINT; Schema: platform_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY platform_schema.users
|
||
ADD CONSTRAINT users_tenant_id_fkey FOREIGN KEY (tenant_id) REFERENCES platform_schema.tenants(id) ON UPDATE CASCADE ON DELETE RESTRICT;
|
||
|
||
|
||
--
|
||
-- Name: admin_logs admin_logs_admin_id_fkey; Type: FK CONSTRAINT; Schema: public; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY public.admin_logs
|
||
ADD CONSTRAINT admin_logs_admin_id_fkey FOREIGN KEY (admin_id) REFERENCES public.users(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: review_tasks review_tasks_user_id_fkey; Type: FK CONSTRAINT; Schema: rvw_schema; Owner: postgres
|
||
--
|
||
|
||
ALTER TABLE ONLY rvw_schema.review_tasks
|
||
ADD CONSTRAINT review_tasks_user_id_fkey FOREIGN KEY (user_id) REFERENCES public.users(id) ON UPDATE CASCADE ON DELETE CASCADE;
|
||
|
||
|
||
--
|
||
-- Name: SCHEMA public; Type: ACL; Schema: -; Owner: postgres
|
||
--
|
||
|
||
REVOKE USAGE ON SCHEMA public FROM PUBLIC;
|
||
|
||
|
||
--
|
||
-- PostgreSQL database dump complete
|
||
--
|
||
|
||
\unrestrict vMbzIt5rdhooQQkVIadThqQNeTLSUjU5BIRHdaDmCIx41txnLZ1zV3bBefNanOQ
|
||
|