Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/vitals/StructureDefinition/VitalSignsPanel

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Observation	http://hl7.org/fhir/StructureDefinition/vitalspanel	Values Differ
copyright
date	2019-08-19T00:00:00+10:00	2019-05-29	Values Differ
description	Defines constraints and extensions on the Observation resource for the minimal set of data to query and retrieve laboratory test results	Vital Signs Panel; a grouping of the vital signs elements.	Values Differ
experimental	false		Removed this item
fhirVersion	4.0.1
kind	resource	complex-type	Values Differ
name	USCoreLaboratoryResultObservationProfile	VitalSignsPanel	Values Differ
publisher	HL7 US Realm Steering Committee	HSPC	Values Differ
purpose
status	active	draft	Values Differ
title	US Core Laboratory Result Observation Profile	Vital Signs Panel	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab	http://hl7.org/fhir/us/vitals/StructureDefinition/VitalSignsPanel	Values Differ
version	3.1.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: "Measurements and simple assertions" "FHIR Vital Signs Panel Profile" Elements differ in definition: "This profile is created to meet the 2015 Edition Common Clinical Data Set 'Laboratory test(s) and Laboratory value(s)/result(s)' requirements." "Vital Signs Panel; a grouping of the vital signs elements."
id	Σ				Σ
meta	ΣI				ΣI
implicitRules	?!ΣI				?!ΣI
language	I				I
text	I				I
contained
extension	I		Extension		I		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	?!I				?!I
identifier	ΣI				ΣI
basedOn	ΣI				ΣI
partOf	ΣI				ΣI
status	?!SΣI				?!SΣI
category	SI		(Slice Definition)		SI		(Slice Definition)
code	SΣI				SΣI				Elements differ in short: "Laboratory Test Name" "Vital Signs Panel" Elements differ in definition: "The test that was performed. A LOINC **SHALL** be used if the concept is present in LOINC." "Vital Signs Panel." Elements differ in comments: "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. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display." "additional codes that translate or map to this code are allowed. For example a more granular LOINC code or code that is used locally in a system." Elements differ in requirements: "Knowing what kind of observation is being made is essential to understanding the observation." "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)." Elements differ in description: "LOINC codes" "This identifies the vital sign result type." Elements differ in description: "LOINC codes" "This identifies the vital sign result type."
id
extension	I		Extension		I		Extension
coding	ΣI				ΣI		(Slice Definition)
text	ΣI				ΣI
subject	SΣI				SΣI
focus	ΣI				ΣI
encounter	ΣI				ΣI
effective[x]	SΣI				SΣI				Elements differ in short: "Clinically relevant time/time-period for observation" "Often just a dateTime for Vital Signs" Elements differ in definition: "For lab tests this is the specimen collection date. For Ask at Order Entry Questions (AOE)'s this is the date the question was asked." "Often just a dateTime for Vital Signs."
issued	ΣI				ΣI
performer	ΣI				ΣI
value[x]	SΣI				SΣI		(Slice Definition)		Elements differ in short: "Result Value" "Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept." Elements differ in definition: "The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT]. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM]. A FHIR [UCUM Codes value set] that defines all UCUM codes is in the FHIR specification." "Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept." Elements differ in requirements: "An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations." "9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305)."
dataAbsentReason	SI				SI
interpretation	I				I
note	I				I
bodySite	I				I
method	I				I
specimen	I				I
device	I				I
referenceRange	I				I
id
extension	I		Extension		I		Extension
modifierExtension	?!ΣI				?!ΣI
low	I				I
high	I				I
type	I				I
appliesTo	I				I
age	I				I
text	I				I
hasMember	ΣI				SΣI		(Slice Definition)		Elements differ in short: "Related resource that belongs to the Observation group" "Used when reporting vital signs panel components" Elements differ in definition: "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." "Used when reporting vital signs panel components." Elements differ in definition for mustSupport: "false" "true" Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])
derivedFrom	ΣI				ΣI
component	ΣI				SΣI				Elements differ in short: "Component results" "Used when reporting systolic and diastolic blood pressure." Elements differ in definition: "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." "Used when reporting systolic and diastolic blood pressure." Elements differ in definition for mustSupport: "false" "true"
id
extension	I		Extension		I		Extension
modifierExtension	?!ΣI				?!ΣI
code	ΣI				SΣI				Elements differ in definition for mustSupport: "false" "true" Elements differ in binding.description: "Codes identifying names of simple observations." "This identifies the vital sign result type."
value[x]	ΣI				SΣI				Elements differ in short: "Actual component result" "Vital Sign Value recorded with UCUM" Elements differ in definition: "The information determined as a result of making the observation, if the information has a simple value." "Vital Sign Value recorded with UCUM." Elements differ in requirements: "An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations." "9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305)." Elements differ in definition for mustSupport: "false" "true"
dataAbsentReason	I				SI				Elements differ in definition for mustSupport: "false" "true"
interpretation	I				I
referenceRange	I				I
Documentation for this format