Measurements and simple assertions made about a patient, device or other subject.

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.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

An Extension

An Extension

A unique identifier assigned to this observation.

Allows observations to be distinguished and referenced.

A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed.

Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.

A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure.

To link an Observation to an Encounter use encounter. See the Notes below for guidance on referencing another Observation.

El estatus de la observación.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Codes providing the status of an observation.

Need to track the status of individual results. Some results are finalized before the whole report is finalized.

A code that classifies the general type of observation being made.

In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set.

Codes for high level observation categories.

Used for filtering what observations are retrieved and displayed.

Tipo de observación que se está registrando, en este caso, incapacidad.

Debe utilizarse un código que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

Codes identifying names of simple observations.

Knowing what kind of observation is being made is essential to understanding the observation.

El sistema de codificación que se utiliza para el tipo de observación.

Se recomienda utilizar SNOMED CT para representar el tipo de observación.

Allows for alternative encodings within a code system, and translations to other code systems.

El sistema de codificación que se utiliza para el tipo de observación.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

El código que representa el tipo de observación.

Debe utilizarse un código que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

Need to refer to a particular code in the system.

La descripción legible del código que representa el tipo de observación.

Debe utilizarse una descripción que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

El texto descriptivo del tipo de observación.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

El paciente al que se refiere la observación.

El sujeto de la observación debe ser siempre un paciente.

Observations have no value if you don't know who or what they're about.

The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.

Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use specimen if a reference to a specimen is required. If a code is required instead of a resource use either bodysite for bodysites or the standard extension focusCode.

El encuentro de atención en salud durante el cual se registró la observación.

El encuentro de atención en salud debe ser ambulatorio, de urgencias o de hospitalización.

For some observations it may be important to know the link between an observation and a particular encounter.

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.

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.

Knowing when an observation was deemed true is important to its relevance as well as determining trends.

The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.

For Observations that don’t require review and verification, it may be the same as the lastUpdated time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the lastUpdated time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.

Who was responsible for asserting the observed value as "true".

May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.

The information determined as a result of making the observation, if the information has a simple value.

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.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

Provides a reason why the expected value in the element Observation.value[x] is missing.

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.

Codes specifying why the result (Observation.value[x]) is missing.

For many results it is necessary to handle exceptional values in measurements.

A categorical assessment of an observation value. For example, high, low, normal.

Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

Codes identifying interpretations of observations.

For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

Comments about the observation or the results.

May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.

Need to be able to provide free text additional information.

Indicates the site on the subject's body where the observation was made (i.e. the target site).

Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component.

If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension bodySite.

Codes describing anatomical locations. May include laterality.

Indicates the mechanism used to perform the observation.

Only used if not implicit in code for Observation.code.

Methods for simple observations.

In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results.

The specimen that was used when this observation was made.

Should only be used if not implicit in code found in Observation.code. Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).

The device used to generate the observation data.

Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant.

Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two referenceRange elements would be used.

Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

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.

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.

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.

All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see Notes below.

Componentes que describen detalles específicos de la incapacidad.

For a discussion on the ways Observations can be assembled in groups together see Notes below.

Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

An Extension

An Extension

Describes what was observed. Sometimes this is called the observation "code".

All code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.

Codes identifying names of simple observations.

Knowing what kind of observation is being made is essential to understanding the observation.

Provides a reason why the expected value in the element Observation.component.value[x] is missing.

"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 "test not done".

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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.

Codes specifying why the result (Observation.value[x]) is missing.

For many results it is necessary to handle exceptional values in measurements.

A categorical assessment of an observation value. For example, high, low, normal.

Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

Codes identifying interpretations of observations.

For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

Guidance on how to interpret the value by comparison to a normal or recommended range.

Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

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.

For a discussion on the ways Observations can be assembled in groups together see Notes below.

Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

An Extension

Código que representa el alcance de la incapacidad (nueva o prórroga).

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

Codes identifying names of simple observations.

Knowing what kind of observation is being made is essential to understanding the observation.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

Se recomienda utilizar SNOMED CT para representar el alcance de la incapacidad.

Allows for alternative encodings within a code system, and translations to other code systems.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

El código que representa el alcance de la incapacidad.

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

Need to refer to a particular code in the system.

La descripción legible del código que representa el alcance de la incapacidad.

Debe utilizarse una descripción que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The information determined as a result of making the observation, if the information has a simple value.

Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El código que representa el alcance de la incapacidad (nueva o prórroga).

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

Se recomienda utilizar el sistema de codificación definido para incapacidades en el SIPE.

Allows for alternative encodings within a code system, and translations to other code systems.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

El código que representa el alcance de la incapacidad.

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

Need to refer to a particular code in the system.

La descripción legible del código que representa el alcance de la incapacidad.

Debe utilizarse una descripción que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

Provides a reason why the expected value in the element Observation.component.value[x] is missing.

"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 "test not done".

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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.

Codes specifying why the result (Observation.value[x]) is missing.

For many results it is necessary to handle exceptional values in measurements.

A categorical assessment of an observation value. For example, high, low, normal.

Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

Codes identifying interpretations of observations.

For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

Guidance on how to interpret the value by comparison to a normal or recommended range.

Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

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.

For a discussion on the ways Observations can be assembled in groups together see Notes below.

Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

An Extension

Código que representa el número de días de incapacidad otorgados.

Debe utilizarse un código que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

Codes identifying names of simple observations.

Knowing what kind of observation is being made is essential to understanding the observation.

El sistema de codificación que se utiliza para el número de días de incapacidad.

Se recomienda utilizar SNOMED CT para representar el número de días de incapacidad.

Allows for alternative encodings within a code system, and translations to other code systems.

El sistema de codificación que se utiliza para el número de días de incapacidad.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

El código que representa el número de días de incapacidad.

Debe utilizarse un código que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

Need to refer to a particular code in the system.

La descripción legible del código que representa el número de días de incapacidad.

Debe utilizarse una descripción que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The information determined as a result of making the observation, if the information has a simple value.

Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El número de días de incapacidad otorgados.

El valor debe representar el número total de días de incapacidad otorgados.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El valor numérico que representa el número de días de incapacidad otorgados.

El valor debe ser un número entero positivo que represente el total de días de incapacidad otorgados.

Precision is handled implicitly in almost all cases of measurement.

How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

How the Quantity should be understood and represented.

Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

La unidad de medida para el número de días de incapacidad otorgados.

La unidad debe ser 'días'.

There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

El sistema de unidades utilizado para el número de días de incapacidad.

Need to know the system that defines the coded form of the unit.

El código que representa la unidad de medida para el número de días de incapacidad otorgados.

El código debe ser 'd' para días, según el sistema UCUM.

Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

Provides a reason why the expected value in the element Observation.component.value[x] is missing.

"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 "test not done".

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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.

Codes specifying why the result (Observation.value[x]) is missing.

For many results it is necessary to handle exceptional values in measurements.

A categorical assessment of an observation value. For example, high, low, normal.

Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

Codes identifying interpretations of observations.

For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

Guidance on how to interpret the value by comparison to a normal or recommended range.

Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

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.

For a discussion on the ways Observations can be assembled in groups together see Notes below.

Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

An Extension

An Extension

Código que representa el número de días de incapacidad por maternidad otorgados.

Debe utilizarse un código que represente el número de días de incapacidad por maternidad, empleando la terminología controlada internacional SNOMED CT.

Codes identifying names of simple observations.

Knowing what kind of observation is being made is essential to understanding the observation.

El sistema de codificación que se utiliza para el número de días de incapacidad por maternidad.

Se recomienda utilizar SNOMED CT para representar el número de días de incapacidad por maternidad.

Allows for alternative encodings within a code system, and translations to other code systems.

El sistema de codificación que se utiliza para el número de días de incapacidad por maternidad.

The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.

Need to be unambiguous about the source of the definition of the symbol.

El código que representa el número de días de incapacidad por maternidad.

Debe utilizarse un código que represente el número de días de incapacidad por maternidad, empleando la terminología controlada internacional SNOMED CT.

Need to refer to a particular code in the system.

La descripción legible del código que representa el número de días de incapacidad por maternidad.

Debe utilizarse una descripción que represente el número de días de incapacidad por maternidad, empleando la terminología controlada internacional SNOMED CT.

Need to be able to carry a human-readable meaning of the code for readers that do not know the system.

A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.

Very often the text is the same as a displayName of one of the codings.

The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.

The information determined as a result of making the observation, if the information has a simple value.

Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). 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.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El número de días de incapacidad por maternidad otorgados.

El valor debe representar el número total de días de incapacidad por maternidad otorgados.

An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.

El valor numérico que representa el número de días de incapacidad por maternidad otorgados.

El valor debe ser un número entero positivo que represente el total de días de incapacidad por maternidad otorgados.

Precision is handled implicitly in almost all cases of measurement.

How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.

How the Quantity should be understood and represented.

Need a framework for handling measures where the value is <5ug/L or >400mg/L due to the limitations of measuring methodology.

La unidad de medida para el número de días de incapacidad por maternidad otorgados.

La unidad debe ser 'días'.

There are many representations for units of measure and in many contexts, particular representations are fixed and required. I.e. mcg for micrograms.

El sistema de unidades utilizado para el número de días de incapacidad por maternidad.

Need to know the system that defines the coded form of the unit.

El código que representa la unidad de medida para el número de días de incapacidad por maternidad otorgados.

El código debe ser 'd' para días, según el sistema UCUM.

Need a computable form of the unit that is fixed across all forms. UCUM provides this for quantities, but SNOMED CT provides many units of interest.

Provides a reason why the expected value in the element Observation.component.value[x] is missing.

"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 "test not done".

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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.

Codes specifying why the result (Observation.value[x]) is missing.

For many results it is necessary to handle exceptional values in measurements.

A categorical assessment of an observation value. For example, high, low, normal.

Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.

Codes identifying interpretations of observations.

For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.

Guidance on how to interpret the value by comparison to a normal or recommended range.

Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.

Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.

El estatus de la observación.

Tipo de observación que se está registrando, en este caso, incapacidad.

Debe utilizarse un código que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

El sistema de codificación que se utiliza para el tipo de observación.

Se recomienda utilizar SNOMED CT para representar el tipo de observación.

El sistema de codificación que se utiliza para el tipo de observación.

El código que representa el tipo de observación.

Debe utilizarse un código que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

La descripción legible del código que representa el tipo de observación.

Debe utilizarse una descripción que represente incapacidades, empleando la terminología controlada internacional SNOMED CT.

El texto descriptivo del tipo de observación.

El paciente al que se refiere la observación.

El sujeto de la observación debe ser siempre un paciente.

El encuentro de atención en salud durante el cual se registró la observación.

El encuentro de atención en salud debe ser ambulatorio, de urgencias o de hospitalización.

Componentes que describen detalles específicos de la incapacidad.

Código que representa el alcance de la incapacidad (nueva o prórroga).

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

Se recomienda utilizar SNOMED CT para representar el alcance de la incapacidad.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

El código que representa el alcance de la incapacidad.

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

La descripción legible del código que representa el alcance de la incapacidad.

Debe utilizarse una descripción que represente el alcance de la incapacidad, empleando la terminología controlada internacional SNOMED CT.

El código que representa el alcance de la incapacidad (nueva o prórroga).

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

Se recomienda utilizar el sistema de codificación definido para incapacidades en el SIPE.

El sistema de codificación que se utiliza para el alcance de la incapacidad.

El código que representa el alcance de la incapacidad.

Debe utilizarse un código que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

La descripción legible del código que representa el alcance de la incapacidad.

Debe utilizarse una descripción que represente el alcance de la incapacidad, empleando la terminología controlada nacional definida para incapacidades en el SIPE.

Código que representa el número de días de incapacidad otorgados.

Debe utilizarse un código que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

El sistema de codificación que se utiliza para el número de días de incapacidad.

Se recomienda utilizar SNOMED CT para representar el número de días de incapacidad.

El sistema de codificación que se utiliza para el número de días de incapacidad.

El código que representa el número de días de incapacidad.

Debe utilizarse un código que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

La descripción legible del código que representa el número de días de incapacidad.

Debe utilizarse una descripción que represente el número de días de incapacidad, empleando la terminología controlada internacional SNOMED CT.

El número de días de incapacidad otorgados.

El valor debe representar el número total de días de incapacidad otorgados.

El valor numérico que representa el número de días de incapacidad otorgados.

El valor debe ser un número entero positivo que represente el total de días de incapacidad otorgados.

La unidad de medida para el número de días de incapacidad otorgados.

La unidad debe ser 'días'.

El sistema de unidades utilizado para el número de días de incapacidad.

El código que representa la unidad de medida para el número de días de incapacidad otorgados.

El código debe ser 'd' para días, según el sistema UCUM.