Identificador lógico deste artefato

Metadados sobre o recurso

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

Idioma do recurso

Resumo do texto do recurso em linguagem natural

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

proposed | active | suspended | inactive | entered-in-error

Tipo da equipe assistêncial

Nome da equipe assistêncial

Paciente referenciado pela equipe assistêncial

Referência ao atendimento

Período de atendimento pela a equipe assistêncial

Lista de participantes envolvidos 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 na equipe assistêncial

Referência ao partipante

Organização do participante

Período de tempo do participante atua no time assistêncial

Motivo pelo qual a equipe assistência foi criada

Referência aos diagnóstico que esta equipe assistencial cobre

Organização da equipe assistêncial

Contato da equipe assistencial

Comentários adicionais sobre a equipe assistencial

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for 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

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 care team as it is known by various participating systems and in a way that remains consistent across servers.

proposed | active | suspended | inactive | entered-in-error

This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid.

Indicates the status of the care team.

Tipo da equipe assistêncial

There may be multiple axis of categorization and one team may serve multiple purposes.

Used for filtering what teams(s) are retrieved and displayed to different types of users.

Nome da equipe assistêncial

The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.).

Paciente referenciado pela equipe assistêncial

Allows the team to care for a group (e.g. marriage) therapy. Allows for an organization to designate a team such as the PICC line team.

Referência ao atendimento

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.

Período de atendimento pela a equipe assistêncial

Allows tracking what team(s) are in effect at a particular time.

Lista de participantes envolvidos 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 na equipe assistêncial

Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly.

Referência ao partipante

Patient only needs to be listed if they have a role other than "subject of care".

Member is optional because some participants may be known only by their role, particularly in draft plans.

Organização do participante

Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.

Período de tempo do participante atua no time assistêncial

Motivo pelo qual a equipe assistência foi criada

Indicates the reason for the care team.

Referência aos diagnóstico que esta equipe assistencial cobre

Organização da equipe assistêncial

Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.

Contato da equipe assistencial

The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.

Comentários adicionais sobre a equipe assistencial

The Care Team includes all the people and organizations who plan to participate in the coordination and delivery of care for 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

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 care team as it is known by various participating systems and in a way that remains consistent across servers.

proposed | active | suspended | inactive | entered-in-error

This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid.

Indicates the status of the care team.

Tipo da equipe assistêncial

There may be multiple axis of categorization and one team may serve multiple purposes.

Used for filtering what teams(s) are retrieved and displayed to different types of users.

Nome da equipe assistêncial

The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.).

Paciente referenciado pela equipe assistêncial

Allows the team to care for a group (e.g. marriage) therapy. Allows for an organization to designate a team such as the PICC line team.

Referência ao atendimento

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.

Período de atendimento pela a equipe assistêncial

Allows tracking what team(s) are in effect at a particular time.

Lista de participantes envolvidos 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 na equipe assistêncial

Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly.

Referência ao partipante

Patient only needs to be listed if they have a role other than "subject of care".

Member is optional because some participants may be known only by their role, particularly in draft plans.

Organização do participante

Practitioners can be associated with multiple organizations. This element indicates which organization they were acting on behalf of.

Período de tempo do participante atua no time assistêncial

Motivo pelo qual a equipe assistência foi criada

Indicates the reason for the care team.

Referência aos diagnóstico que esta equipe assistencial cobre

Organização da equipe assistêncial

Allows for multiple organizations to collaboratively manage cross-organizational, longitudinal care plan.

Contato da equipe assistencial

The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.

Comentários adicionais sobre a equipe assistencial