This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0.  For a full list of available versions, see the Directory of published versions  . Page versions: R5 R4B R4
. Page versions: R5 R4B R4
| Patient Administration  Work Group | Maturity Level: 0 | Informative | Use Context: Not Intended for Production use | 
This is a value set defined by the FHIR project.
Summary
| Defining URL: | http://hl7.org/fhir/ValueSet/verificationresult-can-push-updates | 
| Version: | 3.5.0 | 
| Name: | can-push-updates | 
| Title: | Can-push-updates | 
| Definition: | Ability of the primary source to push updates/alerts | 
| Committee: | Patient Administration  Work Group | 
| OID: | 2.16.840.1.113883.4.642.3.896 (for OID based terminology systems) | 
| Source Resource | XML / JSON | 
This value set is used in the following places:
This value set includes codes from the following code systems:
http://terminology.hl7.org/CodeSystem/can-push-updates
This expansion generated 19 Aug 2018
This value set contains 3 concepts
Expansion based on http://terminology.hl7.org/CodeSystem/can-push-updates version 3.5.0
All codes from system http://terminology.hl7.org/CodeSystem/can-push-updates
| Code | Display | Definition | 
| yes | Yes | |
| no | No | |
| undetermined | Undetermined | 
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information | 
| Source | 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). If the code is in italics, this indicates that the code is not selectable ('Abstract') | 
| 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 |