臺灣榮總腦中風實作指引(TW VGH Stroke IG)
0.1.0 - ci-build
臺灣榮總腦中風實作指引(TW VGH Stroke IG), published by 高雄榮民總醫院 (VGHKS). This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/SitatechCo/TWVGHStroke_IG_Build/ and changes regularly. See the Directory of published versions
| Official URL: http://vgh-stroke-ig.fhir.tw/ValueSet/stroke-evt-procedure-detail-answer | Version: 0.1.0 | |||
| Draft as of 2026-10-07 | Computable Name: StrokeEvtProcedureDetailAnswerVS | |||
| Other Identifiers: OID:2.25.44999852043401334926409052700533166808 | ||||
此 ValueSet 整合 StrokeEvtProcedureDetail 各項目的答案代碼,綁定至該 Profile 的 valueCodeableConcept(required)。主動脈弓分型(aortic-arch-type)填 StrokeAorticArchTypeCS;各血管狹窄程度(right-cca-stenosis、left-cca-stenosis、right-ica-stenosis、left-ica-stenosis、right-vertebral-artery-stenosis、left-vertebral-artery-stenosis)填 StrokeStenosisGradeCS;抽吸取栓策略(aspiration-strategy,代碼 1 至 3)與補充選項(aspiration-strategy-supplement,代碼 4)填 StrokeAspirationStrategyCS;抽吸失敗後救援策略(aspiration-rescue-strategy,限 StrokeAspirationRescueVS 的代碼)與支架取栓後救援策略(stent-retriever-rescue-strategy,限 StrokeStentRetrieverRescueVS 的代碼)填 StrokeRescueStrategyCS;兩者代碼限制由 StrokeEvtProcedureDetail 的 Invariant 檢查。
References
This value set includes codes based on the following rules:
http://vgh-stroke-ig.fhir.tw/CodeSystem/aortic-arch-type version 📦0.1.0http://vgh-stroke-ig.fhir.tw/CodeSystem/stenosis-grade version 📦0.1.0http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy version 📦0.1.0http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy version 📦0.1.0
Expansion performed internally based on:
This value set contains 15 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://vgh-stroke-ig.fhir.tw/CodeSystem/aortic-arch-type | 1 | 第 I 型 | 第 I 型主動脈弓:頭臂動脈起點與主動脈弓外緣大致同高。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aortic-arch-type | 2 | 第 II 型 | 第 II 型主動脈弓:頭臂動脈起點介於主動脈弓外緣與內緣之間。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aortic-arch-type | 3 | 第 III 型 | 第 III 型主動脈弓:頭臂動脈起點低於主動脈弓內緣。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/stenosis-grade | 1 | 狹窄小於 50% | 血管管徑狹窄小於 50%。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/stenosis-grade | 2 | 狹窄 50–99% | 血管管徑狹窄 50% 至 99%。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/stenosis-grade | 3 | 完全阻塞(100%) | 血管完全阻塞。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy | 1 | 只用抽吸導管 | 僅使用抽吸導管取栓(Aspiration catheter only)。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy | 2 | Solumbra(支架取栓器合併抽吸) | 同時使用支架取栓器與抽吸導管取栓(Solumbra 技術)。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy | 3 | 混合使用 | 混合使用不同取栓方式。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy | 4 | 先抽吸再救援 | 先抽吸取栓,再接續救援治療;此選項與代碼 1 至 3 分開記錄。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy | rescue-sr | 支架取栓器救援 | 抽吸未成功改用支架取栓器救援,對應抽吸救援原始選項 1。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy | rescue-aspiration | 抽吸救援 | 支架取栓未成功改用抽吸救援,對應支架取栓救援原始選項 1。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy | rescue-angioplasty | 血管成形術救援 | 以血管成形術救援。抽吸救援與支架取栓救援原始選項皆為 2。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy | rescue-thrombolysis | 血栓溶解救援 | 以血栓溶解治療救援。抽吸救援與支架取栓救援原始選項皆為 3。 | ||
http://vgh-stroke-ig.fhir.tw/CodeSystem/rescue-strategy | rescue-other | 其他救援方式 | 非上述救援方式,詳細內容另以文字記錄。抽吸救援與支架取栓救援原始選項皆為 4。 |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |