rh-inf-extract

Plan, derive, and validate L2 clinical artifacts from normalized sources.

12|1|Updated Apr 15, 2026

Search Tags:#workflow-automation #rh-skills #clinical-informatics #artifact-derivation #l2-artifacts #reviewer-gated

Ready to run

npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-extract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rh-inf-extract
Source: https://github.com/reason-healthcare/rh-skills/tree/main/skills/.curated/rh-inf-extract
Command: npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables clinical informaticists to convert ingested normalized sources into review packets and deterministic L2 artifacts through a structured plan → implement → verify lifecycle, with reviewer gating to ensure quality and safety.

Core Features & Use Cases

Plan extract artifacts from normalized sources and generate topics/<topic>/process/plans/extract-plan.yaml and topics/<topic>/process/plans/extract-plan-readout.md.
Implement approved artifacts via derive, validate, and render steps using rh-skills CLI.
Verify artifacts non-destructively and render human-readable reports for SME review.
Enforce reviewer decisions and manage conflicts within the plan.

Quick Start

Plan the topic with rh-skills plan, review the generated plan, then implement approved artifacts using rh-skills promote derive and render the results.

Frequently Asked Questions about rh-inf-extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I derive structured clinical artifacts from normalized sources?▼

To derive structured clinical artifacts, you extract L2 artifacts from normalized sources using a plan, implement, and verify lifecycle. This generates structured clinical artifacts that can be formalized and rendered in topic directories.

What is a reviewer-gated lifecycle for clinical informatics artifact generation?▼

A reviewer-gated lifecycle for clinical informatics artifact generation enforces quality by requiring reviewer decisions at each stage. It follows a plan, implement, and verify process to ensure clinical safety before finalizing L2 artifacts.

How do I generate extract plans for clinical guidelines using rh-skills?▼

You generate extract plans for clinical guidelines by planning the topic with rh-skills plan. This creates an extract-plan.yaml and an extract-plan-readout.md file within your topic process directories for subsequent implementation.

Can I validate clinical quality measures non-destructively before SME review?▼

Yes, you can validate clinical quality measures non-destructively during the verify step. The process renders human-readable reports for SME review without altering the underlying derived artifacts, ensuring safe evaluation.

Do I need normalized sources under sources/normalized to derive L2 artifacts?▼

Yes, normalized sources under sources/normalized are required to derive L2 artifacts. The extraction process depends on these ingested normalized sources to plan, derive, validate, and render structured clinical artifacts.

How do I render approved clinical artifacts after promoting a derivation plan?▼

To render approved clinical artifacts, promote the derivation plan using rh-skills promote derive, then render the results. This implements approved artifacts via derive, validate, and render steps using the rh-skills CLI.