us-core-observation-screening-assessment vs MassAbnormality

Language of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional Bindings

Purpose

AllLanguages

Max Binding

0..1

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..0

Element maximum cardinalities differ: '2147483647' vs '0'

extension

0..*

Additional content defined by implementations

0..*

Additional content defined by implementations

modifierExtension

0..*

Extensions that cannot be ignored

0..*

Extensions that cannot be ignored

identifier

0..*

Identifier

Business Identifier for observation

0..*

Identifier

Business Identifier for observation

basedOn

0..*

Fulfills plan, proposal or order

0..0

Element maximum cardinalities differ: '2147483647' vs '0'

partOf

0..*

Part of referenced event

0..0

Element maximum cardinalities differ: '2147483647' vs '0'

status

?!SΣ

1..1

registered | preliminary | final | amended +
Binding: ObservationStatus (required): Codes providing the status of an observation.

?!SΣ

1..1

registered | preliminary | final | amended +
Binding: ObservationStatus (required): Codes providing the status of an observation.

Slices for category

1..*

Classification of type of observation
Slice: Unordered, Open by pattern:$this
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

2..*

Classification of type of observation
Slice: Unordered, Open by pattern:$this
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Element minimum cardinalities differ: '1' vs '2'

code

SΣ

1..1

Type of observation (code / type)
Binding: US Core Survey Codes (preferred)

SΣ

1..1

Reference(US Core Patient Profile)

Imaging Name
Binding: US Core Non Laboratory Codes (extensible)
Required Pattern: {"coding":[{"system":"http://hl7.org/fhir/us/breast-radiology/CodeSystem/RadLexCDE","code":"RDES246"}]}

Elements differ in short: 'Type of observation (code / type)' vs 'Imaging Name'
Elements differ in definition: 'Describes what was observed. Sometimes this is called the observation "name".' vs 'The name of the imaging test performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.'
Elements differ in comments: '*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.' vs '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.'

subject

SΣ

1..1

Who and/or what the observation is about

SΣ

1..1

Reference(US Core Patient Profile)

Who and/or what the observation is about

focus

ΣTU

0..*

Reference(Resource)

What the observation is about, when it is not about the subject of record

0..0

Element maximum cardinalities differ: '2147483647' vs '0'

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

Clinically relevant time/time-period for observation
us-core-1: Datetime must be at least to day.

SΣC

0..1

dateTime S, Period, Timing, instant

Clinically relevant time/time-period for observation

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 '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 comments: 'At least a date should be present unless this observation is a historical report.' 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.'

issued

0..1

instant

Date/Time this version was made available

0..1

instant

Date/Time this version was made available

performer

SΣ

0..*

Who is responsible for the observation

0..*

Who is responsible for the observation

Elements differ in definition for mustSupport: 'true' vs 'false'

value[x]

SΣC

0..1

Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period

Actual result

SΣC

0..0

Elements differ in short: 'Actual result' vs 'Result Value'
Elements differ in comments: 'An observation may have a value if it represents an individual survey, screening, or assessment question and answer pair. An observation should not have a value if it represents a multi-question or multi-select “check all that apply” responses. 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.'
Element maximum cardinalities differ: '1' vs '0'

dataAbsentReason

0..1

Why the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

0..0

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.'
Element maximum cardinalities differ: '1' vs '0'

interpretation

0..*

High, low, normal, etc.
Binding: ObservationInterpretationCodes (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

Observed body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

1..1

Observed body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

Element minimum cardinalities differ: '0' vs '1'

0..1

Unique id for inter-element referencing

0..1

Unique id for inter-element referencing

Slices for extension

0..*

Additional content defined by implementations
Slice: Unordered, Open by value:url

1..*

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 element. 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'
Element minimum cardinalities differ: '0' vs '1'

coding

0..*

Coding

Code defined by a terminology system

0..*

Coding

Code defined by a terminology system

text

0..1

Plain text representation of the concept

0..1

Plain text representation of the concept

method

0..1

How it was done
Binding: ObservationMethods (example): Methods for simple observations.

0..1

How it was done
Binding: ObservationMethods (example): Methods for simple 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..0

Element maximum cardinalities differ: '1' vs '0'

referenceRange

0..*

BackboneElement

Provides guide for interpretation

0..0

Element maximum cardinalities differ: '2147483647' vs '0'

0..1

Unique id for inter-element referencing

0..1

Unique id for inter-element referencing

extension

0..*

Additional content defined by implementations

0..*

Additional content defined by implementations

modifierExtension

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

low

0..1

Low Range, if relevant

0..1

Low Range, if relevant

high

0..1

High Range, if relevant

0..1

High Range, if relevant

type

0..1

Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

0..1

Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

appliesTo

0..*

Reference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.

0..*

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

Text based reference range in an observation

0..1