## Intersection of https://nhicore.nhi.gov.tw/pas/StructureDefinition/DiagnosticReport-twpas and https://nhicore.nhi.gov.tw/pas/StructureDefinition/DiagnosticReport-twpas

This is the set of resources that conform to both 檢查報告-DiagnosticReport TWPAS (https://nhicore.nhi.gov.tw/pas/StructureDefinition/DiagnosticReport-twpas) and 檢查報告-DiagnosticReport TWPAS (https://nhicore.nhi.gov.tw/pas/StructureDefinition/DiagnosticReport-twpas).

### Structure

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
DiagnosticReport |  | 0..* |  | A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports
meta | Σ | 1..1 | Meta | Metadata about the resource
extension |  | 0..* | Extension | Additional content defined by implementations
versionId | Σ | 0..1 | id | Version specific identifier
lastUpdated | Σ | 0..1 | instant | When the resource version last changed
source | Σ | 0..1 | uri | Identifies where the resource comes from
profile | Σ | 1..1 | canonical(StructureDefinition) | Profiles this resource claims to conform to
security | Σ | 0..* | Coding | Security Labels applied to this resource Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
tag | Σ | 0..* | Coding | Tags applied to this resource Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created
language |  | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
text |  | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements
contained |  | 0..* | Resource | Contained, inline Resources
extension |  | 0..* | Extension | Additional content defined by implementations
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
identifier | Σ | 0..* | Identifier | Business identifier for report
basedOn |  | 0..* | Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | What was requested
status | ?!Σ | 1..1 | code | registered | partial | preliminary | final + Binding: ?? (required): The status of the diagnostic report.
category | Σ | 1..1 | CodeableConcept | Service category Binding: ?? (example): Codes for diagnostic service sections.
extension |  | 0..* | Extension | Additional content defined by implementations
coding | Σ | 1..1 | Coding | Code defined by a terminology system
text | Σ | 0..1 | string | Plain text representation of the concept
code | Σ C | 1..1 | CodeableConcept | 報告類型，當LOINC無法具體描述檢體種類（例如：`47526-9`時），請填寫及補充說明檢體種類(code.text)。 Binding: ?? (extensible): 最新參考代碼清單請參考[此檔案]。 Constraints: speType
extension |  | 0..* | Extension | Additional content defined by implementations
coding | Σ | 1..1 | Coding | Code defined by a terminology system
extension |  | 0..* | Extension | Additional content defined by implementations
system | Σ | 1..1 | uri | Identity of the terminology system
version | Σ | 0..1 | string | Version of the system - if relevant
code | Σ | 1..1 | code | Symbol in syntax defined by the system
display | Σ | 0..1 | string | Representation defined by the system
userSelected | Σ | 0..1 | boolean | If this coding was chosen directly by the user
text | Σ | 0..1 | string | 檢體種類
subject | Σ | 1..1 | Reference(病人資訊-Patient TWPAS | #sd-Patient-twpas-Patient-twpas) | The subject of the report - usually, but not always, the patient
encounter | Σ | 0..1 | Reference(Encounter) | Health care event when test ordered
effective[x] | S Σ | 1..1 | dateTime | 報告日期，YYYY-MM-DD
issued | Σ | 0..1 | instant | DateTime this version was made
performer | S Σ | 1..1 | Reference(醫事人員-Practitioner TWPAS | #sd-Practitioner-twpas-Practitioner-twpas) | 檢查報告醫師
resultsInterpreter | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) | Primary result interpreter
specimen |  | 0..* | Reference(Specimen) | Specimens this report is based on
result |  | 0..* | Reference(Observation) | Observations
imagingStudy |  | 0..* | Reference(ImagingStudy) | Reference to full details of imaging associated with the diagnostic report
media | Σ | 0..* | BackboneElement | Key images associated with this report
extension |  | 0..* | Extension | Additional content defined by implementations
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
comment |  | 0..1 | string | Comment about the image (e.g. explanation)
link | Σ | 1..1 | Reference(Media) | Reference to the image source
conclusion | S | 1..1 | string | 報告結果-文數字，請勿將醫事機構名稱、病人及醫師姓名等資訊列入結果中上傳，且不得包含HTML或XML等語法。
conclusionCode |  | 0..* | CodeableConcept | Codes for the clinical conclusion of test results Binding: ?? (example): Diagnosis codes provided as adjuncts to the report.
presentedForm | S C | 0..* | Attachment | 報告結果-MIMEType Constraints: UploadContent
extension |  | 0..* | Extension | Additional content defined by implementations
contentType | S Σ | 1..1 | code | Mime type of the content, with charset etc. Binding: ?? (required): The mime type of an attachment. Any valid mime type is allowed. Example General: text/plain; charset=UTF-8, image/png
language | Σ | 0..1 | code | Human language of the content (BCP-47) Binding: ?? (preferred): A human language.
Additional Bindings | Purpose
?? | Max Binding
Example General: en-AU
data |  | 0..1 | base64Binary | Data inline, base64ed
url | S Σ | 1..1 | url | 檢查報告（請填寫完整檔案路徑） Example General: http://www.acme.com/logo-small.png Example General: file://PathologyReport01.pdf
size | Σ | 0..1 | unsignedInt | Number of bytes of content (if url provided)
hash | Σ | 0..1 | base64Binary | Hash of the data (sha-1, base64ed)
title | S Σ | 0..1 | string | 檢查報告名稱 Example General: Official Corporate Logo
creation | Σ | 0..1 | dateTime | Date attachment was first created
Documentation for this format