dsh-medrec-qc

dsh plugin --profile web add dsh-medrec-qc

dsh-medrec-qc — Form check and logic-contradiction prompts for the inpatient medical record front sheet

[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)

<!-- topblock:v1 -->

What it is — Form check and logic-contradiction prompts for the inpatient medical record front sheet. It returns a list of what is inconsistent, where, and what to fix.

Who it is for — medical records and quality control; no command line required.

What you give it — the source material the check works on (a table, register or document); the original is never modified. Excel can be converted to JSON/YAML first, in chat if the platform supports it.

What it does not do — no compliance verdict, no liability finding, no replacement for the reviewer; differences only.

How to start — search "Medical Record QC Suite" in WorkBuddy / Coze (this check is one part of it; availability as listed); or:

dsh plugin --profile <name> add dsh-medrec-qc

<!-- /topblock:v1 -->



dsh-medrec-qc reads an export of the inpatient medical record front sheet (病案首页), one row per discharge, in the column set of the national assessment export, the health statistics export or a hospital-local export, and checks that export's own form completeness, internal arithmetic and coding form: that each required column carries content or the - marker, that the admission and discharge times are present, precise to the minute and not in the wrong order, that the declared length of stay agrees with the two dates, that the primary diagnosis name and code and the primary operation name and code are filled together, that the codes have the written form the pack configures, that the three signature columns reflect three-level physician responsibility, that the discharge mode is one of the defined codes, that the age and the neonatal weights use the prescribed forms, that the count of other diagnoses stays within the configured ceiling, and that a diagnosis incompatible with the recorded sex or two disagreeing times in a death discharge are surfaced for human review.

Install

dsh plugin --profile <name> add dsh-medrec-qc
dsh --profile <name> --dump-config | grep 'dsh-medrec-qc'

What it looks like

Workflow overview: call → plugin → result. The examples below use the real command surface.

What it answers

Examples

The table below is the example set: the first row is the detailed walkthrough, the remaining rows are short cases.

Detailed output

Tool medrec_qc

Input

~~~yaml

target: 2026 年 3 月出院病案首页导出

cases:

• row: 1

病案号: ""

入院时间: "2026-03-01 08:30"

出院时间: "2026-03-06 10:00"

~~~

Output

~~~json

{

"id": "dsh-medrec-qc.MR-001.a58905f0",

"ruleId": "MR-001",

"severity": "error",

"locator": {

"row": 1,

"column": "病案号"

},

"found": "「病案号」为空",

"expected": "附件1 必填栏不能为空项，没有可填写内容时填写\"-\""

}

~~~

Observed from dsh-medrec-qc/tests/fixtures/MR-001/MR-001-unsafe.yaml

You ask · What it answers

A required column is left empty, but I typed - in it. Is that reported? · No. MR-001 treats a lone - as the marker for 'nothing to record here' and reports only the columns that are truly blank. It checks that a required column carries content, not that the content is correct. It is an error because 附件1's note now has been read verbatim (2026-10-13) — see the note below. The same - still counts as a missing signature under MR-009.

The admission time is written as a bare date with no hour or minute, and on one row the discharge time is earlier than the admission time. · MR-002 reports a 入院时间 or 出院时间 value that can be read only to the day, because the recorded time must be precise to the minute, and it also reports a value it cannot parse as a date and time at all. MR-003 compares the literal order of the two fields and reports the row where the discharge time comes first. Both work on the literal values and neither decides which of the two times is the true one.

The front sheet says 5 days, but the dates are 12 June in and 15 June out. · MR-004 recounts the days as discharge date minus admission date and reports the row when the declared 实际住院天数 disagrees; admission and discharge on the same day count as 0 days, and a value that is not a whole number of days is reported too. It compares the three stored values only and does not decide which of them is wrong.

主要诊断名称 is filled in but 主要诊断编码 is blank, and another row carries a code in a strange shape. · MR-005 requires the two to be filled together and names the one that is missing; it checks only that both exist, not that the code matches the diagnosis. MR-006 then tests the code against the written form configured in the pack, and it does not verify that the code exists in any version of the classification directory.

A batch contains no operation records at all. Do the operation rules pass in silence? · No. MR-007 reports itself in skipped with the reason that the material holds no operation record, so the pairing check does not apply, instead of passing in silence. When a row does record an operation, the rule requires 主要手术名称 and 主要手术编码 to be filled together, and MR-008 checks the written form of the operation code only.

A male patient's primary diagnosis is a pregnancy-related condition. Does that block the export? · MR-014 reports it as a warn-level difference for a human to confirm, never as a block: the health-side documents contain no clause making a diagnosis incompatible

…(truncated)