Dados do pagamento reconciliado

Identificador lógico ou físico

Elemento de metadados para identificações adicionais do Recurso

Regras implícitas deste perfil

Conceito codificável que classifica o idioma

Texto livre que descreve a história de forma legível para seres humanos

Outras informações que não existem por si só e só existem por dependência

Conjunto de campos adicionais que são extensões ao modelo de informação

Conjuntos de campos adicionais que são extensões ao modelo de informação e não podem ser ignorados

Status do pagamento

Período de tempo coberto

Data de criação

Entidade que emitiu o pagamento

Requisição de pagamento

Entidade que requisitou o pagamento

Status do pagamento

Descrição do status do pagamento

Data do pagamento

Valor total do pagamento

Identificador do pagamento

Detalhamento do pagamento e formas da remuneração

Identificador do pagamento

Identificador do pagamento anterior

Modelo de remuneração do item

Modelo de remuneração

Guia que originou o pagamento

Entidade que submeteu o pagamento

Resposta de Guia vinculada ao pagamento

Data do pagamento do item

Entidade que é responsável pelo item do pagamento

Entidade que irá receber este item de pagamento

Valor do item de pagamento

Código do formulário

Nota de processamento

Tipo de nota de processamento

Texto da nota de processamento

Dados do pagamento reconciliado

Identificador lógico ou físico

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

Elemento de metadados para identificações adicionais do Recurso

Regras implícitas deste perfil

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.

Conceito codificável que classifica o idioma

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.

Texto livre que descreve a história de forma legível para seres humanos

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.

Outras informações que não existem por si só e só existem por dependência

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.

Conjunto de campos adicionais que são extensões ao modelo de informação

Conjuntos de campos adicionais que são extensões ao modelo de informação e não podem ser ignorados

A unique identifier assigned to this payment reconciliation.

Allows payment reconciliations to be distinguished and referenced.

Status do pagamento

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A code specifying the state of the resource instance.

Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.

Período de tempo coberto

Needed to allow receivers to monitor and reconcile payment issuer schedules.

Data de criação

Need to record a timestamp for use by both the recipient and the issuer.

Entidade que emitiu o pagamento

This party is also responsible for the reconciliation.

Need to identify the party resonsible for the payment and this resource.

Requisição de pagamento

Needed to allow the response to be linked to the request.

Entidade que requisitou o pagamento

Need to identify the party responsible for the request.

Status do pagamento

The resource may be used to indicate that: the request has been held (queued) for processing; that it has been processed and errors found (error); that no errors were found and that some of the adjudication has been undertaken (partial) or that all of the adjudication has been undertaken (complete).

The outcome of the processing.

To advise the requestor of an overall processing outcome.

Descrição do status do pagamento

Provided for user display.

Data do pagamento

To advise the payee when payment can be expected.

Valor total do pagamento

Needed to provide the actual payment amount.

Identificador do pagamento

For example: EFT number or check number.

Enable the receiver to reconcile when payment is received.

Detalhamento do pagamento e formas da remuneração

Needed to show how the payment amount is distributed across the payables.

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.

Identificador do pagamento

Needed for reconciliation of payments.

Identificador do pagamento anterior

Needed for reconciliation of payments.

Modelo de remuneração do item

For example: payment, adjustment, funds advance, etc.

Modelo de remuneração

Needed to provide context for the amount.

Guia que originou o pagamento

Needed to provide a linkage to the original request.

Entidade que submeteu o pagamento

Needed for audit and validation.

Resposta de Guia vinculada ao pagamento

Needed to provide a linkage to the payment commitment.

Data do pagamento do item

Needed for audit and validation.

Entidade que é responsável pelo item do pagamento

To provide contact information.

Entidade que irá receber este item de pagamento

Needed for audit and validation.

Valor do item de pagamento

Needed to explain the distribution of the payment to the payables.

Código do formulário

May be needed to identify specific jurisdictional forms.

The forms codes.

Needed to specify the specific form used for producing output for this response.

Nota de processamento

Provides the specific textual explanations associated with the processing.

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.

Tipo de nota de processamento

The presentation types of notes.

To convey the expectation for when the text is used.

Texto da nota de processamento

Required to provide human readable explanation.

Dados do pagamento reconciliado

Identificador lógico ou físico

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

Elemento de metadados para identificações adicionais do Recurso

Regras implícitas deste perfil

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.

Conceito codificável que classifica o idioma

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.

Texto livre que descreve a história de forma legível para seres humanos

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.

Outras informações que não existem por si só e só existem por dependência

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.

Conjunto de campos adicionais que são extensões ao modelo de informação

Conjuntos de campos adicionais que são extensões ao modelo de informação e não podem ser ignorados

A unique identifier assigned to this payment reconciliation.

Allows payment reconciliations to be distinguished and referenced.

Status do pagamento

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

A code specifying the state of the resource instance.

Need to track the status of the resource as 'draft' resources may undergo further edits while 'active' resources are immutable and may only have their status changed to 'cancelled'.

Período de tempo coberto

Needed to allow receivers to monitor and reconcile payment issuer schedules.

Data de criação

Need to record a timestamp for use by both the recipient and the issuer.

Entidade que emitiu o pagamento

This party is also responsible for the reconciliation.

Need to identify the party resonsible for the payment and this resource.

Requisição de pagamento

Needed to allow the response to be linked to the request.

Entidade que requisitou o pagamento

Need to identify the party responsible for the request.

Status do pagamento

The resource may be used to indicate that: the request has been held (queued) for processing; that it has been processed and errors found (error); that no errors were found and that some of the adjudication has been undertaken (partial) or that all of the adjudication has been undertaken (complete).

The outcome of the processing.

To advise the requestor of an overall processing outcome.

Descrição do status do pagamento

Provided for user display.

Data do pagamento

To advise the payee when payment can be expected.

Valor total do pagamento

Needed to provide the actual payment amount.

Identificador do pagamento

For example: EFT number or check number.

Enable the receiver to reconcile when payment is received.

Detalhamento do pagamento e formas da remuneração

Needed to show how the payment amount is distributed across the payables.

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.

Identificador do pagamento

Needed for reconciliation of payments.

Identificador do pagamento anterior

Needed for reconciliation of payments.

Modelo de remuneração do item

For example: payment, adjustment, funds advance, etc.

Modelo de remuneração

Needed to provide context for the amount.

Guia que originou o pagamento

Needed to provide a linkage to the original request.

Entidade que submeteu o pagamento

Needed for audit and validation.

Resposta de Guia vinculada ao pagamento

Needed to provide a linkage to the payment commitment.

Data do pagamento do item

Needed for audit and validation.

Entidade que é responsável pelo item do pagamento

To provide contact information.

Entidade que irá receber este item de pagamento

Needed for audit and validation.

Valor do item de pagamento

Needed to explain the distribution of the payment to the payables.

Código do formulário

May be needed to identify specific jurisdictional forms.

The forms codes.

Needed to specify the specific form used for producing output for this response.

Nota de processamento

Provides the specific textual explanations associated with the processing.

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.

Tipo de nota de processamento

The presentation types of notes.

To convey the expectation for when the text is used.

Texto da nota de processamento

Required to provide human readable explanation.