القائمة
Look up HL7v2 segment fields, datatypes, components, tables, and message structures. Use when writing converters, checking field positions/optionality, or verifying HL7v2 spec compliance.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Check recent HL7v2 processing errors in Aidbox, diagnose root causes, suggest fixes. Use when asked to check errors, diagnose failures, or troubleshoot message processing.
Look up FHIR R4 resource/datatype fields, types, cardinality, reference targets, and coded enums (including custom resources like IncomingHL7v2Message, OutgoingBarMessage). Use when writing converters or verifying FHIR compliance.
Build a new HL7v2→FHIR message converter or extend an existing one. Orchestrates requirements gathering, then delegates to `/plan` and `/work`.
Create a checkbox task plan for a feature or fix. Output is a markdown file that `/work` executes one task at a time.
Execute a plan produced by `/plan` — one task at a time, with tests and an independent review after each task.
Authenticate ad-hoc curl requests to the local Aidbox using the root Client secret from docker-compose.yaml. Use for debugging and one-off queries from the shell (not from app code — `src/aidbox.ts` already wraps auth).
| name | hl7v2-info |
| description | Look up HL7v2 segment fields, datatypes, components, tables, and message structures. Use when writing converters, checking field positions/optionality, or verifying HL7v2 spec compliance. |
Look up HL7v2 definitions using the reference script:
bun scripts/hl7v2-ref-lookup.ts <code> [--version <version>]
<code>: the HL7v2 identifier to look up. Must be one of:
ORU_R01, ADT_A01PID, OBXPID.3, OBX.2PID.3.1, CWE.10001, 0203CWE, ST, ID--version: HL7v2 version (default 2.8.2). Supported: 2.5, 2.8.2This project has reference data for two HL7v2 versions: v2.5 and v2.8.2.
Do NOT skip this skill and rely on codebase exploration or memory for HL7v2 specifications. The reference data is the authoritative source.
When looking up multiple codes, make separate Bash tool calls in the same response — do NOT use shell & or && to chain commands. The script is allowlisted individually (bun scripts/hl7v2-ref-lookup.ts:*), and chained shell commands bypass the allowlist and trigger permission prompts. Show the full script output to the user without modification.