ID lógico deste artefato, único para este perfil de Observation radiológica.

Metadados sobre o recurso, incluindo versão, perfil e outras informações relevantes.

Um conjunto de regras sob as quais este conteúdo foi criado.

Idioma em que o recurso foi escrito.

Resumo do texto do recurso, para interpretação humana

Recursos contidos no recurso principal

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas

Identificadores do Observation

Executa um plano, uma proposta ou uma ordem

Indica se o Observation é parte de outro evento

registered | preliminary | final | amended +

Conceito - referência a uma terminologia ou apenas texto

Categoria do Observation

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Representação codificada utilizando um sistema de terminologia padronizada

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Identidade do sistema terminológico

Versão do sistema - se relevante

O código específico da categoria do Observation

A descrição legível por humanos do código da categoria do Observation

Indica se o código foi selecionado diretamente pelo usuário

Texto com a representação da categoria

Conceito - referência a uma terminologia ou apenas texto

Sobre quem e/ou sobre o que se trata o Observation

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Indica a qual recurso a referência se refere (por exemplo, Paciente)

Referência lógica, quando a referência literal não é conhecida

Alternativa de texto para o recurso

Do que trata o Observation, quando não se trata do sujeito do registro

Referência ao Evento de saúde durante o qual esto Observation foi realizada

O tempo/período clinicamente relevante paro Observation

Conteúdo adicional definido por implementações

Identificador único para referência entre elementos

Motivo pelo qual os dados do período clinicamente relevante paro Observation estão ausentes

Data e hora em que o Observation foi foi disponibilizada

A pessoa ou organização responsável por realizar o Observation

O valor ou resultado do Observation

Representação em texto do valor ou resultado do Observation

Motivo pelo qual as informações do resultado do Observation estão ausentes

Códigos que identificam interpretações de observações

Notas ou comentários adicionais sobre o Observation

Local específico do corpo no qual o Observation foi realizada

O método ou técnica utilizada para realizar o Observation

Amostra (por exemplo, tecido, sangue) utilizada no Observation

O dispositivo utilizado para capturar o Observation

Intervalo de valores esperados ou típicos para os resultados do Observation

Identificador único para a faixa de referência

Conteúdo adicional definido por implementações

Extensões que alteram a interpretação da faixa de referência

O limite inferior do intervalo de valores esperados para o Observation

O limite superior do intervalo de valores esperados para o Observation

O tipo ou natureza da faixa de referência

Grupos específicos aos quais a faixa de referência se aplica (por exemplo, idade, sexo)

Faixa etária à qual a faixa de referência se aplica

Descrição da faixa de referência

Recurso relacionado que pertence ao grupo de Observation

Identificador único de referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

O tipo de recurso que é referenciado

Referência lógica, quando a referência literal não é conhecida

Texto alternativo para o recurso relacionado

Medições relacionadas a partir das quais a observação é feita

Componentes do Observation

Identificador único para o Component do Observation

Extensões adicionais aplicáveis ao Component do Observation

Extensões que alteram a interpretação do Component do Observation

O código que identifica o Component específico do Observation

Resultado do Component específico do Observation

Motivo pelo qual as informações do Component estão ausentes

Interpretação ou conclusão derivada do Component do Observation

Faixa de valores esperados ou típicos para os resultados do Component

Texto do Observation

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas

Conceito - referência a uma terminologia ou apenas texto

Resultado real do componente

Porque o resultado do componente está faltando

Códigos que identificam interpretações do Component do Observation

Fornece guia para interpretação do resultado do componente

Identificador único para o código do do Component do Observation

Extensões adicionais aplicáveis ao código do Component do Observation

Extensões que alteram a interpretação do código do Component do Observation

Conceito - referência a uma terminologia ou apenas texto

Valor ou resultado codificado do Component do Observation

Motivo pelo qual as informações do código do Component do Observation estão ausentes

Interpretação ou conclusão derivada do código do Component do Observation

Faixa de valores esperados ou típicos para os resultados do código do Component do Observation

Métricas do Component do Observation, incluindo medições de quantidade linear, de área e de volume

Identificador único para o Component de métricas do Observation

Extensões adicionais do Component de métricas do Observation

Extensões que alteram a interpretação do Component de métricas do Observation

Código que identifica a medição quantitativa do Component do Observation

Valor numérico da quantidade medida usando UCUM

Códigos que especificam por que o resultado (Observation.value[x]) está faltando

Códigos que identificam interpretações do Observation

Fornece orientações para interpretação do resultado do Component do Observation

Medidas do Component do Observation, incluindo medições lineares, de área e volume

Identificador único do Component do Observation

Conteúdo adicional definido por implementações

Extensões que alteram a interpretação da medição de intervalo numérico no Component

Código que identifica a medição de intervalo numérico no Component

Valor numérico ou intervalo da medição no Component

Motivo pelo qual os dados da medição de intervalo estão ausentes no Component

Interpretação ou conclusão derivada da medição de intervalo numérico no Component

Faixa de valores esperados ou típicos para os resultados da medição de intervalo no Component

Medição de observação, incluindo medidas lineares, de área e de faixa de volume

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas

Conceito - referência a uma terminologia ou apenas texto

Conjunto de valores no intelvalo classificado por baixo e alto

Códigos que especificam porque o resultado está faltando

Interpretação ou conclusão derivada da medição de razão numérica no Component

Fornece guia para interpretação do resultado do componente

Medição de observação, incluindo medições de dados de amostras lineares, de área e de volume

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas

Conceito - referência a uma terminologia ou apenas texto

Resultado real do componente

Motivo que identifica porque o resultado do componente está faltando

Códigos que identificam interpretações das observações

Fornece um guia para interpretação do resultado do componente

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.

ID lógico deste artefato, único para este perfil de Observation radiológica.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

Metadados sobre o recurso, incluindo versão, perfil e outras informações relevantes.

Um conjunto de regras sob as quais este conteúdo foi criado.

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.

Idioma em que o recurso foi escrito.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human language.

Resumo do texto do recurso, para interpretação humana

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

Recursos contidos no recurso principal

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas

Identificadores do Observation

Allows observations to be distinguished and referenced.

Executa um plano, uma proposta ou uma ordem

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

Indica se o Observation é parte de outro evento

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

registered | preliminary | final | amended +

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.

Conceito - referência a uma terminologia ou apenas texto

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Codes for high level observation categories.

Used for filtering what observations are retrieved and displayed.

Categoria do Observation

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Codes for high level observation categories.

Used for filtering what observations are retrieved and displayed.

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Representação codificada utilizando um sistema de terminologia padronizada

Codes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.

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

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Identidade do sistema terminológico

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.

Versão do sistema - se relevante

Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.

O código específico da categoria do Observation

Need to refer to a particular code in the system.

A descrição legível por humanos do código da categoria do Observation

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

Language translation from base language of resource to another language.

Indica se o código foi selecionado diretamente pelo usuário

Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.

This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.

Texto com a representação da categoria

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.

Conceito - referência a uma terminologia ou apenas texto

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

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

Sobre quem e/ou sobre o que se trata o Observation

One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.

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

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

Indica a qual recurso a referência se refere (por exemplo, Paciente)

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Referência lógica, quando a referência literal não é conhecida

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Alternativa de texto para o recurso

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Do que trata o Observation, quando não se trata do sujeito do registro

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.

Referência ao Evento de saúde durante o qual esto Observation foi realizada

This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).

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

O tempo/período clinicamente relevante paro Observation

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.

Conteúdo adicional definido por implementações

Identificador único para referência entre elementos

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Motivo pelo qual os dados do período clinicamente relevante paro Observation estão ausentes

Data e hora em que o Observation foi foi disponibilizada

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.

A pessoa ou organização responsável por realizar o Observation

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

O valor ou resultado do Observation

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.

Representação em texto do valor ou resultado do Observation

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.

Motivo pelo qual as informações do resultado do Observation estão ausentes

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.

Códigos que identificam interpretações de observações

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.

Notas ou comentários adicionais sobre o Observation

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.

Local específico do corpo no qual o Observation foi realizada

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

Codes describing anatomical locations. May include laterality.

O método ou técnica utilizada para realizar o 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.

Amostra (por exemplo, tecido, sangue) utilizada no Observation

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

O dispositivo utilizado para capturar o Observation

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.

Intervalo de valores esperados ou típicos para os resultados do Observation

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.

Identificador único para a faixa de referência

Conteúdo adicional definido por implementações

Extensões que alteram a interpretação da faixa de referência

O limite inferior do intervalo de valores esperados para o Observation

O limite superior do intervalo de valores esperados para o Observation

O tipo ou natureza da faixa de referência

This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed.

Code for the meaning of a reference range.

Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation.

Grupos específicos aos quais a faixa de referência se aplica (por exemplo, idade, sexo)

This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed.

Codes identifying the population the reference range applies to.

Need to be able to identify the target population for proper interpretation.

Faixa etária à qual a faixa de referência se aplica

Some analytes vary greatly over age.

Descrição da faixa de referência

Recurso relacionado que pertence ao grupo de Observation

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.

Identificador único de referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.

O tipo de recurso que é referenciado

This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.

Aa resource (or, for logical models, the URI of the logical model).

Referência lógica, quando a referência literal não é conhecida

When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy.

When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference

Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it.

Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).

Texto alternativo para o recurso relacionado

This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

Medições relacionadas a partir das quais a observação é feita

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 do Observation

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

Required if not(exists(Observation.valueString))

Identificador único para o Component do Observation

Extensões adicionais aplicáveis ao Component do Observation

Extensões que alteram a interpretação do Component do Observation

O código que identifica o Component específico do Observation

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.

Resultado do Component específico do Observation

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.

Motivo pelo qual as informações do Component estão ausentes

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

Interpretação ou conclusão derivada do Component do Observation

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.

Faixa de valores esperados ou típicos para os resultados do Component

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.

Texto do Observation

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.

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas

Conceito - referência a uma terminologia ou apenas texto

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

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

Resultado real do componente

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.

Porque o resultado do componente está faltando

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

Códigos que identificam interpretações do Component do Observation

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.

Fornece guia para interpretação do resultado do componente

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.