台灣癌症登記長表實作指引 (Taiwan Cancer Registry Long Form Implementation Guide)
0.1.1 - ci-build
台灣癌症登記長表實作指引 (Taiwan Cancer Registry Long Form Implementation Guide) - Local Development build (v0.1.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://hapi.fhir.tw/fhir/ValueSet/lf-Laterality-valueset | Version: 0.1.1 | |||
| Active as of 2024-08-01 | Computable Name: LFLateralityVS | |||
Laterality Value Set
References
Generated Narrative: ValueSet lf-Laterality-valueset
https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem
Generated Narrative: ValueSet
Expansion based on codesystem 側性代碼系統 v0.1.1 (CodeSystem)
This value set contains 7 concepts
| Code | System | Display |
| 0 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 不是成對器官 |
| 1 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 原發起源位在右側 |
| 2 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 原發起源位在左側 |
| 3 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 成對器官，只有單側侵犯，但起源於左側或右側則不清楚 |
| 4 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 成對器官，雙側侵犯但起源之側位不清楚，且病歷描述是單一原發。較少見，如下：(1)雙側卵巢同時有單一組織類型之腫瘤侵犯 (2)雙側卵巢同時有相同或不同之epithelial組織型態(8000-8799)之腫瘤侵犯 (3)雙側同時有視網膜芽細胞瘤(retinoblastomas) (4)雙側同時有Wilm腫瘤(Wilm tumors) (5)雙側瀰漫性肺部結節 |
| 5 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 原發部位為以下部位且為身體中線的腫瘤：C700,C710-C714,C722-C725,C443,C445 |
| 9 | https://hapi.fhir.tw/fhir/CodeSystem/lf-Laterality-codesystem | 成對器官，但其側位不清楚 |
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 |