在申報醫院的首次療程中，進行特殊放射治療所使用的技術

其他放射治療技術

其他放射治療技術應填入其他放射治療技術-通用編碼值集、其他放射治療技術-放射手術專用編碼值集、其他放射治療技術-近距放射治療專用編碼值集、其他放射治療技術-放射線同位素治療專用編碼值集、其他放射治療技術-質子或其他帶電荷粒子治療專用編碼值集、其他放射治療技術-硼捉中子治療專用編碼值集值集中適合的代碼。

由專門術語系統（terminology system）所定義之代碼的參照

專門術語系統(terminology system)的識別

系統定義的語法之符號

代碼系統定義的表示法

在申報醫院的首次療程中，進行特殊放射治療所使用的技術

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

其他放射治療技術

其他放射治療技術應填入其他放射治療技術-通用編碼值集、其他放射治療技術-放射手術專用編碼值集、其他放射治療技術-近距放射治療專用編碼值集、其他放射治療技術-放射線同位素治療專用編碼值集、其他放射治療技術-質子或其他帶電荷粒子治療專用編碼值集、其他放射治療技術-硼捉中子治療專用編碼值集值集中適合的代碼。

由專門術語系統（terminology system）所定義之代碼的參照

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

專門術語系統(terminology system)的識別

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

系統定義的語法之符號

Need to refer to a particular code in the system.

代碼系統定義的表示法

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

在申報醫院的首次療程中，進行特殊放射治療所使用的技術

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

其他放射治療技術

其他放射治療技術應填入其他放射治療技術-通用編碼值集、其他放射治療技術-放射手術專用編碼值集、其他放射治療技術-近距放射治療專用編碼值集、其他放射治療技術-放射線同位素治療專用編碼值集、其他放射治療技術-質子或其他帶電荷粒子治療專用編碼值集、其他放射治療技術-硼捉中子治療專用編碼值集值集中適合的代碼。

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

由專門術語系統（terminology system）所定義之代碼的參照

Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.

Allows for alternative encodings within a code system, and translations to other code systems.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

專門術語系統(terminology system)的識別

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

系統定義的語法之符號

Need to refer to a particular code in the system.

代碼系統定義的表示法

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.