Installable skillMIT

Clinical Documentation Query

Generate compliant physician queries to clarify clinical documentation for accurate coding, severity of illness, and risk of mortality capture

BY a5c-aiUPDATED Oct 27, 2026
INTENDED FOR✳Claude Code>_Codex◈OpenClaw↗CursorInstall in a listed agent.

instructions.md

---
name: clinical-documentation-query
description: Generate compliant physician queries to clarify clinical documentation for accurate coding, severity of illness, and risk of mortality capture
allowed-tools: Read, Grep, Write, Edit, Glob
graph:
  domains: [domain:healthcare]
  specializations: [specialization:clinical-informatics]
  skillAreas: [skill-area:document-processing, skill-area:data-quality, skill-area:compliance-automation]
  workflows: [workflow:experiment-design]
  roles: [role:data-analyst, role:compliance-officer]
---

# Clinical Documentation Query

Generate compliant physician queries to clarify clinical documentation for accurate coding, severity of illness, and risk of mortality capture.

## Overview

This skill enables creation of compliant clinical documentation queries. It encompasses query identification, compliant query writing, physician engagement, and response tracking to improve documentation accuracy and coding specificity.

## Capabilities

### Query Identification
- Documentation gap analysis
- Clinical indicator review
- Coding specificity needs
- Quality measure support
- DRG optimization

### Compliant Query Writing
- Non-leading queries
- Multiple choice formats
- Open-ended questions
- Clinical indicator inclusion
- Evidence-based requests

### Query Types
- Diagnosis clarification
- Severity specification
- Causation documentation
- Present on admission
- Clinical significance

### Response Management
- Query tracking
- Response monitoring
- Documentation updates
- Escalation procedures
- Outcome analysis

## Usage Guidelines

### Query Process
1. Review clinical documentation
2. Identify opportunities
3. Gather clinical evidence
4. Draft compliant query
5. Submit to physician
6. Track response
7. Update documentation

### Compliance Requirements
- Non-leading format
- Clinical evidence basis
- Multiple response options
- Include "unable to determine"
- No financial motivation mention

### Best Practices
- Query concurrently when possible
- Use clinical indicators
- Be specific but not leading
- Provide relevant context
- Track response rates

## Integration Points

### Related Processes
- Clinical Documentation Improvement
- Medical Coding Compliance
- Quality Reporting Program Compliance

### Collaborating Skills
- medical-coding-audit
- quality-metrics-measurement
- regulatory-compliance-assessment

## References

- AHIMA CDI Practice Brief
- ACDIS query guidelines
- OIG compliance guidance
- CDI best practices
COMPATIBILITY & REFERENCES

Platform guidance

Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.