VA PGHD FHIR R4 Governance
2.1.27 - active
VA PGHD FHIR R4 Governance - Local Development build (v2.1.27) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://veteran.apps.va.gov/smart-pgd-fhir/v2/ValueSet/mobile-observation-category-v1.0 | Version: 2.1.27 | |||
| Active as of 2023-03-01 | Computable Name: MobileObservationCategory | |||
Categories that are associated with Observations captured as Patient Generated Data.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
Tag: PGD Terminology Governance (Details: Onc1C code 07542190-470a-4043-af42-aaac98406d57 = 'PGD Terminology Governance')
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/observation-category version 📦2.0.0| Code | Display | Definition |
| vital-signs | Vital 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. |
| laboratory | Laboratory | 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. |
https://connectedcare.va.gov/pghd/code-system version 📦2.1.27
| Code | Display |
| daily-activity-summary | Daily Activity Summary |
| workout | Workout |
| sleep | Sleep |
| nutrition | Nutrition |
| high-frequency-data | High Frequency Data |
| anthropometric-measurement | Anthropometric Measurement |
| pulmonary | Pulmonary |
| cgm-summary | CGM Summary |
Expansion performed internally based on:
This value set contains 10 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://terminology.hl7.org/CodeSystem/observation-category | vital-signs | Vital 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. | ||
http://terminology.hl7.org/CodeSystem/observation-category | laboratory | Laboratory | 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. | ||
https://connectedcare.va.gov/pghd/code-system | daily-activity-summary | Daily Activity Summary | |||
https://connectedcare.va.gov/pghd/code-system | workout | Workout | |||
https://connectedcare.va.gov/pghd/code-system | sleep | Sleep | |||
https://connectedcare.va.gov/pghd/code-system | nutrition | Nutrition | |||
https://connectedcare.va.gov/pghd/code-system | high-frequency-data | High Frequency Data | |||
https://connectedcare.va.gov/pghd/code-system | anthropometric-measurement | Anthropometric Measurement | |||
https://connectedcare.va.gov/pghd/code-system | pulmonary | Pulmonary | |||
https://connectedcare.va.gov/pghd/code-system | cgm-summary | CGM Summary |
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 |