Narrativa gerada: StructureDefinition br-core-consent Nome Bandeiras Card. Tipo Descrição e condicionalismos Consent 0..* Consent A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time #xD; id 0..1 id Identificador lógico deste artefato #xD; meta 0..1 Meta Metadados sobre o recurso #xD; implicitRules 0..1 uri Um conjunto de regras sob as quais este conteúdo foi criado #xD; language 0..1 code Idioma do recurso #xD; text 0..1 Narrative Resumo do texto do recurso em linguagem natural #xD; contained 0..* Resource Recursos contidos no recurso #xD; Fatias para extension 1..* Extension Extensões adicionais que não fazem parte do modelo base Fatia: Não ordenado, Aberto por value:url #xD; extension:baseLegalLGPD S 1..1 (Complexo) Base legal LGPD para tratamento de dados (Art. 7º) URL: https://br-core.saude.gov.br/fhir/StructureDefinition/br-core-base-legal-lgpd #xD; value[x] 1..1 CodeableConcept Value of extension Vínculo: https://terminologia.saude.gov.br/fhir/ValueSet/BRBaseLegalLGPD (required) #xD; modifierExtension 0..* Extension Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas #xD; identifier 0..* Identifier Identificadores externos para este consentimento #xD; status 1..1 code Status do consentimento: draft | proposed | active | rejected | inactive | entered-in-error #xD; scope 1..1 CodeableConcept Escopo do consentimento: patient-privacy | research | treatment | adr #xD; category 1..* CodeableConcept Classificação do consentimento e base legal LGPD Vínculo: https://terminologia.saude.gov.br/fhir/ValueSet/BRBaseLegalLGPD (extensible) #xD; patient 0..1 Reference(BRCorePatient) Titular dos dados pessoais #xD; id 0..1 string Identificador exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; reference 0..1 string Referência literal, URL relativa, interna ou absoluta #xD; type 0..1 uri Tipo ao qual a referência se refere (por exemplo: Patient) #xD; identifier 0..1 Identifier Referência lógica, quando a referência literal não é conhecida #xD; display 0..1 string Texto alternativo para o recurso #xD; dateTime 0..1 dateTime Data e hora do consentimento #xD; performer 0..* Reference(BRCorePatient | BRCorePractitioner | BRCorePractitionerRole | BRCoreRelatedPerson | BRCoreOrganization) Quem concedeu o consentimento #xD; organization 0..* Reference(BRCoreOrganization) Controlador dos dados (organização responsável) #xD; source[x] 0..1 Attachment, Reference(Consent | DocumentReference | Contract | QuestionnaireResponse) Fonte/evidência do consentimento #xD; policy 0..* BackboneElement Políticas que regem o consentimento #xD; id 0..1 string Identificador exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; modifierExtension 0..* Extension Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas #xD; authority 0..1 uri Autoridade responsável pela política (ex: ANPD) #xD; uri 0..1 uri URI da política ou legislação #xD; policyRule 0..1 CodeableConcept Regra de política de consentimento #xD; verification 0..* BackboneElement Verificação do consentimento #xD; id 0..1 string Identificador exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; modifierExtension 0..* Extension Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas #xD; verified 1..1 boolean Consentimento foi verificado #xD; verifiedWith 0..1 Reference(BRCorePatient | BRCoreRelatedPerson) Pessoa que verificou #xD; verificationDate 0..1 dateTime Quando foi verificado #xD; provision 0..1 BackboneElement Regras de acesso e tratamento de dados #xD; id 0..1 string ID exclusivo para referência entre elementos #xD; extension 0..* Extension Extensões adicionais que não fazem parte do modelo base #xD; modifierExtension 0..* Extension Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas #xD; type 0..1 code Tipo de ação: permit | deny #xD; period 0..1 Period Período de validade do consentimento #xD; actor 0..* BackboneElement Agentes autorizados #xD; id 0..1 string ID exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; modifierExtension 0..* Extension Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas #xD; role 1..1 CodeableConcept Como o agente está envolvido #xD; reference 1..1 Reference(Device | BRCoreOrganization | BRCorePatient | BRCorePractitioner | BRCorePractitionerRole | BRCoreRelatedPerson) Recurso para o ator #xD; action 0..* CodeableConcept Ações permitidas ou negadas Vínculo: https://terminologia.saude.gov.br/fhir/ValueSet/BRDireitoTitularDados (extensible) #xD; securityLabel 0..* Coding Rótulos de segurança que definem os dados afetados #xD; purpose 0..* Coding Finalidade do tratamento de dados Vínculo: https://terminologia.saude.gov.br/fhir/ValueSet/BRFinalidadeTratamentoDados (extensible) #xD; class 0..* Coding Tipo ou classe de dados pessoais Vínculo: https://terminologia.saude.gov.br/fhir/ValueSet/BRTipoDadoPessoalLGPD (extensible) #xD; code 0..* CodeableConcept Instâncias de dados específicas #xD; dataPeriod 0..1 Period Período temporal dos dados cobertos #xD; data 0..* BackboneElement Dados específicos cobertos #xD; id 0..1 string ID exclusivo para referência entre elementos #xD; extension 0..* Extension Conteúdo adicional definido por implementações #xD; modifierExtension 0..* Extension Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas #xD; meaning 1..1 code Instância | relacionado | dependente | autorizado #xD; reference 1..1 Reference(Resource) O recurso real ao qual a regra de consentimento se aplica #xD; provision 0..* Provisões aninhadas (sub-regras/exceções) #xD; Documentação para este formato
Este perfil define as características mínimas para o recurso [br-core-consent](StructureDefinition-br-core-consent.html) registrar, pesquisar e buscar consentimentos para tratamento de dados pessoais conforme Lei Geral de Proteção de Dados (LGPD) - Lei nº 13.709/2018. O perfil especifica quais elementos principais, extensões, vocabulários e conjuntos de valores **DEVEM** estar presentes e restringe como os elementos são usados. Além disso, fornece a base para o desenvolvimento de padrões para casos de uso específicos promove a interoperabilidade e a adoção.
A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
exists(f:policy) or exists(f:policyRule)
IF Scope=privacy, there must be a patient
patient.exists() or scope.coding.where(system='something' and code='patient-privacy').exists().not()
exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='patient-privacy'])))
IF Scope=research, there must be a patient
patient.exists() or scope.coding.where(system='something' and code='research').exists().not()
exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='research'])))
patient.exists() or scope.coding.where(system='something' and code='adr').exists().not()
exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='adr'])))
IF Scope=treatment, there must be a patient
patient.exists() or scope.coding.where(system='something' and code='treatment').exists().not()
exists(f:patient) or not(exists(f:scope/f:coding[f:system/@value='something' and f:code/@value='treatment'])))
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
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).
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.
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
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Base legal LGPD para tratamento de dados (Art. 7º)
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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](http://hl7.org/fhir/R4/extensibility.html) for a list).
Extensões adicionais que não podem ser ignoradas, mesmo que não reconhecidas
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
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.
The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.
This element is labelled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Escopo do consentimento: patient-privacy | research | treatment | adr
Allows changes to codes based on scope selection
The four anticipated uses for the Consent Resource.
Classificação do consentimento e base legal LGPD
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).
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.
This is not the time of the original consent, but the time that this statement was made or derived.
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)
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.
Field 19 Informational Material Supplied Indicator
Extensões que não podem ser ignoradas mesmo que não sejam reconhecidas
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Autoridade responsável pela política (ex: ANPD)
This element is for discoverability / documentation and does not modify or qualify the policy rules.
If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource.
Might be a unique identifier of a policy set in XACML, or other rules engine.
ID exclusivo para referência entre elementos
How a rule statement is applied, such as adding additional consent or removing consent.
There is no specific actor associated with the exception
How an actor is involved in the consent considerations.
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.
When the purpose of use tag is on the data, access request purpose of use shall not conflict.
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.
Typical use of this is a Document code with class = CDA.
If this code is found in an instance, then the exception applies.
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.
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)