Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab vs http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation

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	2020-06-27	2022-01-18T12:57:33+00:00	Values Differ
description	Defines constraints and extensions on the Observation resource for the minimal set of data to query and retrieve laboratory test results	This Observation profile represents, if the incoming eICR was not successfully processed for a determination of reportability, the reason it was not processed.	Values Differ
experimental	false
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreLaboratoryResultObservationProfile	RR_Eicr_Processing_Status_Reason_Observation	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 Public Health Work Group (http://www.hl7.org/Special/committees/pher/index.cfm)	Values Differ
purpose
status	active
title	US Core Laboratory Result Observation Profile	eICR Processing Status Reason Observation	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab	http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation	Values Differ
version	4.1.0	2.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	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	SI	0..*	Observation	eICR Processing Status Reason	Elements differ in short: 'Measurements and simple assertions' vs 'eICR Processing Status Reason' 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.' vs 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version fo the RCTC, these are flagged and compoent observations will hold the details of the outdated and expected versions of the RCTC.' Elements differ in definition for mustSupport: 'false' vs 'true'
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) Max Binding: AllLanguages: A human language.		0..1	code	Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language.
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: ObservationStatus (required)	?!Σ	1..1	code	registered | preliminary | final | amended + Binding: ObservationStatus (required): Codes providing the status of an observation. Fixed Value: final	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.		0..*	CodeableConcept	Classification of type of observation Binding: ObservationCategoryCodes (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	Laboratory Test Name Binding: LOINCCodes (extensible): LOINC codes	Σ	1..1	CodeableConcept	Type of observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations. Required Pattern: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.232","code":"RR6","display":"eICR Processing Status Reason"}]}	Elements differ in short: 'Laboratory Test Name' vs 'Type of observation (code / type)' Elements differ in definition: 'The test that was performed. 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.' Elements differ in definition for mustSupport: 'true' vs 'false' Elements differ in binding.description: 'LOINC codes' vs 'Codes identifying names of simple observations.'
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who and/or what the observation is about	Σ	0..1	Reference(Patient | Group | Device | Location)	Who and/or what the observation is about	Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
focus	Σ	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record	Σ	0..*	Reference(Resource)	What the observation is about, when it is not about the subject of record
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Σ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.	Σ	0..1	dateTime, Period, Timing, instant	Clinically relevant time/time-period for observation	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.' 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.' 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	Σ	0..*	Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)	Who is responsible for the observation
value[x]	SΣI	0..1	Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Result Value us-core-4: SHOULD use Snomed CT for coded Results us-core-3: SHALL use UCUM for coded quantity units.	ΣI	0..1	CodeableConcept	Processing status reason Binding: eICR Processing Status Reason (eCR) (extensible): Processing Status Reason Example Example for CodeableConcept: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.274","code":"RRVS30","display":"eICR was processed with the warning of: inactive RCTC code"}]}	Elements differ in short: 'Result Value' vs 'Processing status reason' Elements differ in definition: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT] if the concept exists. 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 'If the incoming eICR was not successfully processed for a determination of reportability, contains the reason it was not processed.' Elements differ in definition for mustSupport: 'true' vs 'false'
dataAbsentReason	SI	0..1	CodeableConcept	Why the result is missing Binding: DataAbsentReason (extensible)	I	0..1	CodeableConcept	Why the result is missing Binding: DataAbsentReason (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: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.		0..*	CodeableConcept	High, low, normal, etc. Binding: ObservationInterpretationCodes (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: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.		0..1	CodeableConcept	Observed body part Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
method		0..1	CodeableConcept	How it was done Binding: ObservationMethods (example): Methods for simple observations.		0..1	CodeableConcept	How it was done Binding: ObservationMethods (example): Methods for simple observations.
specimen		0..1	Reference(Specimen)	Specimen used for this observation		0..1	Reference(Specimen)	Specimen used for this observation
device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device		0..1	Reference(Device | DeviceMetric)	(Measurement) Device
referenceRange	I	0..*	BackboneElement	Provides guide for interpretation obs-3: Must have at least a low or a high or text	I	0..*	BackboneElement	Provides guide for interpretation obs-3: Must have at least a low or a high or text
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	Σ	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	Σ	0..*	Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)	Related measurements the observation is made from
component	Σ	0..*	BackboneElement	Component results	SΣ	0..*	BackboneElement	eICR Processing Status Reason Detail	Elements differ in short: 'Component results' vs 'eICR Processing Status Reason Detail' 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.' vs 'Further details about eICR processing status warnings or errors. If any of the trigger codes used to generate the eICR are from an outdated version of the RCTC or the codes are marked as inactive in the latest version of the RCTC, will contain the details of the outdated and expected versions of the RCTC.' Elements differ in definition for mustSupport: 'false' vs 'true'
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.	SΣ	1..1	CodeableConcept	Type of processing status reason detail Binding: eICR Processing Status Reason Detail Type (eCR) (extensible): Processing Status Reason Detail Type Example General: {"coding":[{"system":"urn:oid:2.16.840.1.114222.4.5.274","code":"RRVS32","display":"Inactive RCTC code detail"}]}	Elements differ in short: 'Type of component observation (code / type)' vs 'Type of processing status reason detail' Elements differ in definition for mustSupport: 'false' vs 'true' Elements differ in binding.description: 'Codes identifying names of simple observations.' vs 'Processing Status Reason Detail Type'
value[x]	Σ	0..1	Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period	Actual component result	SΣ	1..1	CodeableConcept, string	Processing status reason detail Example General: {"coding":[{"system":"http://snomed.info/sct","code":"69092001","display":"Leptospirosis icterohemorrhagica (disorder)"}]}	Elements differ in short: 'Actual component result' vs 'Processing status reason detail' Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1'
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