| # | | Name | Source | Ver | Description |
| 1 | | Argonaut DiagnosticReport Profile | fhir.argonaut.r2#1.0.0 | R2 | |
| 2 | | Argonaut Imaging Reports | fhir.argonaut.clinicalnotes#1.0.0 | R3 | |
| 3 | | AU Base Diagnostic Imaging Report | hl7.fhir.au.base#current | R4 | This profile defines a diagnostic report structure to represent a diagnostic imaging report issued by a diagnostic service provider in an Australian context. |
| 4 | | AU Base Diagnostic Report | hl7.fhir.au.base#current | R4 | This profile defines a diagnostic report structure that localises core concepts, including identifiers and terminology, for use in an Australian context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. [profiling](http://hl7.org/fhir/profiling.html), about how to support these concepts for specific implementation needs. |
| 5 | | AU Base Pathology Report | hl7.fhir.au.base#current | R4 | This profile defines a diagnostic report structure to represent a pathology report issued by a diagnostic service provider in an Australian context. This profile is intended to be capable of supporting reporting for all pathology disciplines (e.g. including microbiology, histopathology, cytology, blood transfusion) with the exception of genomics.
This profile does not provide full support for structured pathology reporting. It is expected that this support is best handled by a set of profiles that represent the structured reporting requirements for each specific protocol (see for example [RCPA’s structured pathology reporting of cancer](https://www.rcpa.edu.au/Library/Practising-Pathology/Structured-Pathology-Reporting-of-Cancer)); this is not in the scope of this implementation guide at this time. |
| 6 | | AU Core DiagnosticReport | hl7.fhir.au.core#current | R4 | This profile sets minimum expectations for a DiagnosticReport resource to record, search, and fetch diagnostic reports associated with a patient. It is based on the [AU Base Diagnostic Report](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-diagnosticreport.html) profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the DiagnosticReport when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context. |
| 7 | | Batch Analysis | hl7.fhir.us.pq-cmc#current | R5 | Batch or lot release testing to ensure that pharmaceutical products meet the product specification. |
| 8 | | BeLaboratoryReport | hl7.fhir.be.lab#current | R4 | Belgian profile for a laboratory report |
| 9 | | BioSignalReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 10 | | Breast Imaging Report | hl7.fhir.us.breast-radiology#current | R4 | Breast Imaging Diagnostic Report. |
| 11 | | CH ELM DiagnosticReport: Laboratory Report | ch.fhir.ig.ch-elm#current | R4 | This CH ELM base profile constrains the DiagnosticReport resource for the purpose of laboratory test reports. |
| 12 | | CH Lab DiagnosticReport: Laboratory Report | ch.fhir.ig.ch-lab-report#current | R4 | This profile constrains the DiagnosticReport resource for the purpose of laboratory test reports in Switzerland. |
| 13 | | CH Lab DiagnosticReport: Laboratory Report | ch.fhir.ig.ch-laboratory-report#current | R4 | This profile constrains the DiagnosticReport resource for the purpose of laboratory test reports in Switzerland. |
| 14 | | Diagnostic Report for Report and Note Exchange Profile | hl7.fhir.ca.baseline#current | R4 | Proposed constraints and extensions on the Diagnostic Report Resource to support collection of diagnostic report information for reports and notes. Generated as a first step toward creating a set of Canadian Baseline FHIR profiles. |
| 15 | | DiagnosticReport (AU IPS) | hl7.fhir.au.ips#current | R4 | This profile is based on the UV profile, with Australian rules added as well (by reference to the Australian profile) |
| 16 | | DiagnosticReport (IPS) | hl7.fhir.uv.ips#current | R4 | This profile constrains the DiagnosticReport resource to represent diagnostic test and procedure reports in a patient summary. |
| 17 | | DiagnosticReport - At-Home In-Vitro Results | hl7.fhir.us.home-lab-report#current | R4 | This profile constrains the US Core Diagnostic Report for Laboratory Results profile to At-Home In-Vitro Tests. |
| 18 | | DiagnosticReport - At-Home In-Vitro Results - COVID-19 | hl7.fhir.us.home-lab-report#current | R4 | This profile further constrains the DiagnosticReport - At-Home In-Vitro Results profile to COVID-19 At-Home In-Vitro Tests. |
| 19 | | DiagnosticReport - Lab Report | hl7.fhir.it.lab-report#current | R4 | Descrizione della risorsa DiagnosticReport per la descrizione delle informazioni cliniche del dominio di Lab Report. |
| 20 | | DiagnosticReport - Stability Study Results dx-PQ | hl7.fhir.uv.dx-pq#current | R5 | Section 11 - Stability Study - Results |
| 21 | | DiagnosticReport - Toxicology Lab Result to MDI | hl7.fhir.us.mdi#current | R4 | This profile contains constraints to the US Core Diagnostic Report Profile to address the use case for sending data from a forensic toxicology LIMS to an MDI CMS.
Each analyzed specimen, represented by a Specimen - Toxicology Lab resource, must be referenced by at least one Observation - Toxicology Lab Result and may be referenced by more than one Observation - Toxicology Lab Result.
For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note. |
| 22 | | DiagnosticReport - Toxicology Lab Result to MDI | hl7.fhir.us.vrsandbox#current | R4 | This profile contains constraints to the US Core Diagnostic Report Profile to address the use case for sending data from a forensic toxicology LIMS to an MDI CMS.
Each analyzed specimen, represented by a Specimen - Toxicology Lab resource, must be referenced by at least one Observation - Toxicology Lab Result and may be referenced by more than one Observation - Toxicology Lab Result.
For specimens received but not analyzed, the laboratory should provide a reason for no analysis in the DiagnosticReport.conclusion and/or each unanalyzed specimen’s Specimen - Toxicology Lab Specimen.note. |
| 23 | | DiagnosticReport Profile for Results Reporting | hl7.fhir.ca.baseline#current | R4 | Proposed constraints on the DiagnosticReport resource for the minimal set of data to query and retrieve diagnostic reports associated with laboratory and other results |
| 24 | | DiagnosticReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 25 | | DiagnosticReport: Laboratory Report | hl7.fhir.eu.laboratory#current | R4 | DiagnosticReport used to represent an entry of a Laboratory Report, including its context, for the scope of the HL7 Europe project. |
| 26 | | DiagnosticReport: Laboratory Report | hl7.eu.fhir.xpandh.lab#current | R4 | CDiagnosticReport used to represent an entry of a Laboratory Report, including its context, for the scope of the XPanDH project. |
| 27 | | DiagnosticReport: Laboratory Report - Microbiology Culture & Susceptibility | hl7.fhir.eu.laboratory#current | R4 | DiagnosticReport used to represent an entry of a specialized Laboratory Report for representing microbiology culture & susceptibility results, including its context, for the scope of the HL7 Europe project. |
| 28 | | FHIRcast Diagnostic Report for Open Events | hl7.fhir.uv.fhircast#current | R4B | Provides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-open events.
At least one business identifier of the DiagnosticReport SHALL be provided in a [FHIR resource]-open request.
Typically the report is associated with an order from an information system. In this case the accession number of the order is provided in the DiagnosticReport's `basedOn` array attribute as a reference using a ServiceRequest reference type and the “ACSN” identifier type. The accession number SHALL be included as a business identifier if it is known.
A reporting system may also include its own identifier and should use an appropriate identifier type and system when supplying such a business identifier.
In radiology reports or other image related uses of FHIRcast, at least one imaging study would likely be the subject of the report and included in the event's context. In this case, the reference to one or more ImagingStudy resources would be provided.
**FHIR R4 versus FHIR R5**
In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change.
In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute.
Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support. |
| 29 | | FHIRcast DiagnosticReport for Close Events | hl7.fhir.uv.fhircast#current | R4B | Provides guidance as to which DiagnosticReport attributes should be present and considerations as to how each attribute should be valued in all [FHIR resource]-close events.
**FHIR R4 versus FHIR R5**
In the FHIR R4 DiagnosticReport resource image study references would be placed in the `imagingStudy` attribute. In a FHIR R5 (or above) DiagnosticReport this attribute has been renamed `study` since the allowed reference types has been expanded to include references to GenomicStudy resources. This is obviously a breaking change.
In FHIRcast deployments based on FHIR R5, the attribute `study` SHALL be used rather than the `imagingStudy` attribute.
Additionally FHIR R5 includes a `supportingInfo` attribute. While not yet formally provided for in FHIR R5, it has been recommended that the next release of FHIR allow an ImagingStudy reference be included in this attribute so that the DiagnosticReport could indicate one or more image studies were consulted during the creation of the report. As such in FHIR R5 deployments, this field is considered labeled as must support. |
| 30 | | Genomics Report | hl7.fhir.uv.genomics-reporting#current | R4 | Genomics profile of DiagnosticReport. |
| 31 | | Genomics Report Profile | hl7.fhir.us.mcode#current | R4 | Genomic analysis summary report. The report may include one or more tests, with two distinct test types. The first type is a targeted mutation test, where a specific mutation on a specific gene is tested for. The result is either positive or negative for that mutation. The second type is a more general test for variants. This type of test returns the identity of variants found in a certain region of the genome. |
| 32 | | IHE SDC/eCP on FHIR DiagnosticReport | hl7.fhir.uv.ihe-sdc-ecc#current | R4 | A DiagnosticReport Profile meant to capture what should be represented in a report parsed from an IHE SDC Form |
| 33 | | ImagingReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 34 | | LaboratoryReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 35 | | MIPHRDiagnosticReportImaging | hl7.fhir.mi.phr#current | R4 | |
| 36 | | MIPHRDiagnosticReportPathology | hl7.fhir.mi.phr#current | R4 | |
| 37 | | Multiple Chronic Condition Care Plan Diagnostic Report and Note | hl7.fhir.us.mcc#current | R4 | This profile constrains [US Core Diagnostic Report and Note](http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note) for use in the MCC FHIR Care Plan or other FHIR Care Plans. |
| 38 | | OCT macula Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for an OCT macula |
| 39 | | OCT RNFL Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for an OCT RNFL |
| 40 | | Ophthalmic diagnostic test report | hl7.fhir.uv.eyecare#current | R4 | Base profile specifically constrained for describing ophthalmic reports |
| 41 | | PA Intervention Report | hl7.fhir.us.physical-activity#current | R4 | Conveys a summary of the interventions and patient interactions that have occurred over the course of the services delivered by a Service Provider, typically in response to a referral |
| 42 | | Personal Functioning and Engagement Narrative History of Status | hl7.fhir.us.pacio-pfe#current | R4 | An exchange of a narrative summary regarding the most recent prior status immediately preceding the current admission, illness, or exacerbation for a patient. The use of this profile is encouraged in the absence of formal prior level assessments. For formal assessments conducted with for example, an assessment instrument, use the [collection](StructureDefinition-pfe-collection.html) and [single observation](StructureDefinition-pfe-observation-single.html) profiles defined in this IG to capture assessment data. |
| 43 | | QICore DiagnosticReport Profile for Laboratory Results Reporting | hl7.fhir.us.qicore#current | R4 | Profile of DiagnosticReport for laboratory results for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors. |
| 44 | | QICore DiagnosticReport Profile for Report and Note Exchange | hl7.fhir.us.qicore#current | R4 | Profile of DiagnosticReport for Note exchange for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors. |
| 45 | | Stability Study Interval Report | hl7.fhir.us.pq-cmc#current | R5 | Batch or lot stability testing to ensure that pharmaceutical products continue to meet the product specification or determine the expiry period. |
| 46 | | Tumor Morphology | hl7.fhir.us.pedcan#current | R4 | ICD-O-3 morphology determined from examination of tumor sample, composed of three parts: histologic type, the malignant potential of the tumor (behavior) and the tumor grade (degree of differentiation). |
| 47 | | US Core DiagnosticReport Profile for Laboratory Results Reporting | hl7.fhir.us.core#current | R4 | Laboratory results are grouped and summarized using the DiagnosticReport resource which typically reference Observation resource(s). Each Observation resource represents an individual laboratory test and result value or component result values, or a nested panel (such as a microbial susceptibility panel) which references other observations. They can also be presented in report form or as free text. This profile sets minimum expectations for the DiagnosticReport resource to record, search, and fetch laboratory results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. |
| 48 | | US Core DiagnosticReport Profile for Report and Note Exchange | hl7.fhir.us.core#current | R4 | To promote interoperability and adoption through common implementation, this profile sets minimum expectations for searching and fetching Diagnostic Reports and Notes using the DiagnosticReport resource. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present and constrains the way the elements are used when using the profile. It provides the floor for standards development for specific use cases. Prior to reviewing this profile, implementers are encouraged to read the Clinical Notes Guidance to understand the overlap of US Core DiagnosticReport Profile for Report and Note exchange and US Core DocumentReference Profile. |
| 49 | | US Pathology Diagnostic Report | hl7.fhir.us.cancer-reporting#current | R4 | It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD). |
| 50 | | VF Diagnostic Report | hl7.fhir.uv.eyecare#current | R4 | The DiagnosticReport profile for a visual field DT |
| 51 | | VitalSignReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
| DiagnosticReport |
C |
D |
|
|
|
I |
|
|
I |
|
|
I |
I |
D |
|
|
|
|
D |
|
|
|
D |
|
D |
|
D |
I |
|
|
|
|
I |
|
|
|
|
|
|
|
D |
|
|
|
|
|
I D |
I D |
|
|
|
| DiagnosticReport.imagingStudy |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
C |
|
|
D |
D |
|
|
|
|
C |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
| DiagnosticReport.imagingStudy.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.id |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C D |
C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.context |
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.image |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.meta |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.meta.profile |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
| DiagnosticReport.implicitRules |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.language |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.text |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.text.status |
|
|
|
|
|
|
|
F |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.contained |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.extension |
|
|
|
|
|
|
S C (2) |
S C (2) |
|
|
|
S C (2) |
|
|
|
|
|
|
S C (2) |
|
S D |
D |
|
S C (3) |
S C D (2) |
|
|
|
|
S C D (6) |
|
|
|
|
|
|
S (2) |
|
|
|
|
S C D (3) |
|
|
S C D (4) |
|
|
|
|
|
|
| DiagnosticReport.extension.value[x] |
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
C |
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.modifierExtension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.identifier |
|
|
D |
D |
D |
C |
C |
S C D (2) |
|
|
|
|
|
|
|
|
|
|
I |
|
|
|
|
C D |
I D |
|
|
D |
D |
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
| DiagnosticReport.identifier.value |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.identifier.system |
|
|
|
|
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.basedOn |
|
|
|
|
|
|
|
C D |
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D |
D |
|
|
|
|
|
|
|
|
|
|
|
S C (2) |
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.status |
C B M |
C I B M |
|
|
|
B M |
D |
D |
|
|
F |
|
|
B M |
|
F |
F |
|
I B M |
|
|
|
|
F |
I |
|
|
D |
|
|
|
|
|
|
F |
F |
|
|
|
|
B M |
|
|
|
D |
|
B M |
B M |
|
|
|
| DiagnosticReport.category |
C F |
C B M |
C D |
B M |
C B M |
C B M |
|
C D |
C B M |
S C F (2) |
|
F |
|
C D |
|
C |
|
|
C I D B M |
|
|
|
S C D (2) |
|
S C I D B M (3) |
|
|
|
|
S C (2) |
S (2) |
|
C B M |
|
C B M |
C B M |
|
|
|
C |
S C F D (2) |
S C F B M (3) |
S F B M (2) |
S C |
|
|
S C F (2) |
S C B M (2) |
|
|
|
| DiagnosticReport.category.coding |
|
|
S B M (2) |
|
|
|
|
S C (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C F |
C |
|
|
|
C |
C |
|
|
|
S C (2) |
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.category.coding.display |
|
|
|
|
|
|
|
C F (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.category.coding.code |
|
|
|
|
|
|
|
C F (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F |
C |
C |
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
F |
| DiagnosticReport.category.coding.system |
|
|
C F |
|
|
|
|
C F (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
F |
C F |
C F |
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
F |
| DiagnosticReport.code |
C D B M |
C D B M |
B M |
B M |
B M |
|
|
|
|
B M |
|
F |
|
D |
|
|
|
|
I |
|
|
|
S C D (3) |
|
I D B M |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
B M |
|
|
C D B M |
|
F |
D B M |
D B M |
|
|
|
| DiagnosticReport.code.text |
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
| DiagnosticReport.code.coding |
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S C (2) |
S C (2) |
|
|
|
|
|
C |
|
|
|
|
S C (2) |
|
| DiagnosticReport.code.coding.display |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.code.coding.code |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F |
|
|
|
C F (2) |
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
C F |
C F |
|
|
|
|
|
|
|
|
|
|
C F |
|
| DiagnosticReport.code.coding.system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F |
|
|
|
C F (2) |
|
|
|
|
|
|
|
|
|
|
|
C F |
C F |
|
C F |
C F |
|
|
|
|
|
|
|
|
|
|
C F |
|
| DiagnosticReport.subject |
C |
C |
C |
|
C |
C |
C |
C |
|
|
C |
|
|
C |
|
C |
|
|
C I |
|
D |
D |
|
C |
C I D |
|
|
C D |
C D |
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
C |
|
C |
C |
|
|
|
| DiagnosticReport.subject.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.encounter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I |
|
|
|
|
|
I D |
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
D |
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.encounter.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.effective[x] |
C D |
C D |
C |
|
C |
C I |
S C D (2) |
D |
|
|
|
|
|
C |
|
C |
|
|
|
|
|
|
C D |
C |
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
C |
|
C |
|
|
|
|
I |
|
|
| DiagnosticReport.effective[x].extension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.issued |
C |
C |
|
|
|
C |
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.performer |
C |
C |
|
|
|
C |
C D |
C D |
|
|
C |
|
|
|
|
|
|
|
I D |
|
|
|
|
C D |
I |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
C D |
|
|
|
|
|
|
| DiagnosticReport.performer.actor |
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.resultsInterpreter |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
I |
|
|
|
|
C D |
I |
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.resultsInterpreter.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.specimen |
|
|
|
|
|
|
|
|
C |
C |
C |
|
|
|
|
|
|
|
|
|
C D |
D |
S C D (3) |
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
C |
| DiagnosticReport.result |
C |
|
|
|
|
|
|
|
C |
C |
C |
|
|
|
S |
S D (2) |
C |
C |
|
|
D |
D |
S C D (3) |
|
|
|
|
|
|
S C (10) |
S (3) |
C |
|
|
|
|
|
|
|
|
S C (2) |
|
|
|
|
S C D (4) |
|
|
|
|
|
| DiagnosticReport.result.reference |
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.note |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.study |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.supportingInfo |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.supportingInfo.extension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.supportingInfo.modifierExtension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.supportingInfo.type |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.supportingInfo.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.media |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
| DiagnosticReport.media.extension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.media.modifierExtension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.media.comment |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.media.link |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.media.link.reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.composition |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.conclusion |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.conclusionCode |
|
|
B M |
B M |
B M |
|
|
|
|
S C D B M (2) |
|
|
|
|
|
|
|
|
|
|
|
|
D B M |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C D |
|
|
|
|
|
|
|
|
I |
C |
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.url |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.contentType |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F D |
|
|
|
|
|
|
|
|
|
|