STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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: R4B R4 R3

4.2.11.403 Code System http://hl7.org/fhir/flag-category

This is a value set defined at http://www.hl7.org/Special/committees/patientcare .

Summary

Defining URL: http://hl7.org/fhir/flag-category
Name: Flag Category
Definition: Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.)
Committee: Patient Care Work Group
OID: 2.16.840.1.113883.4.642.1.403 (for OID based terminology systems)
Source Resource XML / JSON

This Code system is used in the following value sets:

  • Flag Category (Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.))

4.2.11.403.1 Content

4.2.11.403.2 Flag Category

Example list of detail codes for flagged issues. (Not complete or necessarily appropriate.)

This code system http://hl7.org/fhir/flag-category defines the following codes:

Code Display Definition
diet Diet Flags related to the subject's dietary needs.
drug Drug Flags related to the patient's medications.
lab Lab Flags related to performing laboratory tests and related processes (e.g. phlebotomy).
admin Administrative Flags related to administrative and financial processes.
contact Subject contact Flags related to coming into contact with the patient.

 

See the full registry of value sets defined as part of FHIR.

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
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)
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