AIDx-Copilot training and implementationFig. 1![\"Fig.](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/06\/41598_2026_47470_Fig1_HTML.png\")
The alternative text for this image may have been generated using AI.<\/p>\n
Data processing pipeline for preparing supervised training data for AIDx-Copilot. De-identified EHR records from emergency, inpatient, and ICU settings are consolidated into a holistic visit representation. Static attributes (e.g., demographics, history) and dynamic attributes (e.g., labs, orders, diagnoses) are separated, and dynamic events are organized into temporally ordered visit timelines. Timeline snapshots are used to generate predictive question\u2013answer pairs for instruction tuning. The patient timeline shown is illustrative and not a complete clinical record.<\/p>\n
AIDx-Copilot was trained using de-identified clinical records derived from MIMIC-IV10<\/a>,11<\/a>,12<\/a>. I consolidated records from emergency, inpatient, and intensive care settings to cover common hospital documentation patterns.<\/p>\n Data preparation and temporal alignment<\/p>\n Each patient chart was restructured into static attributes (demographics, chronic conditions, medical history) and dynamic attributes (laboratory results, orders, procedures, diagnoses). I generated visit timelines by appending a new \u201csnapshot\u201d when any dynamic field changed.<\/p>\n To reduce temporal leakage in supervised prediction (i.e., using future information to answer past queries), snapshot construction orders events by timestamp and generates questions from the current snapshot while sourcing supervision targets only from strictly later snapshots.<\/p>\n Chat sample generation<\/p>\n To simulate clinical query\u2013response interactions, I generated synthetic dialogue pairs in which questions were derived from dynamic variables (e.g., \u201cWhat does the next lab result show?\u201d) and answers from subsequent timestamps. This yielded approximately eight million question\u2013answer samples for supervised fine-tuning.<\/p>\n Model fine-tuning<\/p>\n The base model was Mixtral-8x7B-Instruct-v0.115<\/a>. I fine-tuned it using Low-Rank Adaptation (LoRA)16<\/a> with DeepSpeed ZeRO optimizations17<\/a>,18<\/a>. Table\u00a01<\/a> lists all training hyperparameters. Following training, LoRA weights were merged with the base model and quantized using ExLLaMA v219<\/a> to reduce memory footprint and enable fast inference.<\/p>\n Table 1 Training hyperparameters for AIDx-Copilot fine-tuning.<\/p>\n Deployment stack<\/p>\n AIDx-Copilot is served behind an OpenAI-compatible API implemented with TabbyAPI20<\/a>. The backend orchestrates EHR retrieval, optional retrieval grounding, and response generation. (Fig. 2<\/a>)<\/p>\n Retrieval-augmented generation (RAG)Fig. 2 Workflow of AIDx, illustrating integration with an EHR database and optional retrieval grounding from medical references before response generation.<\/p>\n To provide access to external medical reference material, AIDx supports retrieval-augmented generation (RAG)21<\/a>. I constructed a reference database from open-access medical textbooks in the LibreTexts Medicine Library22<\/a>. Text was chunked using a recursive splitter (chunk size 1,000 characters; no overlap) and indexed for similarity search. For background and terminology, I follow recent surveys of retrieval-augmented generation for LLMs23<\/a>. Table\u00a02<\/a> summarizes the RAG configuration.<\/p>\n Table 2 RAG pipeline configuration details.<\/p>\n Data-flow boundary and deployment modes<\/p>\n The reference implementation can embed text using OpenAI text-embedding-3-small and store vectors in Pinecone24<\/a>. These choices may involve third-party services depending on deployment. For privacy-sensitive on-premises settings, an equivalent fully local configuration replaces the embedding model with a locally hosted BGE-base-en-v1.5 encoder and replaces the vector store with a self-hosted FAISS index. The application-layer interface (retrieve top passages, append to prompt) remains unchanged.<\/p>\n RAG usage in benchmark evaluation<\/p>\n To clearly delineate system components: the primary benchmark results reported in Table\u00a03<\/a> were obtained without RAG. This means the primary benchmarks test the fine-tuned model in isolation and do not reflect retrieval grounding. Ablation experiments in Section\u00a06.3<\/a> separately evaluate the effect of enabling RAG on benchmark performance.<\/p>\n Evaluation protocol<\/p>\n Evaluation used the MultiMedQA benchmark suite25<\/a>. I loaded all benchmarks from the Open Life Science AI MultiMedQA collection on Hugging Face (https:\/\/huggingface.co\/collections\/openlifescienceai\/multimedqa<\/a>).<\/p>\n Dataset identifiers and revisions<\/p>\n To make the benchmark configuration unambiguous, I record the dataset repositories and the revision (Git commit on the main branch) used at the time of evaluation:<\/p>\n MedQA (USMLE): openlifescienceai\/medqa @ 153e61c.<\/p>\n PubMedQA: openlifescienceai\/pubmedqa @ 50fc41d.<\/p>\n MedMCQA: openlifescienceai\/medmcqa @ c8b1a7c.<\/p>\n MMLU Clinical Knowledge: openlifescienceai\/mmlu_clinical_knowledge @ e151167.<\/p>\n MMLU Professional Medicine: openlifescienceai\/mmlu_professional_medicine @ a7a792b.<\/p>\n MMLU Anatomy: openlifescienceai\/mmlu_anatomy @ a7a792b.<\/p>\n MMLU College Biology: openlifescienceai\/mmlu_college_biology @ 94b1278.<\/p>\n MMLU College Medicine: openlifescienceai\/mmlu_college_medicine @ d983527.<\/p>\n MMLU Medical Genetics: openlifescienceai\/mmlu_medical_genetics @ f248e4a.<\/p>\n For each dataset and MMLU subject, I used the test split.<\/p>\n Prompt template<\/p>\n For each question, AIDx-Copilot received the prompt shown in Listing\u00a01. The system message establishes the medical assistant role. The user message contains the question stem and answer options verbatim from the dataset. The formatting constraint restricts the model to outputting a single-letter answer.<\/p>\n Listing 1 Exact prompt template used for all benchmark evaluations. Placeholders question and options are filled from each dataset item. For RAG-enabled ablation runs, retrieved passages are prepended to the user message as shown in Section 3.5.<\/p>\n Decoding and scoring<\/p>\n For each question, AIDx-Copilot produced a single answer under deterministic decoding (temperature=0, top_p=1, repetition_penalty=1.0; no self-consistency voting, no chain-of-thought). A regular expression (BEST ANSWER:\\(\\backslash\\)s*([A-D]) for four-option items; BEST ANSWER:\\(\\backslash\\)s*([A-C]) for PubMedQA) extracted the predicted letter. Items where the regex failed to match were scored as incorrect. Accuracy was computed as exact match with the reference label.<\/p>\n Uncertainty reporting<\/p>\n For each dataset, I report a Wilson 95% confidence interval for accuracy to reflect uncertainty due to finite test set size.<\/p>\n Ablation study design<\/p>\n To isolate the contributions of EHR-based fine-tuning and retrieval grounding, I evaluated four configurations on the full MultiMedQA suite under the identical deterministic protocol described above: <\/p>\n 1.<\/p>\n Base: Mixtral-8x7B-Instruct-v0.1 without fine-tuning or RAG. This is the unmodified base model with quantization applied identically to the fine-tuned variant.<\/p>\n 2.<\/p>\n Base + RAG: Base model with retrieval grounding enabled. For each benchmark question, the question text was used as the retrieval query, and the top-5 passages from the LibreTexts Medicine index were prepended to the user message under the header \u201cReference context:\u201d.<\/p>\n 3.<\/p>\n Fine-tuned (FT): AIDx-Copilot after EHR-based fine-tuning, without RAG. This is the configuration reported in the primary results (Table\u00a03<\/a>).<\/p>\n 4.<\/p>\n Fine-tuned + RAG (FT + RAG): AIDx-Copilot with retrieval grounding enabled using the same RAG procedure as configuration\u00a02.<\/p>\n All four configurations used the same quantized inference stack, prompt template (with or without prepended context), and scoring procedure.<\/p>\n Operational metrics<\/p>\n To assess deployment feasibility, I measured inference latency, throughput, VRAM consumption, and retrieval overhead on the hardware configuration described in Table\u00a06<\/a>. Latency was measured as wall-clock time from prompt submission to final token generation, averaged over 200 randomly sampled MedQA questions. Throughput was measured as questions processed per minute in sequential mode. VRAM was measured at peak allocation during inference using nvidia-smi.<\/p>\n Operational governance and security<\/p>\n AIDx is intended as a clinician-in-the-loop system. In practice, on-premises deployment requires basic governance controls so hospitals can answer three questions for any given output: who used the system, what exactly ran, and what information influenced the answer. The controls below describe the minimum operational safeguards supported by the AIDx design.<\/p>\n Audit logging (what happened): record the request timestamp, user\/role identifier, patient record identifier (or pseudonym), model version, retrieval index version, and the identifiers of retrieved reference passages. Store response metadata (e.g., token counts, latency) and keep logs within the institutional boundary.<\/p>\n Role-based access control (who can do what): restrict actions by role (e.g., clinician: query and view results; administrator: configure deployment settings; auditor: review logs). Require explicit permissions for configuration changes and access to any log data.<\/p>\n Versioning and change control (what exactly ran): version the deployed model artifact and retrieval index, and record the active versions on each request. Support rollback to a prior approved version if a regression or incident is detected.<\/p>\n Incident response (what to do when things go wrong): define triggers for investigation (e.g., unusual error rates, suspected prompt injection, unauthorized access), assign ownership for triage, and document procedures to disable retrieval, roll back a model\/index, or take the system offline.<\/p>\n Ethical and regulatory considerations<\/p>\n All benchmark data used are publicly available. Training data were derived from de-identified MIMIC-IV records. AIDx can be deployed on-premises to support HIPAA-aligned operation. GDPR and the EU AI Act motivate transparency, logging, risk management, and human oversight13<\/a>,14<\/a>.<\/p>\n Reproducibility and code availability<\/p>\n To make the evaluation transparent and replicable at the benchmark level, this work specifies: datasets, splits, and dataset revisions (Section\u00a04.4<\/a>); the exact prompt template (Listing\u00a01); decoding settings (temperature=0, top_p=1, repetition_penalty=1.0); the scoring regex and failure-handling rule; all training hyperparameters (Table\u00a01<\/a>); and RAG configuration details (Table\u00a02<\/a>). Per-dataset confidence intervals are reported in Table\u00a03<\/a>.<\/p>\n To support independent reproduction of the evaluation protocol, Supplementary Algorithm S1 provides pseudocode for the scoring script. The full evaluation code \u2014 including the benchmark runner, prompt construction, regex scoring, Wilson confidence interval computation, and the RAG retrieval reference implementation \u2014 is deposited at Zenodo (https:\/\/doi.org\/10.5281\/zenodo.19207085<\/a>). The evaluation can be executed against any OpenAI-compatible API endpoint. The AIDx training code, serving stack, and model artifacts are proprietary and are not publicly released.<\/p>\n","protected":false},"excerpt":{"rendered":"Overview The goal of this work was to design and assess a locally deployable LLM-based clinical assistant using…\n","protected":false},"author":2,"featured_media":70119,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[24,38937,25,38940,24633,17633,38938,1668,1743,1737,4965,38939,1744,7402,160],"class_list":["post-70118","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ai","tag-ai","tag-ai-driven-clinical-decision-support","tag-artificial-intelligence","tag-benchmark-evaluation","tag-business-and-industry","tag-computational-biology-and-bioinformatics","tag-ehr-integration","tag-health-care","tag-humanities-and-social-sciences","tag-mathematics-and-computing","tag-medical-research","tag-model-efficiency","tag-multidisciplinary","tag-retrieval-augmented-generation","tag-science"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/70118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=70118"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/70118\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/70119"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=70118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=70118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=70118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Fig.](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/06\/41598_2026_47470_Fig2_HTML.png\")
The alternative text for this image may have been generated using AI.<\/p>\n![\"figure](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/06\/41598_2026_47470_Figd_HTML.png\")
The alternative text for this image may have been generated using AI.<\/p>\n