Home > Clinical > DiagnosticReport [diagnosticreport]
Resource DiagnosticReport - Content4.16
The findings and interpretation of diagnostic tests performed on patients and/or specimens. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretation, and formatted representation of diagnostic reports.
The resource name as it appears in a RESTful URL is [root]/diagnosticreport/
A diagnostic report is used for the set of information that is typically provided by a diagnostic service when investigations are complete. The information includes a mix of atomic results, text reports, images, and codes. The mix varies depending on the nature of the diagnostic procedure, and sometimes on the nature of the outcomes for a particular investigation.
The Diagnostic Report Resource is suitable for the following kinds of Diagnostic Reports:
The Diagnostic Report is not intended to support:
Comments on the suitability of this resource and/or requirements analysis for that would be welcome through the community input above.
The actual atomic result data are delegated to the common Observation Resource to make it easier to reuse them in a wider context.
There is a wide variety of names associated with the various parts of a diagnostic report. Doctors request for "tests" or "results" to be done. What the diagnostic service returns is variously called the "tests" or "results" or the "report". The individual data items are called "results" or "tests" both collectively and individually. Collections of individual data items are sometimes called "batteries" or "panels", which have various implications in different contexts. The naming confusion is worsened because of the wide variety of forms that the result of a diagnostic investigation can take, as described above. Languages other than English have their own variations on this theme.
This resource uses one particular set of terms. A practitioner "requests" a set of "tests". The diagnostic service returns a "report" which contains a "narrative" - a written summary of the outcomes, and "results" - the individual pieces of atomic data. The results are assembled in a "group" which is a nested structure that can be used to define relationships between the individual data items.
Resource Content4.16.1
<DiagnosticReport xmlns="http://hl7.org/fhir"> <!-- from Resource: extension, narrative, and contained --> <status value="[code]"/><!-- 1..1 registered|interim|final|amended|cancelled|withdrawn § --> <issued value="[dateTime]"/><!-- 1..1 Date this version was released § --> <subject><!-- 1..1 Resource(Patient|Group|Device) The subject of the report § --></subject> <performer><!-- 1..1 Resource(Organization) Responsible Diagnostic Service § --></performer> <reportId><!-- 0..1 Identifier Id for external references to this report § --></reportId> <requestDetail> <!-- 0..* What was requested --> <encounter><!-- 0..1 Resource(Encounter) Context where request was made --></encounter> <requestOrderId><!-- 0..1 Identifier Id assigned by requester --></requestOrderId> <receiverOrderId><!-- 0..1 Identifier Receiver's Id for the request --></receiverOrderId> <requestTest><!-- 0..* CodeableConcept Test Requested --></requestTest> <bodySite><!-- 0..1 CodeableConcept Location of requested test (if applicable) --></bodySite> <requester><!-- 0..1 Resource(Organization|Practitioner) Responsible for request --></requester> <clinicalInfo value="[string]"/><!-- 0..1 Clinical information provided --> </requestDetail> <serviceCategory><!-- 0..1 CodeableConcept Biochemistry, Haematology etc. § --></serviceCategory> <diagnosticTime value="[dateTime]"/><!-- 1..1 Effective time of diagnostic report § --> <results> <!-- 1..1 Results grouped by specimen/kind/category --> <name><!-- 1..1 CodeableConcept Name/Code for this group of results --></name> <specimen><!-- 0..1 Resource(Specimen) Specimen details for this group --></specimen> <group><!-- 0..* Content as for DiagnosticReport.results Nested Report Group --></group> <result><!-- 0..* Resource(Observation) An atomic data result --></result> </results> <image><!-- 0..* Resource(Media|ImagingStudy) Key images associated with this report --></image> <conclusion value="[string]"/><!-- 0..1 Clinical Interpretation of test results --> <codedDiagnosis><!-- 0..* CodeableConcept Codes for the conclusion --></codedDiagnosis> <representation><!-- 0..* Attachment Entire Report as issued --></representation> </DiagnosticReport>
Alternate definitions: Schema/Schematron, Resource Profile
Notes:4.16.2
Search Parameters for RESTful searches. The standard parameters also apply. See Searching for more information.