Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight vs http://paciowg.github.io/functional-status-ig/StructureDefinition/pacio-fs

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	2021-09-23T10:50:45-07:00	Values Differ
description	Defines constraints on Observation to represent body weight observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile.	An exchange of functional status observation for a patient. This profile is used for exchanging a single observation data generally included in a set of observation data collected through the use of a structured resource (e.g. assessment tool, instrument, or screen).	Values Differ
experimental	false		Removed the item 'false'
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreBodyWeightProfile	FunctionalStatus	Values Differ
publisher	HL7 International - US Realm Steering Committee		Removed the item 'HL7 International - US Realm Steering Committee'
purpose
status	active
title	US Core Body Weight Profile	PACIO Functional Status	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-body-weight	http://paciowg.github.io/functional-status-ig/StructureDefinition/pacio-fs	Values Differ
version	4.0.0	0.1.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	I				I				Elements differ in short: "US Core Body Weight Profile" "Measurements and simple assertions" Elements differ in definition: "Defines constraints on Observation to represent body weight observations with a standard LOINC code and UCUM units of measure. This profile is derived from the US Core Vital Signs Profile." "Measurements and simple assertions made about a patient, device or other subject."
id	Σ				Σ
meta	Σ				Σ
implicitRules	?!Σ				?!Σ
language
text
contained
extension			Extension				Extension		Elements differ in short: "Additional content defined by implementations" "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." "An Extension"
modifierExtension	?!				?!
identifier	Σ				Σ
basedOn	Σ				Σ				Elements differ in short: "Fulfills plan, proposal or order" "Currently not used in FunctionalStatus."
partOf	Σ				Σ				Elements differ in short: "Part of referenced event" "Currently not used in FunctionalStatus."
status	?!SΣ				?!Σ				Elements differ in short: "registered | preliminary | final | amended +" "Should have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used." Elements differ in definition for mustSupport: "true" "false"
Slices for category	S								Elements differ in short: "Classification of type of observation" "A second category code may be used along with the code “functioning”. For example, for assessment tool/survey instrument observations use “survey” as a second code." Elements differ in definition for mustSupport: "true" "false"
code	SΣ				Σ				Elements differ in short: "Body Weight" "For a Post-Acute Care Assessment, code should be a LOINC code and text for the question or concept name." Elements differ in definition: "Coded Responses from C-CDA Vital Sign Results." "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)." "Knowing what kind of observation is being made is essential to understanding the observation." Elements differ in definition for mustSupport: "true" "false"
subject	SΣ				Σ				Elements differ in short: "Who and/or what the observation is about" "Subject should only be Patient for functional status" Elements differ in definition for mustSupport: "true" "false"
focus	Σ				Σ				Elements differ in short: "What the observation is about, when it is not about the subject of record" "Currently not used in FunctionalStatus."
encounter	Σ				Σ
effective[x]	SΣI				Σ				Elements differ in short: "Often just a dateTime for Vital Signs" "Clinically relevant time/time-period for observation" Elements differ in definition: "Often just a dateTime for Vital Signs." "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." Elements differ in definition for mustSupport: "true" "false"
issued	Σ				Σ				Elements differ in short: "Date/Time this version was made available" "Currently not used in FunctionalStatus."
performer	Σ				Σ				Elements differ in short: "Who is responsible for the observation" "The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization."
Slices for value[x]	SΣI				ΣI				Elements differ in short: "Vital Signs Value" "Whenever possible should use the CodeableConcept datatype to provide a suitable code to define the concept for the observation data. As for values like an assessment score or roll-up value, the datatype for this element should be determined by Observation.code. However, for values that are ordinal, may use the CodeableConcept datatype along with the Ordinal Value Extension." Elements differ in definition: "Vital Signs value are typically recorded using the Quantity data type." "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)." "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" "false"
dataAbsentReason	SI				I				Elements differ in definition for mustSupport: "true" "false"
interpretation									Elements differ in short: "High, low, normal, etc." "Currently not used in FunctionalStatus."
note
bodySite									Elements differ in short: "Observed body part" "Currently not used in FunctionalStatus."
method									Elements differ in short: "How it was done" "Currently not used in FunctionalStatus."
specimen									Elements differ in short: "Specimen used for this observation" "Currently not used in FunctionalStatus."
device									Elements differ in short: "(Measurement) Device" "Currently not used in FunctionalStatus."
referenceRange	I				I				Elements differ in short: "Provides guide for interpretation" "Currently not used in FunctionalStatus."
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
low	I				I
high	I				I
type
appliesTo
age
text
hasMember	Σ				Σ				Elements differ in short: "Used when reporting vital signs panel components" "Currently not used in FunctionalStatus." Elements differ in definition: "Used when reporting vital signs panel components." "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]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
derivedFrom	Σ				SΣ				Elements differ in short: "Related measurements the observation is made from" "Should point back to the QuestionnaireResponse that this resource is derived from." Elements differ in definition for mustSupport: "false" "true" Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse]])
component	SΣI				Σ				Elements differ in short: "Component observations" "If used, the answers for the associated questions (for the purpose of grouping answers under a heading and displaying side-by-side columns)" Elements differ in definition: "Used when reporting component observation such as systolic and diastolic blood pressure." "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." Elements differ in definition for mustSupport: "true" "false"
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
code	SΣ				Σ				Elements differ in short: "Type of component observation (code / type)" "If used, the LOINC code or text of the column header (for the purpose of grouping answers under a heading and displaying side-by-side columns)." Elements differ in definition for mustSupport: "true" "false" Elements differ in binding.description: "The vital sign codes from the base FHIR and US Core Vital Signs." "Codes identifying names of simple observations."
value[x]	SΣI				Σ				Elements differ in short: "Vital Sign Component Value" "The code and text for the answer to the (associated) question." 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." "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)." "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" "false"
dataAbsentReason	SI				I				Elements differ in definition for mustSupport: "true" "false"
interpretation
referenceRange
Documentation for this format