Phenomics Exchange for Research and Diagnostics
0.1.0 - ci-build International flag

Phenomics Exchange for Research and Diagnostics, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phenomics-exchange-ig/ and changes regularly. See the Directory of published versions

ValueSet: Observation categories

Official URL: http://hl7.org/fhir/uv/phenomics-exchange/ValueSet/observation-categories Version: 0.1.0
Draft as of 2024-06-18 Computable Name: ObservationCategories

Copyright/Legal: Global Alliance for Genomics and Health

ValueSet description here

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

 

Expansion

This value set contains 10 concepts

CodeSystemDisplayDefinition
  social-historyhttp://terminology.hl7.org/CodeSystem/observation-categorySocial History

Social History Observations define the patient's occupational, personal (e.g., lifestyle), social, familial, and environmental history and health risk factors that may impact the patient's health.

  vital-signshttp://terminology.hl7.org/CodeSystem/observation-categoryVital Signs

Clinical observations measure the body's basic functions such as blood pressure, heart rate, respiratory rate, height, weight, body mass index, head circumference, pulse oximetry, temperature, and body surface area.

  imaginghttp://terminology.hl7.org/CodeSystem/observation-categoryImaging

Observations generated by imaging. The scope includes observations regarding plain x-ray, ultrasound, CT, MRI, angiography, echocardiography, and nuclear medicine.

  laboratoryhttp://terminology.hl7.org/CodeSystem/observation-categoryLaboratory

The results of observations generated by laboratories. Laboratory results are typically generated by laboratories providing analytic services in areas such as chemistry, hematology, serology, histology, cytology, anatomic pathology (including digital pathology), microbiology, and/or virology. These observations are based on analysis of specimens obtained from the patient and submitted to the laboratory.

  procedurehttp://terminology.hl7.org/CodeSystem/observation-categoryProcedure

Observations generated by other procedures. This category includes observations resulting from interventional and non-interventional procedures excluding laboratory and imaging (e.g., cardiology catheterization, endoscopy, electrodiagnostics, etc.). Procedure results are typically generated by a clinician to provide more granular information about component observations made during a procedure. An example would be when a gastroenterologist reports the size of a polyp observed during a colonoscopy.

  surveyhttp://terminology.hl7.org/CodeSystem/observation-categorySurvey

Assessment tool/survey instrument observations (e.g., Apgar Scores, Montreal Cognitive Assessment (MoCA)).

  examhttp://terminology.hl7.org/CodeSystem/observation-categoryExam

Observations generated by physical exam findings including direct observations made by a clinician and use of simple instruments and the result of simple maneuvers performed directly on the patient's body.

  therapyhttp://terminology.hl7.org/CodeSystem/observation-categoryTherapy

Observations generated by non-interventional treatment protocols (e.g. occupational, physical, radiation, nutritional and medication therapy)

  activityhttp://terminology.hl7.org/CodeSystem/observation-categoryActivity

Observations that measure or record any bodily activity that enhances or maintains physical fitness and overall health and wellness. Not under direct supervision of practitioner such as a physical therapist. (e.g., laps swum, steps, sleep data)

  phenotypehttp://hl7.org/fhir/uv/phenomics-exchange/CodeSystem/categoriesPhenotype

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