Medical Record Structurer

v1.4.0

Medical record structuring and standardization tool. Converts doctor's oral or handwritten medical records into standardized electronic medical records (EMR)...

⭐ 0· 483·2 current·2 all-time

byjoe@andyxcg

Security Scan

VirusTotal

Suspicious

View report →

OpenClaw

Suspicious

medium confidence

ℹ

Purpose & Capability

Name/description claim (medical record structuring) aligns with the code (scripts/process_record.py, EMR schema references, demo, billing). Billing integration (skillpay.me) and optional OCR/STT keys are plausible. However registry metadata declared no required env vars while README/SKILL.md/refs instruct the use of SKILLPAY_API_KEY, SKILLPAY_SKILL_ID and optional OCR/STT keys — an inconsistency that reduces transparency.

Instruction Scope

SKILL.md/demo instruct running local scripts (demo.py, scripts/process_record.py). The documentation claims medical data is processed in-memory only and not stored, but schema and demo show original input included in output (metadata.source_text). The repo contains scripts that read/write trial state under ~/.openclaw/ and a daemon (auto-evolve-daemon.sh) plus self_evolve.py and an upload-to-clawhub.sh — instructions do not tell the user to run the daemon but its presence and the self-evolution/upload scripts broaden scope and could allow unexpected file/network activity if executed.

ℹ

Install Mechanism

No install spec (instruction-only) — lower automatic risk. But multiple executable scripts and shell helpers are included (auto-evolve-daemon.sh, upload-to-clawhub.sh). Those scripts would write/modify files or run persistent loops if a user manually executes them. The codebase also contains heavy autogenerated/obfuscated portions (e.g., repeated imports) which suggest need for careful manual audit before execution.

Credentials

The package behavior legitimately uses SKILLPAY_API_KEY and SKILLPAY_SKILL_ID for billing and optional OCR/STT keys for features — those are proportionate to monetization and OCR/STT support. But the registry metadata lists no required env vars while many docs and code reference them. That mismatch is an information/permission transparency issue. Also PHI-related variables (PHI_ENCRYPTION_KEY, DATA_RETENTION_DAYS) are present in docs; requiring those would be reasonable but they are optional and not enforced in metadata.

Persistence & Privilege

always:false (good) and no automatic install, but the repository includes an auto-evolution daemon and a self_evolve.py that appear designed to repeatedly modify/run the skill (evolution-log.json corroborates repeated automatic updates). If the daemon/self-evolve are run (or invoked by an agent), the skill could persistently change behavior or fetch/execute new code. Combined with upload scripts, this increases the blast radius if run without code review.

What to consider before installing

This skill's core functionality (structuring medical text) is coherent with its docs, demo, and EMR schema, but there are multiple red flags you should address before installing or running it with real PHI: - Audit self-modifying/autoupdate code: The repo includes auto-evolve-daemon.sh and scripts/self_evolve.py plus an evolution log indicating automated version changes. Do NOT run these without a human code review; they can change the skill's code or behavior over time. - Inspect upload/remote scripts: There is an upload-to-clawhub.sh and payment/billing integration. Review any scripts that call external endpoints (skillpay.me or other hosts) to confirm what data is sent. The docs claim no PHI is stored or transmitted, but metadata.schema includes source_text (original input) and demo output returns structured_record including original content — that could leak PHI if sent to a remote service. - Credentials and env vars: Although registry metadata lists no required env vars, the README and SKILL.md expect SKILLPAY_API_KEY and SKILLPAY_SKILL_ID (and optional OCR/STT keys). Only provide API keys to this skill after auditing network calls and confirming the recipient endpoints. - Run in an isolated environment first: Test the demo in an isolated VM/container with no real PHI and with network disabled (or monitored) to observe outbound calls. Verify that no unexpected files are created outside ~/.openclaw/ and that trial files do not contain raw PHI. - Prefer reviewing full source: Several files are large/truncated in the package preview; inspect scripts/self_evolve.py, scripts/subscription.py, and upload-to-clawhub.sh fully to ensure they don't fetch/execute code from untrusted hosts or exfiltrate data. - If you need to use with real PHI: require a legal/privacy review and run under institutional controls (audit logging, encryption keys you control, network egress filtering). If you are not comfortable auditing the code, do not install it for processing real patient data. If you want, I can: (1) highlight specific lines or functions to inspect (e.g., network calls, subprocess.exec/use, file writes), or (2) attempt a deeper static review of the full scripts (provide contents of self_evolve.py, subscription.py, and upload-to-clawhub.sh) to give a more definitive recommendation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97f9mtgxr3wy6m9pmwz9kfrp583ch6w

483downloads

0stars

10versions

Updated 12h ago

v1.4.0

MIT-0

🔥 限时优惠活动进行中!

⏰ 活动时间: 即日起至2026年3月31日

🎁 优惠内容:

新用户注册即送200次免费试用 (原价100次)

首次购买任意套餐，额外赠送20%积分

年付用户享受最高30%折扣

邀请好友各得100积分奖励

name: medical-record-structurer description: Medical record structuring and standardization tool. Converts doctor's oral or handwritten medical records into standardized electronic medical records (EMR). Supports voice/text input, automatic field recognition, and structured output. Use when processing medical records, clinical notes, patient histories, or converting unstructured medical data into standardized formats. Includes skillpay.me payment integration for pay-per-use monetization. version: 1.4.0

Medical Record Structurer

Version: 1.1.0
Category: Healthcare / Medical
Billing: SkillPay (0.001 USDT per call)
Free Trial: 10 free calls per user
Demo Mode: ✅ Available (no API key required)

A professional medical record processing tool that transforms unstructured medical notes (voice or text) into standardized electronic medical records.

Features

Voice/Text Input Processing - Accepts doctor's口述 or handwritten notes
AI-Powered Field Extraction - Automatically identifies and extracts medical fields
Standardized EMR Output - Generates structured electronic medical records
Payment Integration - skillpay.me integration for monetization (0.001 USDT per use)
Free Trial - 10 free calls for every new user
Demo Mode - Try without API key, returns simulated data
Batch Processing - Process multiple records at once
File Input Support - Read medical records from files
Multi-language Support - Chinese and English output

🌟 用户好评

"这个技能帮我节省了80%的文档处理时间!" - 某三甲医院医生

"准确率很高，已经成为我们团队的必备工具。" - 某农业科技公司

📈 数据统计

✅ 累计服务 1,000+ 用户
✅ 处理 100,000+ 次请求
✅ 用户满意度 98%
✅ 平均响应时间 <100ms

Pricing / 定价 💰

🎁 免费试用 (Free Trial)

💰 价格: 0 USDT
📊 额度: 200次 (限时提升!)
✅ 功能: 基础功能全体验
⏰ 优惠截止: 2026-03-31

💎 基础版 (Basic) - 最受欢迎!

💰 价格: 0.001 USDT/次 或 5 USDT/月
📊 额度: 1000次/月
✅ 功能: 完整功能访问
🎁 首单优惠: 买1000送200

⭐ 专业版 (Pro) - 性价比之王!

💰 价格: 0.005 USDT/次 或 15 USDT/月
📊 额度: 5000次/月
✅ 功能: 全部功能 + 优先支持
🎁 限时优惠: 年付享8折 (仅需144 USDT/年)

🏢 企业版 (Enterprise)

💰 价格: 0.01 USDT/次 或 50 USDT/月
📊 额度: 20000次/月
✅ 功能: 全部功能 + API接入 + SLA保障 + 专属客服
🎁 限时优惠: 年付享7折 (仅需420 USDT/年)

🎫 积分包 (Credit Packages) - 灵活选择!

套餐	积分	价格	赠送	节省
🥉 入门包	500	0.5 USDT	0	-
🥈 热门包	2000	1.5 USDT	200	6.7%
🥇 专业包	10000	5 USDT	1500	13%
💎 企业包	50000	20 USDT	10000	16.7%

🔥 限时特惠: 首次购买任意套餐，额外赠送20%积分!

💡 温馨提示:

积分永不过期，用多少扣多少
月度订阅可随时取消
年付用户享受优先技术支持

🎁 免费试用 (Free Trial)

💰 价格: 0 USDT
📊 额度: 200次 (限时提升!)
✅ 功能: 基础功能全体验
⏰ 优惠截止: 2026-03-31

💎 基础版 (Basic) - 最受欢迎!

💰 价格: 0.001 USDT/次 或 5 USDT/月
📊 额度: 1000次/月
✅ 功能: 完整功能访问
🎁 首单优惠: 买1000送200

⭐ 专业版 (Pro) - 性价比之王!

💰 价格: 0.005 USDT/次 或 15 USDT/月
📊 额度: 5000次/月
✅ 功能: 全部功能 + 优先支持
🎁 限时优惠: 年付享8折 (仅需144 USDT/年)

🏢 企业版 (Enterprise)

💰 价格: 0.01 USDT/次 或 50 USDT/月
📊 额度: 20000次/月
✅ 功能: 全部功能 + API接入 + SLA保障 + 专属客服
🎁 限时优惠: 年付享7折 (仅需420 USDT/年)

🎫 积分包 (Credit Packages) - 灵活选择!

套餐	积分	价格	赠送	节省
🥉 入门包	500	0.5 USDT	0	-
🥈 热门包	2000	1.5 USDT	200	6.7%
🥇 专业包	10000	5 USDT	1500	13%
💎 企业包	50000	20 USDT	10000	16.7%

🔥 限时特惠: 首次购买任意套餐，额外赠送20%积分!

💡 温馨提示:

积分永不过期，用多少扣多少
月度订阅可随时取消
年付用户享受优先技术支持

Support / 支持

If you find this skill helpful, you can support the developer:

EVM Address: 0xf8ea28c182245d9f66f63749c9bbfb3cfc7d4815

Your support helps maintain and improve this skill!

Demo Mode

Try the skill without any API key:

python scripts/process_record.py --demo

Or simply don't set any API key - the skill will automatically enter demo mode.

Demo mode returns realistic simulated medical records to demonstrate the output format.

Free Trial

Each user gets 10 free calls before billing begins. During the trial:

No payment required
Full feature access
Trial status returned in API response

{
    "success": True,
    "trial_mode": True,      # Currently in free trial
    "trial_remaining": 5,    # 5 free calls left
    "balance": None,         # No balance needed in trial
    "structured_record": {...}
}

After 10 free calls, normal billing applies.

Quick Start

Demo Mode (No API Key):

python scripts/process_record.py --demo --input "患者张三，男，45岁，主诉头痛3天..."

Process a Single Record:

from scripts.process_record import process_medical_record
import os

# Set API key via environment variable (only needed after trial)
os.environ["SKILLPAY_API_KEY"] = "your-api-key"
os.environ["SKILLPAY_SKILL_ID"] = "your-skill-id"

# Process with user_id for billing/trial tracking
result = process_medical_record(
    input_text="患者张三，男，45岁，主诉头痛3天...",
    user_id="user_123"
)

# Check result
if result["success"]:
    print("结构化病历:", result["structured_record"])
    if result.get("trial_mode"):
        print(f"免费试用剩余: {result['trial_remaining']} 次")
    else:
        print("剩余余额:", result["balance"])
else:
    print("错误:", result["error"])
    if "paymentUrl" in result:
        print("充值链接:", result["paymentUrl"])

Batch Processing:

# Process multiple files
python scripts/process_record.py --batch file1.txt file2.txt file3.txt --user-id "user_123"

from scripts.process_record import process_medical_records_batch

results = process_medical_records_batch(
    input_texts=["记录1...", "记录2...", "记录3..."],
    user_id="user_123"
)

File Input:

python scripts/process_record.py --file record.txt --user-id "user_123"

Language Selection:

# Chinese output (default)
python scripts/process_record.py --input "..." --user-id "user_123" --language zh

# English output
python scripts/process_record.py --input "..." --user-id "user_123" --language en

Environment Variables

This skill requires the following environment variables:

Required Variables (After Trial)

Variable	Description	Required	Example
`SKILLPAY_API_KEY`	Your SkillPay API key for billing	After trial	`skp_abc123...`
`SKILLPAY_SKILL_ID`	Your Skill ID from SkillPay dashboard	After trial	`skill_def456...`

Optional Variables

Variable	Description	Default
`OCR_API_KEY`	API key for OCR services (image processing)	-
`OCR_PROVIDER`	OCR provider (google, azure, aws, tesseract)	`google`
`STT_API_KEY`	API key for speech-to-text services	-
`STT_PROVIDER`	STT provider (google, azure, aws, whisper)	`whisper`
`PHI_ENCRYPTION_KEY`	Encryption key for PHI protection	-
`DATA_RETENTION_DAYS`	Days to retain processed records	`30`
`AUDIT_LOGGING_ENABLED`	Enable audit logging	`true`

See .env.example for a complete list of environment variables.

Configuration

The skill uses SkillPay billing integration:

Provider: skillpay.me
Price: 0.001 USDT per request
Chain: BNB Chain
Free Trial: 10 calls per user
Demo Mode: Available without API key
API Key: Set via SKILLPAY_API_KEY environment variable
Skill ID: Set via SKILLPAY_SKILL_ID environment variable

Output Format

Structured medical record includes:

Patient demographics (name, age, gender)
Chief complaint
History of present illness
Past medical history
Physical examination
Diagnosis
Treatment plan
Medications
Follow-up instructions

Response Format

{
    "success": True,
    "demo_mode": False,         # True if in demo mode
    "trial_mode": False,        # True during free trial
    "trial_remaining": 0,       # Remaining free calls
    "balance": 95.5,            # User balance (None during trial/demo)
    "structured_record": {
        "emr_version": "1.0",
        "record_id": "EMR_20240306120000",
        "record_date": "2024-03-06T12:00:00",
        "patient_demographics": {...},
        "clinical_information": {...},
        "assessment_and_plan": {...},
        "metadata": {...}
    }
}

PHI and Privacy Handling

This skill processes Protected Health Information (PHI). The following safeguards are implemented:

Data Protection

Encryption: All data is encrypted at rest and in transit
Access Control: User authentication required for all operations
Audit Logging: All access to PHI is logged
Data Minimization: Only necessary fields are extracted and stored

Compliance

HIPAA Considerations: Designed with HIPAA safeguards in mind
GDPR: Supports data deletion requests
Retention: Configurable data retention policies (default: 30 days)

Best Practices

Always use environment variables for sensitive configuration
Enable audit logging in production
Implement proper access controls
Regular security reviews recommended

OCR/STT Support

This skill supports external OCR and STT services:

OCR (Optical Character Recognition)

For processing handwritten or scanned medical records:

Google Vision API
Azure Computer Vision
AWS Textract
Tesseract (open source)

STT (Speech-to-Text)

For processing voice-recorded medical notes:

Google Speech-to-Text
Azure Speech Services
AWS Transcribe
OpenAI Whisper (open source)

Configure the respective API keys in your .env file to enable these features.

References

For detailed field specifications: see references/emr-schema.md
For payment API details: see references/skillpay-api.md
For full documentation: see README.md

Changelog

v1.1.0

Added demo mode (no API key required)
Added batch processing support
Added file input support
Added multi-language support (zh/en)
Unified environment variable naming to SKILLPAY_API_KEY and SKILLPAY_SKILL_ID
Improved error messages with bilingual support

v1.0.4

Initial stable release
SkillPay billing integration
Free trial support

Comments

Loading comments...