|Patient Administration Work Group||Maturity Level : 0||Informative||Use Context : Any|
This is a value set defined by the FHIR project.
This value set defines a set of codes that can be used to indicate special courtesies provided to the patient.
|Committee:||Patient Administration Work Group|
|OID:||2.16.840.1.113883.4.642.3.252 (for OID based terminology systems)|
|Source Resource||XML / JSON|
This value set is used in the following places:
|EXT||extended courtesy||extended courtesy|
|NRM||normal courtesy||normal courtesy|
|PRF||professional courtesy||professional courtesy|
|STF||staff||Courtesies extended to the staff of the entity providing service.|
|VIP||very important person||very important person|
Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.)
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|