Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/DiagnosticReport
copyright	Used by permission of HL7 International, all rights reserved Creative Commons License
date	2019-05-21	2022-04-20	Values Differ
description	Defines constraints and extensions on the DiagnosticReport resource for the minimal set of data to query and retrieve diagnostic reports associated with clinical notes for a patient	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.	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreDiagnosticReportProfileNoteExchange
publisher	HL7 International - US Realm Steering Committee	HL7 International - Cross-Group Projects	Values Differ
purpose
status	active
title	US Core DiagnosticReport Profile for Report and Note exchange	US Core DiagnosticReport Profile for Report and Note Exchange	Values Differ
type	DiagnosticReport
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note
version	4.0.0	6.1.0-snapshot1	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
DiagnosticReport		0..*	DiagnosticReport	US Core Diagnostic Report Profile for Report and Note exchange	C	0..*	DiagnosticReport	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports us-core-10: effective[x] SHALL be present if the status is 'partial', 'preliminary', 'final', 'amended', 'corrected' or 'appended'	Elements differ in short: 'US Core Diagnostic Report Profile for Report and Note exchange' vs 'A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports' Elements differ in definition: 'The US Core Diagnostic Report Profile for Report and Note exchange is based upon the requirements of the Argonauts to exchang imaginge reports.' vs '\-' Elements differ in comments: 'This is intended to capture a single report and is not suitable for use in displaying summary information that covers multiple reports. For example, this resource has not been designed for laboratory cumulative reporting formats nor detailed structured reports for sequencing.' vs '\-'
id	Σ	0..1	string	Logical id of this artifact	Σ	0..1	id	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding		0..1	code	Language of the resource content Binding: ?? (preferred): A human language. Additional Bindings Purpose ?? Max Binding
text		0..1	Narrative	Text summary of the resource, for human interpretation		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Business identifier for report	Σ	0..*	Identifier	Business identifier for report
basedOn		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)	What was requested		0..*	Reference(CarePlan | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)	What was requested
status	?!SΣ	1..1	code	registered | partial | preliminary | final + Binding: ?? (required)	?!SΣC	1..1	code	(USCDI) registered | partial | preliminary | final + Binding: ?? (required)	Elements differ in short: 'registered | partial | preliminary | final +' vs '(USCDI) registered | partial | preliminary | final +'
category	SΣ	1..*	CodeableConcept	Service category Binding: ?? (extensible)	SΣ	1..*	CodeableConcept	(USCDI) Service category Slice: Unordered, Open by pattern:$this Binding: ?? (example): Codes for diagnostic service sections.	Elements differ in short: 'Service category' vs '(USCDI) Service category'
code	SΣ	1..1	CodeableConcept	US Core Report Code Binding: ?? (extensible): LOINC codes	SΣ	1..1	CodeableConcept	(USCDI) US Core Report Code Binding: ?? (extensible): LOINC codes	Elements differ in short: 'US Core Report Code' vs '(USCDI) US Core Report Code' Elements differ in comments: 'UsageNote= The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists.' vs 'The typical patterns for codes are: 1) a LOINC code either as a translation from a "local" code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists.'
subject	SΣ	1..1	Reference(US Core Patient Profile)	The subject of the report - usually, but not always, the patient	SΣ	1..1	Reference(US Core Patient Profile)	(USCDI) The subject of the report - usually, but not always, the patient	Elements differ in short: 'The subject of the report - usually, but not always, the patient' vs '(USCDI) The subject of the report - usually, but not always, the patient' Elements differ in definition: 'The subject of the report. Usually, but not always, this is a patient. However diagnostic services also perform analyses on specimens collected from a variety of other sources.' vs 'The subject of the report. Usually, but not always, this is a patient. However, diagnostic services also perform analyses on specimens collected from a variety of other sources.'
encounter	SΣ	0..1	Reference(US Core Encounter Profile)	Health care event when test ordered	SΣ	0..1	Reference(US Core Encounter Profile)	(USCDI) Health care event when test ordered	Elements differ in short: 'Health care event when test ordered' vs '(USCDI) Health care event when test ordered'
effective[x]	SΣ	1..1	dateTime S, Period	Clinically relevant time/time-period for report	SΣC	0..1	dateTime S, Period	(USCDI) Diagnostically relevant time (typically the time of the procedure)	Elements differ in short: 'Clinically relevant time/time-period for report' vs '(USCDI) Diagnostically relevant time (typically the time of the procedure)' Element minimum cardinalities differ: '1' vs '0'
issued	SΣ	0..1	instant	DateTime this version was made	SΣ	0..1	instant	(USCDI) DateTime this version was made	Elements differ in short: 'DateTime this version was made' vs '(USCDI) DateTime this version was made'
performer	SΣ	0..*	Reference(US Core Practitioner Profile S | US Core Organization Profile S | US Core PractitionerRole Profile | US Core CareTeam Profile)	Responsible Diagnostic Service	SΣ	0..*	Reference(US Core Practitioner Profile S | US Core Organization Profile S | US Core PractitionerRole Profile | US Core CareTeam Profile)	(USCDI) Responsible Diagnostic Service	Elements differ in short: 'Responsible Diagnostic Service' vs '(USCDI) Responsible Diagnostic Service'
resultsInterpreter	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam)	Primary result interpreter	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam)	Primary result interpreter
specimen		0..*	Reference(Specimen)	Specimens this report is based on		0..*	Reference(Specimen)	Specimens this report is based on
result		0..*	Reference(Observation)	Observations	S	0..*	Reference(US Core Laboratory Result Observation Profile S | US Core Observation Clinical Result Profile S | Observation)	(USCDI) Observations	Elements differ in short: 'Observations' vs '(USCDI) Observations' Elements differ in definition for mustSupport: 'false' vs 'true'
imagingStudy		0..*	Reference(ImagingStudy)	Reference to full details of imaging associated with the diagnostic report		0..*	Reference(ImagingStudy)	Reference to full details of imaging associated with the diagnostic report
media	Σ	0..*	BackboneElement	Key images associated with this report	SΣ	0..*	BackboneElement	(USCDI) Key images associated with this report	Elements differ in short: 'Key images associated with this report' vs '(USCDI) Key images associated with this report' Elements differ in definition for mustSupport: 'false' vs 'true'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
comment		0..1	string	Comment about the image (e.g. explanation)		0..1	string	Comment about the image (e.g. explanation)
link	Σ	1..1	Reference(Media)	Reference to the image source	SΣ	1..1	Reference(Media)	(USCDI) Reference to the image source	Elements differ in short: 'Reference to the image source' vs '(USCDI) Reference to the image source' Elements differ in definition for mustSupport: 'false' vs 'true'
conclusion		0..1	string	Clinical conclusion (interpretation) of test results		0..1	string	Clinical conclusion (interpretation) of test results
conclusionCode		0..*	CodeableConcept	Codes for the clinical conclusion of test results Binding: ?? (example): Diagnosis codes provided as adjuncts to the report.		0..*	CodeableConcept	Codes for the clinical conclusion of test results Binding: ?? (example): Diagnosis codes provided as adjuncts to the report.
presentedForm	S	0..*	Attachment	Entire report as issued	S	0..*	Attachment	(USCDI) Entire report as issued	Elements differ in short: 'Entire report as issued' vs '(USCDI) Entire report as issued'
Documentation for this format