臺灣榮總腦中風實作指引（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/aspiration-strategy | Version: 0.1.0 | |||
| Draft as of 2026-10-07 | Computable Name: StrokeAspirationStrategyVS | |||
| Other Identifiers: OID:2.25.286826428408057775160058533856209912844 | ||||
此 ValueSet 收錄所有抽吸取栓策略代碼。
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://vgh-stroke-ig.fhir.tw/CodeSystem/aspiration-strategy version 📦0.1.0
Expansion performed internally based on codesystem 腦中風－抽吸取栓策略代碼 v0.1.0 (CodeSystem)
This value set contains 4 concepts
| System | Code | Display (en) | Definition | JSON | XML |
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 分開記錄。 |
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 |