Profile Comparison between http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-diagnostic-report vs http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-diagnostic-report

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/us/core/StructureDefinition/us-core-diagnosticreport-note
copyright		<copyright value="This material contains content from LOINC (http://loinc.org ). Refer to terminology.hl7.org for copyright information. LOINC® is available at no cost under the license at http://loinc.org/license . LOINC® is a registered United States trademark of Regenstrief Institute, Inc."/>	Added the item '<copyright value="This material contains content from LOINC (http://loinc.org ). Refer to terminology.hl7.org for copyright information. LOINC® is available at no cost under the license at http://loinc.org/license . LOINC® is a registered United States trademark of Regenstrief Institute, Inc."/>'
date	2021-08-12T15:45:55+00:00	2023-07-11T15:48:53+00:00	Values Differ
description		It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD).	Added the item 'It is expected that labs will populate dateTimes with the most specific time information known when sending to EHRs (YYYY-MM-DD).'
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USPathologyDiagnosticReport
publisher	HL7 International - Orders and Observations	HL7 Orders and Observations Work Group	Values Differ
purpose
status	active
title	US Pathology Diagnostic Report
type	DiagnosticReport
url	http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-diagnostic-report
version	0.1.0	1.0.0	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..*	USCoreDiagnosticReportProfileNoteExchange	US Core Diagnostic Report Profile for Report and Note exchange	C	0..*	USCoreDiagnosticReportProfileNoteExchange	A Diagnostic report - a combination of request information, atomic results, images, interpretation, as well as formatted reports	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(US Pathology Service Request)	What was requested	Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/CarePlan], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImmunizationRecommendation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MedicationRequest], CanonicalType[http://hl7.org/fhir/StructureDefinition/NutritionOrder], CanonicalType[http://hl7.org/fhir/StructureDefinition/ServiceRequest]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/cancer-reporting/StructureDefinition/us-pathology-service-request]])
status	?!SΣ	1..1	code	registered | partial | preliminary | final + Binding: ?? (required)	?!SΣC	1..1	code	registered | partial | preliminary | final + Binding: ?? (required)
category	SΣ	1..*	CodeableConcept	Service category Binding: ?? (extensible)	SΣ	1..*	CodeableConcept	Service category Slice: Unordered, Open by pattern:$this Binding: ?? (example): Codes for diagnostic service sections.
code	SΣ	1..1	CodeableConcept	US Core Report Code Binding: ?? (extensible): LOINC codes	SΣ	1..1	CodeableConcept	US Core Report Code Binding: ?? (extensible): LOINC codes	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)	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)	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	Diagnostically relevant time (typically the time of the procedure) path-reporting-1: effectiveDateTime SHALL include the month and day	Elements differ in short: 'Clinically relevant time/time-period for report' vs '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	DateTime this version was made
performer	SΣ	0..*	Reference(US Core Practitioner Profile | US Core Organization Profile | US Pathology Related Practitioner Roles | US Core CareTeam Profile)	Responsible Diagnostic Service	SΣ	0..*	Reference(US Core Practitioner Profile | US Core Organization Profile | US Pathology Related Practitioner Roles | US Core CareTeam Profile)	Responsible Diagnostic Service
resultsInterpreter	SΣ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam)	Primary result interpreter	SΣ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam)	Primary result interpreter
specimen	S	0..*	Reference(US Pathology Specimen)	Specimens this report is based on	S	0..*	Reference(US Pathology 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 Test Result Profile S | US Core Observation Imaging Result Profile S)	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	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)	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	Entire report as issued
Documentation for this format