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 neste 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 para este Appointment (p.ex. identificador do sistema local ou da RNDS)

Situação atual do agendamento (proposto, pendente, agendado, concluído, cancelado, etc.)

Razão codificada para cancelamento do agendamento

Categoria ampla do serviço de saúde

Tipo específico de serviço/atendimento a ser realizado

Especialidade clínica requerida para o atendimento

Classificação do agendamento (p.ex. rotina, retorno, encaixe)

Códigos que expressam a justificativa para o agendamento

Referências clínicas (p.ex., Condition, Procedure, Observation) que justificam o agendamento

Nível de prioridade do agendamento (inteiro; 0 para rotina, valores maiores indicam maior prioridade)

Resumo textual do propósito do agendamento

Referências a recursos que dão contexto ao agendamento (p.ex., DocumentReference, ImagingStudy)

Data/hora planejada de início do atendimento

Data/hora planejada de término do atendimento

Duração estimada do atendimento em minutos

Slots do agendador reservados para este Appointment

Data em que o agendamento foi criado

Informações adicionais relevantes sobre o agendamento

Instruções para o paciente sobre o agendamento

Referência à solicitação (ServiceRequest, CarePlan, etc.) que originou o agendamento

Participantes envolvidos no agendamento (profissional, paciente, organização, dispositivo, etc.)

Função ou papel do participante no agendamento (p.ex. médico, paciente, intérprete)

Referência ao recurso que representa o participante

Indica se a presença do participante é obrigatória

Confirmação do participante (accepted, declined, tentative, needs-action)

Intervalo de tempo durante o qual o participante está disponível

Período ou faixa de tempo solicitada para o agendamento (antes da confirmação)

A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).

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 neste 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 para este Appointment (p.ex. identificador do sistema local ou da RNDS)

Situação atual do agendamento (proposto, pendente, agendado, concluído, cancelado, etc.)

If the Appointment's status is "cancelled" then all participants are expected to have their calendars released for the appointment period, and as such any Slots that were marked as BUSY can be re-set to FREE.

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

Razão codificada para cancelamento do agendamento

Categoria ampla do serviço de saúde

Tipo específico de serviço/atendimento a ser realizado

For a provider to provider appointment the code "FOLLOWUP" may be appropriate, as this is expected to be discussing some patient that was seen in the past.

Especialidade clínica requerida para o atendimento

Classificação do agendamento (p.ex. rotina, retorno, encaixe)

Códigos que expressam a justificativa para o agendamento

Referências clínicas (p.ex., Condition, Procedure, Observation) que justificam o agendamento

Nível de prioridade do agendamento (inteiro; 0 para rotina, valores maiores indicam maior prioridade)

Seeking implementer feedback on this property and how interoperable it is.

Using an extension to record a CodeableConcept for named values may be tested at a future connectathon.

Resumo textual do propósito do agendamento

Referências a recursos que dão contexto ao agendamento (p.ex., DocumentReference, ImagingStudy)

Data/hora planejada de início do atendimento

Data/hora planejada de término do atendimento

Duração estimada do atendimento em minutos

Slots do agendador reservados para este Appointment

Data em que o agendamento foi criado

This property is required for many use cases where the age of an appointment is considered in processing workflows for scheduling and billing of appointments.

Informações adicionais relevantes sobre o agendamento

Additional text to aid in facilitating the appointment. For instance, a comment might be, "patient should proceed immediately to infusion room upon arrival"

Where this is a planned appointment and the start/end dates are not set then this field can be used to provide additional guidance on the details of the appointment request, including any restrictions on when to book it.

Instruções para o paciente sobre o agendamento

Referência à solicitação (ServiceRequest, CarePlan, etc.) que originou o agendamento

Participantes envolvidos no agendamento (profissional, paciente, organização, dispositivo, etc.)

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Função ou papel do participante no agendamento (p.ex. médico, paciente, intérprete)

The role of the participant can be used to declare what the actor will be doing in the scope of this appointment.

If the actor is not specified, then it is expected that the actor will be filled in at a later stage of planning.

This value SHALL be the same when creating an AppointmentResponse so that they can be matched, and subsequently update the Appointment.

Referência ao recurso que representa o participante

Indica se a presença do participante é obrigatória

Confirmação do participante (accepted, declined, tentative, needs-action)

Intervalo de tempo durante o qual o participante está disponível

Período ou faixa de tempo solicitada para o agendamento (antes da confirmação)

This does not introduce a capacity for recurring appointments.

A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or device(s) for a specific date/time. This may result in one or more Encounter(s).

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 neste 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 para este Appointment (p.ex. identificador do sistema local ou da RNDS)

Situação atual do agendamento (proposto, pendente, agendado, concluído, cancelado, etc.)

If the Appointment's status is "cancelled" then all participants are expected to have their calendars released for the appointment period, and as such any Slots that were marked as BUSY can be re-set to FREE.

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

Razão codificada para cancelamento do agendamento

Categoria ampla do serviço de saúde

Tipo específico de serviço/atendimento a ser realizado

For a provider to provider appointment the code "FOLLOWUP" may be appropriate, as this is expected to be discussing some patient that was seen in the past.

Especialidade clínica requerida para o atendimento

Classificação do agendamento (p.ex. rotina, retorno, encaixe)

Códigos que expressam a justificativa para o agendamento

Referências clínicas (p.ex., Condition, Procedure, Observation) que justificam o agendamento

Nível de prioridade do agendamento (inteiro; 0 para rotina, valores maiores indicam maior prioridade)

Seeking implementer feedback on this property and how interoperable it is.

Using an extension to record a CodeableConcept for named values may be tested at a future connectathon.

Resumo textual do propósito do agendamento

Referências a recursos que dão contexto ao agendamento (p.ex., DocumentReference, ImagingStudy)

Data/hora planejada de início do atendimento

Data/hora planejada de término do atendimento

Duração estimada do atendimento em minutos

Slots do agendador reservados para este Appointment

Data em que o agendamento foi criado

This property is required for many use cases where the age of an appointment is considered in processing workflows for scheduling and billing of appointments.

Informações adicionais relevantes sobre o agendamento

Additional text to aid in facilitating the appointment. For instance, a comment might be, "patient should proceed immediately to infusion room upon arrival"

Where this is a planned appointment and the start/end dates are not set then this field can be used to provide additional guidance on the details of the appointment request, including any restrictions on when to book it.

Instruções para o paciente sobre o agendamento

Referência à solicitação (ServiceRequest, CarePlan, etc.) que originou o agendamento

Participantes envolvidos no agendamento (profissional, paciente, organização, dispositivo, etc.)

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Função ou papel do participante no agendamento (p.ex. médico, paciente, intérprete)

The role of the participant can be used to declare what the actor will be doing in the scope of this appointment.

If the actor is not specified, then it is expected that the actor will be filled in at a later stage of planning.

This value SHALL be the same when creating an AppointmentResponse so that they can be matched, and subsequently update the Appointment.

Referência ao recurso que representa o participante

Indica se a presença do participante é obrigatória

Confirmação do participante (accepted, declined, tentative, needs-action)

Intervalo de tempo durante o qual o participante está disponível

Período ou faixa de tempo solicitada para o agendamento (antes da confirmação)

This does not introduce a capacity for recurring appointments.