Back to Glossary

Domain

Technology

Systems, databases, interfaces and data standards

428 technology terms

report riskrpt_rsk

The risk level classification assigned to a clinical or operational report, indicating the potential impact or danger associated with the reported data. Used in clinical decision support and quality management workflows to prioritize follow-up actions and escalation protocols.

report routerpt_rte

The designated delivery or distribution pathway for a clinical or operational report, specifying how the report is transmitted to its intended recipients. Captures whether delivery occurs via electronic health record messaging, secure email, fax, or patient portal in healthcare information systems.

report scorerpt_scr

A calculated numeric rating assigned to a structured clinical summary in EHR or quality reporting systems. Used by data engineers to rank reports by completeness, accuracy, or clinical relevance for analytics pipelines and quality measure dashboards.

report sequencerpt_seq

An integer ordering value assigned to structured clinical summaries within a series, batch, or episode in EHR and claims systems. Data engineers use this field to maintain correct ordering when processing multi-part clinical reports or adjudication outputs.

report severityrpt_sev

A coded classification indicating the seriousness of the condition or finding documented in a structured clinical summary. Used in EHR, adverse event, and pharmacovigilance systems to triage and route reports; critical for data engineers building alerting pipelines.

report sexrpt_sex

The biological sex classification of the patient or population cohort captured within a clinical or operational report. Used in clinical analytics, quality measure stratification, and public health reporting to segment outcomes and utilization data by sex across healthcare populations.

report sourcerpt_src

A reference identifier indicating the originating system, facility, or provider that generated a structured clinical summary. Found in EHR, claims, and HIE data, this field is essential for data lineage tracking and source-to-target mapping in integration workflows.

report start daterpt_start_dt

The effective beginning date of the data period or clinical activity captured in a structured clinical summary. Used across EHR, claims, and pharmacy systems to define reporting windows; data engineers rely on this field for partitioning and time-series filtering.

report start timerpt_start_tm

The precise timestamp marking the beginning of the period or event covered by a clinical or operational report. Used in scheduling, clinical workflow tracking, and audit logging to establish when the reported activity, encounter, or observation interval commenced within healthcare systems.

report staterpt_st

The U.S. state or territory associated with the subject matter or geographic scope of a clinical or operational report. Used in public health surveillance, regulatory compliance reporting, and multi-state health plan analytics to filter and aggregate data by jurisdiction.

report statusrpt_sts

A coded field representing the current processing or clinical state of a structured clinical summary, such as draft, final, amended, or voided. Critical in EHR and claims systems for data engineers filtering active versus historical records in downstream analytical tables.

report strengthrpt_str

The drug concentration or dosage strength referenced within a clinical or operational report, typically expressed in units such as mg, mcg, or mg/mL. Used in pharmacy utilization reports, medication reconciliation summaries, and clinical trial documentation to identify specific formulation details.

report subtotalrpt_subtot

An intermediate aggregated numeric value within a clinical or operational report representing a partial sum before final totals are calculated. Used in financial, claims, and utilization reports to break down costs, counts, or units by category prior to overall consolidation across healthcare datasets.

report system identifierrpt_sys_id

The unique system-generated key assigned to a specific clinical or operational report instance within a healthcare information system. Serves as the primary reference for linking, tracking, auditing, and retrieving the report across integrated platforms including EHR, data warehouses, and reporting engines.

report targetrpt_tgt

A reference identifier specifying the intended destination system, provider, or population for a structured clinical summary. Used in HIE, care management, and quality reporting platforms; data engineers use this field for routing logic and destination-based data partitioning.

report taxonomy coderpt_tax_cd

The National Uniform Claim Committee (NUCC) taxonomy code identifying the clinical specialty or provider type referenced within a report. Used in credentialing, claims adjudication, and network analytics to classify the specialty context under which clinical services or report data were generated.

report temperaturerpt_temp

The recorded body temperature value for a patient documented within a clinical report, typically expressed in Fahrenheit or Celsius. Used in vital signs summaries, clinical decision support alerts, and inpatient monitoring reports to track patient physiological status over a care episode.

report termination daterpt_term_dt

The date on which a clinical or operational report's coverage period, validity, or active status ends. Used in longitudinal reporting, regulatory submissions, and member or contract management workflows to define the closing boundary of the data scope captured within the report.

report timerpt_tm

The time-of-day value recording when a structured clinical summary was generated or submitted within an EHR or claims system. Data engineers use this field alongside report date for precise event sequencing, deduplication, and timestamp normalization in data pipelines.

report timestamprpt_ts

A combined date and time value capturing the exact moment a structured clinical summary was created, submitted, or last modified in EHR, claims, or pharmacy systems. Used by data engineers for audit logging, change data capture, and precise event ordering in ETL workflows.

PreviousPage 12 of 22Next