Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Observation	http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalCharacteristic	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-27T20:42:33+00:00	Values Differ
description	The US Core Observation Clinical Result Profile is based upon the core FHIR Observation Resource and, along with the US Core DiagnosticReport Profile, meets the US Core Data for Interoperability (USCDI) requirements for *Diagnostic Imaging* and *Clinical Tests* Data Classes. This profile sets minimum expectations for the Observation resource to record and search non-laboratory clinical test results (e.g., radiology and other clinical observations generated from procedures). An example would be when a gastroenterologist reports the size of a polyp observed during a colonoscopy. This profile is the basis for the US Core Laboratory Result Observation Profile, which defines additional data elements to record and search laboratory test results. The US Core Observation Clinical Result Profile sets minimum expectations to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.	Profile for observations about the pronouns and possessive adjectives a person wishes to be addressed by. This profile is intended for draft use only. For further details on this profile see [Draft Specifications for Personal Characteristics](draft_specifications_for_personal_characteristics.html).	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreObservationClinicalResultProfile	SDOHCCObservationPersonalPronouns	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 International Patient Care WG	Values Differ
purpose
status	active	draft	Values Differ
title	US Core Observation Clinical Result Profile	SDOHCC Observation Personal Pronouns	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result	http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationPersonalPronouns	Values Differ
version	6.1.0	2.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	C	0..*	Observation	Measurements and simple assertions us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present	C	0..*	SDOHCCObservationPersonalCharacteristic	Personal characteristic observation	Elements differ in short: 'Measurements and simple assertions' vs 'Personal characteristic observation' Elements differ in definition: '\-' vs 'For observations about the pronouns and possessive adjectives a person wishes to be addressed by.' Elements differ in comments: '\-' vs 'For observations about the personal pronouns of an individual.'
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): Codes providing the status of an observation.	?!SΣ	1..1	code	final | corrected | entered-in-error | unknown Binding: ?? (required)	Elements differ in short: '(USCDI) registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown' Elements differ in definition: 'The status of the result value.' vs 'The status of the observation value.' Elements differ in requirements: 'Need to track the status of individual results. Some results are finalized before the whole report is finalized.' vs 'Further constrained to values that are relevant for personal characteristic observations.'
Slices for category	S	1..*	CodeableConcept	(USCDI) Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ?? (preferred): Codes for high level observation categories.		1..*	CodeableConcept	Classification of type of observation Slice: Unordered, Open by value:$this 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'
code	SΣ	1..1	CodeableConcept	(USCDI) Clinical Test or Procedure Name Binding: ?? (extensible)	SΣ	1..1	CodeableConcept	Type of observation (code / type) Binding: ?? (preferred): Codes identifying names of simple observations. Required Pattern: {"coding":[{"system":"http://loinc.org","code":"90778-2"}]}	Elements differ in short: '(USCDI) Clinical Test or Procedure Name' vs 'Type of observation (code / type)' Elements differ in definition: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation "name".' 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.' vs '*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. NOTE: In LOINC, System Patient is used in the modeling of codes referenced by the Personal Characteristics profiles (e.g., 72826-1 Race OMB.1997, 69490-1 Ethnicity OMB.1997, 76691-5 Gender identity, 76690-7 Sexual orientation, 90778-2 Personal pronouns – Reported, and 99502-7 Recorded sex or gender). If the draft profiles are adopted, new LOINC codes without System Patient would be needed since these profiles can also be used to capture characteristics of a provider (using an extension) or a related person (using focus).'
subject	SΣ	1..1	Reference(US Core Patient Profile)	(USCDI) Who and/or what the observation is about	SΣC	0..1	Reference(US Core 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' Element minimum cardinalities differ: '1' vs '0'
focus	ΣTU	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	ΣC	0..1	Reference(RelatedPerson)	What the observation is about, when it is not about the subject of record	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	0..1	dateTime S, Period, Timing, instant	(USCDI) Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day.	Σ	0..1	dateTime, Period	Clinically relevant time/time-period for observation	Elements differ in short: '(USCDI) Clinically relevant time/time-period for observation' vs 'Clinically relevant time/time-period for observation' Elements differ in comments: 'At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events.' vs 'At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events. NOTE: dateTime is Must Support, but currently tooling does not support this.' Elements differ in definition for mustSupport: 'true' vs 'false'
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	SΣC	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)	Who is responsible for the observation	Elements differ in definition for mustSupport: 'false' vs 'true'
value[x]	SΣC	0..1	Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	(USCDI) Result Value us-core-3: SHALL use UCUM for coded quantity units.	SΣC	1..1	CodeableConcept	Actual result Binding: ?? (preferred): Codes for personal pronouns	Elements differ in short: '(USCDI) Result Value' vs 'Actual result' Elements differ in definition: 'The clinical test or procedure result value. 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.' vs 'The information determined as a result of making the observation, if the information has a simple value.' 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.' 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. This is a value set is for testing purposes only and will ultimately need to be aligned with vetted value sets being developed by the Gender Harmony Project. See https://build.fhir.org/ig/HL7/fhir-gender-harmony/branches/main/terminology.html#appendix-1--proposed-value-sets' 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
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	SΣ	0..*	Coding	Code defined by a terminology system	Elements differ in definition for mustSupport: 'false' vs 'true'
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..0			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' Element maximum cardinalities differ: '1' vs '0'
interpretation		0..*	CodeableConcept	High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations.		0..0			Element maximum cardinalities differ: '2147483647' vs '0'
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..0			Element maximum cardinalities differ: '1' vs '0'
method		0..1	CodeableConcept	How it was done Binding: ?? (example): Methods for simple observations.	S	1..1	CodeableConcept	How it was done Binding: ?? (extensible): Methods for personal characteristic observations.	Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1' Elements differ in binding.description: 'Methods for simple observations.' vs 'Methods for personal characteristic observations.'
specimen		0..1	Reference(Specimen)	Specimen used for this observation		0..0			Element maximum cardinalities differ: '1' vs '0'
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..0			Element maximum cardinalities differ: '2147483647' vs '0'
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(Observation | QuestionnaireResponse | MolecularSequence)	Related resource that belongs to the Observation group	Σ	0..*	Reference(Observation | QuestionnaireResponse | MolecularSequence)	Related resource that belongs to the Observation group
derivedFrom	Σ	0..*	Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)	Related measurements the observation is made from	SΣC	0..*	Reference(DocumentReference | QuestionnaireResponse | Observation)	Related measurements the observation is made from	Elements differ in definition for mustSupport: 'false' vs 'true'
component	Σ	0..*	BackboneElement	Component results	Σ	0..*	BackboneElement	Component results
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: ?? (example): Codes identifying names of simple observations.	Σ	1..1	CodeableConcept	Type of component observation (code / type) Binding: ?? (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	C	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.
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