Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey vs http://hl7.org/fhir/us/pacio-fp/StructureDefinition/fp-collection

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Observation
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	2022-05-13T16:07:55-04:00	Values Differ
description	To promote interoperability and adoption through common implementation, the US Core Observation Survey Profile sets minimum expectations for the Observation Resource to record, search, and fetch retrieve observations that represent the questions and responses to form/survey and assessment tools. It can be used to represent individual responses, panels of multi-question surveys, and multi-select responses to “check all that apply” questions. It identifies which core elements, extensions, vocabularies and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific uses cases.	A point in time collection of post-acute care observations for a patient. This profile is used for exchanging a set of observation data collected through the use of a structured resource (e.g. assessment tool, instrument, or screen).	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreObservationSurveyProfile	FunctionalPerformanceCollection	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 Patient Care Work Group	Values Differ
purpose
status	active
title	US Core Observation Survey Profile	Functional Performance Collection	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey	http://hl7.org/fhir/us/pacio-fp/StructureDefinition/fp-collection	Values Differ
version	5.0.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	I	0..*	Observation	Survey Observation us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present us-core-3: SHALL use UCUM for coded quantity units.	I	0..*	Observation	Measurements and simple assertions	Elements differ in short: 'Survey Observation' 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	string	Logical id of this artifact	Σ	0..1	string	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: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages Max Binding		0..1	code	Language of the resource content Binding: CommonLanguages (preferred): A human language. Additional Bindings Purpose AllLanguages 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)	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Fulfills plan, proposal or order' vs 'Currently not used in FunctionalPerformanceCollection.'
partOf	Σ	0..*	Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)	Part of referenced event	Σ	0..*	Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Part of referenced event' vs 'Currently not used in FunctionalPerformanceCollection.'
status	?!SΣ	1..1	code	registered | preliminary | final | amended + Binding: ObservationStatus (required): Codes providing the status of an observation.	?!Σ	1..1	code	Should have the value 'final' when all the observatons are complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used. Binding: ObservationStatus (required): Codes providing the status of an observation.	Elements differ in short: 'registered | preliminary | final | amended +' vs 'Should have the value 'final' when all the observatons are 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' vs 'false'
Slices for category	S	1..*	CodeableConcept	Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.	S	1..*	CodeableConcept	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. Slice: Ordered, Open by pattern:coding Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.	Elements differ in short: 'Classification of type of observation' vs '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 requirements: 'To identify that observation is derived from a questionnaire.' vs 'Used for filtering what observations are retrieved and displayed.'
code	SΣ	1..1	CodeableConcept	Type of observation (code / type) Binding: US Core Survey Codes (preferred)	Σ	1..1	CodeableConcept	For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment. Binding: Functional Performance ValueSet LOINC SNOMED (extensible)	Elements differ in short: 'Type of observation (code / type)' vs 'For a Post-Acute Care structured assessment resource such as an instrument or screen, use a LOINC code to identify the instrument/screen name or panel/section title to indicate the kind of assessment.' Elements differ in definition for mustSupport: 'true' vs 'false'
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who and/or what the observation is about	Σ	1..1	Reference(US Core Patient Profile)	Should only reference a Patient resource.	Elements differ in short: 'Who and/or what the observation is about' vs 'Should only reference a Patient resource.' Elements differ in definition for mustSupport: 'true' vs 'false'
focus	Σ	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	Σ	0..*	Reference(Resource)	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'What the observation is about, when it is not about the subject of record' vs 'Currently not used in FunctionalPerformanceCollection.'
encounter	Σ	0..1	Reference(Encounter)	Healthcare event during which this observation is made	Σ	0..1	Reference(US Core Encounter Profile)	Healthcare event during which this observation is made
effective[x]	SΣI	0..1	dateTime S, Period, Timing, instant	Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day.	Σ	1..1	dateTime, Period	Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).	Elements differ in short: 'Clinically relevant time/time-period for observation' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).' Elements differ in definition: '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".' vs 'Clinical relevant time for an assessment such as post-acute care observations performed with structured evaluation tools is the time the evaluation occurs, i.e., when the clinician obtains the answers entered in the tool. However, the only timing available may be when then tool is completed by the clinician. That timing is generally documented as a point in time (dateTime).' Elements differ in comments: 'At least a date should be present unless this observation is a historical report.' vs 'The use of effective[x] and dateTime versus Period is subject to implementer workflow and needs. In most situations, an observation is considered as a point in time, even if the assessment occurred over a period of time. Period is included in this implementation guide to provide additional flexibility for specific use cases. However, it is expected most observations will be recorded using DateTime. Furthermore, any retrieval of information should return the relevant if DateTime is requested, even if the original observation was recorded as a period. Some implementers may choose to use additional functions in there retrieves to 'normalize' intervals, as is done in Clinical Quality Language (CQL).' Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '0' vs '1'
issued	Σ	0..1	instant	Date/Time this version was made available	Σ	0..1	instant	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Date/Time this version was made available' vs 'Currently not used in FunctionalPerformanceCollection.'
performer	SΣ	0..*	Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile)	Who is responsible for the observation	Σ	1..*	Reference(US Core Practitioner Profile | US Core PractitionerRole Profile | US Core Organization Profile)	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.	Elements differ in short: 'Who is responsible for the observation' vs '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.' Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '0' vs '1'
value[x]	SΣI	0..1	Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual result	ΣI	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field.	Elements differ in short: 'Actual result' vs 'If used, should use the CodeableConcept datatype whenever possible to provide a suitable code to define the concept for the observation data. When capturing a collection of related observations, typically this field is not used. If the outcome of an assessment includes one or more summary scores, leave this field unused and use the 'hasMember' field to point to one or more Observation resources with each of which has a score provided in the 'value' field.' Elements differ in comments: 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value.' vs 'An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section] below.' Elements differ in definition for mustSupport: 'true' vs 'false'
dataAbsentReason	SI	0..1	CodeableConcept	Why the result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.	I	0..1	CodeableConcept	Currently not used in FunctionalPerformanceCollection. Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.	Elements differ in short: 'Why the result is missing' vs 'Currently not used in FunctionalPerformanceCollection.' Elements differ in comments: '"Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate.' vs 'Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values.' Elements differ in definition for mustSupport: 'true' vs 'false'
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	Currently not used in FunctionalPerformanceCollection. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.	Elements differ in short: 'High, low, normal, etc.' vs 'Currently not used in FunctionalPerformanceCollection.'
note		0..*	Annotation	Comments about the observation		0..*	Annotation	Comments about the observation
bodySite		0..1	CodeableConcept	Observed body part Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.		0..1	CodeableConcept	Currently not used in FunctionalPerformanceCollection. Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.	Elements differ in short: 'Observed body part' vs 'Currently not used in FunctionalPerformanceCollection.'
method		0..1	CodeableConcept	How it was done Binding: ObservationMethods (example): Methods for simple observations.		0..1	CodeableConcept	Currently not used in FunctionalPerformanceCollection. Binding: ObservationMethods (example): Methods for simple observations.	Elements differ in short: 'How it was done' vs 'Currently not used in FunctionalPerformanceCollection.'
specimen		0..1	Reference(Specimen)	Specimen used for this observation		0..1	Reference(Specimen)	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Specimen used for this observation' vs 'Currently not used in FunctionalPerformanceCollection.'
device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device		0..1	Reference(Device | DeviceMetric)	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: '(Measurement) Device' vs 'Currently not used in FunctionalPerformanceCollection.'
referenceRange	I	0..*	BackboneElement	Provides guide for interpretation	I	0..*	BackboneElement	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Provides guide for interpretation' vs 'Currently not used in FunctionalPerformanceCollection.'
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	I	0..1	SimpleQuantity	Low Range, if relevant	I	0..1	SimpleQuantity	Low Range, if relevant
high	I	0..1	SimpleQuantity	High Range, if relevant	I	0..1	SimpleQuantity	High Range, if relevant
type		0..1	CodeableConcept	Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.		0..1	CodeableConcept	Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.
appliesTo		0..*	CodeableConcept	Reference range population Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.		0..*	CodeableConcept	Reference range population Binding: ObservationReferenceRangeAppliesToCodes (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	SΣ	0..*	Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile | MolecularSequence)	Reference to panel or multi-select responses	SΣ	0..*	Reference(Functional Performance Observation)	Each post-acute care observation in the collection.	Elements differ in short: 'Reference to panel or multi-select responses' vs 'Each post-acute care observation in the collection.' Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' 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.' Elements differ in comments: 'This grouping element is used to represent surveys that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the "panel" observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. In a survey that has a heirarchical grouping of questions, the observation "panels" can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.'
derivedFrom	SΣ	0..*	Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence)	Related Observations or QuestionnaireResponses that the observation is made from	SΣ	0..*	Reference(SDC Questionnaire Response)	Should point back to the SDC QuestionnaireResponse that this resource is derived from.	Elements differ in short: 'Related Observations or QuestionnaireResponses that the observation is made from' vs 'Should point back to the SDC QuestionnaireResponse that this resource is derived from.' Elements differ in definition: 'Observations or QuestionnaireResponses from which this observation value is derived.' vs 'The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image.' Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse]])
component	Σ	0..*	BackboneElement	Component results	Σ	0..*	BackboneElement	Currently not used in FunctionalPerformanceCollection.	Elements differ in short: 'Component results' vs 'Currently not used in FunctionalPerformanceCollection.'
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	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations.	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations.
value[x]	Σ	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual component result	Σ	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual component result
dataAbsentReason	I	0..1	CodeableConcept	Why the component result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.	I	0..1	CodeableConcept	Why the component result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	High, low, normal, etc. Binding: ObservationInterpretationCodes (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