Domain
Claims
ICD-10, CPT, EDI 837/835, adjudication and remittance
3,542 claims terms
A cloud computing model providing virtualized computing infrastructure including servers, storage, and networking over the internet on a pay-per-use basis. IaaS is used by healthcare organizations to host data warehouses, claims processing systems, and EHR platforms with scalable on-demand resources.
The HIPAA standard electronic transaction for submitting institutional healthcare claims from hospitals, skilled nursing facilities, and other institutional providers to insurance payers. Uses the X12 837I format and replaces the paper UB-04 claim form. Includes revenue codes and condition codes.
The annual cap on member cost-sharing for covered services under ACA-compliant plans. Stored in benefits configuration tables within EHR and claims systems. Triggers full insurer payment once member's accumulated deductible, copay, and coinsurance data reaches this threshold.
A CMS value-based payment program under MACRA that adjusts Medicare physician payments based on performance in quality, cost, improvement activities, and promoting interoperability categories. MIPS scores determine positive or negative payment adjustments applied to Medicare Part B fee schedule payments.
The portion of healthcare costs paid directly by a member including deductibles, copayments, and coinsurance, tracked in claims adjudication and member benefit systems to accumulate toward the OOP maximum threshold and reported in EOB and remittance data across EHR and payer platforms.
The upper limit value for a patient paid amount. Used in healthcare data management and clinical workflows. This field is commonly used in electronic health records (EHR), healthcare information systems (HIS), and clinical data warehouses for out of pocket management and reporting.
The unique identifier assigned by a healthcare payer to a specific claim upon receipt and adjudication. Also known as Internal Control Number or Document Control Number. Used to track claims through the adjudication process and reference specific claims in appeals, adjustments, and provider inquiries.
The date on which payment funds were issued by the healthcare payer to the provider or member as recorded in the BPR segment of the X12 835 remittance advice transaction. Used in claims payment reconciliation, accounts receivable management, and provider payment lag analysis.
The process of submitting pharmacy claims to insurance payers for reimbursement of prescription drug costs. Uses the NCPDP B1 transaction standard for real-time point-of-sale pharmacy claim submission. Includes drug cost, dispensing fee, and member cost sharing calculations for PBM adjudication.
Standardized two-digit CMS code appearing on professional claims (837P) identifying the physical or virtual setting where a healthcare service was rendered, such as 11 for Office, 21 for Inpatient Hospital, or 02 for Telehealth. Used in claims adjudication, provider reimbursement logic, and utilization analytics within payer and EHR systems.
A cloud computing model (PaaS) used in healthcare data engineering to deploy and manage EHR integrations, claims processing pipelines, and analytics environments without managing underlying infrastructure. Common in HIPAA-compliant Azure, AWS, and Google Cloud healthcare implementations.
A health plan model combining features of HMO and PPO plans allowing members to choose in-network providers for lower cost sharing or out-of-network providers at higher cost without a referral. POS plans use a primary care physician gatekeeper model for in-network care coordination.
The process by which credentialing systems confirm a provider's qualifications such as licensure, degrees, and board certifications directly with the issuing institution. Used in provider data management and NCQA-compliant credentialing platforms, this data is critical for maintaining accurate provider rosters in EHR and payer systems.
A payer-required approval process captured in claims, PBM, and EHR systems before specific medications, procedures, or services are covered. Data engineers integrate PA status codes into adjudication workflows, utilization management pipelines, and pharmacy benefit systems to enforce coverage policies and track approval and denial outcomes.
The HIPAA standard electronic transaction for submitting professional healthcare claims from physicians, therapists, and other non-institutional providers to insurance payers. Uses the X12 837P format and replaces the paper CMS-1500 claim form. Required for Medicare, Medicaid, and commercial payer billing.
A standardized code used on the X12 835 remittance advice transaction to explain why a claim or service line was adjusted or denied by a payer. RARC codes provide supplemental information alongside Claim Adjustment Reason Codes and are maintained by CMS for use in Medicare and commercial claims processing.
Four-digit UB-04 code identifying the specific hospital department or service category responsible for a charge on an institutional claim (837I), such as room and board, pharmacy, or radiology. Used in claims adjudication, cost center reporting, and inpatient facility billing analytics.
The financial process that facilities use to manage the administrative and clinical functions associated with claims processing, payment, and revenue generation.
Structured clinical documentation in EHR systems capturing a provider's systematic inquiry across body systems such as cardiovascular, respiratory, and neurological to identify unreported symptoms. Data engineers use ROS fields for clinical NLP extraction, quality measure scoring, and HEDIS or risk adjustment analytics.
Identifies the beginning date of service at the claim line level in professional, institutional, and pharmacy claims systems. Used by data engineers to determine service duration, validate against authorization windows, and support line-level adjudication and episode grouping logic.