# Report Template Comparison

> Perform comprehensive template consistency comparison for medical report singles between test and production environments. Use when the user provides report single images or PDFs (test environment first, production environment second) and requests template comparison testing, requiring strict field name matching, structural consistency, module completeness, and visual style alignment.

- Skill: `bigassulike/report-template-comparison` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bigassulike/report-template-comparison`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bigassulike/report-template-comparison/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: bigassulike (https://skillmd.com/u/bigassulike)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/bigassulike/report-template-comparison

---


# Report Template Comparison Testing

## Purpose

This skill enables precise, repeatable template consistency testing for medical inspection report singles. It ensures the production environment report template matches the test environment in structure, field names, modules, page layout, and visual styles, while allowing business data values (results, times, doctor names) to differ.

## Core Principles

- Table header and table footer information must be consistent in structure, field names, module order, page number format, remarks, and signature areas.
- Customer information field **names** must be exactly identical. No missing fields, no renaming, no synonym substitution (e.g., "其他信息" vs "其它信息"), no empty value vs explicit "/" symbol.
- Detection detail table field **names** (English abbreviation, item, result, prompt, unit, reference interval, detection method, instrument) must be identical. Results/values may differ.
- Reference range, result interpretation & suggestion modules must have identical structure, field names, and item order.
- Font weight, font size, bold positions, title/header/field/remark/footer styles, spacing, and overall layout must be consistent.
- Clearly distinguish: field value empty (nothing displayed) ≠ field value explicitly showing "/" or other symbols.

## Must-Check Items

1. **Header Information**
   - Hospital logo, Chinese/English report title, title position and style
   - Customer information field completeness and order (name, gender, age, medical record number, barcode, controlled number, sample number, sample appearance, sample type, testing department, submitting department, submitting ward, bed number, clinical diagnosis, requested items)
   - Requested items and clinical diagnosis fields presence and location

2. **Customer Information Area** (Strict Name Matching)
   - Every field name must match exactly (no missing, no renaming, no "其他" vs "其它", no "医生" vs "医师")
   - Field arrangement order and line-breaking behavior must be consistent
   - Font weight and size must be consistent

3. **Detection Detail Table (Main Table on Page 1)**
   - Table header field names and order must match exactly (English abbr, item, result, prompt, unit, reference interval/range, detection method, instrument)
   - Complete list of detection items must be identical (no missing items or different item names)
   - Fixed information such as units and detection methods must be consistent
   - Table column order, borders, background, font weight must be consistent
   - Reference interval, unit, detection method columns: even if some items have no value, the column must exist and format consistent (allow blank or display "/" / "未检出"); blank value ≠ "/" symbol

4. **Reference Range Module (Usually Page 2)**
   - Module title 【参考范围】 must exist
   - Table fields (item, reference range) must match
   - Item order and content structure must be consistent

5. **Result Interpretation & Suggestion Module (Usually Page 3 or bottom of Page 1)**
   - Module title 【结果解读与建议】 or 【结果解读与建议】 must exist
   - Table fields (item, clinical manifestation, dietary supplement / clinical significance) must match
   - Item order must be consistent

6. **Footer Information**
   - Remark content and identifier explanations (*, ★ etc.) must match
   - Submitting doctor, tester, reviewer, page number format must match
   - Collection time, receive time, testing time, report time fields must be complete and format consistent
   - Page number format (e.g., "第 1 页/共 2 页") must be correct and unbroken

7. **Font & Visual Style**
   - Title, table header, field names, values, remarks, footer: font, size, weight, bold position must be consistent
   - Overall layout spacing and module arrangement must be basically consistent

## Judgment Criteria

- Any of the above items has **field name missing, field name different, field order different, module missing, page number error, or obvious style difference** → **Not pass / Fix and retest**
- Only result values, prompt arrows, time values, doctor signatures differ → **Pass**

## Output Requirements

Always produce output in the following structure:

## 比对结论

**本次模板比对结果：通过 / 不通过 / 需修复后复测**

## 通过项

- List of items that fully match (field names, structure, modules, styles)

## 问题项

| 检查项 | 测试环境 | 生产环境 | 问题类型 |
|--------|----------|----------|----------|
| ...    | ...      | ...      | 模板差异 / 数据差异 |

- Problem items must clearly state "模板差异" (template difference) or "数据差异" (data difference)
- For template differences, specify exact field name mismatch, missing field, order issue, etc.

## 风险与建议

- High/medium/low risk summary
- Specific next steps for production environment fix
- Font weight / visual style confirmation if needed

## Verification Checklist (Before Finalizing)

- [ ] All field names in customer information checked for exact match (including "其他信息" vs "其它信息")
- [ ] Empty value vs "/" symbol explicitly distinguished
- [ ] Page number format verified as correct (not broken like "第 页/共 1 1")
- [ ] Table header field order and names verified
- [ ] Module titles and structures verified
- [ ] Font weight and layout style differences noted if visible in images/PDF
- [ ] Conclusion clearly states Pass / Not pass / Fix and retest

## Notes

- Always treat test environment report as the baseline template.
- Production environment must match test environment template structure and names.
- Data value differences (results, times, signatures) are allowed and should be classified as "数据差异".
- When user provides multiple pages, compare page-by-page and summarize overall template consistency.