REDS GO
1.0.0 - draft
REDS GO - Downloaded Version 1.0.0 See the Directory of published versions
| Official URL: http://www.saude.gov.br/fhir/r4/ValueSet/BRStatusRequisicaoRegulacaoAssistencial | Version: 1.0.0 | |||
| Active as of 2023-04-13 | Computable Name: Status de requisição de regulação assistencial | |||
Status de requisição de regulação assistencial.
References
Última atualização: 2023-04-13 13:17:22+0000; Língua: pt-BR
http://hl7.org/fhir/request-status| Código | Ecrã | Definição | Portuguese (Brazil) (pt) |
| draft | Draft | The request has been created but is not yet complete or ready for action. | Rascunho |
| active | Active | The request is in force and ready to be acted upon. | Ativo |
| on-hold | On Hold | The request (and any implicit authorization to act) has been temporarily withdrawn but is expected to resume in the future. | Em espera |
| revoked | Revoked | The request (and any implicit authorization to act) has been terminated prior to the known full completion of the intended actions. No further activity should occur. | Revogado |
| completed | Completed | The activity described by the request has been fully performed. No further activity will occur. | Completo |
| entered-in-error | Entered in error | This request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity has occurred, the status should be "revoked" rather than "entered-in-error".). | Em estado de erro |
| unknown | Unknown | The authoring/source system does not know which of the status values currently applies for this request. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, but the authoring/source system does not know which. | Desconhecido |
Expansão efectuada internamente com base em codesystem RequestStatus v4.0.1 (CodeSystem)
Este conjunto de valores contém 7 conceitos
| Código | Sistema | Ecrã (pt-BR) | Definição |
| draft | http://hl7.org/fhir/request-status | Draft | The request has been created but is not yet complete or ready for action. |
| active | http://hl7.org/fhir/request-status | Active | The request is in force and ready to be acted upon. |
| on-hold | http://hl7.org/fhir/request-status | On Hold | The request (and any implicit authorization to act) has been temporarily withdrawn but is expected to resume in the future. |
| revoked | http://hl7.org/fhir/request-status | Revoked | The request (and any implicit authorization to act) has been terminated prior to the known full completion of the intended actions. No further activity should occur. |
| completed | http://hl7.org/fhir/request-status | Completed | The activity described by the request has been fully performed. No further activity will occur. |
| entered-in-error | http://hl7.org/fhir/request-status | Entered in error | This request should never have existed and should be considered 'void'. (It is possible that real-world decisions were based on it. If real-world activity has occurred, the status should be "revoked" rather than "entered-in-error".). |
| unknown | http://hl7.org/fhir/request-status | Unknown | The authoring/source system does not know which of the status values currently applies for this request. Note: This concept is not to be used for "other" - one of the listed statuses is presumed to apply, but the authoring/source system does not know which. |
Explanation of the columns that may appear on this page:
| Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance) |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |