Technology

Date of birth for a member, patient, or covered individual as recorded or validated within a health information system. Used in eligibility verification, age-based benefits determination, claims adjudication, and demographic analytics to confirm identity and drive age-dependent clinical and administrative rules.

Arterial blood pressure reading, typically expressed as systolic over diastolic values in mmHg, captured within a health information system during a clinical encounter. Used in vital signs documentation, chronic disease management, population health analytics, and quality measure reporting to track cardiovascular health indicators.

Date on which a transaction, appointment, authorization, or record was cancelled as logged by a health information system. Used in scheduling analytics, utilization reporting, and claims management to track cancellation patterns, assess access to care impacts, and reconcile voided transactions in financial systems.

Classification label assigned by a health information system to group records, transactions, or entities into defined functional or administrative categories. Used in data governance, reporting segmentation, and workflow routing to organize information consistently across clinical, financial, and operational domains within the system.

Dollar value of a service or item as assigned by a health information system at the point of charge capture, reflecting the facility or professional gross charge before any contractual adjustments or payments. Used in revenue cycle analytics and claims submission to establish the starting financial value of a healthcare transaction.

Primary symptom, concern, or reason for visit as recorded within a health information system at the initiation of a clinical encounter. Used in clinical documentation, triage workflows, and diagnostic coding to establish the presenting problem that drives the clinical assessment, treatment plan, and encounter-level coding decisions.

Field identifying a subordinate record, entity, or node within a hierarchical data structure maintained by a health information system. Used in organizational hierarchy modeling, care team relationships, and data lineage tracking to represent parent-child dependencies between records such as encounters, claims lines, or facility sub-units.

Municipality name associated with an address record stored within a health information system, applicable to patients, members, facilities, or service locations. Used in geographic analytics, care access reporting, member correspondence, claims routing, and population health segmentation to identify location-based patterns and administrative jurisdictions.

Categorizes a healthcare delivery system into a defined classification tier, such as integrated delivery network, hospital system, or ambulatory network. Used in data governance and interoperability frameworks to segment systems by operational scope and capability level.

A unique standardized identifier assigned to a specific healthcare delivery system, enabling consistent cross-referencing across platforms, payer contracts, and interoperability exchanges. Used in claims adjudication, member attribution, and network management to link records to the originating system.

A free-text field capturing supplemental notes or operational annotations related to a healthcare delivery system. Used by administrators and analysts to document exceptions, system-specific configurations, or contextual details not captured in structured data fields.

Records the date on which a process, task, or workflow associated with a healthcare delivery system was fully completed. Used in operational tracking and audit trails to confirm closure of system-level activities such as migrations, integrations, or compliance submissions.

A flag designating whether data associated with a healthcare delivery system is subject to confidentiality restrictions, such as sensitive service categories under 42 CFR Part 2 or state privacy laws. Drives access controls and data masking logic in downstream reporting and exchange workflows.

Represents the total number of occurrences, transactions, or records associated with a healthcare delivery system within a defined scope or time period. Used in operational reporting, capacity planning, and data quality assessments to quantify system-level activity volumes.

Identifies the country associated with a healthcare delivery system, used to apply jurisdiction-specific regulatory requirements, currency, and coding standards. Critical for multinational health plans and cross-border care coordination where country determines applicable compliance frameworks.

Captures the username or system identifier of the user or automated process that originally created a record within a healthcare delivery system. Used in audit logging, data lineage tracking, and compliance reviews to establish accountability for record origination.

The calendar date on which a record was first entered or generated within a healthcare delivery system. Used in data governance, audit trails, and longitudinal analysis to establish the origin point of a record and support retention policy enforcement.

The precise timestamp at which a record was first created within a healthcare delivery system. Combined with the created date to support sequencing of concurrent transactions, audit logging, and troubleshooting data integrity issues in high-volume processing environments.

Stores the serum or urine creatinine value recorded within a clinical or laboratory information system, serving as a key biomarker for kidney function assessment. Used in clinical decision support, chronic kidney disease staging, and medication dosing calculations requiring renal adjustment.

The system-generated or system-recorded calendar date associated with a transaction, event, or record within a healthcare information system. Distinct from service or encounter dates, this value reflects the date as recorded by the processing system and is used in data reconciliation and audit workflows.