Prompt Details
Model
Chat - (gpt-5.2)
Token size
607
Example input
[Legal / Medical / Finance / Technical Docs / Customer Support]: Medical
[PDFs / Databases / Internal Docs / Mixed]: Mixed (Clinical PDFs, Medical Databases, Internal Hospital Protocols)
[Low / Medium / High]: High
[Simple / Multi-step / Analytical]: Analytical
[Chatbot / Research Assistant / Internal Search]: Research Assistant
Example output
1οΈβ£ Domain Knowledge Architecture
Industry Knowledge Structure
Clinical Guidelines
Drug Information
Disease Knowledge Base
Diagnostic Protocols
Treatment Procedures
Medical Research Papers
Core Knowledge Categories
Symptoms & Diagnosis
Medication & Drug Interactions
Treatment Pathways
Clinical Trial Evidence
Patient Safety Guidelines
Domain Terminology Mapping
Map synonyms and abbreviations
Example mappings:
Myocardial Infarction β Heart Attack
Hypertension β High Blood Pressure
ECG β Electrocardiogram
---
2οΈβ£ Document Processing Strategy
Domain Document Segmentation Rules
Split clinical papers by:
Abstract
Methods
Results
Discussion
Split guidelines by medical procedure sections
Metadata Tagging Framework
Disease Category
Medical Specialty
Drug Name
Publication Year
Clinical Evidence Level
Terminology Normalization
Convert abbreviations to standard medical terms
Normalize drug names (generic vs brand)
---
3οΈβ£ Retrieval Strategy Design
Query Interpretation for Medical Language
Recognize symptoms, diseases, treatments
Identify medical abbreviations in queries
Retrieval Prioritization Rules
Clinical guidelines first
Peer-reviewed research second
Internal protocols third
Domain-Aware Relevance Scoring
Score higher if:
Matches disease entity
Matches treatment protocol
Matches medical specialty
---
4οΈβ£ Specialized Chunking Strategy
Domain-Specific Section Splitting
Split medical documents by:
Diagnosis section
Treatment section
Risk factors section
Context Preservation Logic
Maintain relationship between symptoms, diagnosis, and treatment
Medical Clause Handling
Preserve dosage instructions and safety warnings in the same chunk
---
5οΈβ£ Compliance & Risk Considerations
Sensitive Data Protection
Remove patient-identifiable information (PHI)
Encrypt medical records
Regulatory Constraints
HIPAA compliance
Medical data governance policies
Access Control Logic
Doctors: Full medical access
Staff: Limited protocol access
Researchers: Research-only datasets
---
6οΈβ£ Query Understanding Layer
Domain Intent Detection
Diagnosis query
Treatment query
Drug interaction query
Research evidence query
Specialized Query Expansion Rules
Expand disease synonyms
Include related symptoms
Context Interpretation
Interpret symptom combinations as potential diagnoses
---
7οΈβ£ Answer Generation Workflow
Evidence-Based Response Construction
Retrieve top medical documents
Extract treatment recommendations
Summarize evidence findings
Citation Requirements
Cite clinical guideline source
Cite research paper reference
Confidence Scoring
High: Clinical guideline match
Medium: Research study match
Low: Indirect evidence
---
8οΈβ£ Knowledge Update Strategy
Industry Data Refresh Rules
Weekly update for research publications
Monthly update for clinical guidelines
Version Tracking Logic
Track guideline revisions
Maintain historical protocol versions
Knowledge Lifecycle Management
Archive outdated medical protocols
Replace with latest clinical recommendations
---
9οΈβ£ Monitoring & Evaluation
Domain Accuracy Metrics
Medical factual correctness
Clinical recommendation accuracy
Retrieval Relevance Evaluation
Percentage of medically relevant sources retrieved
Error Detection Mechanisms
Flag conflicting treatment guidelines
Detect outdated medical recommendations
---
π Executive Domain RAG Blueprint
Core Domain Challenge
Ensuring medically accurate responses while handling complex terminology
Most Critical System Safeguard
Strict PHI protection and regulatory compliance
One Optimization Opportunity
Implement medical ontology integration (UMLS / SNOMED) for better disease and treatment retrieval.
By purchasing this prompt, you agree to our terms of service
GPT-5.2
Generic RAG systems struggle with domain-specific terminology, structured documents, and regulatory constraints.
This prompt designs a domain-adapted RAG architecture that handles specialized documents, retrieval rules, and compliance requirements.
Buyer Benefits
π§ Domain-aware retrieval logic
π Industry document structuring strategy
π Specialized query interpretation
β Compliance-aware knowledge handling
β Vertical SaaS knowledge architecture
π Use this prompt to design industry-specif
...more
Added over 1 month ago
