Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi vs http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-tumor-size

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs	http://hl7.org/fhir/StructureDefinition/Observation	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	2020-11-17	2023-03-28T19:28:28+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 Body Mass Index (BMI) observations with a standard LOINC code and UCUM units of measure. It is based on the US Core Vital Signs Profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets which **SHALL** be present in the Observation resource when using this profile. It provides the floor for standards development for specific use cases.	Records the dimensions of a tumor	Values Differ
experimental	false		Removed the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreBMIProfile	TumorSize	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 International Clinical Interoperability Council	Values Differ
purpose
status	active
title	US Core BMI Profile	Tumor Size Profile	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-bmi	http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-tumor-size	Values Differ
version	6.0.0-ballot	3.0.0-ballot	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 Body Mass Index (BMI) Profile	C	0..*	Observation	Measurements and simple assertions must-have-focus-or-specimen-invariant: Either `focus` OR `specimen` MUST be populated	Elements differ in short: 'US Core Body Mass Index (BMI) 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	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 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	registered | preliminary | final | amended + Binding: ?? (required)	?!Σ	1..1	code	registered | preliminary | final | amended + Binding: ?? (required): Codes providing the status of an observation.	Elements differ in definition for mustSupport: 'true' vs 'false'
Slices for category	S	1..*	CodeableConcept	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 definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
code	SΣ	1..1	CodeableConcept	Coded Responses from C-CDA Vital Sign Results Binding: ?? (extensible): The vital sign codes from the base FHIR and US Core Vital Signs. Required Pattern: {"coding":[{"system":"http://loinc.org","code":"39156-5"}]}	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":"21889-1"}]}	Elements differ in short: 'Coded Responses from C-CDA Vital Sign Results' 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)	Who and/or what the observation is about	SΣ	1..1	Reference(Cancer Patient Profile)	The patient whose tumor was measured.	Elements differ in short: 'Who and/or what the observation is about' vs 'The patient whose tumor was measured.' 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 'The patient whose tumor was measured. SHALL be a `Patient` resource conforming to `CancerPatient`.'
focus	ΣTU	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	SΣ	0..1	Reference(Tumor Profile)	Identifies a tumor that has NOT been removed from the body	Elements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'Identifies a tumor that has NOT been removed from the body' Elements differ in definition: 'The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.' vs 'Reference to a BodyStructure resource conforming to Tumor.' Elements differ in comments: 'Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [focusCode].' vs 'Use **only** when the tumor **has not** been removed from the body. If the tumor has been removed, use `specimen` instead and leave `focus` empty.' Elements differ in definition for mustSupport: 'false' vs 'true' Element maximum cardinalities differ: '2147483647' vs '1'
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	Often just a dateTime for Vital Signs	SΣ	0..1	dateTime, Period, Timing, instant	Clinically relevant time/time-period for observation	Elements differ in short: '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(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)	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	Vital Signs Value Slice: Unordered, Open by type:$this Binding: ?? (extensible): Common UCUM units for recording Vital Signs.	ΣC	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Not used in this profile	Elements differ in short: 'Vital Signs Value' vs 'Not used in this profile' Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'Not used in this profile' 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	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 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.	S	0..1	CodeableConcept	Method for measuring the tumor Binding: ?? (extensible)	Elements differ in short: 'How it was done' vs 'Method for measuring the tumor' Elements differ in definition: 'Indicates the mechanism used to perform the observation.' vs 'Method for measuring the tumor' Elements differ in comments: 'Only used if not implicit in code for Observation.code.' vs 'Tumors are typically measured via gross pathology after excision, or via diagnostic imaging or physical exam prior to removal. If `specimen` is set, `method` is expected to be a "gross pathology" code. If `focus` is set, `method` is expected to be a type of diagnostic imaging or physical exam.' Elements differ in definition for mustSupport: 'false' vs 'true'
specimen		0..1	Reference(Specimen)	Specimen used for this observation	S	0..1	Reference(Human Specimen Profile)	Identifies a tumor that has been removed from the body	Elements differ in short: 'Specimen used for this observation' vs 'Identifies a tumor that has been removed from the body' Elements differ in definition: 'The specimen that was used when this observation was made.' vs 'Reference to a Specimen resource consistent with HumanSpecimen with type = http://terminology.hl7.org/CodeSystem/v2-0487#TUMOR.' Elements differ in comments: 'Should only be used if not implicit in code found in `Observation.code`. Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).' vs 'Use specimen **only** when the tumor **has** been removed from the body. If the tumor has been not removed, use `focus` instead and leave `specimen` empty.' Elements differ in definition for mustSupport: 'false' vs 'true'
device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device
referenceRange	C	0..*	BackboneElement	Provides guide for interpretation	C	0..*	BackboneElement	Provides guide for interpretation
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)	Related resource that belongs to the Observation group	Elements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group' Elements differ in definition: 'Used when reporting vital signs panel components.' vs 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' 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	Component observations	SΣ	1..*	BackboneElement	Component results Slice: Unordered, Open by pattern:code	Elements differ in short: 'Component observations' vs 'Component results' Elements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs 'Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' Element minimum cardinalities differ: '0' vs '1'
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	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 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	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: '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	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 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