DiagnosticReport
Description
DiagnosticReport is shown in Patient Finder in the report category. The text found in either the conclusion
or the presentedForm.data
will be shown pseudonymised in the Patient Finder application. For example the text found in the example below will go from: The patient John Doe has a broken bone.
to: The patient [FIRSTNAME] [LASTNAME] has a broken bone.
.
Notes on specific fields:
code
: The code is a required field in FHIR, but it is not used in Patient Finder.media.link.reference
: Since we do not load the resource Media, we will only show the identifier of this media as a textual value, so it can be referenced in the source data if one has acces
Instances
An example of a DiagnosticReport resource can be found here: DiagnosticReport Example 1
Profile
PatientFinderDiagnosticReport (DiagnosticReport) | I | DiagnosticReport | |
id | Σ | 0..1 | string |
meta | Σ | 0..1 | Meta |
implicitRules | Σ ?! | 0..1 | uri |
language | 0..1 | codeBinding | |
text | 0..1 | Narrative | |
contained | 0..* | Resource | |
extension | I | 0..* | Extension |
modifierExtension | ?! I | 0..* | Extension |
identifier | S Σ | 0..* | Identifier |
id | 0..1 | string | |
extension | I | 0..* | Extension |
use | Σ ?! | 0..1 | codeBinding |
type | Σ | 0..1 | CodeableConceptBinding |
system | Σ | 0..1 | uri |
value | S Σ | 0..1 | string |
period | Σ | 0..1 | Period |
assigner | Σ | 0..1 | Reference(Organization) |
basedOn | 0..* | Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | |
status | S Σ ?! | 1..1 | codeBinding |
category | S Σ | 0..* | CodeableConcept |
id | 0..1 | string | |
extension | I | 0..* | Extension |
coding | Σ | 0..* | Coding |
id | 0..1 | string | |
extension | I | 0..* | Extension |
system | Σ | 0..1 | uri |
version | Σ | 0..1 | string |
code | S Σ | 0..1 | code |
display | S Σ | 0..1 | string |
userSelected | Σ | 0..1 | boolean |
text | Σ | 0..1 | string |
code | Σ | 1..1 | CodeableConceptBinding |
subject | S Σ | 0..1 | Reference(Patient) |
encounter | Σ | 0..1 | Reference(Encounter) |
effective[x] | Σ | 0..1 | |
effectiveDateTime | S Σ | 0..1 | dateTime |
effectivePeriod | S Σ | 0..1 | Period |
id | 0..1 | string | |
extension | I | 0..* | Extension |
start | S Σ I | 0..1 | dateTime |
end | Σ I | 0..1 | dateTime |
issued | Σ | 0..1 | instant |
performer | S Σ | 0..* | Reference(Practitioner | Organization) |
resultsInterpreter | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam) |
specimen | 0..* | Reference(Specimen) | |
result | 0..* | Reference(Observation) | |
imagingStudy | 0..* | Reference(ImagingStudy) | |
media | S Σ | 0..* | BackboneElement |
id | 0..1 | string | |
extension | I | 0..* | Extension |
modifierExtension | Σ ?! I | 0..* | Extension |
comment | 0..1 | string | |
link | S Σ | 1..1 | Reference(Media) |
conclusion | S | 0..1 | string |
conclusionCode | 0..* | CodeableConcept | |
presentedForm | S | 0..* | Attachment |
id | 0..1 | string | |
extension | I | 0..* | Extension |
contentType | Σ | 0..1 | codeBinding |
language | Σ | 0..1 | codeBinding |
data | 0..1 | base64Binary | |
url | Σ | 0..1 | url |
size | Σ | 0..1 | unsignedInt |
hash | Σ | 0..1 | base64Binary |
title | Σ | 0..1 | string |
creation | Σ | 0..1 | dateTime |
<StructureDefinition xmlns="http://hl7.org/fhir"> <id value="pf-diagnostic-report" /> <url value="https://fhir.iqvia.com/patientfinder/StructureDefinition/pf-diagnostic-report" /> <name value="PatientFinderDiagnosticReport" /> <title value="DiagnosticReport" /> <status value="draft" /> <description value="DiagnosticReport is represented the Patient Finder category report. The text in the conclusion will be pseudonymized." /> <fhirVersion value="4.0.1" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <name value="FHIR to Patient Finder Mapping" /> </mapping> <kind value="resource" /> <abstract value="false" /> <type value="DiagnosticReport" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport" /> <derivation value="constraint" /> <differential> <element id="DiagnosticReport.identifier"> <path value="DiagnosticReport.identifier" /> <mustSupport value="true" /> </element> <element id="DiagnosticReport.identifier.value"> <path value="DiagnosticReport.identifier.value" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report source id" /> </mapping> </element> <element id="DiagnosticReport.status"> <path value="DiagnosticReport.status" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report status" /> </mapping> </element> <element id="DiagnosticReport.category"> <path value="DiagnosticReport.category" /> <mustSupport value="true" /> </element> <element id="DiagnosticReport.category.coding.code"> <path value="DiagnosticReport.category.coding.code" /> <mustSupport value="true" /> </element> <element id="DiagnosticReport.category.coding.display"> <path value="DiagnosticReport.category.coding.display" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report report type" /> </mapping> </element> <element id="DiagnosticReport.subject"> <path value="DiagnosticReport.subject" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Patient" /> </type> <mustSupport value="true" /> </element> <element id="DiagnosticReport.effective[x]"> <path value="DiagnosticReport.effective[x]" /> <slicing> <discriminator> <type value="type" /> <path value="$this" /> </discriminator> <ordered value="false" /> <rules value="open" /> </slicing> </element> <element id="DiagnosticReport.effective[x]:effectiveDateTime"> <path value="DiagnosticReport.effective[x]" /> <sliceName value="effectiveDateTime" /> <min value="0" /> <max value="1" /> <type> <code value="dateTime" /> </type> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report date" /> </mapping> </element> <element id="DiagnosticReport.effective[x]:effectivePeriod"> <path value="DiagnosticReport.effective[x]" /> <sliceName value="effectivePeriod" /> <min value="0" /> <max value="1" /> <type> <code value="Period" /> </type> <mustSupport value="true" /> </element> <element id="DiagnosticReport.effective[x]:effectivePeriod.start"> <path value="DiagnosticReport.effective[x].start" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report date" /> </mapping> </element> <element id="DiagnosticReport.performer"> <path value="DiagnosticReport.performer" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> </type> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="(Practitioner) report care provider" /> </mapping> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="(Organization) report specialism" /> </mapping> </element> <element id="DiagnosticReport.media"> <path value="DiagnosticReport.media" /> <mustSupport value="true" /> </element> <element id="DiagnosticReport.media.link"> <path value="DiagnosticReport.media.link" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report attachment id" /> </mapping> </element> <element id="DiagnosticReport.conclusion"> <path value="DiagnosticReport.conclusion" /> <mustSupport value="true" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report content" /> </mapping> </element> <element id="DiagnosticReport.presentedForm"> <path value="DiagnosticReport.presentedForm" /> <mustSupport value="true" /> </element> <element id="DiagnosticReport.presentedForm.data"> <path value="DiagnosticReport.presentedForm.data" /> <mapping> <identity value="fhir-patient-finder-mapping" /> <map value="report content" /> </mapping> </element> </differential> </StructureDefinition>
{ "resourceType": "StructureDefinition", "id": "pf-diagnostic-report", "url": "https://fhir.iqvia.com/patientfinder/StructureDefinition/pf-diagnostic-report", "name": "PatientFinderDiagnosticReport", "title": "DiagnosticReport", "status": "draft", "description": "DiagnosticReport is represented the Patient Finder category report. The text in the conclusion will be pseudonymized.", "fhirVersion": "4.0.1", "mapping": [ { "identity": "fhir-patient-finder-mapping", "name": "FHIR to Patient Finder Mapping" } ], "kind": "resource", "abstract": false, "type": "DiagnosticReport", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport", "derivation": "constraint", "differential": { "element": [ { "id": "DiagnosticReport.identifier", "path": "DiagnosticReport.identifier", "mustSupport": true }, { "id": "DiagnosticReport.identifier.value", "path": "DiagnosticReport.identifier.value", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report source id" } ] }, { "id": "DiagnosticReport.status", "path": "DiagnosticReport.status", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report status" } ] }, { "id": "DiagnosticReport.category", "path": "DiagnosticReport.category", "mustSupport": true }, { "id": "DiagnosticReport.category.coding.code", "path": "DiagnosticReport.category.coding.code", "mustSupport": true }, { "id": "DiagnosticReport.category.coding.display", "path": "DiagnosticReport.category.coding.display", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report report type" } ] }, { "id": "DiagnosticReport.subject", "path": "DiagnosticReport.subject", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Patient" ] } ], "mustSupport": true }, { "id": "DiagnosticReport.effective[x]", "path": "DiagnosticReport.effective[x]", "slicing": { "discriminator": [ { "type": "type", "path": "$this" } ], "ordered": false, "rules": "open" } }, { "id": "DiagnosticReport.effective[x]:effectiveDateTime", "path": "DiagnosticReport.effective[x]", "sliceName": "effectiveDateTime", "min": 0, "max": "1", "type": [ { "code": "dateTime" } ], "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report date" } ] }, { "id": "DiagnosticReport.effective[x]:effectivePeriod", "path": "DiagnosticReport.effective[x]", "sliceName": "effectivePeriod", "min": 0, "max": "1", "type": [ { "code": "Period" } ], "mustSupport": true }, { "id": "DiagnosticReport.effective[x]:effectivePeriod.start", "path": "DiagnosticReport.effective[x].start", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report date" } ] }, { "id": "DiagnosticReport.performer", "path": "DiagnosticReport.performer", "type": [ { "code": "Reference", "targetProfile": [ "http://hl7.org/fhir/StructureDefinition/Practitioner", "http://hl7.org/fhir/StructureDefinition/Organization" ] } ], "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "(Practitioner) report care provider" }, { "identity": "fhir-patient-finder-mapping", "map": "(Organization) report specialism" } ] }, { "id": "DiagnosticReport.media", "path": "DiagnosticReport.media", "mustSupport": true }, { "id": "DiagnosticReport.media.link", "path": "DiagnosticReport.media.link", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report attachment id" } ] }, { "id": "DiagnosticReport.conclusion", "path": "DiagnosticReport.conclusion", "mustSupport": true, "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report content" } ] }, { "id": "DiagnosticReport.presentedForm", "path": "DiagnosticReport.presentedForm", "mustSupport": true }, { "id": "DiagnosticReport.presentedForm.data", "path": "DiagnosticReport.presentedForm.data", "mapping": [ { "identity": "fhir-patient-finder-mapping", "map": "report content" } ] } ] } }
DiagnosticReport | |
Definition | The findings and interpretation of diagnostic tests performed on patients, groups of patients, devices, and locations, and/or specimens derived from these. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretations, and formatted representation of diagnostic reports. |
Cardinality | 0...* |
Alias | Report, Test, Result, Results, Labs, Laboratory |
Comments | This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing. |
Invariants |
|
Mappings |
|
DiagnosticReport.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
DiagnosticReport.meta | |
Definition | 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. |
Cardinality | 0...1 |
Type | Meta |
Summary | True |
Invariants |
|
DiagnosticReport.implicitRules | |
Definition | 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. |
Cardinality | 0...1 |
Type | uri |
Modifier | True |
Summary | True |
Comments | 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. |
Invariants |
|
DiagnosticReport.language | |
Definition | The base language in which the resource is written. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Comments | 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). |
Invariants |
|
DiagnosticReport.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | Narrative |
Alias | narrative, html, xhtml, display |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.contained | |
Definition | 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. |
Cardinality | 0...* |
Type | Resource |
Alias | inline resources, anonymous resources, contained resources |
Comments | 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. |
Mappings |
|
DiagnosticReport.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.modifierExtension | |
Definition | 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Alias | extensions, user content |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier | |
Definition | Identifiers assigned to this report by the performer or other systems. |
Cardinality | 0...* |
Type | Identifier |
Must Support | True |
Summary | True |
Alias | ReportID, Filler ID, Placer ID |
Requirements | Need to know what identifier to use when making queries about this report from the source laboratory, and for linking to the report outside FHIR context. |
Comments | Usually assigned by the Information System of the diagnostic service provider (filler id). |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.identifier.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier.use | |
Definition | The purpose of this identifier. |
Cardinality | 0...1 |
Type | code |
Binding | Identifies the purpose for this identifier, if known . |
Modifier | True |
Summary | True |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
Summary | True |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. |
Comments | Identifier.system is always case sensitive. |
Invariants |
|
Examples | General http://www.acme.com/identifiers/patient |
Mappings |
|
DiagnosticReport.identifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. |
Invariants |
|
Examples | General 123456 |
Mappings |
|
DiagnosticReport.identifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Cardinality | 0...1 |
Type | Period |
Summary | True |
Invariants |
|
Mappings |
|
DiagnosticReport.identifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Cardinality | 0...1 |
Type | Reference(Organization) |
Summary | True |
Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. |
Invariants |
|
Mappings |
|
DiagnosticReport.basedOn | |
Definition | Details concerning a service requested. |
Cardinality | 0...* |
Type | Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) |
Alias | Request |
Requirements | This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.status | |
Definition | The status of the diagnostic report. |
Cardinality | 1...1 |
Type | code |
Binding | The status of the diagnostic report. |
Must Support | True |
Modifier | True |
Summary | True |
Requirements | Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. |
Invariants |
|
Mappings |
|
DiagnosticReport.category | |
Definition | A code that classifies the clinical discipline, department or diagnostic service that created the report (e.g. cardiology, biochemistry, hematology, MRI). This is used for searching, sorting and display purposes. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Codes for diagnostic service sections. |
Must Support | True |
Summary | True |
Alias | Department, Sub-department, Service, Discipline |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.category.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding | |
Definition | A reference to a code defined by a terminology system. |
Cardinality | 0...* |
Type | Coding |
Summary | True |
Requirements | Allows for alternative encodings within a code system, and translations to other code systems. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.category.coding.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.system | |
Definition | The identification of the code system that defines the meaning of the symbol in the code. |
Cardinality | 0...1 |
Type | uri |
Summary | True |
Requirements | Need to be unambiguous about the source of the definition of the symbol. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.version | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.code | |
Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Cardinality | 0...1 |
Type | code |
Must Support | True |
Summary | True |
Requirements | Need to refer to a particular code in the system. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.display | |
Definition | A representation of the meaning of the code in the system, following the rules of the system. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Summary | True |
Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.coding.userSelected | |
Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). |
Cardinality | 0...1 |
Type | boolean |
Summary | True |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.category.text | |
Definition | 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. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | 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. |
Comments | Very often the text is the same as a displayName of one of the codings. |
Invariants |
|
Mappings |
|
DiagnosticReport.code | |
Definition | A code or name that describes this diagnostic report. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | Codes that describe Diagnostic Reports. |
Summary | True |
Alias | Type |
Invariants |
|
Mappings |
|
DiagnosticReport.subject | |
Definition | The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources. |
Cardinality | 0...1 |
Type | Reference(Patient) |
Must Support | True |
Summary | True |
Alias | Patient |
Requirements | SHALL know the subject context. |
Invariants |
|
Mappings |
|
DiagnosticReport.encounter | |
Definition | The healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. |
Cardinality | 0...1 |
Type | Reference(Encounter) |
Summary | True |
Alias | Context |
Requirements | Links the request to the Encounter context. |
Comments | 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). |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x] | |
Definition | The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Alias | Observation time, Effective Time, Occurrence |
Requirements | Need to know where in the patient history to file/present this report. |
Comments | 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. |
Slicing | Unordered, Open, by $this(Type) |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x]:effectiveDateTime | |
Definition | The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Alias | Observation time, Effective Time, Occurrence |
Requirements | Need to know where in the patient history to file/present this report. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x]:effectivePeriod | |
Definition | The time or time-period the observed values are related to. When the subject of the report is a patient, this is usually either the time of the procedure or of specimen collection(s), but very often the source of the date/time is not known, only the date/time itself. |
Cardinality | 0...1 |
Type | Period |
Must Support | True |
Summary | True |
Alias | Observation time, Effective Time, Occurrence |
Requirements | Need to know where in the patient history to file/present this report. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x]:effectivePeriod.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.effective[x]:effectivePeriod.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x]:effectivePeriod.start | |
Definition | The start of the period. The boundary is inclusive. |
Cardinality | 0...1 |
Type | dateTime |
Must Support | True |
Summary | True |
Comments | If the low element is missing, the meaning is that the low boundary is not known. |
Invariants |
|
Mappings |
|
DiagnosticReport.effective[x]:effectivePeriod.end | |
Definition | The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Comments | The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. |
Invariants |
|
Mappings |
|
DiagnosticReport.issued | |
Definition | The date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. |
Cardinality | 0...1 |
Type | instant |
Summary | True |
Alias | Date published, Date Issued, Date Verified |
Requirements | Clinicians need to be able to check the date that the report was released. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.performer | |
Definition | The diagnostic service that is responsible for issuing the report. |
Cardinality | 0...* |
Type | Reference(Practitioner | Organization) |
Must Support | True |
Summary | True |
Alias | Laboratory, Service, Practitioner, Department, Company, Authorized by, Director |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.resultsInterpreter | |
Definition | The practitioner or organization that is responsible for the report's conclusions and interpretations. |
Cardinality | 0...* |
Type | Reference(Practitioner | PractitionerRole | Organization | CareTeam) |
Summary | True |
Alias | Analyzed by, Reported by |
Requirements | 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. |
Comments | Might not be the same entity that takes responsibility for the clinical report. |
Invariants |
|
Mappings |
|
DiagnosticReport.specimen | |
Definition | Details about the specimens on which this diagnostic report is based. |
Cardinality | 0...* |
Type | Reference(Specimen) |
Requirements | Need to be able to report information about the collected specimens on which the report is based. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.result | |
Definition | [Observations](observation.html) that are part of this diagnostic report. |
Cardinality | 0...* |
Type | Reference(Observation) |
Alias | Data, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer |
Requirements | Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. |
Comments | Observations can contain observations. |
Invariants |
|
Mappings |
|
DiagnosticReport.imagingStudy | |
Definition | One or more links to full details of any imaging performed during the diagnostic investigation. Typically, this is imaging performed by DICOM enabled modalities, but this is not required. A fully enabled PACS viewer can use this information to provide views of the source images. |
Cardinality | 0...* |
Type | Reference(ImagingStudy) |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.media | |
Definition | A list of key images associated with this report. The images are generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). |
Cardinality | 0...* |
Type | BackboneElement |
Must Support | True |
Summary | True |
Alias | DICOM, Slides, Scans |
Requirements | Many diagnostic services include images in the report as part of their service. |
Invariants |
|
Mappings |
|
DiagnosticReport.media.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.media.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.media.modifierExtension | |
Definition | 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). |
Cardinality | 0...* |
Type | Extension |
Modifier | True |
Summary | True |
Alias | extensions, user content, modifiers |
Requirements | 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. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.media.comment | |
Definition | A comment about the image. Typically, this is used to provide an explanation for why the image is included, or to draw the viewer's attention to important features. |
Cardinality | 0...1 |
Type | string |
Requirements | The provider of the report should make a comment about each image included in the report. |
Comments | 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. |
Invariants |
|
Mappings |
|
DiagnosticReport.media.link | |
Definition | Reference to the image source. |
Cardinality | 1...1 |
Type | Reference(Media) |
Must Support | True |
Summary | True |
Invariants |
|
Mappings |
|
DiagnosticReport.conclusion | |
Definition | Concise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. |
Cardinality | 0...1 |
Type | string |
Must Support | True |
Alias | Report |
Requirements | Need to be able to provide a conclusion that is not lost among the basic result data. |
Invariants |
|
Mappings |
|
DiagnosticReport.conclusionCode | |
Definition | One or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Diagnosis codes provided as adjuncts to the report. |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm | |
Definition | Rich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. |
Cardinality | 0...* |
Type | Attachment |
Must Support | True |
Requirements | Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. |
Comments | "application/pdf" is recommended as the most reliable and interoperable in this context. |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm.id | |
Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Cardinality | 0...1 |
Type | string |
Mappings |
|
DiagnosticReport.presentedForm.extension | |
Definition | 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. |
Cardinality | 0...* |
Type | Extension |
Alias | extensions, user content |
Comments | 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. |
Slicing | Unordered, Open, by url(Value) |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm.contentType | |
Definition | Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate. |
Cardinality | 0...1 |
Type | code |
Binding | The mime type of an attachment. Any valid mime type is allowed. |
Summary | True |
Requirements | Processors of the data need to be able to know how to interpret the data. |
Invariants |
|
Examples | General text/plain; charset=UTF-8, image/png |
Mappings |
|
DiagnosticReport.presentedForm.language | |
Definition | The human language of the content. The value can be any valid value according to BCP 47. |
Cardinality | 0...1 |
Type | code |
Binding | A human language. |
Summary | True |
Requirements | Users need to be able to choose between the languages in a set of attachments. |
Invariants |
|
Examples | General en-AU |
Mappings |
|
DiagnosticReport.presentedForm.data | |
Definition | The actual data of the attachment - a sequence of bytes, base64 encoded. |
Cardinality | 0...1 |
Type | base64Binary |
Requirements | The data needs to able to be transmitted inline. |
Comments | The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON. |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm.url | |
Definition | A location where the data can be accessed. |
Cardinality | 0...1 |
Type | url |
Summary | True |
Requirements | The data needs to be transmitted by reference. |
Comments | If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data. |
Invariants |
|
Examples | General http://www.acme.com/logo-small.png |
Mappings |
|
DiagnosticReport.presentedForm.size | |
Definition | The number of bytes of data that make up this attachment (before base64 encoding, if that is done). |
Cardinality | 0...1 |
Type | unsignedInt |
Summary | True |
Requirements | Representing the size allows applications to determine whether they should fetch the content automatically in advance, or refuse to fetch it at all. |
Comments | The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference. |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm.hash | |
Definition | The calculated hash of the data using SHA-1. Represented using base64. |
Cardinality | 0...1 |
Type | base64Binary |
Summary | True |
Requirements | Included so that applications can verify that the contents of a location have not changed due to technical failures (e.g., storage rot, transport glitch, incorrect version). |
Comments | The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see Provenance.signature for mechanism to protect a resource with a digital signature. |
Invariants |
|
Mappings |
|
DiagnosticReport.presentedForm.title | |
Definition | A label or set of text to display in place of the data. |
Cardinality | 0...1 |
Type | string |
Summary | True |
Requirements | Applications need a label to display to a human user in place of the actual data if the data cannot be rendered or perceived by the viewer. |
Invariants |
|
Examples | General Official Corporate Logo |
Mappings |
|
DiagnosticReport.presentedForm.creation | |
Definition | The date that the attachment was first created. |
Cardinality | 0...1 |
Type | dateTime |
Summary | True |
Requirements | This is often tracked as an integrity issue for use of the attachment. |
Invariants |
|
Mappings |
|
Attribute list
Attribute | Description | Example |
---|---|---|
identifier.value | The code that identifies the diagnostic report | 'diagnostic-report-example-1' |
status | The status of the diagnostic report | #final |
category.coding.code | The code showing the type of report | SNOMED CT: '#394914008 |
category.coding.display | The textual value showing the type of report | 'Radiology' |
subject.reference | A reference to the patient that the diagnostic report is about | 'Patient/patient-1' |
effectiveDateTime | The date/time that the report was first published in the source system | '2013-12-10T08:00:00Z' |
performer.reference | (Practitioner) A reference to the person who wrote the report | 'Practitioner/practitioner-1' |
performer.reference | (Organization) A reference to the specialism responsible for the report | 'Organization/specialism-1' |
media.link.reference | A reference to the media associated with this report | '872154798' |
conclusion | The full text of the report. This field can be used instead of presentedForm.data | 'The patient John Doe has a broken bone.' |
presentedForm.data | The full text of the report. This field can be used instead of conclusion | 'The patient John Doe has a broken bone.' |