Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference vs http://hl7.org/fhir/us/codex-radiation-therapy/StructureDefinition/codexrt-radiotherapy-disease-status

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs	http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-cancer-disease-status	Values Differ
copyright	Used by permission of HL7 International, all rights reserved Creative Commons License		Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
date	2022-04-20	2023-07-28T13:07:08+00:00	Values Differ
description	To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Observation resource to record, search, and fetch head circumference observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies which *additional* 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.	Disease Status Reported by Radiation Oncologist	Values Differ
experimental	false		Removed the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreHeadCircumferenceProfile	RadiotherapyDiseaseStatus	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 Cross Group Projects Work Group	Values Differ
purpose
status	active	draft	Values Differ
title	US Core Head Circumference Profile	Radiotherapy Disease Status	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-head-circumference	http://hl7.org/fhir/us/codex-radiation-therapy/StructureDefinition/codexrt-radiotherapy-disease-status	Values Differ
version	6.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
Observation	C	0..*	USCoreVitalSignsProfile	US Core Head Circumference Profile	C	0..*	CancerDiseaseStatus	Measurements and simple assertions	Elements differ in short: 'US Core Head Circumference Profile' vs 'Measurements and simple assertions' Elements differ in definition: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.' Elements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
id	Σ	0..1	id	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	Extension Slice: Unordered, Open by value:url	Elements differ in short: 'Additional content defined by implementations' vs 'Extension' Elements differ in definition: 'May 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.' vs 'An Extension'
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	Business Identifier for observation	Σ	0..*	Identifier	Business Identifier for observation
basedOn	Σ	0..*	Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)	Fulfills plan, proposal or order	Σ	0..*	Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)	Fulfills plan, proposal or order
partOf	Σ	0..*	Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)	Part of referenced event	Σ	0..*	Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)	Part of referenced event
status	?!SΣ	1..1	code	(USCDI) registered | preliminary | final | amended + Binding: ?? (required)	?!SΣ	1..1	code	registered | preliminary | final | amended + Binding: ?? (required): Codes providing the status of an observation.	Elements differ in short: '(USCDI) registered | preliminary | final | amended +' vs 'registered | preliminary | final | amended +'
Slices for category	S	1..*	CodeableConcept	(USCDI) Classification of type of observation Slice: Unordered, Open by value:coding.code, value:coding.system Binding: ?? (preferred): Codes for high level observation categories.		0..*	CodeableConcept	Classification of type of observation Binding: ?? (preferred): Codes for high level observation categories.	Elements differ in short: '(USCDI) Classification of type of observation' vs 'Classification of type of observation' Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
code	SΣ	1..1	CodeableConcept	(USCDI) Head Circumference Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs. Required Pattern: {"coding":[{"system":"http://loinc.org","code":"9843-4"}]}	SΣ	1..1	CodeableConcept	Type of observation (code / type) Binding: ?? (example): Codes identifying names of simple observations. Required Pattern: {"coding":[{"system":"http://loinc.org","code":"97509-4"}]}	Elements differ in short: '(USCDI) Head Circumference' vs 'Type of observation (code / type)' Elements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation "name".' Elements differ in requirements: '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.' Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
subject	SΣ	1..1	Reference(US Core Patient Profile)	(USCDI) Who and/or what the observation is about	SΣ	1..1	Reference(Cancer Patient Profile)	Who and/or what the observation is about	Elements differ in short: '(USCDI) Who and/or what the observation is about' vs 'Who and/or what the observation is about' Elements differ in definition: 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.' vs 'Patient whose disease status is recorded.'
focus	ΣTU	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	SΣ	0..*	Reference(Primary Cancer Condition Profile | Secondary Cancer Condition Profile | Tumor Profile)	What the observation is about, when it is not about the subject of record	Elements differ in definition for mustSupport: 'false' vs 'true'
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this observation is made	Σ	0..1	Reference(Encounter)	Healthcare event during which this observation is made
effective[x]	SΣC	1..1	dateTime S, Period	(USCDI) Often just a dateTime for Vital Signs	SΣ	0..1	dateTime	Clinically relevant time/time-period for observation	Elements differ in short: '(USCDI) Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation' Elements differ in definition: 'Often just a dateTime for Vital Signs.' vs 'The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself.' Element minimum cardinalities differ: '1' vs '0'
issued	Σ	0..1	instant	Date/Time this version was made available	Σ	0..1	instant	Date/Time this version was made available
performer	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)	Who is responsible for the observation	Σ	0..*	Reference(US Core Practitioner Profile)	Who is responsible for the observation
Slices for value[x]	SΣC	0..1	Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	(USCDI) Vital Signs Value Slice: Unordered, Open by type:$this Binding: ?? (extensible): Common UCUM units for recording Vital Signs.	SΣC	0..1	CodeableConcept	Actual result Binding: ?? (required) RestrictDiseaseProgressionQualifier: Only allow qualifier for one value status	Elements differ in short: '(USCDI) Vital Signs Value' vs 'Actual result' Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.' Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
id		0..1	string	Unique id for inter-element referencing		0..1	string	Unique id for inter-element referencing
Slices for extension		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url		0..*	Extension	Additional content defined by implementations Slice: Unordered, Open by value:url
coding	Σ	0..*	Coding	Code defined by a terminology system	Σ	0..*	Coding	Code defined by a terminology system
text	Σ	0..1	string	Plain text representation of the concept	Σ	0..1	string	Plain text representation of the concept
dataAbsentReason	SC	0..1	CodeableConcept	(USCDI) Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	C	0..1	CodeableConcept	Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	Elements differ in short: '(USCDI) Why the result is missing' vs 'Why the result is missing' Elements differ in definition for mustSupport: 'true' vs 'false'
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.
note		0..*	Annotation	Comments about the observation		0..*	Annotation	Comments about the observation
bodySite		0..1	CodeableConcept	Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality.		0..1	CodeableConcept	Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality.
method		0..1	CodeableConcept	How it was done Binding: ?? (example): Methods for simple observations.		0..1	CodeableConcept	How it was done Binding: ?? (example): Methods for simple observations.
specimen		0..1	Reference(Specimen)	Specimen used for this observation		0..1	Reference(Specimen)	Not used in this profile	Elements differ in short: 'Specimen used for this observation' vs 'Not used in this profile' Elements differ in definition: 'The specimen that was used when this observation was made.' vs 'Not used in this profile'
device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device		0..1	Reference(Device | DeviceMetric)	Not used in this profile	Elements differ in short: '(Measurement) Device' vs 'Not used in this profile' Elements differ in definition: 'The device used to generate the observation data.' vs 'Not used in this profile'
referenceRange	C	0..*	BackboneElement	Provides guide for interpretation	C	0..*	BackboneElement	Not used in this profile	Elements differ in short: 'Provides guide for interpretation' vs 'Not used in this profile' Elements differ in definition: 'Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two `referenceRange` elements would be used.' vs 'Not used in this profile'
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
low	C	0..1	??	Low Range, if relevant	C	0..1	??	Low Range, if relevant
high	C	0..1	??	High Range, if relevant	C	0..1	??	High Range, if relevant
type		0..1	CodeableConcept	Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range.		0..1	CodeableConcept	Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range.
appliesTo		0..*	CodeableConcept	Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to.		0..*	CodeableConcept	Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to.
age		0..1	Range	Applicable age range, if relevant		0..1	Range	Applicable age range, if relevant
text		0..1	string	Text based reference range in an observation		0..1	string	Text based reference range in an observation
hasMember	Σ	0..*	Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)	Used when reporting vital signs panel components	Σ	0..*	Reference(Observation | QuestionnaireResponse | MolecularSequence)	Not used in this profile	Elements differ in short: 'Used when reporting vital signs panel components' vs 'Not used in this profile' Elements differ in definition: 'Used when reporting vital signs panel components.' vs 'Not used in this profile' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
derivedFrom	Σ	0..*	Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence | Vital Signs Profile)	Related measurements the observation is made from	Σ	0..*	Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)	Related measurements the observation is made from
component	SΣC	0..*	BackboneElement	(USCDI) Component observations	Σ	0..*	BackboneElement	Not used in this profile	Elements differ in short: '(USCDI) Component observations' vs 'Not used in this profile' Elements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs 'Not used in this profile' Elements differ in definition for mustSupport: 'true' vs 'false'
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
code	SΣ	1..1	CodeableConcept	(USCDI) Type of component observation (code / type) Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations.	Elements differ in short: '(USCDI) Type of component observation (code / type)' vs 'Type of component observation (code / type)' Elements differ in definition for mustSupport: 'true' vs 'false' Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'
value[x]	SΣC	0..1	Quantity S, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	(USCDI) Vital Sign Component Value Binding: ?? (extensible): Common UCUM units for recording Vital Signs.	Σ	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual component result	Elements differ in short: '(USCDI) Vital Sign Component Value' vs 'Actual component result' Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.' Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' Elements differ in definition for mustSupport: 'true' vs 'false'
dataAbsentReason	SC	0..1	CodeableConcept	(USCDI) Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	C	0..1	CodeableConcept	Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing.	Elements differ in short: '(USCDI) Why the component result is missing' vs 'Why the component result is missing' Elements differ in definition for mustSupport: 'true' vs 'false'
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.
referenceRange		0..*	See referenceRange (Observation)	Provides guide for interpretation of component result		0..*	See referenceRange (Observation)	Provides guide for interpretation of component result
Documentation for this format