reason.healthcare avatar

reason.healthcare

Official

@reason-healthcare

0Followers
|
33Public Repos
|
18Published Skills

Products and services focused on clinical reasoning by Vermonster.

Skills Distribution
DomainBusiness, Fi...Clinical Informatics (40%)Software Specifica.. (30%)FHIR Resource Engi.. (30%)

Agent Skills by reason.healthcare

Showing 18 vetted skills indexed across 1 GitHub repositories.

reason-healthcarereason-healthcare
12

speckit-checklist

Generate unit-test style checklists to validate software feature requirements quality.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-constitution

Synchronize governance constitutions in .specify/memory/constitution.md with semantic versioning.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-implement

Execute speckit task plans across setup, tests, core, integration, and polish phases.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-taskstoissues

Convert tasks into dependency-ordered GitHub issues for spec-kit repositories.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-clarify

Identify underspecified areas in feature specifications and log clarifications.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-plan

Automate SPEC-like implementation planning workflows to generate design artifacts like research.md and contracts.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-analyze

Analyzes spec.md, plan.md and tasks.md inconsistencies after task generation.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-specify

Convert natural language feature ideas into structured, testable specs.

Official
Advanced
reason-healthcarereason-healthcare
12

speckit-tasks

Translate spec-kit design artifacts into a dependency-ordered tasks.md.

Official
Advanced
reason-healthcarereason-healthcare
12

<skill-name>

Define front-matter-driven Skill units with entry points for rh-skills workflows.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-discovery

Organize healthcare informatics evidence into discovery-plan.yaml and discovery-readout.md.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-extract

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

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-verify

Coordinate topic-wide verification across the RH lifecycle into a read-only report.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-resolve

Resolve open conflicts across extract-plan.yaml and formalize-plan.yaml before implementation.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-formalize

Translate L2 structured artifacts into L3 FHIR computable resources.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-ingest

Plan and execute end-to-end clinical source ingestion workflows via the rh-skills CLI.

Official
Advanced
reason-healthcarereason-healthcare
12

rh-inf-status

Summarizes project health and per-topic readiness from rh-skills status.

Official
Basic
reason-healthcarereason-healthcare
12

rh-inf-cql

Extract, translate, test, and package CQL libraries from structured YAML using rh-skills.

Official
Advanced

Frequently Asked Questions About reason.healthcare

FAQPage Schema
What specific clinical tasks are enabled by these capabilities?

These capabilities enable the end-to-end ingestion of clinical sources, the extraction of L2 clinical artifacts, and the formalization of these artifacts into L3 FHIR computable resources. Additionally, users can package and test CQL libraries directly from structured YAML definitions to ensure clinical logic accuracy.

Which target personas benefit from these informatics skills?

Clinical informaticists, healthcare software engineers, and compliance officers benefit from these skills. The framework is designed for professionals managing complex clinical data lifecycles, requiring rigorous verification of informatics evidence and the translation of natural language requirements into testable, structured technical specifications.

What are the prerequisites for implementing these clinical reasoning units?

Implementation requires a repository structure compatible with the spec-kit standard, including defined front-matter for skill units. Users must maintain governance constitutions in .specify/memory/constitution.md and ensure clinical source data is normalized for ingestion into the rh-skills environment to facilitate successful artifact extraction and verification.