一键在 Manus 中运行任何 Skill

include-instrument

星标1

分支0

更新时间2026年5月4日 04:27

Decide whether to inline a validated instrument (copy items into Questionnaire.json) versus reference it via subQuestionnaire. Surfaces license + fidelity tradeoffs and records the decision. Use when the user wants to "add PHQ-9" (or any published instrument) to a draft.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

jmandel

jmandel/formtastic

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Include instrument

When to use this

The user names a published instrument ("add PHQ-9", "include GAD-7") and you need to actually wire it in.
A research turn surfaced a candidate instrument the user is about to accept.

Two ways to include

A. Inline (copy items)

Copy the instrument's items directly into the form's item[].

✅ Self-contained: the form ships with everything the patient sees.
✅ Easy to localize and re-skin.
❌ Drifts from the canonical source over time.
❌ License risk for non-public-domain instruments.

B. subQuestionnaire reference

Use the SDC subQuestionnaire extension on a display (or group) item:

{
  "linkId": "phq9",
  "type": "display",
  "extension": [{
    "url": "http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-subQuestionnaire",
    "valueCanonical": "http://loinc.org/q/44249-1"
  }]
}

✅ Renderer pulls the canonical version each time.
✅ License-clean: you're referencing, not copying.
❌ Renderer support varies. Pin a renderer or test before shipping.

License triage

License	Approach
Public domain (PHQ-9, GAD-7, AUDIT, SF-36 v1)	Inline OK.
Free-with-attribution (NIH PROMIS short forms; many AHRQ)	Inline OK; preserve attribution copy.
Permission required (BDI-II, HADS, some PROMIS CAT)	subQuestionnaire only. Note license in `decisions.md`.
Trade secret	Don't include. Refuse and explain.

Always cite the source instrument in the form via an instrument-typed citation (refType=instrument, refId=valueCanonical) regardless of method.

Recording the decision

After including (or referencing) an instrument, append to decisions.md:

2026-05-12 — Included PHQ-9 inline. Public domain in this jurisdiction. Source: USPSTF https://www.uspreventiveservicestaskforce.org/.../phq-9.

Pitfalls

Modifying the wording of a copyrighted instrument and shipping the modification ("just simplifying it"). Don't.
Inlining an instrument without recording the decision — when the user re-asks "where did this come from?" later, the conversation log may have been compacted away.
Mixing instrument items with locally-authored items in the same group. Keep them in their own group with a display-typed attribution header.

同仓库更多 Skills

同仓库

propose-edit

jmandel/formtastic

Produce a clean output/proposed-questionnaire.json or output/suggestions.json with stable linkIds, exact baseVersion, and the current typed proposal vocabulary. Use whenever you're about to suggest a structural change to the form.

2026-05-081

respond-and-organize

jmandel/formtastic

Write product-facing replies and organize run outputs in the canonical Formtastic artifact layout. Always applies to every turn because reply.md is the visible chat response and all structured output depends on the run directory contract.

2026-05-081

research-output

jmandel/formtastic

Create organized, copyright-safe research artifacts under output/research/. Always applies to evidence, guideline, citation, article, source-review, or literature turns.

2026-05-071

cochrane-search

jmandel/formtastic

Search Cochrane Reviews for systematic-review evidence and effect sizes. Use when the user wants the strongest evidence-base summary for a treatment, screening, or diagnostic question. Produces structured effect-size estimates with confidence intervals.

2026-05-071

guideline-search

jmandel/formtastic

Find clinical practice guidelines from authoritative bodies (NICE, USPSTF, ACP, AHRQ, GIN). Use when the user asks "what does the guideline say" or wants to anchor a question or threshold to a recommended practice. Produces guideline-typed citations with the canonical URL of the recommendation.

2026-05-071

pubmed-search

jmandel/formtastic

Search PubMed via NCBI E-utilities to ground questionnaire items in primary literature. Use when the user asks for evidence, citations, or "what does the research say about X." Produces an organized research bundle with PubMed metadata, abstracts when available, and source-grounded notes.

2026-05-071

name	include-instrument
description	Decide whether to inline a validated instrument (copy items into Questionnaire.json) versus reference it via subQuestionnaire. Surfaces license + fidelity tradeoffs and records the decision. Use when the user wants to "add PHQ-9" (or any published instrument) to a draft.

Include instrument

When to use this

The user names a published instrument ("add PHQ-9", "include GAD-7") and you need to actually wire it in.
A research turn surfaced a candidate instrument the user is about to accept.

Two ways to include

A. Inline (copy items)

Copy the instrument's items directly into the form's item[].

✅ Self-contained: the form ships with everything the patient sees.
✅ Easy to localize and re-skin.
❌ Drifts from the canonical source over time.
❌ License risk for non-public-domain instruments.

B. subQuestionnaire reference

Use the SDC subQuestionnaire extension on a display (or group) item:

{
  "linkId": "phq9",
  "type": "display",
  "extension": [{
    "url": "http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-subQuestionnaire",
    "valueCanonical": "http://loinc.org/q/44249-1"
  }]
}

✅ Renderer pulls the canonical version each time.
✅ License-clean: you're referencing, not copying.
❌ Renderer support varies. Pin a renderer or test before shipping.

License triage

License	Approach
Public domain (PHQ-9, GAD-7, AUDIT, SF-36 v1)	Inline OK.
Free-with-attribution (NIH PROMIS short forms; many AHRQ)	Inline OK; preserve attribution copy.
Permission required (BDI-II, HADS, some PROMIS CAT)	subQuestionnaire only. Note license in `decisions.md`.
Trade secret	Don't include. Refuse and explain.

Always cite the source instrument in the form via an instrument-typed citation (refType=instrument, refId=valueCanonical) regardless of method.

Recording the decision

After including (or referencing) an instrument, append to decisions.md:

2026-05-12 — Included PHQ-9 inline. Public domain in this jurisdiction. Source: USPSTF https://www.uspreventiveservicestaskforce.org/.../phq-9.

Pitfalls

Modifying the wording of a copyrighted instrument and shipping the modification ("just simplifying it"). Don't.
Inlining an instrument without recording the decision — when the user re-asks "where did this come from?" later, the conversation log may have been compacted away.
Mixing instrument items with locally-authored items in the same group. Keep them in their own group with a display-typed attribution header.