Identificador lógico deste artefato

Metadados sobre o recurso

Um ou mais códigos que servem para identificar o tipo de recurso

Idioma do recurso

Um texto resumindo as informações do recurso

Recursos contidos no recurso

Extensões adicionais que não fazem parte do modelo base

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

Identificadores externos para este recurso

O status clínico da condição ou do diagnóstico

unconfirmed | provisional | differential | confirmed | refuted | entered-in-error

Categoria da condição

Severidade da condição

Identifica a suspeita diagnóstica com relação à condição de saúde avaliada.

Local anatômico da condição, se relevante

Referencia os dados sobre o indivíduo cuja a condição de saúde está sendo avaliada.

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

Referência literal. URL relativa, interna ou externa

Tipo de recurso ao qual a referência é feita

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

Texto alternativo para o recurso

Referência ao atendimento no qual a condição foi diagnosticada

Data ou idade estimada ou real do começo dos sintomas

Data ou idade estimada ou real em que o diagnóstico foi resolvido ou entrou em remissão

Data na qual o registro foi registrado pela primeira vez

Quem registrou a condição

Pessoa que afirma a condição

Estágio/grau da condição, geralmente avaliado formalmente

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos descrevendo estágios da condição (por exemplo, estágios de câncer)

Referência aos dados de diagnóstico de laboratório clínico relacionados à suspeita diagnóstica.

Códigos que descrevem o tipo do estadiamento (por exemplo, clínico ou patológico)

Evidências de apoio ao diagnóstico

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos que descrevem a manifestação ou sintomas de uma condição

Referência à informações de apoio

Informações adicionais sobre a condição

A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

Identificador lógico deste artefato

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

Um ou mais códigos que servem para identificar o tipo de recurso

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

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.

Um texto resumindo as informações do recurso

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

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.

Extensões adicionais que não fazem parte do modelo base

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

Identificadores externos para este recurso

This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.

O status clínico da condição ou do diagnóstico

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.

The clinical status of the condition or diagnosis.

unconfirmed | provisional | differential | confirmed | refuted | entered-in-error

This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.

The verification status to support or decline the clinical status of the condition or diagnosis.

Categoria da condição

In this profile, Condition represents a health problem of the patient. Therefore one of the category value(s) must be problem-list-item.

Severidade da condição

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.

Identifica a suspeita diagnóstica com relação à condição de saúde avaliada.

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.

Code for a clinical problem that is selected from SNOMED CT or a code for absent/unknown problem

0..1 to account for primarily narrative only resources.

Local anatômico da condição, se relevante

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.

Referencia os dados sobre o indivíduo cuja a condição de saúde está sendo avaliada.

Group is typically used for veterinary or public health use cases.

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

Referência literal. URL relativa, interna ou externa

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.

Tipo de recurso ao qual a referência é feita

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

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.

Referência ao atendimento no qual a condição foi diagnosticada

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".

Data ou idade estimada ou real do começo dos sintomas

Age is generally used when the patient reports an age at which the Condition began to occur.

Data ou idade estimada ou real em que o diagnóstico foi resolvido ou entrou em remissão

There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.

Data na qual o registro foi registrado pela primeira vez

Quem registrou a condição

Pessoa que afirma a condição

Estágio/grau da condição, geralmente avaliado formalmente

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos descrevendo estágios da condição (por exemplo, estágios de câncer)

Codes describing condition stages (e.g. Cancer stages).

Referência aos dados de diagnóstico de laboratório clínico relacionados à suspeita diagnóstica.

Códigos que descrevem o tipo do estadiamento (por exemplo, clínico ou patológico)

Codes describing the kind of condition staging (e.g. clinical or pathological).

Evidências de apoio ao diagnóstico

The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos que descrevem a manifestação ou sintomas de uma condição

Codes that describe the manifestation or symptoms of a condition.

Referência à informações de apoio

Informações adicionais sobre a condição

A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.

Identificador lógico deste artefato

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

Um ou mais códigos que servem para identificar o tipo de recurso

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

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.

Um texto resumindo as informações do recurso

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

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.

Extensões adicionais que não fazem parte do modelo base

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

Identificadores externos para este recurso

This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.

Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.

O status clínico da condição ou do diagnóstico

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.

The clinical status of the condition or diagnosis.

unconfirmed | provisional | differential | confirmed | refuted | entered-in-error

This element is labeled as a modifier because the status contains the code refuted and entered-in-error that mark the Condition as not currently valid.

The verification status to support or decline the clinical status of the condition or diagnosis.

Categoria da condição

In this profile, Condition represents a health problem of the patient. Therefore one of the category value(s) must be problem-list-item.

Severidade da condição

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.

Identifica a suspeita diagnóstica com relação à condição de saúde avaliada.

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.

Code for a clinical problem that is selected from SNOMED CT or a code for absent/unknown problem

0..1 to account for primarily narrative only resources.

Local anatômico da condição, se relevante

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.

Referencia os dados sobre o indivíduo cuja a condição de saúde está sendo avaliada.

Group is typically used for veterinary or public health use cases.

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

Referência literal. URL relativa, interna ou externa

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.

Tipo de recurso ao qual a referência é feita

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

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.

Referência ao atendimento no qual a condição foi diagnosticada

This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".

Data ou idade estimada ou real do começo dos sintomas

Age is generally used when the patient reports an age at which the Condition began to occur.

Data ou idade estimada ou real em que o diagnóstico foi resolvido ou entrou em remissão

There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.

Data na qual o registro foi registrado pela primeira vez

Quem registrou a condição

Pessoa que afirma a condição

Estágio/grau da condição, geralmente avaliado formalmente

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos descrevendo estágios da condição (por exemplo, estágios de câncer)

Codes describing condition stages (e.g. Cancer stages).

Referência aos dados de diagnóstico de laboratório clínico relacionados à suspeita diagnóstica.

Códigos que descrevem o tipo do estadiamento (por exemplo, clínico ou patológico)

Codes describing the kind of condition staging (e.g. clinical or pathological).

Evidências de apoio ao diagnóstico

The evidence may be a simple list of coded symptoms/manifestations, or references to observations or formal assessments, or both.

Identificador único para referenciação cruzada

Extensões adicionais que não fazem parte do modelo de dados básico

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

Códigos que descrevem a manifestação ou sintomas de uma condição

Codes that describe the manifestation or symptoms of a condition.

Referência à informações de apoio

Informações adicionais sobre a condição