rh-inf-formalize

Translate L2 structured artifacts into L3 FHIR computable resources.

12|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-formalize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rh-inf-formalize
Source: https://github.com/reason-healthcare/rh-skills/tree/main/skills/.curated/rh-inf-formalize
Command: npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-formalize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converges L2 structured artifacts into L3 FHIR computable resources, enabling deterministic, testable clinical rules and packaged outputs.

Core Features & Use Cases

  • Maps each L2 artifact type to its appropriate FHIR targets (PlanDefinition, Library, ValueSet, etc.).
  • Supports multi-type convergence with per-artifact strategies, pre-execution checks, and a formalize cycle (plan, implement, verify).
  • Produces ready-to-package computable artifacts and guidance for packaging and validation in RH Skills.

Quick Start

Plan and implement formalize for a topic to generate a computable FHIR package.

Frequently Asked Questions about rh-inf-formalize

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

FAQPage Schema
How do I translate structured clinical artifacts into computable FHIR resources?

To translate structured clinical artifacts into computable FHIR resources, this skill converges L2 artifacts into L3 FHIR targets like PlanDefinition and Library. It orchestrates plan, implement, and verify modes to produce deterministic, testable clinical rules for packaging.

What is the best way to package clinical decision support rules using FHIR?

The best way to package clinical decision support rules using FHIR is mapping L2 artifacts to appropriate FHIR targets. This process enforces frontmatter metadata, provenance, and validation guidance to generate ready-to-package computable artifacts.

Can I map multiple L2 artifact types to different FHIR targets simultaneously?

Yes, you can map multiple L2 artifact types to different FHIR targets simultaneously. The formalization process supports multi-type convergence with per-artifact strategies and strict pre-execution checks for deterministic outputs.

Does FHIR formalization require frontmatter metadata and provenance tracking?

Yes, FHIR formalization requires frontmatter metadata and provenance tracking. The skill enforces these strict checks during the planning, formalization, and packaging cycles to ensure deterministic and testable clinical resources.

How do I plan and implement a formalize cycle for a clinical topic?

To plan and implement a formalize cycle for a clinical topic, you generate a computable FHIR package by executing the structured modes. The process applies pre-execution checks and artifact-level targets to verify the computable outputs.