메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | fhir-info |
| description | 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. |
Look up FHIR definitions using the reference script:
bun scripts/fhir-ref-lookup.ts <Query> [--inherited]
bun scripts/fhir-ref-lookup.ts --list
<Query>: the FHIR identifier to look up. Supported forms:
Patient, Observation, Encounter, IncomingHL7v2MessageHumanName, CodeableConcept, Coding, Reference, PeriodPatientContact, ObservationComponent, ObservationReferenceRangeUnmappedCode (custom resource helpers)Patient.name, Observation.status, HumanName.given--inherited (-i): include inherited fields from parent types (e.g., DomainResource, Resource, Element)--list: list all known types grouped by kindThis skill reads the generated TypeScript types in src/fhir/:
src/fhir/hl7-fhir-r4-core/ — FHIR R4 core (150 resources, 47 datatypes, 467 backbone elements)src/fhir/aidbox-hl7v2-custom/ — custom resources (IncomingHL7v2Message, OutgoingBarMessage, UnmappedCode)The types are regenerated from the FHIR R4 package via bun run regenerate-fhir. If you've made changes to custom resource definitions in fhir/ or need to refresh after an upstream update, run that script first.
Because the data source is generated TypeScript (not raw StructureDefinitions), the skill cannot report:
[0..1], [0..*], [1..1], [1..*] — richer min/max (e.g. [0..3]) is lost.constraint), slicing, must-support flags — not in the TS output.src/fhir/.When you need any of the above, query Aidbox directly: curl http://localhost:8080/fhir/StructureDefinition/<Resource>.
Reference<> points to, or the allowed values of a coded fieldDo NOT skip this skill and rely on codebase exploration or memory for FHIR specifications. The generated types are the authoritative source for this project's runtime shape.
When looking up multiple types/fields, make separate Bash tool calls in the same response — do NOT use shell & or && to chain commands. Show the full script output to the user without modification.
hl7v2-info skill — HL7v2 side of the same need (segments, fields, datatypes, tables, messages).specs/v2-to-fhir/mappings/ — authoritative HL7v2↔FHIR field mappings (CSV). This skill covers the FHIR target shape only; use the mapping CSVs to determine which HL7v2 field maps to which FHIR element.Check recent HL7v2 processing errors in Aidbox, diagnose root causes, suggest fixes. Use when asked to check errors, diagnose failures, or troubleshoot message processing.
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).
Look up HL7v2 segment fields, datatypes, components, tables, and message structures. Use when writing converters, checking field positions/optionality, or verifying HL7v2 spec compliance.