rh-inf-extract

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.

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.

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.

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.

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.

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.