An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

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.

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

Identificadores externos para este recurso

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Status atual do atendimento: planned | arrived | triaged | in-progress | onleave | finished | cancelled +

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Current state of the encounter.

Classificação do atendimento com o paciente

Classification of the encounter.

Tipo específico do atendimento

Since there are many ways to further classify encounters, this element is 0..*.

Prioridade do atendimento

Referência ao paciente ou grupo deste atendimento

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

Participantes no atendimento

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

Função do participante no atendimento

The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

Referência à profissionais envolvidos no atendimento

Hora de início e término do atendimento

If not (yet) known, the end of the Period may be omitted.

Queixa principal do atendimento

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Referência ao motivo do atendimento

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

A organização (instalação) responsável por este encontro

An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.

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

Resumo do texto do recurso em linguagem natural

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

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

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The purpose of this identifier.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

Allows users to make use of identifiers when the identifier system is not known.

Establishes the namespace for the value - that is, a URL that describes a set values that are unique.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

The portion of the identifier typically relevant to the user and which is unique within the context of the system.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Status atual do atendimento: planned | arrived | triaged | in-progress | onleave | finished | cancelled +

Note that internal business rules will determine the appropriate transitions that may occur between statuses (and also classes).

Current state of the encounter.

Lista de status de atendimentos anteriores

The current status is always found in the current version of the resource, not the status history.

Identificador único para referência 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

Status de atendimentos anteriores: planned | arrived | triaged | in-progress | onleave | finished | cancelled +

Current state of the encounter.

O tempo em que o episódio estava no status especificado

Classificação do atendimento com o paciente

Classification of the encounter.

Lista de classes de atendimentos anteriores

Identificador único para referência 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

Classe dos atendimento anteriore

Classification of the encounter.

Período do atendimento anteriore

Tipo específico do atendimento

Since there are many ways to further classify encounters, this element is 0..*.

Tipo específico do serviço

Prioridade do atendimento

Referência ao paciente ou grupo deste atendimento

While the encounter is always about the patient, the patient might not actually be known in all contexts of use, and there may be a group of patients that could be anonymous (such as in a group therapy for Alcoholics Anonymous - where the recording of the encounter could be used for billing on the number of people/staff and not important to the context of the specific patients) or alternately in veterinary care a herd of sheep receiving treatment (where the animals are not individually tracked).

Referência ao episódio de cuidado relacionado a este atendimento

Referência ao ServiceRequest que iniciou este atendimento

Participantes no atendimento

Identificador único para referência 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

Função do participante no atendimento

The participant type indicates how an individual participates in an encounter. It includes non-practitioner participants, and for practitioners this is to describe the action type in the context of this encounter (e.g. Admitting Dr, Attending Dr, Translator, Consulting Dr). This is different to the practitioner roles which are functional roles, derived from terms of employment, education, licensing, etc.

Período de atuação do participante

Referência à profissionais envolvidos no atendimento

Referência ao agendamento desde atendimento

Hora de início e término do atendimento

If not (yet) known, the end of the Period may be omitted.

Duração do atendimento

May differ from the time the Encounter.period lasted because of leave of absence.

Queixa principal do atendimento

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Referência ao motivo do atendimento

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Lista de diagnósticos deste atendimento

Identificador único para referência 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

O diagnóstico ou procedimento relevante para este atendimento

For systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).

Papel deste diagnóstico no atendimento (por exemplo, internação, faturamento, alta…)

Classificação do diagnóstico

Referências as contas desde atendimento

The billing system may choose to allocate billable items associated with the Encounter to different referenced Accounts based on internal business rules.

Detalhes sobre a internação em um serviço de saúde

An Encounter may cover more than just the inpatient stay. Contexts such as outpatients, community clinics, and aged care facilities are also included.

The duration recorded in the period of this encounter covers the entire scope of this hospitalization record.

Identificador único para referência 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

Identificador de pré-internação

Referência ao local/organização de onde o paciente veio antes da internação

De onde o paciente foi admitido (encaminhamento médico, transferência)

O tipo de readmissão hospitalar (se houver). Se o valor estiver ausente, a internação não será dentificada como uma reinternação

The reason for re-admission of this hospitalization encounter.

Preferências alimentares do paciente

For example, a patient may request both a dairy-free and nut-free diet preference (not mutually exclusive).

Medical, cultural or ethical food preferences to help with catering requirements.

Used to track patient's diet restrictions and/or preference. For a complete description of the nutrition needs of a patient during their stay, one should use the nutritionOrder resource which links to Encounter.

Cortesias especiais (VIP, membro do conselho)

Special courtesies.

Necessidades especiais: cadeira de rodas, tradutor, maca, etc

Special arrangements.

Referência ao local/organização de encaminhamento pós-alta

Categoria ou tipo de local após a alta

Lista de locais onde o paciente esteve

Virtual encounters can be recorded in the Encounter by specifying a location reference to a location of type "kind" such as "client's home" and an encounter.class = "virtual".

Identificador único para referência 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

Local onde o atendimento acontece

O status do local: planned | active | reserved | completed

When the patient is no longer active at a location, then the period end date is entered, and the status may be changed to completed.

O tipo físico do local (geralmente o nível na hierarquia do local - quarto, enfermaria, etc.)

This information is de-normalized from the Location resource to support the easier understanding of the encounter resource and processing in messaging or query.

There may be many levels in the hierachy, and this may only pic specific levels that are required for a specific usage scenario.

Período de tempo durante o qual o paciente esteve presente no local

A organização (instalação) responsável por este encontro

Outro atendimento do qual este atendimento faz parte

This is also used for associating a child's encounter back to the mother's encounter.

Refer to the Notes section in the Patient resource for further details.