Generated Narrative: StructureDefinition LTCOperationOutcomeFeeAudit Name Flags Card. Type Description & Constraints OperationOutcome 0..* OperationOutcome 支付審核系統之申報檢核結果；API 交易層級之回覆結果代碼（rtncode）由 VS_TW_LTC_FeeAuditRtnCode（vs-tw-ltc-feeaudit-rtncode）表達，例：0 成功回傳、1 Request 輸入參數錯誤、40 查無資料、90 發生無法預期錯誤；本 Profile 之 issue 則表達個別服務紀錄之檢核錯誤（err_code／err_message） #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:caseNo S 0..1 string 核銷案號（case_no，最長 30 碼）；OperationOutcome 無 identifier 元素，故沿用既有 Extension ExtTWLTCExportCaseNo（Ext-TW-LTC-Export-CaseNo）承載案件編號，該 Extension 之 ^context 已涵蓋 OperationOutcome，於本 Profile 中其語意為支付審核系統之核銷案號 URL: http://ltc-ig.fhir.tw/StructureDefinition/Ext-TW-LTC-Export-CaseNo #xD; issue S 1..* BackboneElement 檢核錯誤項目；每一筆錯誤訊息（err_info／exception_records／delete_exception_records）對應一個 issue，同一筆服務紀錄有多筆錯誤時以多個 issue 表達 #xD; severity S 1..1 code 錯誤嚴重程度；因檢核未通過而導致該筆服務紀錄申報、分案或刪除失敗者，使用 error #xD; code S 1..1 code FHIR 問題類型代碼；欄位必填或長度／格式檢核（E1xxx、E2xxx）建議使用 required 或 value，資料查詢與寫入異常（E4xxx）建議使用 not-found 或 processing，審核規則與支付碼專屬檢核（E5xxx、EBA／EBC／ECB／EGA／EOT／ESC 系列）建議使用 business-rule #xD; details S 1..1 CodeableConcept 錯誤內容，承載回覆明細之錯誤碼（err_code，最長 5 碼）與錯誤原因（err_message，最長 200 字） #xD; coding S 1..1 Coding 錯誤碼（err_code），綁定支付審查錯誤代碼值集 VS_TW_LTC_FeeAuditErrorCode，例：E1001（服務紀錄識別碼不可空白）、E4015（單位已執行申報確認通知，不在受理新的服務紀錄申報）、E4032（此筆服務紀錄不存在） Binding: 支付審查－錯誤代碼 (extensible) #xD; text S 0..1 string 錯誤原因（err_message）之顯示文字 #xD; diagnostics S 0..1 string 錯誤原因原文或補充說明，可放回覆明細之 err_message 全文，或 API 層級之回覆訊息（errmsg）、批次處理結果（batch_proc_result）等敘述文字 #xD; expression S 0..* string 指向出錯的服務紀錄識別碼（objid），即 err_record.objid、exception_records.objid 或 delete_exception_records.objid。表述時須將實際的 objid 值寫入條件，方能唯一指出是哪一筆服務紀錄，例：Claim.identifier.where(system='http://ltc-ig.fhir.tw/identifier/feeaudit/objid' and value='882601914')；僅寫出路徑而未帶入 objid 值者無法定位錯誤來源 #xD; Documentation for this format
此 Profile 說明本 IG 如何進一步定義 FHIR 的 OperationOutcome Resource，以呈現衛生福利部支付審核系統（照管平台）回覆的服務紀錄檢核錯誤與 API 回覆結果代碼。適用情境包含：（1）「服務記錄申報」（FeeApply）之回覆明細中的錯誤服務記錄（err_record），每筆含識別碼（objid）與多筆錯誤訊息（err_info：err_code 錯誤碼、err_message 錯誤原因）；（2）「(查詢A) 申報結果查詢」回覆之分案異常資料（exception_records）與服務紀錄刪除失敗資料（delete_exception_records），其結構同為 objid、err_code、err_message；（3）API 交易層級之回覆結果代碼（rtncode）與回覆訊息（errmsg）。每一筆錯誤訊息（err_info）對應一個 OperationOutcome.issue。
支付審核系統之申報檢核結果；API 交易層級之回覆結果代碼（rtncode）由 VS_TW_LTC_FeeAuditRtnCode（vs-tw-ltc-feeaudit-rtncode）表達，例：0 成功回傳、1 Request 輸入參數錯誤、40 查無資料、90 發生無法預期錯誤；本 Profile 之 issue 則表達個別服務紀錄之檢核錯誤（err_code／err_message）
A collection of error, warning, or information messages that result from a system action.
Can result from the failure of a REST call or be part of the response message returned from a request message.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Grouping is handled through multiple repetitions from whatever context references the outcomes (no specific grouper required)
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
核銷案號（case_no，最長 30 碼）；OperationOutcome 無 identifier 元素，故沿用既有 Extension ExtTWLTCExportCaseNo（Ext-TW-LTC-Export-CaseNo）承載案件編號，該 Extension 之 ^context 已涵蓋 OperationOutcome，於本 Profile 中其語意為支付審核系統之核銷案號
此 Extension 用於表示長照 SDK 的案件編號（CASENO），適用於 Claim、CarePlan、Communication 或 OperationOutcome 資源。
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
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.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
檢核錯誤項目；每一筆錯誤訊息（err_info／exception_records／delete_exception_records）對應一個 issue，同一筆服務紀錄有多筆錯誤時以多個 issue 表達
An error, warning, or information message that results from a system action.
AcknowledgementDetail or Observation[classCode="ALRT" and moodCode="EVN"]
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Additional content defined by implementations
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.
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
錯誤嚴重程度；因檢核未通過而導致該筆服務紀錄申報、分案或刪除失敗者，使用 error
Indicates whether the issue indicates a variation from successful processing.
This is labeled as "Is Modifier" because applications should not confuse hints and warnings with errors.
Indicates how relevant the issue is to the overall success of the action.
How the issue affects the success of the action.
./typeCode[parent::AcknowledgmentDetail] or unique(./inboundRelationship[parent::Observation and typeCode='SUBJ' and isNormalActRelationship()]/source[classCode="OBS" and moodCode="EVN" and implies(code, ActCode#SEV and isNormalAct())/value[xsi:type="CD"]
FHIR 問題類型代碼；欄位必填或長度／格式檢核（E1xxx、E2xxx）建議使用 required 或 value，資料查詢與寫入異常（E4xxx）建議使用 not-found 或 processing，審核規則與支付碼專屬檢核（E5xxx、EBA／EBC／ECB／EGA／EOT／ESC 系列）建議使用 business-rule
Describes the type of the issue. The system that creates an OperationOutcome SHALL choose the most applicable code from the IssueType value set, and may additional provide its own code for the error in the details element.
Expresses the issue in a human and computer-friendly way, allowing the requesting system to behave differently based on the type of issue. The required element provides a base level of computable interoperability across all systems for processing an outcome, allowing systems to respond appropriately regardless of the internal system error codes returned.
A code that describes the type of issue.
錯誤內容，承載回覆明細之錯誤碼（err_code，最長 5 碼）與錯誤原因（err_message，最長 200 字）
Additional details about the error. This may be a text description of the error or a system code that identifies the error.
A human readable description of the error issue SHOULD be placed in details.text.
A code that provides details as the exact issue.
Extensions are always sliced by (at least) url
錯誤碼（err_code），綁定支付審查錯誤代碼值集 VS_TW_LTC_FeeAuditErrorCode，例：E1001（服務紀錄識別碼不可空白）、E4015（單位已執行申報確認通知，不在受理新的服務紀錄申報）、E4032（此筆服務紀錄不存在）
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.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
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.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
錯誤原因原文或補充說明，可放回覆明細之 err_message 全文，或 API 層級之回覆訊息（errmsg）、批次處理結果（batch_proc_result）等敘述文字
Additional diagnostic information about the issue.
This may be a description of how a value is erroneous, a stack dump to help trace the issue or other troubleshooting information.
Deprecated: Path of element(s) related to issue
This element is deprecated because it is XML specific. It is replaced by issue.expression, which is format independent, and simpler to parse. For resource issues, this will be a simple XPath limited to element names, repetition indicators and the default child accessor that identifies one of the elements in the resource that caused this issue to be raised. For HTTP errors, will be "http." + the parameter name.
The root of the XPath is the resource or bundle that generated OperationOutcome. Each XPath SHALL resolve to a single node. This element is deprecated, and is being replaced by expression.
Allows systems to highlight or otherwise guide users to elements implicated in issues to allow them to be fixed more easily.
指向出錯的服務紀錄識別碼（objid），即 err_record.objid、exception_records.objid 或 delete_exception_records.objid。表述時須將實際的 objid 值寫入條件，方能唯一指出是哪一筆服務紀錄，例：Claim.identifier.where(system='http://ltc-ig.fhir.tw/identifier/feeaudit/objid' and value='882601914')；僅寫出路徑而未帶入 objid 值者無法定位錯誤來源
A [simple subset of FHIRPath](http://hl7.org/fhir/R4/fhirpath.html#simple) limited to element names, repetition indicators and the default child accessor that identifies one of the elements in the resource that caused this issue to be raised.
The root of the FHIRPath is the resource or bundle that generated OperationOutcome. Each FHIRPath SHALL resolve to a single node.