内視鏡を使用して実施された検査、治療に関する診断レポート。

これは単一のレポートをキャプチャすることを目的としており、複数のレポートをカバーする要約情報の表示に使用するのには適していない。たとえば、このリソースは、検査結果の累積レポート形式やシーケンスの詳細な構造化レポート用に作られていない。
【JP Core仕様】DiagnosticReportリソースの共通プロフィール

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.

主にレポートの見読性と検索性の向上を目的に、所見を中心としたhuman-readableなnarrativeデータを格納することを推奨する。

レポートの詳細はpresentedForm要素に格納されるレポート本体での確認を前提とする。

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.

製品またはシステムが管理する、施設内で診断レポートを一意に識別するためのID。

通常、診断サービスプロバイダの情報システム（フィラーID）によって割り当てられる。

発生源の検査室からこのレポートについてクエリを作成するとき、およびFHIRコンテキスト外のレポートにリンクするときに使用する識別子を知る必要がある。

他のシステムから依頼されたオーダ情報。

通常、依頼元となるServiceRequestリソースを参照する。他のシステムと連携していない場合は参照不要。

This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon.

診断レポートのステータス。

「preliminary」（作成中、未確定、未承認）もしくは 「final」（作成完了、確定済、承認済）を指定する。

The status of the diagnostic report.

Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports.

診断レポートの分野を表すコード。

これは、検索、並べ替え、および表示の目的で使用される。

HL7 V2 table 0074

診断レポートを作成した臨床分野、部門、または診断サービス（心臓病学、生化学、血液学、放射線医学など）を分類するコード

JP_DiagnosticReportCategory_VSの中から「LP7796-8」（Endoscopy（内視鏡））を指定する。

内視鏡分野の診断レポートを分類するためのコード。

JP_DocumentCodes_Endoscopy_VSの中から適切な内視鏡分野の報告書のコードを指定する（例：「18751-8」（上部消化管内視鏡報告書））。該当する適切な報告書のコードが登録されていない場合は、「19805-1」（内視鏡検査報告書）を指定する。

診断レポートの対象患者に関する情報。

JP Core Patientリソースを参照する。

SHALL know the subject context.

この診断レポートを書くきっかけとなった情報。

JP Core Encounterリソースを参照する。

Links the request to the Encounter context.

診断レポートの作成日時。

DateTimeを採用する。

Need to know where in the patient history to file/present this report.

レポート確定日時。

StatusがFinalになった日時を指定する。

Clinicians need to be able to check the date that the report was released.

内視鏡検査、治療を実施した医師。

JP Core Practitionerリソースを参照する。

Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis.

通常、この診断レポートの確定者。

通常、JP Core Practitionerリソースを参照する。

Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis.

この診断レポートの検体に関する情報。

内視鏡では省略してよい。

Need to be able to report information about the collected specimens on which the report is based.

この診断レポートの一部となるObservationに関する情報。

Observationsは階層構造を持てる。

個々の結果または結果のグループをサポートする必要がある。結果のグループ化は任意だが、意味がある場合にグループ化される。

診断レポートに関連づけれられたDICOM画像検査に関する情報。

JP Core ImagingStudy Endoscopyリソースを参照する。

診断レポートに関連づけられたメディアに関する情報。

主に、レポートに添付されるキー画像を指す。

多くの診断業務では提供情報の一部としてレポートに画像を含む。

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).

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.

メディアに関するコメント。

内視鏡では省略してよい。

The provider of the report should make a comment about each image included in the report.

メディアの参照先。

総合診断に相当する要約結論。

テキストで可能な限り記載する。

Need to be able to provide a conclusion that is not lost among the basic result data.

内視鏡診断レポートの要約結論を表す1つ以上のコード。

JED Project（https://jedproject.jges.net/）が対象とする検査種別については、指定された質的診断コードを使用することを強く推奨する。

診断レポート本体。

診断レポート本体をPDF形式やxml形式などで添付する（フォーマットは不問）。

Gives laboratory the ability to provide its own fully formatted report for clinical fidelity.

内視鏡を使用して実施された検査、治療に関する診断レポート。

主にレポートの見読性と検索性の向上を目的に、所見を中心としたhuman-readableなnarrativeデータを格納することを推奨する。

レポートの詳細はpresentedForm要素に格納されるレポート本体での確認を前提とする。

製品またはシステムが管理する、施設内で診断レポートを一意に識別するためのID。

他のシステムから依頼されたオーダ情報。

通常、依頼元となるServiceRequestリソースを参照する。他のシステムと連携していない場合は参照不要。

診断レポートのステータス。

「preliminary」（作成中、未確定、未承認）もしくは 「final」（作成完了、確定済、承認済）を指定する。

診断レポートの分野を表すコード。

JP_DiagnosticReportCategory_VSの中から「LP7796-8」（Endoscopy（内視鏡））を指定する。

内視鏡分野の診断レポートを分類するためのコード。

JP_DocumentCodes_Endoscopy_VSの中から適切な内視鏡分野の報告書のコードを指定する（例：「18751-8」（上部消化管内視鏡報告書））。該当する適切な報告書のコードが登録されていない場合は、「19805-1」（内視鏡検査報告書）を指定する。

診断レポートの対象患者に関する情報。

JP Core Patientリソースを参照する。

この診断レポートを書くきっかけとなった情報。

JP Core Encounterリソースを参照する。

診断レポートの作成日時。

DateTimeを採用する。

レポート確定日時。

StatusがFinalになった日時を指定する。

内視鏡検査、治療を実施した医師。

JP Core Practitionerリソースを参照する。

通常、この診断レポートの確定者。

通常、JP Core Practitionerリソースを参照する。

この診断レポートの検体に関する情報。

内視鏡では省略してよい。

この診断レポートの一部となるObservationに関する情報。

診断レポートに関連づけれられたDICOM画像検査に関する情報。

JP Core ImagingStudy Endoscopyリソースを参照する。

診断レポートに関連づけられたメディアに関する情報。

主に、レポートに添付されるキー画像を指す。

メディアに関するコメント。

内視鏡では省略してよい。

メディアの参照先。

総合診断に相当する要約結論。

テキストで可能な限り記載する。

内視鏡診断レポートの要約結論を表す1つ以上のコード。

JED Project（https://jedproject.jges.net/）が対象とする検査種別については、指定された質的診断コードを使用することを強く推奨する。

診断レポート本体。

診断レポート本体をPDF形式やxml形式などで添付する（フォーマットは不問）。

内視鏡を使用して実施された検査、治療に関する診断レポート。

これは単一のレポートをキャプチャすることを目的としており、複数のレポートをカバーする要約情報の表示に使用するのには適していない。たとえば、このリソースは、検査結果の累積レポート形式やシーケンスの詳細な構造化レポート用に作られていない。
【JP Core仕様】DiagnosticReportリソースの共通プロフィール

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.

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.

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).

IETF language tag

主にレポートの見読性と検索性の向上を目的に、所見を中心としたhuman-readableなnarrativeデータを格納することを推奨する。

レポートの詳細はpresentedForm要素に格納されるレポート本体での確認を前提とする。

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.

May be used to represent additional information that is not part of the basic definition of the resource. 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.

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.

製品またはシステムが管理する、施設内で診断レポートを一意に識別するためのID。

通常、診断サービスプロバイダの情報システム（フィラーID）によって割り当てられる。

発生源の検査室からこのレポートについてクエリを作成するとき、およびFHIRコンテキスト外のレポートにリンクするときに使用する識別子を知る必要がある。

他のシステムから依頼されたオーダ情報。

通常、依頼元となるServiceRequestリソースを参照する。他のシステムと連携していない場合は参照不要。

This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon.

診断レポートのステータス。

「preliminary」（作成中、未確定、未承認）もしくは 「final」（作成完了、確定済、承認済）を指定する。

The status of the diagnostic report.

Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports.

診断レポートの分野を表すコード。

これは、検索、並べ替え、および表示の目的で使用される。

HL7 V2 table 0074

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.

カテゴリーコードシステムの識別URL

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.

診断レポートを作成した臨床分野、部門、または診断サービス（心臓病学、生化学、血液学、放射線医学など）を分類するコード

JP_DiagnosticReportCategory_VSの中から「LP7796-8」（Endoscopy（内視鏡））を指定する。

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.

カテゴリーコードシステムの識別URL

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.

内視鏡分野の診断レポートを分類するためのコード。

JP_DocumentCodes_Endoscopy_VSの中から適切な内視鏡分野の報告書のコードを指定する（例：「18751-8」（上部消化管内視鏡報告書））。該当する適切な報告書のコードが登録されていない場合は、「19805-1」（内視鏡検査報告書）を指定する。

診断レポートの対象患者に関する情報。

JP Core Patientリソースを参照する。

SHALL know the subject context.

この診断レポートを書くきっかけとなった情報。

JP Core Encounterリソースを参照する。

Links the request to the Encounter context.

診断レポートの作成日時。

DateTimeを採用する。

Need to know where in the patient history to file/present this report.

レポート確定日時。

StatusがFinalになった日時を指定する。

Clinicians need to be able to check the date that the report was released.

内視鏡検査、治療を実施した医師。

JP Core Practitionerリソースを参照する。

Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis.

通常、この診断レポートの確定者。

通常、JP Core Practitionerリソースを参照する。

Need to know whom to contact if there are queries about the results. Also may need to track the source of reports for secondary data analysis.

この診断レポートの検体に関する情報。

内視鏡では省略してよい。

Need to be able to report information about the collected specimens on which the report is based.

この診断レポートの一部となるObservationに関する情報。

Observationsは階層構造を持てる。

個々の結果または結果のグループをサポートする必要がある。結果のグループ化は任意だが、意味がある場合にグループ化される。

診断レポートに関連づけれられたDICOM画像検査に関する情報。

JP Core ImagingStudy Endoscopyリソースを参照する。

診断レポートに関連づけられたメディアに関する情報。

主に、レポートに添付されるキー画像を指す。

多くの診断業務では提供情報の一部としてレポートに画像を含む。

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.

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).

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.

メディアに関するコメント。

内視鏡では省略してよい。

The provider of the report should make a comment about each image included in the report.

メディアの参照先。

総合診断に相当する要約結論。

テキストで可能な限り記載する。

Need to be able to provide a conclusion that is not lost among the basic result data.

内視鏡診断レポートの要約結論を表す1つ以上のコード。

JED Project（https://jedproject.jges.net/）が対象とする検査種別については、指定された質的診断コードを使用することを強く推奨する。

診断レポート本体。

診断レポート本体をPDF形式やxml形式などで添付する（フォーマットは不問）。

Gives laboratory the ability to provide its own fully formatted report for clinical fidelity.