{
"resourceType": "StructureDefinition",
"url": "http://jpfhir.jp/fhir/core/StructureDefinition/JP_DiagnosticReport_LabResult",
"version": "1.0.0",
"name": "JPCoreDiagnosticReportLabResultProfile",
"title": "JP Core DiagnosticReport LabResult Profile",
"status": "active",
"publisher": "FHIR® Japanese implementation research working group in Japan Association of Medical Informatics (JAMI)",
"description": "このプロファイルはDiagnosticReportリソースに対して、検体検査結果のデータを送受信するための制約と拡張を定めたものである。",
"copyright": "FHIR® Japanese implementation research working group in Japan Association of Medical Informatics (JAMI)",
"fhirVersion": "4.0.1",
"mapping": [
{
"identity": "workflow",
"uri": "http://hl7.org/fhir/workflow",
"name": "Workflow Pattern"
},
{
"identity": "v2",
"uri": "http://hl7.org/v2",
"name": "HL7 v2 Mapping"
},
{
"identity": "rim",
"uri": "http://hl7.org/v3",
"name": "RIM Mapping"
},
{
"identity": "w5",
"uri": "http://hl7.org/fhir/fivews",
"name": "FiveWs Pattern Mapping"
}
],
"kind": "resource",
"abstract": false,
"type": "DiagnosticReport",
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"derivation": "constraint",
"differential": {
"element": [
{
"id": "DiagnosticReport.identifier",
"path": "DiagnosticReport.identifier",
"comment": "Usually assigned by the Information System of the diagnostic service provider (filler id).\r\n\r\n【JP仕様】
\r\n検体検査結果の場合、「依頼者オーダ番号(ORC-2)」だけで十分
\r\n・複数の容器で1つの結果のまとまり
\r\n・容器ごとに結果が出るタイミングはずれる
\r\n・オーダ側でオーダ番号が1つにまとまるか別になるかは有り得る
"
},
{
"id": "DiagnosticReport.basedOn",
"path": "DiagnosticReport.basedOn",
"comment": "Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports.\r\n\r\n【JP仕様】
\r\nServiceRequestリソースを参照(ObservationLabresultと同様）
"
},
{
"id": "DiagnosticReport.status",
"path": "DiagnosticReport.status",
"comment": "Note that FHIR strings SHALL NOT exceed 1MB in size\r\n\r\n【JP仕様】
\r\n有れば：ORC-5
\r\nもしくは
\r\n無ければ：OBR-25(\"F\")のAND結果
\r\n 例：全部\"F\"なら\"F\"、それ以外の場合は要検討
\r\n設定する値は、DiagnosticReportStatus（コード）から1つ選ぶ
\r\nコード体系：HL7 Table 0038のコードと定義
"
},
{
"id": "DiagnosticReport.category",
"path": "DiagnosticReport.category",
"comment": "Multiple categories are allowed using various categorization schemes. The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code.\r\n\r\n【JP仕様】
\r\nDiagnostic Service Section Codesの\"LAB\"を使用
"
},
{
"id": "DiagnosticReport.code",
"path": "DiagnosticReport.code",
"comment": "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.\r\n\r\n【JP仕様】
\r\nLOINCの臨床検査の分類コードを割り当てる。
\r\n検査レポートの利用用途に合わせて、JLAC10のコードを振っても良い。
"
},
{
"id": "DiagnosticReport.subject",
"path": "DiagnosticReport.subject",
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.\r\n\r\n【JP仕様】
\r\nPatientリソースを参照
"
},
{
"id": "DiagnosticReport.encounter",
"path": "DiagnosticReport.encounter",
"comment": "This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).\r\n\r\n【JP仕様】
\r\nEncounterリソースを参照
\r\n
\r\n【議論】
\r\n入院の場合には、ラベル印刷日時とは限らない。
"
},
{
"id": "DiagnosticReport.effective[x]",
"path": "DiagnosticReport.effective[x]",
"comment": "If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.\r\n\r\n【JP仕様】
\r\n検体採取時間
"
},
{
"id": "DiagnosticReport.issued",
"path": "DiagnosticReport.issued",
"comment": "May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report.\r\n\r\n【JP仕様】
\r\nこのデータが出来た時間
"
},
{
"id": "DiagnosticReport.performer",
"path": "DiagnosticReport.performer",
"comment": "This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report.\r\n\r\n【JP仕様】
\r\n検査に関わった人もしくは組織
"
},
{
"id": "DiagnosticReport.resultsInterpreter",
"path": "DiagnosticReport.resultsInterpreter",
"comment": "Might not be the same entity that takes responsibility for the clinical report.\r\n\r\n【JP仕様】
\r\n検査責任者
"
},
{
"id": "DiagnosticReport.specimen",
"path": "DiagnosticReport.specimen",
"comment": "If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.\r\n\r\n【JP仕様】
\r\n該当するspecimenを設定
"
},
{
"id": "DiagnosticReport.result",
"path": "DiagnosticReport.result",
"comment": "Observations can contain observations.\r\n\r\n【JP仕様】
\r\n該当するObservationを設定
"
},
{
"id": "DiagnosticReport.imagingStudy",
"path": "DiagnosticReport.imagingStudy",
"comment": "ImagingStudy and the image element are somewhat overlapping - typically, the list of image references in the image element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.\r\n\r\n【JP仕様】
\r\n使わない
"
},
{
"id": "DiagnosticReport.media",
"path": "DiagnosticReport.media",
"comment": "【JP仕様】
\r\nレポート1つに対して、複数の画像・コメントがぶら下がる
"
},
{
"id": "DiagnosticReport.media.comment",
"path": "DiagnosticReport.media.comment",
"comment": "The comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.\r\n\r\n【JP仕様】
\r\n画像に対するコメント
"
},
{
"id": "DiagnosticReport.media.link",
"path": "DiagnosticReport.media.link",
"comment": "References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.\r\n\r\n【JP仕様】
\r\n画像に対するリンク
"
},
{
"id": "DiagnosticReport.conclusion",
"path": "DiagnosticReport.conclusion",
"comment": "Note that FHIR strings SHALL NOT exceed 1MB in size\r\n\r\n【JP仕様】
\r\n原則使わない
"
},
{
"id": "DiagnosticReport.conclusionCode",
"path": "DiagnosticReport.conclusionCode",
"comment": "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.\r\n\r\n【JP仕様】
\r\n原則使わない
"
},
{
"id": "DiagnosticReport.presentedForm",
"path": "DiagnosticReport.presentedForm",
"comment": "\"application/pdf\" is recommended as the most reliable and interoperable in this context.\r\n\r\n【JP仕様】
\r\n原則使わない
"
}
]
}
}