documentation:vocabulary:ppi
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| documentation:vocabulary:ppi [2020/01/08 14:51] – [Table] ptalapova | documentation:vocabulary:ppi [2024/09/25 08:40] (current) – Depreciation of page and posting of corresponding link in Github wiki jcruz | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== PPI (Participant Provided Information) ====== | ====== PPI (Participant Provided Information) ====== | ||
| - | PPI is a coding system | + | Thank you for visiting |
| - | + | ||
| - | ===== Source ===== | + | |
| - | + | ||
| - | All PPI information is manually obtained from the All of Us PPI Codebook. | + | |
| - | + | ||
| - | ===== Layout ===== | + | |
| - | + | ||
| - | PPI Questionnaire layout consists of Modules, Topics, Questions, and Answers. | + | |
| - | + | ||
| - | ^ PPI source type value ^ Description | + | |
| - | | Module | + | |
| - | | Topic | A semantic module section containing a thematic set of questions or answers | + | |
| - | | Question | + | |
| - | | Answer | + | |
| - | + | ||
| - | ===== Concept Names ===== | + | |
| - | + | ||
| - | PPI source names are represented in a “display” field. However, to avoid concept name duplicates, modified PPI names have been made through the parsing of their source codes (values of a “pmi_code” field). Original “display” values were put into the CONCEPT_SYNONYM table. | + | |
| - | + | ||
| - | ===== Standard concept ===== | + | |
| - | + | ||
| - | If a PPI concept | + | |
| - | If a PPI concept does not have a standard LOINC or SNOMED equivalent, | + | |
| - | + | ||
| - | ===== Domains and Concept Classes ===== | + | |
| - | + | ||
| - | ^ PPI source type value ^ Concept Class ^ Domain | + | |
| - | | Module | + | |
| - | | Topic | Topic | Observation | + | |
| - | | Question | + | |
| - | | Answer | + | |
| - | | Protocol modification | + | |
| - | | Physical measurement | + | |
| - | + | ||
| - | ===== Internal PPI relationships ===== | + | |
| - | + | ||
| - | A purpose of Internal PPI relationships is to build a PPI Hierarchy, which makes it easier to understand the relations between PPI concepts of different types. | + | |
| - | + | ||
| - | ^ Relationship | + | |
| - | | PPI parent code of | PPI Module | + | |
| - | | ::: | PPI Topic | - Respective PPI Topic\\ - Respective PPI Question\\ - Respective PPI Answer | + | |
| - | | ::: | PPI Question | + | |
| - | | ::: | PPI Answer | + | |
| - | | Answer of (PPI) | PPI Answer | + | |
| - | | Maps to | PPI Module | + | |
| - | | ::: | PPI Topic | The same PPI Topic as a Standard concept | + | |
| - | | ::: | PPI Question | + | |
| - | | ::: | PPI Modifier | + | |
| - | | ::: | PPI Clinical Observation | + | |
| - | | Maps to (obligatory with "Maps to value" | + | |
| - | | Is a | PPI Topic | - Parental Standard PPI Module \\ - Parental Standard PPI Topic\\ - Parental Standard PPI Question | + | |
| - | | ::: | PPI Question | + | |
| - | ===== External PPI relationships ===== | + | |
| - | + | ||
| - | A purpose of Internal of External PPI relationships is the following: | + | |
| - | * to build PPI-LOINC-SNOMED hierarchical crosswalks based on the Internal PPI Hierarchy. | + | |
| - | * to simplify s cross-analysis of patient-related information with a context of combined use of the PPI and such a coding system as either the LOINC or SNOMED. | + | |
| - | + | ||
| - | ===== Hierarchical crosswalks ===== | + | |
| - | + | ||
| - | The PPI Hierarchical crosswalks include only standard concepts. A PPI standard concept value depends on the existence of an equivalent mapping either to the SNOMED or LOINC. In turn, a standard SNOMED/ | + | |
documentation/vocabulary/ppi.1578495064.txt.gz · Last modified: by ptalapova
