Clinical

External pointer or foreign key linking a patient-reported finding to a related clinical record, encounter, or terminology code in EHR or claims systems. Critical for data engineers building cross-system joins and maintaining referential integrity in clinical data pipelines.

Calendar date on which a documented patient-reported symptom was determined to have resolved or ceased. Used to calculate symptom duration, measure treatment effectiveness, and close open symptom records within clinical documentation and care management systems.

Respiratory rate measured in breaths per minute recorded at the time a patient-reported symptom was assessed. Used as a key vital sign to evaluate pulmonary and systemic status associated with the presenting complaint during clinical encounters and triage workflows.

Outcome measurement associated with a patient-reported finding, such as a structured response from a clinical assessment tool in EHR or care management systems. Data engineers use this field to populate outcomes reporting, quality measures, and longitudinal patient tracking datasets.

Structured documentation of body systems reviewed during a clinical encounter related to a patient-reported symptom. Captures the clinician's systematic inquiry across relevant systems such as cardiovascular, respiratory, and neurological, supporting medical decision-making and coding accuracy.

Version or iteration number tracking updates made to a patient-reported symptom record after initial documentation. Used to maintain an audit trail of clinical modifications, ensuring data integrity and supporting compliance reviews within EHR and clinical data management systems.

Clinician-assigned or algorithm-derived risk level associated with a patient-reported symptom, indicating the likelihood of deterioration, serious underlying pathology, or adverse outcome. Used in triage, care escalation protocols, and population health risk stratification workflows.

Documented pathway or anatomical location through which a symptom manifests or through which an associated treatment is administered. Captures relevant anatomical or pharmacological route context tied to the patient-reported complaint in clinical documentation systems.

Calendar date on which a clinical appointment or follow-up visit was scheduled in response to a patient-reported symptom. Used to track care access timelines, monitor scheduling workflows, and measure interval between symptom documentation and planned clinical evaluation.

Clock time at which a clinical appointment or intervention was scheduled in response to a patient-reported symptom. Used alongside scheduled date to manage appointment coordination, resource allocation, and care access metrics within clinical scheduling and EHR systems.

Calculated numeric rating derived from standardized patient-reported outcome instruments, such as PHQ-9 or pain scales, stored in EHR and care management systems. Data engineers use this field to stratify patient populations and drive risk scoring and quality measure calculations.

Numeric ordering value assigned to a patient-reported finding within a clinical encounter or assessment in EHR systems. Data engineers rely on this field to correctly order multiple symptoms recorded in a single visit when reconstructing clinical timelines and encounter-level datasets.

The date on which clinical services related to a patient-reported symptom were delivered, captured in EHR and medical claims systems. Data engineers use this field as a key temporal anchor for episode-of-care construction, claims adjudication alignment, and HEDIS measure date logic.

Coded or structured value indicating the clinical seriousness of a patient-reported finding, ranging from mild to severe, as recorded in EHR and care management platforms. Data engineers use this field for risk stratification, utilization prediction models, and population health segmentation pipelines.

Biological sex of the patient recorded at the time of symptom documentation. Used to contextualize clinical findings, apply sex-specific diagnostic criteria, support epidemiological analysis, and meet demographic reporting requirements tied to the symptom encounter record.

Origin indicator identifying the system, provider, or assessment tool from which a patient-reported finding was collected, such as EHR, patient portal, or claims. Data engineers use this field to resolve data provenance, deduplication, and source-of-truth conflicts in integrated clinical datasets.

The date on which a patient-reported finding was first experienced or documented, captured in EHR and care management systems. Data engineers use this field to calculate symptom duration, establish episode onset for clinical analytics, and support chronic condition progression tracking.

Clock time at which a patient-reported symptom first began or was first observed during a clinical encounter. Used with symptom onset date to establish precise symptom timing, calculate duration, and support time-sensitive clinical protocols such as stroke or sepsis pathways.

US state or territory associated with the location where a patient-reported symptom was documented or where the patient resides. Used for geographic analysis, public health reporting, jurisdictional compliance, and regional disease surveillance tied to symptom records.

Current state of a patient-reported finding, such as active, resolved, or chronic, as recorded in EHR and care management systems. Data engineers use this field to filter active clinical problems, build longitudinal condition timelines, and support quality measure logic requiring current symptom state.