DiagnosticReport-eu-lab
Summary
A test report, containing the overall findings and clinical interpretation relating to one or more pathology tests.
The report may reference individual test results, test groups or a combination of these. Test results and test groups are represented using the Observation resource and referenced from DiagnosticReport using DiagnosticReport.result.
For information on how test results and test groups are represented, refer to England-Observation-Lab-Pathology (Test Result) and England-Observation-Lab-Pathology (Test Group).
Resource and Profile Links
- R4 Resource (Base): DiagnosticReport
- Profile: DiagnosticReport-eu-lab
Profile Views
Refer to Profile Descriptions for a definition of the different profile view formats.
| DiagnosticReportLabEu (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Laboratory Report DiagnosticReport Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionLaboratory Report DiagnosticReport 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDiagnosticReport.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.languageShort description Language of the resource content DefinitionThe 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). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idDiagnosticReport.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDiagnosticReport.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | Element idDiagnosticReport.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| DiagnosticReportCompositionR5 | C | 0..1 | Extension(Reference(Composition)) | Element idDiagnosticReport.extension:DiagnosticReportCompositionR5Short description Associated Lab Report Composition Alternate namesextensions, user content DefinitionThis extension implements the R5 composition element. It allow to link this DiagnosticReport with the Composition documenting this Laboratory Report. 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. Extension(Reference(Composition)) Extension URLhttp://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.compositionMappings
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.value[x]Short description Reference to a Composition resource for the DiagnosticReport structure DefinitionThe Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| valueReference | Reference(CompositionLabReportEu) | Data type | ||||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | Σ | 0..* | Identifier | Element idDiagnosticReport.identifierShort description Report identifier Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this Laboratory Report by the performer or other systems. It shall be common to several report versions 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. Composition.identifier SHALL be equal to one of the DiagnosticReport.identifier, if at least one exists The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | C | 0..* | Reference(ServiceRequestLabEu) | Element idDiagnosticReport.basedOnShort description What was requested Alternate namesRequest DefinitionDetails concerning a service requested. This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. 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. Reference(ServiceRequestLabEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idDiagnosticReport.statusShort description Status of the Report DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. DiagnosticReport.status and Composition.status shall be aligned, based on the http://hl7.eu/fhir/laboratory/ConceptMap/ConceptMap-eu-diagRptStatus2CompStatus mapping The status of the diagnostic report. DiagnosticReportStatus (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| category | Σ | 0..* | CodeableConceptIPS | Element idDiagnosticReport.categoryShort description Report Category Alternate namesDepartment, Sub-department, Service, Discipline DefinitionA code that classifies this laboratory report. Two basic categories has been selected in this guide: laboratory specialty and Study type. Laboratory specialty is characteristic of the laboratory that produced the test result while Study type is an arbitrary classificion of the test type. DiagnosticReport.category and Composition.category shall be aligned Unordered, Open, by $this(Pattern) BindingCodes for diagnostic service sections. DiagnosticServiceSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| studyType | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:studyTypeShort description The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory services, i.e., results of tests performed, could be characterized using typology of services, commonly called study types. Study type could be seen as an attribute or grouping mechanism that assigns a common clinical sense to certain types of laboratory test results., e.g., Hemoglobin, Platelet count, etc. belongs to 'Hematology study'. In comparison to the laboratory specialty which is an attribute of laboratory, study type is a categorization of laboratory service. It needs to be mentioned that classification of test to study types in not standardized. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specialty | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:specialtyShort description The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory specialty is an attribute of any laboratory setting representing professional qualification of the laboratory to execute certain kind of laboratory tests. Specialty could be used as parameter for searching/querying of laboratory test results. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| code | Σ | 1..1 | CodeableConceptIPSBinding | Element idDiagnosticReport.codeShort description Type of (Laboratory) Report Alternate namesType DefinitionSpecifies that it refers to a Laboratory Report At least one DiagnosticReport.code.coding and Composition.type.coding SHALL be equal Codes that describe Diagnostic Reports. LabReportTypesEuVs (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| subject | Σ C | 1..1 | Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) | Element idDiagnosticReport.subjectShort description Who and/or what this report is about Alternate namesPatient DefinitionWho or what this report is about. The report can be about a human patient, a living subject, a device (e.g. a machine), a location or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). SHALL know the subject context. DiagnosticReport and Composition SHALL have the same subject Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | Element idDiagnosticReport.encounterShort description The healthcare event which this Laboratory Report is about (when test ordered). Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. 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). DiagnosticReport and Composition SHALL have the same encounter. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| effective[x] | Σ | 0..1 | Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report. Alternate namesObservation time, Effective Time, Occurrence DefinitionThe 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. Need to know where in the patient history to file/present this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDiagnosticReport.issuedShort description DateTime this version was made Alternate namesDate published, Date Issued, Date Verified DefinitionThe date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. Clinicians need to be able to check the date that the report was released. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performer | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.performerShort description Responsible Diagnostic Service. Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| resultsInterpreter | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.resultsInterpreterShort description Primary result interpreter Alternate namesAnalyzed by, Reported by DefinitionThe practitioner or organization that is responsible for the report's conclusions and interpretations. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specimen | C | 0..* | Reference(SpecimenEu) | Element idDiagnosticReport.specimenShort description Specimens this report is based on. DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| result | C | 0..* | Reference(ObservationResultsLaboratoryEu) | Element idDiagnosticReport.resultShort description results Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations. Reference(ObservationResultsLaboratoryEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| imagingStudy | C | 0..0 | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| media | Σ | 0..* | BackboneElement | Element idDiagnosticReport.mediaShort description Additional data (like images, diagrams or documents) associated with this report Alternate namesDICOM, Slides, Scans, DICOM; Slides; Scans; Pictures; Documents; Diagrams DefinitionA list of additional data, other then presented form of the report, associated with this report. This data is generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Some diagnostic reports may include additional data such as images, diagrams or documents that are relevant to the report. This additional information can provide further context and support for the findings presented in the report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| comment | 0..1 | string | Element idDiagnosticReport.media.commentShort description Comment about the image or data (e.g. explanation) DefinitionAllows for a comment about the image or data, such as an explanation of its significance or context within the diagnostic report. The provider of the report should make a comment about each image or data included in the report. This comment can provide valuable context and help the reader understand the significance of the image or data in relation to the overall findings of the report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| link | Σ C | 1..1 | Reference(Media) | Element idDiagnosticReport.media.linkShort description Reference to the image or data DefinitionA reference to the image or data associated with this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data. Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. 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. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| presentedForm | C | 0..* | Attachment | Element idDiagnosticReport.presentedFormShort description Entire report as issued (pdf recommended) DefinitionRich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. "application/pdf" is recommended as the most reliable and interoperable in this context. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| DiagnosticReportLabEu (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Laboratory Report DiagnosticReport Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionLaboratory Report DiagnosticReport 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDiagnosticReport.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.languageShort description Language of the resource content DefinitionThe 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). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idDiagnosticReport.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDiagnosticReport.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | Element idDiagnosticReport.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| DiagnosticReportCompositionR5 | C | 0..1 | Extension(Reference(Composition)) | Element idDiagnosticReport.extension:DiagnosticReportCompositionR5Short description Associated Lab Report Composition Alternate namesextensions, user content DefinitionThis extension implements the R5 composition element. It allow to link this DiagnosticReport with the Composition documenting this Laboratory Report. 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. Extension(Reference(Composition)) Extension URLhttp://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.compositionMappings
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.value[x]Short description Reference to a Composition resource for the DiagnosticReport structure DefinitionThe Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| valueReference | Reference(CompositionLabReportEu) | Data type | ||||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | Σ | 0..* | Identifier | Element idDiagnosticReport.identifierShort description Report identifier Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this Laboratory Report by the performer or other systems. It shall be common to several report versions 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. Composition.identifier SHALL be equal to one of the DiagnosticReport.identifier, if at least one exists The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | C | 0..* | Reference(ServiceRequestLabEu) | Element idDiagnosticReport.basedOnShort description What was requested Alternate namesRequest DefinitionDetails concerning a service requested. This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. 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. Reference(ServiceRequestLabEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idDiagnosticReport.statusShort description Status of the Report DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. DiagnosticReport.status and Composition.status shall be aligned, based on the http://hl7.eu/fhir/laboratory/ConceptMap/ConceptMap-eu-diagRptStatus2CompStatus mapping The status of the diagnostic report. DiagnosticReportStatus (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| category | Σ | 0..* | CodeableConceptIPS | Element idDiagnosticReport.categoryShort description Report Category Alternate namesDepartment, Sub-department, Service, Discipline DefinitionA code that classifies this laboratory report. Two basic categories has been selected in this guide: laboratory specialty and Study type. Laboratory specialty is characteristic of the laboratory that produced the test result while Study type is an arbitrary classificion of the test type. DiagnosticReport.category and Composition.category shall be aligned Unordered, Open, by $this(Pattern) BindingCodes for diagnostic service sections. DiagnosticServiceSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| studyType | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:studyTypeShort description The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory services, i.e., results of tests performed, could be characterized using typology of services, commonly called study types. Study type could be seen as an attribute or grouping mechanism that assigns a common clinical sense to certain types of laboratory test results., e.g., Hemoglobin, Platelet count, etc. belongs to 'Hematology study'. In comparison to the laboratory specialty which is an attribute of laboratory, study type is a categorization of laboratory service. It needs to be mentioned that classification of test to study types in not standardized. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specialty | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:specialtyShort description The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory specialty is an attribute of any laboratory setting representing professional qualification of the laboratory to execute certain kind of laboratory tests. Specialty could be used as parameter for searching/querying of laboratory test results. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| code | Σ | 1..1 | CodeableConceptIPSBinding | Element idDiagnosticReport.codeShort description Type of (Laboratory) Report Alternate namesType DefinitionSpecifies that it refers to a Laboratory Report At least one DiagnosticReport.code.coding and Composition.type.coding SHALL be equal Codes that describe Diagnostic Reports. LabReportTypesEuVs (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| subject | Σ C | 1..1 | Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) | Element idDiagnosticReport.subjectShort description Who and/or what this report is about Alternate namesPatient DefinitionWho or what this report is about. The report can be about a human patient, a living subject, a device (e.g. a machine), a location or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). SHALL know the subject context. DiagnosticReport and Composition SHALL have the same subject Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | Element idDiagnosticReport.encounterShort description The healthcare event which this Laboratory Report is about (when test ordered). Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. 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). DiagnosticReport and Composition SHALL have the same encounter. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| effective[x] | Σ | 0..1 | Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report. Alternate namesObservation time, Effective Time, Occurrence DefinitionThe 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. Need to know where in the patient history to file/present this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDiagnosticReport.issuedShort description DateTime this version was made Alternate namesDate published, Date Issued, Date Verified DefinitionThe date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. Clinicians need to be able to check the date that the report was released. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performer | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.performerShort description Responsible Diagnostic Service. Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| resultsInterpreter | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.resultsInterpreterShort description Primary result interpreter Alternate namesAnalyzed by, Reported by DefinitionThe practitioner or organization that is responsible for the report's conclusions and interpretations. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specimen | C | 0..* | Reference(SpecimenEu) | Element idDiagnosticReport.specimenShort description Specimens this report is based on. DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| result | C | 0..* | Reference(ObservationResultsLaboratoryEu) | Element idDiagnosticReport.resultShort description results Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations. Reference(ObservationResultsLaboratoryEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| imagingStudy | C | 0..0 | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| media | Σ | 0..* | BackboneElement | Element idDiagnosticReport.mediaShort description Additional data (like images, diagrams or documents) associated with this report Alternate namesDICOM, Slides, Scans, DICOM; Slides; Scans; Pictures; Documents; Diagrams DefinitionA list of additional data, other then presented form of the report, associated with this report. This data is generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Some diagnostic reports may include additional data such as images, diagrams or documents that are relevant to the report. This additional information can provide further context and support for the findings presented in the report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| comment | 0..1 | string | Element idDiagnosticReport.media.commentShort description Comment about the image or data (e.g. explanation) DefinitionAllows for a comment about the image or data, such as an explanation of its significance or context within the diagnostic report. The provider of the report should make a comment about each image or data included in the report. This comment can provide valuable context and help the reader understand the significance of the image or data in relation to the overall findings of the report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| link | Σ C | 1..1 | Reference(Media) | Element idDiagnosticReport.media.linkShort description Reference to the image or data DefinitionA reference to the image or data associated with this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data. Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. 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. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| presentedForm | C | 0..* | Attachment | Element idDiagnosticReport.presentedFormShort description Entire report as issued (pdf recommended) DefinitionRich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. "application/pdf" is recommended as the most reliable and interoperable in this context. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
| DiagnosticReportLabEu (DiagnosticReport) | C | DiagnosticReport | Element idDiagnosticReportShort description Laboratory Report DiagnosticReport Alternate namesReport, Test, Result, Results, Labs, Laboratory DefinitionLaboratory Report DiagnosticReport 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.
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.idShort description Logical id of this artifact DefinitionThe 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. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idDiagnosticReport.metaShort description Metadata about the resource DefinitionThe 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idDiagnosticReport.implicitRulesShort description A set of rules under which this content was created DefinitionA 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 cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idDiagnosticReport.languageShort description Language of the resource content DefinitionThe 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). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idDiagnosticReport.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idDiagnosticReport.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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.
| |||
| extension | C | 0..* | Extension | Element idDiagnosticReport.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| DiagnosticReportCompositionR5 | C | 0..1 | Extension(Reference(Composition)) | Element idDiagnosticReport.extension:DiagnosticReportCompositionR5Short description Associated Lab Report Composition Alternate namesextensions, user content DefinitionThis extension implements the R5 composition element. It allow to link this DiagnosticReport with the Composition documenting this Laboratory Report. 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. Extension(Reference(Composition)) Extension URLhttp://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..0 | Extension | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.urlShort description identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.compositionMappings
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idDiagnosticReport.extension:DiagnosticReportCompositionR5.value[x]Short description Reference to a Composition resource for the DiagnosticReport structure DefinitionThe Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| valueReference | Reference(CompositionLabReportEu) | Data type | ||||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | Σ | 0..* | Identifier | Element idDiagnosticReport.identifierShort description Report identifier Alternate namesReportID, Filler ID, Placer ID DefinitionIdentifiers assigned to this Laboratory Report by the performer or other systems. It shall be common to several report versions 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. Composition.identifier SHALL be equal to one of the DiagnosticReport.identifier, if at least one exists The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | C | 0..* | Reference(ServiceRequestLabEu) | Element idDiagnosticReport.basedOnShort description What was requested Alternate namesRequest DefinitionDetails concerning a service requested. This allows tracing of authorization for the report and tracking whether proposals/recommendations were acted upon. 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. Reference(ServiceRequestLabEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idDiagnosticReport.statusShort description Status of the Report DefinitionThe status of the diagnostic report. Diagnostic services routinely issue provisional/incomplete reports, and sometimes withdraw previously released reports. DiagnosticReport.status and Composition.status shall be aligned, based on the http://hl7.eu/fhir/laboratory/ConceptMap/ConceptMap-eu-diagRptStatus2CompStatus mapping The status of the diagnostic report. DiagnosticReportStatus (required) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| category | Σ | 0..* | CodeableConceptIPS | Element idDiagnosticReport.categoryShort description Report Category Alternate namesDepartment, Sub-department, Service, Discipline DefinitionA code that classifies this laboratory report. Two basic categories has been selected in this guide: laboratory specialty and Study type. Laboratory specialty is characteristic of the laboratory that produced the test result while Study type is an arbitrary classificion of the test type. DiagnosticReport.category and Composition.category shall be aligned Unordered, Open, by $this(Pattern) BindingCodes for diagnostic service sections. DiagnosticServiceSectionCodes (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| studyType | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:studyTypeShort description The way of grouping of the test results into clinically meaningful domains (e.g. hematology study, microbiology study, etc.) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory services, i.e., results of tests performed, could be characterized using typology of services, commonly called study types. Study type could be seen as an attribute or grouping mechanism that assigns a common clinical sense to certain types of laboratory test results., e.g., Hemoglobin, Platelet count, etc. belongs to 'Hematology study'. In comparison to the laboratory specialty which is an attribute of laboratory, study type is a categorization of laboratory service. It needs to be mentioned that classification of test to study types in not standardized. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specialty | Σ | 0..* | CodeableConceptBinding | Element idDiagnosticReport.category:specialtyShort description The clinical domain of the laboratory performing the observation (e.g. microbiology, toxicology, chemistry) Alternate namesDepartment, Sub-department, Service, Discipline DefinitionLaboratory specialty is an attribute of any laboratory setting representing professional qualification of the laboratory to execute certain kind of laboratory tests. Specialty could be used as parameter for searching/querying of laboratory test results. Codes for diagnostic service sections. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| code | Σ | 1..1 | CodeableConceptIPSBinding | Element idDiagnosticReport.codeShort description Type of (Laboratory) Report Alternate namesType DefinitionSpecifies that it refers to a Laboratory Report At least one DiagnosticReport.code.coding and Composition.type.coding SHALL be equal Codes that describe Diagnostic Reports. LabReportTypesEuVs (preferred) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| subject | Σ C | 1..1 | Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) | Element idDiagnosticReport.subjectShort description Who and/or what this report is about Alternate namesPatient DefinitionWho or what this report is about. The report can be about a human patient, a living subject, a device (e.g. a machine), a location or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). SHALL know the subject context. DiagnosticReport and Composition SHALL have the same subject Reference(PatientEuCore | PatientAnimalEu | Device | Group | Location) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | Element idDiagnosticReport.encounterShort description The healthcare event which this Laboratory Report is about (when test ordered). Alternate namesContext DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) which this DiagnosticReport is about. Links the request to the Encounter context. 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). DiagnosticReport and Composition SHALL have the same encounter. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| effective[x] | Σ | 0..1 | Element idDiagnosticReport.effective[x]Short description Clinically relevant time/time-period for report. Alternate namesObservation time, Effective Time, Occurrence DefinitionThe 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. Need to know where in the patient history to file/present this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| effectiveDateTime | dateTime | There are no (further) constraints on this element Data type | ||||
| effectivePeriod | Period | There are no (further) constraints on this element Data type | ||||
| issued | Σ | 0..1 | instant | There are no (further) constraints on this element Element idDiagnosticReport.issuedShort description DateTime this version was made Alternate namesDate published, Date Issued, Date Verified DefinitionThe date and time that this version of the report was made available to providers, typically after the report was reviewed and verified. Clinicians need to be able to check the date that the report was released. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performer | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.performerShort description Responsible Diagnostic Service. Alternate namesLaboratory, Service, Practitioner, Department, Company, Authorized by, Director DefinitionThe diagnostic service that is responsible for issuing the report. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| resultsInterpreter | Σ C | 0..* | Reference(CareTeam | Organization | Practitioner | PractitionerRole) | Element idDiagnosticReport.resultsInterpreterShort description Primary result interpreter Alternate namesAnalyzed by, Reported by DefinitionThe practitioner or organization that is responsible for the report's conclusions and interpretations. 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. If a DiagnosticReport.resultsInterpreter exists this is expected to be a Composition.author; otherwise a DiagnosticReport.performer should be an author. Reference(CareTeam | Organization | Practitioner | PractitionerRole) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| specimen | C | 0..* | Reference(SpecimenEu) | Element idDiagnosticReport.specimenShort description Specimens this report is based on. DefinitionDetails about the specimens on which this diagnostic report is based. Need to be able to report information about the collected specimens on which the report is based. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| result | C | 0..* | Reference(ObservationResultsLaboratoryEu) | Element idDiagnosticReport.resultShort description results Alternate namesData, Atomic Value, Result, Atomic result, Data, Test, Analyte, Battery, Organizer DefinitionObservations that are part of this diagnostic report. Need to support individual results, or groups of results, where the result grouping is arbitrary, but meaningful. Observations can contain observations. Reference(ObservationResultsLaboratoryEu) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| imagingStudy | C | 0..0 | Reference(ImagingStudy) | There are no (further) constraints on this element Element idDiagnosticReport.imagingStudyShort description Reference to full details of imaging associated with the diagnostic report DefinitionOne 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| media | Σ | 0..* | BackboneElement | Element idDiagnosticReport.mediaShort description Additional data (like images, diagrams or documents) associated with this report Alternate namesDICOM, Slides, Scans, DICOM; Slides; Scans; Pictures; Documents; Diagrams DefinitionA list of additional data, other then presented form of the report, associated with this report. This data is generally created during the diagnostic process, and may be directly of the patient, or of treated specimens (i.e. slides of interest). Some diagnostic reports may include additional data such as images, diagrams or documents that are relevant to the report. This additional information can provide further context and support for the findings presented in the report. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| id | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.media.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.extensionShort description Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idDiagnosticReport.media.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| comment | 0..1 | string | Element idDiagnosticReport.media.commentShort description Comment about the image or data (e.g. explanation) DefinitionAllows for a comment about the image or data, such as an explanation of its significance or context within the diagnostic report. The provider of the report should make a comment about each image or data included in the report. This comment can provide valuable context and help the reader understand the significance of the image or data in relation to the overall findings of the report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| link | Σ C | 1..1 | Reference(Media) | Element idDiagnosticReport.media.linkShort description Reference to the image or data DefinitionA reference to the image or data associated with this report. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| conclusion | 0..1 | string | There are no (further) constraints on this element Element idDiagnosticReport.conclusionShort description Clinical conclusion (interpretation) of test results Alternate namesReport DefinitionConcise and clinically contextualized summary conclusion (interpretation/impression) of the diagnostic report. Need to be able to provide a conclusion that is not lost among the basic result data. Note that FHIR strings SHALL NOT exceed 1MB in size The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| conclusionCode | 0..* | CodeableConcept | There are no (further) constraints on this element Element idDiagnosticReport.conclusionCodeShort description Codes for the clinical conclusion of test results DefinitionOne or more codes that represent the summary conclusion (interpretation/impression) of the diagnostic report. 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. Diagnosis codes provided as adjuncts to the report. SNOMEDCTClinicalFindings (example) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| presentedForm | C | 0..* | Attachment | Element idDiagnosticReport.presentedFormShort description Entire report as issued (pdf recommended) DefinitionRich text representation of the entire result as issued by the diagnostic service. Multiple formats are allowed but they SHALL be semantically equivalent. Gives laboratory the ability to provide its own fully formatted report for clinical fidelity. "application/pdf" is recommended as the most reliable and interoperable in this context. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
|
Additional Guidance
meta.profile
This element SHALL be populated with a value of http://hl7.eu/fhir/laboratory/StructureDefinition/DiagnosticReport-eu-lab
extension:noteR5
General comments about the test report. Refer to Extension UKCore-DiagnosticReportNote for further information.
Information relating specifically to the report conclusion SHOULD be conveyed using DiagnosticReport.conclusion and/or DiagnosticReport.conclusionCode.
Notes may be captured at a number of levels within a test report. There may also be notes related to the specimen, test group or individual test results. It is the consuming systems responsibility to ensure all relevant notes are displayed to the user.
identifier
This element SHOULD be populated with at least one unique, persistent business identifier for the test report, assigned by the performing laboratory.
basedOn
Reference to the ServiceRequest.
status
This element SHALL be populated with a value taken from the DiagnosticReportStatus ValueSet.
category
As a minimum, this element SHOULD be populated with the following value, taken from the LabSpecialtyEuVs ValueSet:
"category": { "coding": [ { "system": "http://snomed.info/sct", "code": "394915009", "display": "General pathology (speciality)" } ] }
code
This element SHALL be populated with the following value, taken from the UKCoreReportCode ValueSet.
"code": { "coding": [ { "system": "http://snomed.info/sct", "code": "721981007", "display": "Diagnostic studies report" } ] }
Note: The clinical code and name of a test result or a test group are defined in the code element of the corresponding Observation resource.
subject
Reference to the Patient.
issued
The date and time the test report was issued.
performer
Reference to the performing Organization.
specimen
Reference(s) to the Specimen(s) used during testing.
result
References to the results included in the test report.
The references may be to individual test results, test groups or a combination of these. Test results and test groups are represented using the Observation resource. Refer to England-Observation-Lab-Pathology (Test Result) and England-Observation-Lab-Pathology (Test Group) for further information.
Test results which are part of a test group will not be referenced by this element; the reference will be to the test group which will in turn reference the associated test results.
conclusion
A clinical interpretation/summary of the test results in a free text format.
conclusionCode
A coded finding of the test report.