Skip to content

Patient Encounter Workflow

Overview

This interactive diagram illustrates the complete journey of a patient encounter from arrival through final billing. It shows the parallel activities and data flows across four key domains: the patient experience, clinical staff operations, clinical information systems, and administrative/financial systems. This comprehensive view helps healthcare professionals and students understand how clinical care, documentation, and revenue cycle management integrate through data capture and exchange.

Interactive Diagram

View the Diagram Fullscreen

Description

The patient encounter workflow is a complex, multi-system process that coordinates clinical care delivery with administrative and financial operations. Understanding this workflow is essential for healthcare data professionals, as it reveals critical data capture points, system interactions, and the dependencies between clinical documentation and billing processes.

The workflow demonstrates how patient data flows through four parallel "swimlanes":

  1. Patient Lane - The patient's perspective and key touchpoints during the encounter
  2. Clinical Staff Lane - Activities performed by registration, nursing, and physician staff
  3. Clinical Systems Lane - Electronic health record (EHR), computerized provider order entry (CPOE), and diagnostic systems
  4. Administrative Systems Lane - Eligibility verification, medical coding, claims processing, and payment posting

Each encounter generates structured and unstructured data that must be captured, validated, coded, and transmitted according to healthcare data standards including HL7, FHIR, ICD-10, CPT, and X12 EDI formats.

Workflow Steps

Patient Lane

  1. Patient Arrives - Patient presents to clinic or hospital seeking care
  2. Provides Information - Shares demographics, insurance details, and chief complaint
  3. Undergoes Care - Receives examination, diagnostic tests, procedures, and treatments
  4. Receives Instructions - Gets discharge instructions, prescriptions, and follow-up appointment details
  5. Receives Bill/EOB - Reviews Explanation of Benefits showing charges and insurance coverage

Clinical Staff Lane

  1. Registration - Front desk verifies patient identity, confirms insurance eligibility, and collects copayment. Data captured: Demographics, insurance policy numbers, reason for visit
  2. Triage/Vitals - Nursing staff records vital signs, documents chief complaint, current medications, and allergies. Data captured: Blood pressure, temperature, pulse, respiratory rate, height, weight, pain level
  3. Provider Assessment - Physician or advanced practice provider conducts history taking, physical examination, and develops differential diagnosis. Data captured: History of present illness, review of systems, physical exam findings, assessment
  4. Order Entry - Provider orders diagnostic tests, imaging studies, medications, and procedures through CPOE. Data captured: Lab orders, imaging orders, medication orders with dosing, procedure requests
  5. Results Review - Provider reviews and interprets diagnostic test results, refines diagnosis and treatment plan. Data captured: Result interpretations, revised diagnoses, clinical decision documentation
  6. Documentation - Provider completes encounter note with clinical narrative, assigns diagnosis codes (ICD-10), and documents procedures performed (CPT codes). Data captured: Encounter note, problem list updates, ICD-10 diagnosis codes, CPT/HCPCS procedure codes
  7. Discharge/Follow-up - Provider prescribes medications, writes referrals, schedules follow-up appointments, and provides patient instructions. Data captured: Prescriptions, referral orders, follow-up appointments, patient education materials provided

Clinical Systems Lane

  1. EHR: Create Encounter - Electronic health record system creates new encounter record and loads patient's historical clinical context including prior diagnoses, medications, allergies, and test results
  2. CPOE: Receive Orders - Computerized Provider Order Entry system receives orders from provider, performs drug interaction checking, and routes orders to appropriate fulfillment systems
  3. Lab/Imaging: Perform Tests - Laboratory and radiology information systems receive orders and manage specimen collection, test execution, and quality control processes
  4. Results Interface - Test results flow back to EHR via HL7 v2 or FHIR interfaces, triggering provider notifications for abnormal values
  5. EHR: Document Finalization - Provider electronically signs completed encounter note, locking the clinical documentation and triggering downstream billing workflows

Administrative Systems Lane

  1. Eligibility Check - Real-time verification of insurance coverage and benefits via payer portal or claims clearinghouse, determining copay, deductible, and covered services
  2. Charge Capture - Billing system extracts billable services from clinical documentation using the Charge Description Master (CDM), which maps clinical activities to charge codes
  3. Medical Coding - Professional coders review documentation to assign accurate ICD-10 diagnosis codes, CPT procedure codes, and HCPCS supply codes. May use AI-assisted coding tools and natural language processing
  4. Claim Generation - Billing system creates standardized electronic claim (CMS-1500 for professional claims, UB-04 for facility claims) with all required data elements including patient demographics, diagnoses, procedures, rendering provider NPI, and charges
  5. Claim Submission - Electronic claim transmitted to insurance payer via X12 EDI 837 transaction through claims clearinghouse, which performs initial validation and routing
  6. Adjudication Wait - Payer's adjudication engine applies coverage rules, medical necessity criteria, and contractual fee schedules to determine allowed amount and payment
  7. Payment Posting - Billing system records payment received via Electronic Remittance Advice (ERA), applies contractual adjustments per fee schedule, and calculates remaining patient responsibility (deductible, coinsurance, non-covered services)

Decision Points

The workflow includes four critical decision points where outcomes determine the path forward:

  1. Eligibility Active? - After registration, the system verifies insurance eligibility. If coverage is inactive or invalid, the patient must provide alternative payment method or reschedule. If active, the encounter proceeds normally.

  2. Admit to Hospital? - After provider assessment, a decision is made whether the patient requires inpatient admission or can be managed as outpatient. This fundamentally changes the billing pathway (inpatient DRG-based vs. outpatient fee-for-service).

  3. Coding Complete? - Before claim submission, the coding staff validates that documentation supports assigned codes and all required codes are present. Incomplete coding returns to the coder for additional work.

  4. Claim Accepted? - After submission, the clearinghouse and payer validate claim data. Rejections (immediate failures due to data errors) require correction and resubmission. Accepted claims proceed to adjudication.

Key Concepts

This workflow diagram illustrates several fundamental healthcare data concepts:

  • Clinical Data Capture - Points where structured and unstructured clinical data are recorded in the EHR
  • Health Data Standards - HL7 v2, FHIR, X12 EDI, ICD-10, CPT, HCPCS code systems and messaging formats
  • Revenue Cycle Management - The business process of converting clinical services into billed charges and payments
  • Claims Processing - Generation, submission, adjudication, and payment posting lifecycle
  • Medical Coding - Translation of clinical documentation into standardized diagnosis and procedure codes
  • Interoperability - System-to-system data exchange between EHR, lab, imaging, and billing systems
  • Data Quality - Accuracy, completeness, and timeliness requirements at each workflow stage
  • Documentation Requirements - Clinical detail needed to support medical necessity and coding
  • Charge Capture - Identification and recording of all billable services
  • Adjudication - Payer's process of reviewing claims and determining payment
  • Denial Management - Handling claim rejections, denials, and appeals

Data Standards in Use

Clinical Standards

  • HL7 v2 - Laboratory result interfaces (ORU messages), order interfaces (ORM messages)
  • HL7 FHIR - Modern API-based clinical data exchange (Patient, Encounter, Observation, DiagnosticReport resources)
  • LOINC - Laboratory test identification codes
  • SNOMED CT - Clinical terminology for problem lists and clinical findings
  • RxNorm - Medication terminology and codes

Administrative Standards

  • X12 EDI 837 - Professional (837P) and Institutional (837I) claim submission formats
  • X12 EDI 835 - Electronic Remittance Advice (ERA) for payment posting
  • X12 EDI 270/271 - Eligibility inquiry and response
  • ICD-10-CM - Diagnosis codes required on all claims
  • CPT - Current Procedural Terminology codes for professional services and procedures
  • HCPCS Level II - Codes for supplies, durable medical equipment, and certain services
  • NDC - National Drug Codes for pharmacy claims
  • CMS-1500 - Standard professional claim form format
  • UB-04 - Standard institutional claim form format

Typical Timeframes and Performance Metrics

Understanding normal workflow timing helps identify bottlenecks and performance issues:

  • Registration to Rooming: 5-15 minutes (target: <10 min)
  • Rooming to Provider Entry: 5-20 minutes (target: <15 min)
  • Provider Time: 10-30 minutes depending on visit complexity
  • Lab Results: 1-24 hours (stat labs 1 hour, routine chemistry 4-6 hours, cultures 24-72 hours)
  • Imaging Results: 30 minutes to 24 hours (X-ray 1-2 hours, CT/MRI 4-24 hours)
  • Provider Documentation Completion: Same day to 7 days (target: <24 hours, regulatory max: 30 days)
  • Coding to Claim Submission: 1-7 days (target: <3 days)
  • Claim Submission to Payer Acknowledgment: 24-48 hours
  • Adjudication: 14-30 days from submission
  • Payment Receipt: 14-45 days from submission (target: <30 days)
  • Total A/R Days: 30-60 days from date of service (benchmark: <40 days)

Common Pain Points and Data Quality Issues

Real-world encounter workflows encounter numerous challenges:

Registration and Eligibility

  • Issue: Real-time eligibility checks fail 10-15% of the time due to payer system issues
  • Impact: Registration delays, incorrect copay collection, claim denials
  • Data Issue: Patient provides incorrect member ID or effective dates

Clinical Documentation

  • Issue: Providers complete documentation 2-7 days after encounter, delaying charge capture
  • Impact: Slow revenue cycle, lost charges, compliance risk
  • Data Issue: Incomplete documentation missing diagnoses, procedures, or medical necessity justification

Order and Result Interfaces

  • Issue: HL7 interface failures cause missing lab results or duplicate orders in EHR
  • Impact: Provider must manually enter results, patient safety risk, care delays
  • Data Issue: Interface mapping errors, missing patient identifier matching

Medical Coding

  • Issue: Documentation does not support specificity required by ICD-10 (e.g., laterality, encounter type)
  • Impact: Coders query providers, delaying claim submission 3-5 days
  • Data Issue: Vague diagnosis terms, missing procedure documentation

Claim Rejections

  • Issue: 5-10% of claims rejected due to data quality errors (invalid codes, missing modifiers, incorrect patient demographics)
  • Impact: 30-60 day payment delay, additional staff work to correct and resubmit
  • Data Issue: Mismatched patient name/DOB/ID with payer eligibility records, expired authorization numbers

Claim Denials

  • Issue: 10-15% of accepted claims denied due to medical necessity, duplicate claims, or coverage limitations
  • Impact: Appeal process adds 60-90 days to payment timeline, 50-60% of denials never reworked
  • Data Issue: Lack of prior authorization, missing diagnosis codes supporting medical necessity, incorrect place of service

Usage Notes

This diagram uses a swimlane layout to show parallel activities across four organizational domains. Each swimlane represents a different role or system:

Swimlane Structure: - Patient: The consumer perspective and key interaction points - Clinical Staff: Human-performed activities (registration, nursing, physician) - Clinical Systems: Automated system processes (EHR, CPOE, lab/radiology systems) - Administrative Systems: Billing and revenue cycle management systems

Node Types: - Rectangles: Process steps or actions performed by staff or systems - Diamonds: Decision points where workflow branches based on conditions - Small text: Hover descriptions explaining each step's purpose and data captured

Color Coding: - Blue nodes: Patient activities and touchpoints - Green nodes: Clinical staff activities - Purple nodes: Clinical system processes - Orange nodes: Administrative and financial processes - Yellow diamonds: Decision points requiring evaluation

Flow Interpretation: - Arrows show the sequence and dependencies between steps - Horizontal flow represents progression through time (left to right) - Vertical connections show interactions between different swimlanes (e.g., clinical staff triggering system processes)

This encounter workflow connects to several important healthcare data topics:

Learning Objectives

After studying this workflow diagram, learners should be able to:

  1. Identify the four primary domains involved in patient encounter workflows
  2. Trace the flow of data from initial registration through final payment posting
  3. Explain the purpose and data captured at each major workflow step
  4. Recognize the decision points that determine workflow paths
  5. Describe how clinical documentation drives downstream billing processes
  6. List the healthcare data standards used at different workflow stages
  7. Identify common pain points and data quality issues in real-world implementations
  8. Understand the timing and dependencies between clinical and financial workflows
  9. Explain the relationship between clinical system processes and administrative system triggers
  10. Analyze how data quality issues at one stage impact downstream processes

Use Cases for This Workflow Model

This encounter workflow model is valuable for:

  • Healthcare IT Students - Understanding system integration points and data flows
  • Medical Coding Students - Seeing how clinical documentation becomes coded data for billing
  • Health Information Management - Analyzing revenue cycle dependencies on data quality
  • Clinical Staff Training - Explaining how documentation impacts billing and compliance
  • System Implementation - Identifying integration requirements for EHR, CPOE, and billing systems
  • Process Improvement - Analyzing bottlenecks and optimizing workflow efficiency
  • Compliance and Audit - Understanding documentation and coding requirements
  • Data Analytics - Identifying data sources and capture points for reporting