| # | | 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 | | Batch Analysis | hl7.fhir.us.pq-cmc#current | R5 | Batch or lot release testing to ensure that pharmaceutical products meet the product specification. |
| 4 | | BioSignalReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 5 | | Breast Imaging Report | hl7.fhir.us.breast-radiology#current | R4 | Breast Imaging Diagnostic Report. |
| 6 | | 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. |
| 7 | | 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. |
| 8 | | 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. |
| 9 | | 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. |
| 10 | | DiagnosticReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 11 | | 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. |
| 12 | | ImagingReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 13 | | LaboratoryReport-IEHR | fhir.uv.crossborderdataexchange#current | R4 | |
| 14 | | 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. |
| 15 | | 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 |
| 16 | | 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. |
| 17 | | 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. |
| 18 | | 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. |
| 19 | | 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. |
| 20 | | 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). |
| 21 | | 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. |
| 22 | | 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. |
| 23 | | 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). |
| 24 | | 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 |
| DiagnosticReport |
C |
D |
|
I |
|
|
|
|
|
|
|
I |
|
|
D |
|
|
|
|
|
I D |
I D |
|
|
| DiagnosticReport.imagingStudy |
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
C |
| DiagnosticReport.id |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.context |
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.image |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.meta |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.meta.profile |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
| DiagnosticReport.implicitRules |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
| DiagnosticReport.language |
|
|
|
|
|
|
|
|
|
C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.text |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.contained |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.extension |
|
|
S C (2) |
|
|
|
|
S D |
D |
S C (3) |
|
|
|
S (2) |
|
S C D (3) |
|
|
S C D (4) |
|
|
|
|
|
| DiagnosticReport.modifierExtension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
| DiagnosticReport.identifier |
|
|
C |
|
|
|
|
|
|
C D |
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
| DiagnosticReport.basedOn |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
S C (2) |
|
|
|
|
|
|
|
|
|
| DiagnosticReport.status |
C B M |
C I B M |
D |
|
|
F |
|
|
|
F |
|
|
|
|
B M |
|
|
|
D |
|
B M |
B M |
|
|
| DiagnosticReport.category |
C F |
C B M |
|
C B M |
S C F (2) |
|
|
|
|
|
S (2) |
C B M |
|
|
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 |
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.category.coding.code |
|
|
|
|
|
|
|
|
|
|
|
|
F |
|
|
|
|
|
|
|
|
|
|
F |
| DiagnosticReport.category.coding.system |
|
|
|
|
|
|
|
|
|
|
|
|
F |
|
|
|
|
|
|
|
|
|
|
F |
| DiagnosticReport.code |
C D B M |
C D B M |
|
|
B M |
|
|
|
|
|
|
|
|
|
B M |
|
|
C D B M |
|
F |
D B M |
D B M |
|
|
| DiagnosticReport.code.text |
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
| DiagnosticReport.code.coding |
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
| DiagnosticReport.subject |
C |
C |
C |
|
|
|
|
D |
D |
C |
|
|
|
|
|
|
|
|
C |
|
C |
C |
|
|
| DiagnosticReport.subject.reference |
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.encounter |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
|
|
| DiagnosticReport.effective[x] |
C D |
C D |
S C D (2) |
|
|
|
|
|
|
C |
|
|
|
|
|
C |
|
C |
|
|
|
|
I |
|
| DiagnosticReport.issued |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.performer |
C |
C |
C D |
|
|
|
|
|
|
C D |
|
|
|
|
|
C |
|
|
C D |
|
|
|
|
|
| DiagnosticReport.performer.actor |
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.resultsInterpreter |
|
|
|
|
|
|
|
|
|
C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.specimen |
|
|
|
C |
C |
|
|
C D |
D |
|
|
C |
C |
|
|
|
|
|
|
C |
|
|
|
C |
| DiagnosticReport.result |
C |
|
|
C |
C |
C |
C |
D |
D |
|
S (3) |
|
|
|
S C (2) |
|
|
|
|
S C D (4) |
|
|
|
|
| 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.composition |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.conclusion |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.conclusionCode |
|
|
|
|
S C D B M (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm |
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
I |
C |
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.url |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DiagnosticReport.presentedForm.contentType |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F D |
|
|
|
|
|
|
|
|
|