This page is part of the Da Vinci Risk Adjustment FHIR Implementation Guide (v2.1.0: STU 2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://hl7.org/fhir/us/davinci-ra/ValueSet/remark-reason | Version: 2.1.0 | |||
| Standards status: Trial-use | Maturity Level: 2 | Computable Name: RemarkReason | ||
| Other Identifiers: OID:2.16.840.1.113883.4.642.40.29.48.6 | ||||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License  | 
    ||||
Reason for the remark
References
http://hl7.org/fhir/us/davinci-ra/CodeSystem/remark-reason
Expansion performed internally based on codesystem Remark Reason Codes v2.1.0 (CodeSystem)
This value set contains 3 concepts
| Code | System | Display (en-US) | Definition | 
| never-had-condition | http://hl7.org/fhir/us/davinci-ra/CodeSystem/remark-reason | Patient never had the condition | Reason for the assessed-not-present remark is because the patient has never had this condition. | 
| inactive-condition | http://hl7.org/fhir/us/davinci-ra/CodeSystem/remark-reason | Condition no longer active | Reason for the assessed-not-present remark is because the patient's condition is no longer active. | 
| inapplicable-gap | http://hl7.org/fhir/us/davinci-ra/CodeSystem/remark-reason | Inapplicable gap | Reason for the assessed-not-present remark is because the patient has an active condition but the gap does not accurately describe it. | 
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 |