DICOM影像檢查中產生的內容。每項檢查包含若干系列(series)，每一系列只使用一種影像儀器（例如X光、電腦斷層掃描CT、核磁共振MR、超音波等），每個系列由在相同背景下獲得或製作的服務-物件對實例（Service-Object Pair Instances，簡稱SOP實例，包含影像或其他類型的資料）所組成。但一項檢查中可能包括多個使用不同影像儀器的系列。

構建resource時遵循的一系列規則的參照，在處理內容時必須理解這些規則。通常這是對IG所定義之特殊規則及其他profiles的參照。

宣告這套規則限制了內容只能被有限的交易夥伴所理解。這從本質上限制了資料的長期有用性。然而，現有的健康生態體系高度分裂，還沒有準備好以普遍可計算的方式定義、收集和交換資料。只要有可能，實作者和/或規範編寫者應該避免使用這個資料項目。通常在使用時，此URL是對IG的參照，此IG將這些特殊規則與其他profiles、value sets等一起定義為其敘述的一部分。

可以用來表示不屬於此resource的基本定義的額外資訊，並修改包含它所內嵌（contained）的資料項目的理解和/或對包含資料項目之後續使用的理解。通常修飾用的資料項目提供否定或限定的資訊。為了使擴充的使用安全和可管理，對擴充的定義和使用有一套嚴格的管理。雖然任何實作者都可以定義一個擴充，但在定義擴充時 必須（SHALL） 滿足一組要求。處理resource的應用程式需要檢查修飾用的擴充資料項目。
修飾用的擴充資料項目 必須沒有（SHALL NOT） 改變resource或DomainResource上任何資料項目的含義（包括不能改變modifierExtension本身的含義）。

任何應用程式、專案或標準使用擴充時，都不應該帶有任何負面的聯想。使用擴充是允許FHIR規範為每個人保留一個核心的簡易性。

修飾用的資料項目擴充允許將不能安全地忽略的擴充，與絕大多數可以安全地忽略的擴充明確區分開來。這樣做有助於促進可互操作性，因為無需禁止實作者使用擴充，想要瞭解更多資訊，請參見[修飾用的資料項目擴充之定義]（http://hl7.org/fhir/R4/extensibility.html#modifierExtension）。

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

影像檢查的當前狀態。

「未知」並不意味著「其他」類型；必須符合已確定的某種狀態。當創建系統不確定當前狀態時，會使用「未知」這一選項。

影像檢查的當前狀態；應填入所綁定值集中的其中一個代碼。

列出所有系列中用於實際影像獲取的儀器類型，即在DICOM Context Group 29（值集的唯一識別碼為1.2.840.10008.6.1.19）中定義的類型。

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

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

影像檢查的對象，通常是病人。

影像檢查的對象，若為品質保證的標準對照物（QA幻影）可用 Device 作記錄。若其檢查對象是多隻小動物（如多隻老鼠），則可以將它們作為 Group 來進行記錄。

檢查開始的日期和時間

提供影像檢查資料存取的網路服務，包括查詢、觀看或下載影像檢查資料。更多有關如何使用DICOM端點的詳細資訊，請查看實作指引。整體檢查的網絡連接設定（端點）適用於檢查中的每一個影像系列。但如果某個影像系列有自己特定的網路連接設定(稱為系統端點)，且這個設定的類型（Endpoint.connectionType）與整體檢查的端點相同，則該系列將依據其自身的設定進行連接。

常見的端點類型包括：DICOM WADO-RS，它透過RESTful API以原始或轉換後的格式（如JPG、PNG）來查DICOM影像檔案；DICOM WADO-URI，這也能查詢原始或轉換後的影像，但它是透過HTTP查詢方式實現；DICOM QIDO-RS，它允許使用RESTful查詢方式來獲取DICOM資訊，而無需下載影像檔案本身；還有IHE Invoke Image Display（IID），這是一種標準的網路影像查看器(viewer)啟動方式。

說明了如何查看（例如：使用IHE的IID profile）或查詢（例如：使用DICOM的WADO-URI和WADO-RS）影像檢查、其影像系列或單個影像的方法。整體檢查的基礎位置設定（baseLocation）通常適用於檢查中的所有影像系列。但如果某個影像系列有自己的基礎位置設定（稱為系列級baseLocation），且這個設定與整體檢查的設定類型相同，則該系列將按照自己的設定進行操作。

在醫學影像檢查中，顯示的series數量有時會比Resource實際包含的更多。這可能是由於Resource的限制、安全問題或其他因素所致。如果Resource中包含至少一個series的資料項目，那麼這個series數量就應當被明確標出。

在醫學影像檢查中，顯示的SOP instances數量有時會比Resource實際包含的更多。這可能是由於instance的限制、安全問題或其他因素所致。如果Resource中包含至少一個instance的資料項目，那麼這個資料項目就應該被包含在內。

執行的處置類型代碼

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

此資料項目為可擴充綁定預設國際標準值集，但實作者可視實務專案需求只綁定以下slices中的任一值集。目前未只限定綁定預設值集是因為尚無slice值集與預設國際標準值集的代碼對應表，待後續有相對的代碼對應表後將建議採用國際標準值集作為唯一綁定值集並針對該值集進行擴充與管理，以利進行跨國與跨系統之資料交換。

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

代碼可以在列舉清單（enumerations）或代碼清單（code lists）中非常隨意地定義，直至有非常正式的定義，例如：SNOMED CT—更多資訊見HL7 v3核心原則（Core Principles ）。編碼的排序是未定義的因而 必須沒有（SHALL NOT） 被用來推斷意義。一般來說，最多只有一個編碼值（coding values）會被標記為UserSelected = true。

允許代碼系統中的替代編碼，以及翻譯到其他編碼系統。

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

代碼可以在列舉清單（enumerations）或代碼清單（code lists）中非常隨意地定義，直至有非常正式的定義，如SNOMED CT—更多資訊見HL7 v3核心原則（Core Principles ）。編碼的排序是未定義的因而 必須沒有（SHALL NOT） 被用來推斷意義。一般來說，最多只有一個編碼值（coding values）會被標記為UserSelected = true。

允許代碼系統中的替代編碼，以及翻譯到其他編碼系統。

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

代碼可以在列舉清單（enumerations）或代碼清單（code lists）中非常隨意地定義，直至有非常正式的定義，例如：SNOMED CT—更多資訊見HL7 v3核心原則（Core Principles ）。編碼的排序是未定義的因而 必須沒有（SHALL NOT） 被用來推斷意義。一般來說，最多只有一個編碼值（coding values）會被標記為UserSelected = true。

允許代碼系統中的替代編碼，以及翻譯到其他編碼系統。

定義代碼中符號意義的代碼系統識別

URI可以是一個OID（urn:oid:...）或一個UUID（urn:uuid:...）；OID和UUID 必須(SHALL) 參照HL7 OID註冊中心；否則，URI應該來自HL7的FHIR定義的特殊URI列表，或者它應該參照一些明確建立的系统定義。

需要明確說明符號定義的來源

系統定義的語法之符號；符號可能是一個預先定義的代碼，也可能是代碼系統定義的語法中的表達式（如後組合配對／後組合式）。

需要參照系統中的一個特定代碼

遵循系統的規則以呈現代碼含義的表示法

需要能為不了解此系統的讀者呈現可讀的代碼含義

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

代碼可以在列舉清單（enumerations）或代碼清單（code lists）中非常隨意地定義，直至有非常正式的定義，例如：SNOMED CT—更多資訊見HL7 v3核心原則（Core Principles ）。編碼的排序是未定義的因而 必須沒有（SHALL NOT） 被用來推斷意義。一般來說，最多只有一個編碼值（coding values）會被標記為UserSelected = true。

允許代碼系統中的替代編碼，以及翻譯到其他編碼系統。

輸入資料的使用者所見／所選／所說的人類可讀文字表述，和（或）其代表使用者的預期含義。

很多時候，此文字表述與其中一個代碼的顯示名稱相同。

專門術語中的代碼並不總是能捕捉人類使用的細微差別的正確意義，或者根本就沒有合適的代碼；這些情況下，文字表述被用來捕捉來源的全部意義。

說明為什麼要求進行影像檢查的臨床情況

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

應填入所綁定值集中適合的代碼，確定無適合的代碼才可以使用其他值集的代碼來表示。

這表示有另外一個Resource，其存在是進行這項檢查的合理原因。

影像管理員(Imaging Manager)對此影像檢查的描述，它是由醫療機構自己生成的，用來描述或分類此影像檢查（元件）的內容。

每項影像檢查有一個或多個系列的影像或其他內容

可以用來表示不屬於資料項目的基本定義的附加資訊，並且修改對它所內嵌（contained）的資料項目的理解和（或）對包含資料項目之後續使用的理解。通常，修飾用的資料項目提供否定或限定。為了使擴充的使用安全和可管理，對擴充的定義和使用有一套嚴格的管理。儘管任何實作者都可以定義一個擴充，但作為擴充定義的一部分，有一套要求 必須（SHALL） 滿足。處理resource的應用程式被要求檢查修飾用的擴充資料項目。 修飾用的擴充資料項目 必須沒有（SHALL NOT） 改變resource或DomainResource上任何資料項目的含義（包括不能改變modifierExtension本身的含義）。

無論使用或定義擴充的機構或管轄區，任何應用程式、專案或標準使用擴充都不背負任何汙名（stigma）。使用擴充是允許FHIR規範為每個人保留一個核心的簡易性。

修飾用的資料項目擴充將不能安全地忽略的擴充與絕大多數可以安全地忽略的擴充明確區分開來。透過消除禁止實作者擴充存在的需求來促進可互通性。更多訊息，請參見修飾用的資料項目擴充之定義。

此系列的DICOM系列實例UID

見DICOM PS3.3 C.7.3

此系列的DICOM系列實例UID

此影像檢查中此系列的數字識別碼

此系列序列所使用的成像儀器

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

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

對此系列的描述

在醫學影像檢查中，顯示的SOP instances數量有時會比Resource實際包含的更多。這可能是由於instance的限制、安全問題或其他因素所致。如果Resource中包含至少一個instance的資料項目，那麼這個資料項目就應該被包含在內。

提供影像檢查資料存取的網路服務，包括查詢、觀看或下載影像檢查資料。更多有關如何使用DICOM端點的詳細資訊，請查看實作指引。整體檢查的網絡連接設定（端點）適用於檢查中的每一個影像系列。但如果某個影像系列有自己特定的網路連接設定(稱為系統端點)，且這個設定的類型（Endpoint.connectionType）與整體檢查的端點相同，則該系列將依據其自身的設定進行連接。

常見的端點類型包括：DICOM WADO-RS，它透過RESTful API以原始或轉換後的格式（如JPG、PNG）來查DICOM影像檔案；DICOM WADO-URI，這也能查詢原始或轉換後的影像，但它是透過HTTP查詢方式實現；DICOM QIDO-RS，它允許使用RESTful查詢方式來獲取DICOM資訊，而無需下載影像檔案本身；還有IHE Invoke Image Display（IID），這是一種標準的網路影像查看器(viewer)啟動方式。

說明了如何查詢（例如：使用DICOM的WADO-URI和WADO-RS）其影像系列或單個系列的方法。整體檢查的基礎位置設定（baseLocation）通常適用於檢查中的所有影像系列。但如果某個影像系列有自己的基礎位置設定（稱為系列級baseLocation），且這個設定與整體檢查的設定類型相同，則該系列將按照自己的設定進行操作。

所檢查的解剖結構。參見DICOM第16部分附件L（http://dicom.nema.org/medical/dicom/current/output/chtml/part16/chapter_L.html），瞭解DICOM與SNOMED-CT的對應關係。bodySite可指示成像的身體部位的橫向性；如果是這樣，它應與ImagingStudy.series.siderality的任何內容一致。

應填入所綁定值集中適合的代碼，確定無適合的代碼才可以使用其他值集的代碼來表示。

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of the system.

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

要進行影像檢查的檢體，例如：活體組織切片的整片掃描成像的檢體。

此系列開始的日期和時間

系列中的單一SOP實例，例如：影像或表現狀態。

可以用來表示不屬於資料項目的基本定義的附加資訊，並且修改對它所內嵌（contained）的資料項目的理解和（或）對包含資料項目之後續使用的理解。通常，修飾用的資料項目提供否定或限定。為了使擴充的使用安全和可管理，對擴充的定義和使用有一套嚴格的管理。儘管任何實作者都可以定義一個擴充，但作為擴充定義的一部分，有一套要求 必須（SHALL） 滿足。處理resource的應用程式被要求檢查修飾用的擴充資料項目。 修飾用的擴充資料項目 必須沒有（SHALL NOT） 改變resource或DomainResource上任何資料項目的含義（包括不能改變modifierExtension本身的含義）。

無論使用或定義擴充的機構或管轄區，任何應用程式、專案或標準使用擴充都不背負任何汙名（stigma）。使用擴充是允許FHIR規範為每個人保留一個核心的簡易性。

修飾用的資料項目擴充將不能安全地忽略的擴充與絕大多數可以安全地忽略的擴充明確區分開來。透過消除禁止實作者擴充存在的需求來促進可互通性。更多訊息，請參見修飾用的資料項目擴充之定義。

此影像或其他DICOM內容的DICOM SOP實例UID

見DICOM PS3.3 C.12.1

DICOM SOP實例的UID

DICOM實例類型

此系列中該實例的序號

DICOM影像檢查中產生的內容。每項檢查包含若干系列(series)，每一系列只使用一種影像儀器（例如X光、電腦斷層掃描CT、核磁共振MR、超音波等），每個系列由在相同背景下獲得或製作的服務-物件對實例（Service-Object Pair Instances，簡稱SOP實例，包含影像或其他類型的資料）所組成。但一項檢查中可能包括多個使用不同影像儀器的系列。

resource的邏輯ID，在resource的URL中使用。一旦指定，這個值永遠不會改變。

一個resource使用新增操作（create operation）提交給伺服器時，此resource沒有id，它的id在resource被創建後由伺器分配/指定。

關於resource的metadata。這是由基礎建設維護的內容。內容的更改可能並不總是與resource的版本更改相關聯。

構建resource時遵循的一系列規則的參照，在處理內容時必須理解這些規則。通常這是對IG所定義之特殊規則及其他profiles的參照。

宣告這套規則限制了內容只能被有限的交易夥伴所理解。這從本質上限制了資料的長期有用性。然而，現有的健康生態體系高度分裂，還沒有準備好以普遍可計算的方式定義、收集和交換資料。只要有可能，實作者和/或規範編寫者應該避免使用這個資料項目。通常在使用時，此URL是對IG的參照，此IG將這些特殊規則與其他profiles、value sets等一起定義為其敘述的一部分。

編寫此resource的語言

提供語言是為了支援索引和可存取性（通常，文字表述轉語音等服務使用此語言標籤）。html lanuage tag適用於此敘述。resource上的語言標籤可用於指定從resource中的資料所產成的其他表述之語言。不是所有的內容都必須使用此語言。不應該假定Resource.language自動適用於敘述。如果指定語言，它也應該被指定在html中的div資料項目（關於xml:lang和html lang屬性之間的關係，見HTML5中的規則）。

人類語言；鼓勵使用CommonLanguages代碼表中的代碼，但不強制一定要使用此代碼表，你也可使用其他代碼表的代碼或單純以文字表示。

人可讀的敘述，包含resource的摘要，可用於向人表述resource的內容。敘述不需要對所有的結構化資料進行編碼，但需要包含足夠的細節使人在閱讀敘述時理解「臨床安全性」。resource定義有哪些內容應該在敘述中表示，以確保臨床安全。

內嵌（contained）的resource沒有敘述，非內嵌（contained）的resource則**建議應該（SHOULD）**有敘述。有時resource可能只有文字表述，很少或沒有額外的結構化資料（只要滿足所有minOccurs=1的資料項目）。這可能出現在舊系統的資料，當資訊以 「文字表述區塊（text blob） 」的形式被取得，或者文字表述是原始輸入或說明，而編碼資訊稍後再添加。

這些resource內嵌（contains）的resource不會另外存於任何FHIR伺服器，意即它們無法在任何FHIR伺服器中被找到，也無法有自己獨立的資料異動／交易（transaction）範圍。

當內容可以從任何FHIR伺服器找到時，不應該以內嵌（contained）resource的方式呈現，因為一旦失去識別，再次恢復它是非常困難的（並且取決於情境）。內嵌（contained）的resource可在它們的meta資料項目中表述profiles和tag，但不應該有安全標號（security labels）。

可用於表示不屬於此resource基本定義的額外資訊。為了擴充的使用安全和可管理，對擴充的定義和使用有一套嚴格的管理。儘管任何實作者都可以定義一個擴充，但作為擴充定義的一部分，必須（SHALL） 滿足一系列要求。

任何應用程式、專案或標準使用擴充時，都不應該帶有任何負面的聯想。使用擴充是允許FHIR規範為每個人保留一個核心的簡易性。

可以用來表示不屬於此resource的基本定義的額外資訊，並修改包含它所內嵌（contained）的資料項目的理解和/或對包含資料項目之後續使用的理解。通常修飾用的資料項目提供否定或限定的資訊。為了使擴充的使用安全和可管理，對擴充的定義和使用有一套嚴格的管理。雖然任何實作者都可以定義一個擴充，但在定義擴充時 必須（SHALL） 滿足一組要求。處理resource的應用程式需要檢查修飾用的擴充資料項目。
修飾用的擴充資料項目 必須沒有（SHALL NOT） 改變resource或DomainResource上任何資料項目的含義（包括不能改變modifierExtension本身的含義）。

任何應用程式、專案或標準使用擴充時，都不應該帶有任何負面的聯想。使用擴充是允許FHIR規範為每個人保留一個核心的簡易性。

修飾用的資料項目擴充允許將不能安全地忽略的擴充，與絕大多數可以安全地忽略的擴充明確區分開來。這樣做有助於促進可互操作性，因為無需禁止實作者使用擴充，想要瞭解更多資訊，請參見[修飾用的資料項目擴充之定義]（http://hl7.org/fhir/R4/extensibility.html#modifierExtension）。

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

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.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

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.

A reference to a code defined by a 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.

The identification of the code system that defines the meaning of the symbol in the code.

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.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of 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.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

ImagingStudy的識別碼，如DICOM檢查實例UID (Study Instance UID)和檢查單號(Accession Number)。

有關DICOM檢查實例UID的編碼，請參閱「影像檢查實作說明(Imaging Study Implementation Notes)」下的討論。檢查單號(Accession Number)應使用ACSN識別碼類型 (Identifier type)。

如果此 ImagingStudy 中存在一個或多個 series 資料項目，那麼就應該有一個DICOM Study UID識別碼（見DICOM PS 3.3 C.7.2 .

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.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

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.

A reference to a code defined by a 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.

The identification of the code system that defines the meaning of the symbol in the code.

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.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of 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.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

影像檢查的當前狀態。

「未知」並不意味著「其他」類型；必須符合已確定的某種狀態。當創建系統不確定當前狀態時，會使用「未知」這一選項。

影像檢查的當前狀態；應填入所綁定值集中的其中一個代碼。

列出所有系列中用於實際影像獲取的儀器類型，即在DICOM Context Group 29（值集的唯一識別碼為1.2.840.10008.6.1.19）中定義的類型。

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.

The identification of the code system that defines the meaning of the symbol in the code.

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.

A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).

Need to refer to a particular code in the system.

A representation of the meaning of the code in the system, following the rules of 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.

影像檢查的對象，通常是病人。

影像檢查的對象，若為品質保證的標準對照物（QA幻影）可用 Device 作記錄。若其檢查對象是多隻小動物（如多隻老鼠），則可以將它們作為 Group 來進行記錄。

進行此影像檢查的健康照護事件（例如：病人與健康照護服務提供者的互動）。

病人接受影像檢查時所在的就醫情境。不過，有些相關事件可能在病人就醫前或完成就醫後發生，但這些事件仍與就醫情境有關（例如：病人入院前的檢查）。

檢查開始的日期和時間

導致進行此影像檢查的診斷報告清單

支援分組處置（一項影像檢查支援多個醫令處置，如胸腔/腹部/骨盆CT）。

請求/轉診的醫師

誰閱讀了檢查報告並解讀了影像或其他內容

提供影像檢查資料存取的網路服務，包括查詢、觀看或下載影像檢查資料。更多有關如何使用DICOM端點的詳細資訊，請查看實作指引。整體檢查的網絡連接設定（端點）適用於檢查中的每一個影像系列。但如果某個影像系列有自己特定的網路連接設定(稱為系統端點)，且這個設定的類型（Endpoint.connectionType）與整體檢查的端點相同，則該系列將依據其自身的設定進行連接。

常見的端點類型包括：DICOM WADO-RS，它透過RESTful API以原始或轉換後的格式（如JPG、PNG）來查DICOM影像檔案；DICOM WADO-URI，這也能查詢原始或轉換後的影像，但它是透過HTTP查詢方式實現；DICOM QIDO-RS，它允許使用RESTful查詢方式來獲取DICOM資訊，而無需下載影像檔案本身；還有IHE Invoke Image Display（IID），這是一種標準的網路影像查看器(viewer)啟動方式。

說明了如何查看（例如：使用IHE的IID profile）或查詢（例如：使用DICOM的WADO-URI和WADO-RS）影像檢查、其影像系列或單個影像的方法。整體檢查的基礎位置設定（baseLocation）通常適用於檢查中的所有影像系列。但如果某個影像系列有自己的基礎位置設定（稱為系列級baseLocation），且這個設定與整體檢查的設定類型相同，則該系列將按照自己的設定進行操作。

在醫學影像檢查中，顯示的series數量有時會比Resource實際包含的更多。這可能是由於Resource的限制、安全問題或其他因素所致。如果Resource中包含至少一個series的資料項目，那麼這個series數量就應當被明確標出。

在醫學影像檢查中，顯示的SOP instances數量有時會比Resource實際包含的更多。這可能是由於instance的限制、安全問題或其他因素所致。如果Resource中包含至少一個instance的資料項目，那麼這個資料項目就應該被包含在內。

此影像檢查是此處置(Procedure)的一部分

執行的處置類型代碼

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

此資料項目為可擴充綁定預設國際標準值集，但實作者可視實務專案需求只綁定以下slices中的任一值集。目前未只限定綁定預設值集是因為尚無slice值集與預設國際標準值集的代碼對應表，待後續有相對的代碼對應表後將建議採用國際標準值集作為唯一綁定值集並針對該值集進行擴充與管理，以利進行跨國與跨系統之資料交換。

resource中資料項目的唯一ID（用於內部參照）。這可以是任何不含空格的字串。

擴充的資料項目