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

Base legal LGPD para tratamento de dados (Art. 7º)

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

Identificadores externos para este consentimento

Status do consentimento: draft | proposed | active | rejected | inactive | entered-in-error

Escopo do consentimento: patient-privacy | research | treatment | adr

Classificação do consentimento e base legal LGPD

Titular dos dados pessoais

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

Tipo ao qual a referência se refere (por exemplo: Patient)

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

Texto alternativo para o recurso

Data e hora do consentimento

Quem concedeu o consentimento

Controlador dos dados (organização responsável)

Fonte/evidência do consentimento

Políticas que regem o consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Autoridade responsável pela política (ex: ANPD)

URI da política ou legislação

Regra de política de consentimento

Verificação do consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Consentimento foi verificado

Pessoa que verificou

Quando foi verificado

Regras de acesso e tratamento de dados

ID exclusivo para referência entre elementos

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

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

Tipo de ação: permit | deny

Período de validade do consentimento

Agentes autorizados

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Como o agente está envolvido

Recurso para o ator

Ações permitidas ou negadas

Rótulos de segurança que definem os dados afetados

Finalidade do tratamento de dados

Tipo ou classe de dados pessoais

Instâncias de dados específicas

Período temporal dos dados cobertos

Dados específicos cobertos

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Instância | relacionado | dependente | autorizado

O recurso real ao qual a regra de consentimento se aplica

Provisões aninhadas (sub-regras/exceções)

A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.

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

Base legal LGPD para tratamento de dados (Art. 7º)

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

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

Identificadores externos para este consentimento

This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.

Status do consentimento: draft | proposed | active | rejected | inactive | entered-in-error

This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

Indicates the state of the consent.

The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.

Escopo do consentimento: patient-privacy | research | treatment | adr

The four anticipated uses for the Consent Resource.

Classificação do consentimento e base legal LGPD

Titular dos dados pessoais

Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

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 ao qual a referência se refere (por exemplo: Patient)

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.

Data e hora do consentimento

This is not the time of the original consent, but the time that this statement was made or derived.

Quem concedeu o consentimento

Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.

Controlador dos dados (organização responsável)

Fonte/evidência do consentimento

The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

Políticas que regem o consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Autoridade responsável pela política (ex: ANPD)

URI da política ou legislação

This element is for discoverability / documentation and does not modify or qualify the policy rules.

Regra de política de consentimento

If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.

Regulatory policy examples.

Might be a unique identifier of a policy set in XACML, or other rules engine.

Verificação do consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Consentimento foi verificado

Pessoa que verificou

Quando foi verificado

Regras de acesso e tratamento de dados

ID exclusivo para referência entre elementos

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

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

Tipo de ação: permit | deny

How a rule statement is applied, such as adding additional consent or removing consent.

Período de validade do consentimento

Agentes autorizados

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Como o agente está envolvido

How an actor is involved in the consent considerations.

Recurso para o ator

Ações permitidas ou negadas

Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.

Rótulos de segurança que definem os dados afetados

If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.

Security Labels from the Healthcare Privacy and Security Classification System.

Finalidade do tratamento de dados

When the purpose of use tag is on the data, access request purpose of use shall not conflict.

Tipo ou classe de dados pessoais

Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.

Instâncias de dados específicas

Typical use of this is a Document code with class = CDA.

If this code is found in an instance, then the exception applies.

Período temporal dos dados cobertos

This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.

Dados específicos cobertos

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Instância | relacionado | dependente | autorizado

How a resource reference is interpreted when testing consent restrictions.

O recurso real ao qual a regra de consentimento se aplica

Provisões aninhadas (sub-regras/exceções)

A record of a healthcare consumer’s choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.

Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.

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

Base legal LGPD para tratamento de dados (Art. 7º)

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

An Extension

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.

Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).

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

Identificadores externos para este consentimento

This identifier identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.

Status do consentimento: draft | proposed | active | rejected | inactive | entered-in-error

This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.

Indicates the state of the consent.

The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.

Escopo do consentimento: patient-privacy | research | treatment | adr

The four anticipated uses for the Consent Resource.

Classificação do consentimento e base legal LGPD

Titular dos dados pessoais

Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

Referência literal, URL relativa, interna ou absoluta

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 ao qual a referência se refere (por exemplo: Patient)

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.

Data e hora do consentimento

This is not the time of the original consent, but the time that this statement was made or derived.

Quem concedeu o consentimento

Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.

Controlador dos dados (organização responsável)

Fonte/evidência do consentimento

The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.

Políticas que regem o consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Autoridade responsável pela política (ex: ANPD)

URI da política ou legislação

This element is for discoverability / documentation and does not modify or qualify the policy rules.

Regra de política de consentimento

If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.

Regulatory policy examples.

Might be a unique identifier of a policy set in XACML, or other rules engine.

Verificação do consentimento

Identificador exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Consentimento foi verificado

Pessoa que verificou

Quando foi verificado

Regras de acesso e tratamento de dados

ID exclusivo para referência entre elementos

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

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

Tipo de ação: permit | deny

How a rule statement is applied, such as adding additional consent or removing consent.

Período de validade do consentimento

Agentes autorizados

ID exclusivo para referência entre elementos

Conteúdo adicional definido por implementações

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

Como o agente está envolvido

How an actor is involved in the consent considerations.

Recurso para o ator

Ações permitidas ou negadas

Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.

Rótulos de segurança que definem os dados afetados

If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. When the purpose of use tag is on the data, access request purpose of use shall not conflict.

Security Labels from the Healthcare Privacy and Security Classification System.

Finalidade do tratamento de dados

When the purpose of use tag is on the data, access request purpose of use shall not conflict.

Tipo ou classe de dados pessoais

Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.

Instâncias de dados específicas

Typical use of this is a Document code with class = CDA.