Loading...
Loading...
Found 13 Skills
Plan a digital health study or research protocol, including enrollment, consent, data collection, assessment schedules, study operations, and outcome measures.
Plan user journeys, onboarding flows, engagement strategies, and day-to-day workflows for digital health products.
Plan healthcare privacy, research, and regulatory compliance for a digital health product, including HIPAA, IRB, FDA, GDPR, governance, and operational controls.
Stage 2 of the Clinical ASR Flywheel. Use when curating clinical terms, tagging IPA, and synthesizing a NeMo manifest. NOT for scoring (use /digital-health-clinical-asr-eval).
Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIA_API_KEY check, deps install, TTS+ASR smoke test.
Stage 3 of Clinical ASR Flywheel. Score a NeMo manifest, produce the five-section KER leaderboard (by-ipa_source diagnostic). Not for ASR auth (/riva-asr).
Stage 4 of the Clinical ASR Flywheel. Use when priority KER is above 0.3 to run stock NeMo SFT on Parakeet TDT v2 and offline cycle N+1 re-eval. NOT for generic word boosting (use /finetune-asr).
Sets up the translation supplements an IG-Publisher-based FHIR Implementation Guide needs for its non-default languages, putting each one exactly where the publisher reads it — either by translating from the default-language source or by harvesting an already-published rendering in the target language. The default language stays authoritative and every machine translation needs a bilingual human review. Use this skill when a guide builds green and an additional language rendering is wanted, when the /<lang>/ pages show the default language instead of the translation, when deciding where a .po supplement or a translated page belongs, or when the user mentions Übersetzung, translation supplement, input/translations, po file, i18n-lang or i18n-default-lang. Do not use for measuring or comparing guides, for migrating one onto the MII KDS module template, or for a template package's own language mechanism; see fhir-ig-analysis and mii-ig-migration.
Measures one or more FHIR Implementation Guides read-only and reports the numbers as JSON and Markdown — scope, complexity, content hygiene, duplication, linguistics, maturity and risk — and compares several IGs side by side using normalised metrics. It builds, changes and publishes nothing. Use this skill when reviewing or QA-ing an MII KDS module IG before a release, when comparing a module against kerndatensatz-basis or another Implementierungsleitfaden, when tracking how a module grows between releases, or when someone asks how large, how clean or how mature a guide actually is. Do not use for migrating a guide onto the module template or for translating one; see mii-ig-migration and fhir-ig-translation.
Migrates a Simplifier-published MII KDS module Implementation Guide onto the MII KDS module template — preserves the module's identity, transfers the FSH artefacts, rewrites Simplifier/FQL directives into IG Publisher equivalents, and sets up the bilingual page set. Covers both source shapes — a SUSHI/IG-Publisher project, and a Forge-authored repo of raw FHIR XML/JSON resources with no sushi-config.yaml or input/fsh, converted with gofsh first. Use when moving a KDS module off Simplifier or Forge, when a rendered IG URL and its repo are handed over, when FQL blocks or {{tree}} and {{render}} directives stop rendering after such a move, or when the user mentions Kerndatensatz, KDS-Modul, Implementierungsleitfaden, Manteldokument, sushi-config, ig.ini, gofsh, StructureDefinition XML or the IG Publisher in the context of moving a guide. Not for authoring new profiles, creating a module from scratch, or translating a guide already on the template — the catalog ships fhir-ig-translation for that.
Set up and maintain a persistent, LLM-managed knowledge base for a digital health project — turning clinical observations, papers, interviews, and planning docs into a compounding, interlinked wiki.
Walk through the full process of building a digital health app — from defining the need through planning to implementation.