Fundamentals of the US Healthcare Domain: How the System Works
A practical guide to how the US healthcare system is structured, covering payers, providers, the patient journey, revenue cycle management, medical coding, healthcare IT systems, and the regulatory framework that shapes every IT project in this space.
What is the US healthcare domain?
The US healthcare domain is the industry sector covering all organisations, processes, systems, and regulations that govern how care is delivered and paid for in the United States. It spans hospitals, clinics, and physicians who deliver care, insurers and government programmes that pay for it, and the technology that connects them.
For IT professionals and Business Analysts, understanding this sector means knowing the payer landscape, the claim lifecycle, the revenue cycle, and the compliance framework well enough to gather requirements and deliver projects for US healthcare clients. This is one of the most regulated and technology-intensive sectors in global IT services.
What this guide covers
- 1Key stakeholders: patients, payers, providers
- 2Payer types: private insurance, Medicare, Medicaid, VA
- 3Revenue cycle and the claim lifecycle
- 4Medical coding: ICD-10, CPT, HCPCS
- 5Regulations: HIPAA, ACA, Cures Act, GDPR context
- 6Healthcare IT: EHR, FHIR, HL7, EDI standards
What Is the US Healthcare Sector?
The United States operates the world’s largest healthcare market by spending, accounting for roughly 17% of GDP, or approximately $4.5 trillion annually (CMS, National Health Expenditure data). Unlike most developed economies with single-payer systems, the US operates a multi-payer model where private insurance, government programmes, and out-of-pocket payments each fund a substantial share of care.
For IT professionals and Business Analysts based in India, Australia, the UK, or anywhere else working on US client projects, this creates a distinct challenge: the US system’s complexity does not translate directly from other markets. The terminology (prior auth, denial management, EOB, CPT codes), the regulatory framework (HIPAA, HITECH, Cures Act), and the system architecture (EHR platforms, clearinghouses, health information exchanges) are specific to the US context and must be learned as a separate body of knowledge.
Annual US healthcare spend
Approximately 17% of US GDP. The largest healthcare market by spending in the world (CMS).
Americans with health coverage
Covered through a mix of employer plans, Medicare, Medicaid, VA, and individual marketplace plans.
No single system
Private insurers, federal programmes, and state programmes operate in parallel with different rules and IT requirements.
Key Stakeholders in the US Healthcare System
Every US healthcare transaction involves three types of participant. Understanding their distinct roles, data flows, and system interactions is the starting point for any IT or BA professional entering this sector.
Providers
The professionals and facilities delivering medical treatment. Their primary IT systems are EHR platforms for clinical documentation and practice management systems for scheduling and billing.
- Primary Care Physicians (PCPs): first point of contact, routine and preventive care, referrals to specialists
- Specialists: cardiologists, oncologists, orthopaedic surgeons, dermatologists, and other experts
- Facilities: hospitals, urgent care clinics, ambulatory surgical centres (ASCs), skilled nursing facilities (SNFs), and pharmacies
Payers
Entities that create health plans, collect premiums, process claims, and reimburse providers. They operate the adjudication engines that determine what gets paid. The type of payer determines the claim format, compliance rules, and IT integration pattern.
- Private insurers: UnitedHealthcare, Anthem/Elevance, Aetna, Cigna, BCBS plans
- Government programmes: Medicare (CMS), Medicaid (state-administered), CHIP, VA/Tricare
- Self-insured employers and their TPAs: Sedgwick, HealthSmart, Meritain
Patients and Members
The individuals receiving care and utilising health insurance benefits. From an IT perspective, patients generate data throughout the care journey: at registration, during clinical encounters, on patient portals, and at billing. Their engagement is shaped by payer rules on cost-sharing: premiums, deductibles, copays, and coinsurance.
- Member: the insurance term for an enrolled patient
- Patient: the clinical term for someone receiving care
- Guarantor: the financially responsible party for the bill
For IT and BA professionals: The stakeholder you are building for determines which system and which data standard is in scope. A project for a provider organisation involves EHR and practice management systems with clinical data. A project for a payer involves claims adjudication, member portals, and authorisation systems. A project at the intersection involves interoperability, typically FHIR APIs.
Elements of the US Healthcare Domain
A complete understanding of the US healthcare sector for IT and BA professionals covers five interconnected elements. Each maps to a distinct category of IT project.
1. Payer Landscape
Who funds healthcare: private insurance (employer-sponsored and individual), Medicare, Medicaid, VA/Tricare, and self-insured employers. Each payer type has distinct IT requirements, claim formats, and regulatory obligations.
2. Provider Landscape
Who delivers care: PCPs, specialists, hospitals, clinics, ASCs, SNFs, pharmacies. Provider type determines the clinical workflow, the EHR platform, and the billing model (professional 837P vs institutional 837I claims).
3. Revenue Cycle and Claims
The financial lifecycle from patient registration through claim submission, adjudication, and payment. RCM is the largest single category of US healthcare IT work. The claim lifecycle is the process every BA and QA professional must understand first.
4. Medical Coding
The standardised alphanumeric codes that classify diagnoses (ICD-10-CM) and procedures (CPT/HCPCS). Every claim is built on these codes, making coding knowledge essential for anyone working on revenue cycle, billing, or compliance projects.
5. Regulatory Framework
The laws that shape every healthcare IT project: HIPAA (patient data privacy), ACA (coverage and marketplace rules), HITECH (EHR incentives), and the 21st Century Cures Act (interoperability mandates and FHIR APIs).
6. Healthcare IT and Standards
The systems (EHR, RCM, payer adjudication, clearinghouses) and the standards that connect them: HL7 FHIR for interoperability, EDI X12 for claims transactions, and DICOM for medical imaging.
The Payers: Who Pays for Care
Healthcare services in the US are funded through a combination of private insurance, government programmes, and out-of-pocket payments. The type of payer determines the IT system architecture, the claims format, and the compliance requirements for any project.
Private Insurance
Often provided by employers or purchased individually through ACA Marketplace exchanges. Employer-sponsored insurance covers the largest share of Americans. Insurers include UnitedHealthcare, Anthem/Elevance Health, Aetna, Cigna, Humana, and the Blue Cross Blue Shield network of plans. Private payers run complex adjudication systems and represent the majority of commercial healthcare IT work.
Government Programmes
Medicare
Federal programme primarily for people aged 65 and older, plus certain younger people with disabilities. Administered by CMS with four parts: A (hospital), B (medical), C (Advantage managed care), D (prescription).
Medicaid
Joint federal and state programme providing health coverage for individuals and families with limited income and resources. Each state administers its own programme with variable eligibility rules and IT systems (MMIS).
VA / Veterans Health Administration
Dedicated programme serving military veterans, operating its own hospital network and using the VistA/Oracle Health EHR system. Separate from commercial payer systems.
Tricare
Healthcare programme for active-duty military service members, their families, and retired military personnel. Administered by the Defense Health Agency.
CHIP
Children’s Health Insurance Programme: covers uninsured children in families that earn too much to qualify for Medicaid but cannot afford private insurance.
Pharmacy Benefit Managers
Express Scripts, CVS Caremark, OptumRx: manage prescription drug benefits on behalf of payers. Separate IT systems govern formulary management, claims adjudication for drugs, and specialty pharmacy.
The most important payer distinction for IT projects: commercial vs government. Government programmes (especially Medicare and Medicaid) carry stricter regulatory requirements, different claims formats, and unique compliance obligations. Medicaid projects vary significantly by state because each state runs its own programme under a federal framework.
Build US healthcare knowledge for BA and IT roles
Techcanvass’s US Healthcare Domain Training covers payers, providers, the claim lifecycle, RCM, prior authorisation, HIPAA, and FHIR with real IT project context.
The Providers: Who Delivers Care
Providers are the clinical entities and professionals that render medical services. Provider type determines the EHR platform, the billing model, and the regulatory requirements that apply to an IT project.
| Provider Type | Who They Are | Primary IT Systems | Billing Model |
|---|---|---|---|
| Primary Care Physicians (PCPs) | First point of contact: family medicine, internal medicine, paediatricians. Handle routine checkups, basic care, preventive services, and referrals to specialists. | Ambulatory EHR (Epic, athena, eClinicalWorks), Practice Management | 837P professional claim |
| Specialists | Experts in specific medical fields: cardiologists, oncologists, orthopaedic surgeons, dermatologists. Patients are referred to them by PCPs. | Specialty EHR, ambulatory platforms, specialty-specific workflows (oncology, cardiology) | 837P professional claim |
| Hospitals | Inpatient care, emergency departments, surgical services. Operate 24/7 with complex multi-department workflows. The largest and most complex EHR implementations. | Hospital EHR (Epic, Oracle Health, Meditech), CPOE, PACS, pharmacy systems | 837I institutional claim; DRG-based inpatient payment |
| Urgent Care / ASCs | Walk-in urgent care clinics for non-emergency care; ambulatory surgical centres for outpatient procedures. | Simpler ambulatory EHR or practice management platforms | 837P or 837I depending on setting |
| Skilled Nursing Facilities (SNFs) | Post-acute care for patients recovering from surgery or illness. Often covered under Medicare Part A. | Long-term care EHRs (PointClickCare, MatrixCare) | UB-04 form; PDPM payment model for Medicare |
| Pharmacies | Dispense medications prescribed by providers. Interact with PBMs for drug claims adjudication. | Pharmacy management systems; NCPDP D.0 claim standard | NCPDP electronic prescription and claim |
Revenue Cycle Management: The Financial Lifecycle
Revenue Cycle Management (RCM) is the overarching process covering the complete financial lifecycle of a patient encounter, from the first scheduling contact through to final payment collection. The flow of money from patient or payer to the provider is the revenue cycle, and it operates through a standardised workflow that every IT professional in US healthcare must understand.
| RCM Stage | What Happens | IT System | Common IT Project |
|---|---|---|---|
| Registration and Eligibility Verification | Patient demographics captured; insurance eligibility checked in real time before service is rendered to confirm coverage, copay, and deductible status | EHR registration, eligibility (270/271 EDI) | Real-time eligibility integration, automated insurance verification |
| Documentation and Coding | Clinical events translated into standardised codes: ICD-10-CM for diagnoses, CPT/HCPCS for procedures and services performed. Accurate coding determines what and how much gets paid. | EHR documentation, coding tools, computer-assisted coding (CAC) | Coding automation, CAC implementation, coding audit tools |
| Claim Submission | Provider submits the claim (837P or 837I) to the payer directly or via a clearinghouse. Clearinghouses validate the claim format before forwarding to the payer. | Clearinghouse (Change Healthcare, Availity), claims scrubbing | Clearinghouse integration, claims scrubbing rule engine |
| Adjudication | The insurance company reviews the claim, checks it against the patient’s plan, applies coverage rules and medical necessity, and determines how much it will pay | Payer adjudication engine, prior authorisation system | Denial analytics, prior-auth automation, payer edit management |
| Explanation of Benefits (EOB) | A document sent to the patient explaining what medical services were reviewed, what was approved or denied, and what the insurance paid. The ERA (835) is the electronic equivalent sent to the provider. | 835 ERA payment posting, member portal (EOB display) | ERA automation, payment variance reporting, secondary billing |
| Patient Billing | Patient billed for any remaining balance after insurance payment: copays, deductibles, or coinsurance. The out-of-pocket amount the patient must pay before or after insurance covers the rest. | Patient billing portal, payment plans, financial assistance screening | Patient payment portal, price transparency, financial counselling workflow |
Key RCM Metrics IT Projects Aim to Improve
Days in Accounts Receivable
How long it takes on average to collect payment. Industry benchmark is under 40 days; lower is better.
Claim Denial Rate
Percentage of submitted claims denied by payers. Best-in-class is below 5%. Denial analytics is a top automation target.
Clean Claim Rate
Percentage of claims accepted on first submission without error. Target is above 95%.
First Pass Resolution Rate
Claims resolved (paid or denied with reason) on first submission. Higher FPRR reduces rework cost.
Prior Authorisation is a separate but related process. Before certain procedures, medications, or specialist referrals, the provider must obtain payer approval. It is one of the most administratively burdensome processes in US healthcare, generating significant IT investment. CMS has mandated FHIR-based prior-auth APIs for Medicare Advantage, Medicaid, and CHIP payers, making it an active development area across the sector.
The Claim Lifecycle in Detail
The claim is the document a provider submits to a payer requesting payment for services rendered. It is the financial heartbeat of the US healthcare system, and understanding its lifecycle in detail is the single most important piece of domain knowledge for anyone working on revenue cycle IT projects.
| Stage | Description | BA / IT Relevance |
|---|---|---|
| 1. Charge Capture | Clinical services translated into billable charges using ICD-10 and CPT codes | Charge master maintenance, coding automation, charge-capture workflow design |
| 2. Claim Creation | Charges assembled into an 837P (professional) or 837I (institutional) EDI transaction | Claims generation configuration, EDI 837 transaction requirements, claim types |
| 3. Claim Scrubbing | Automated pre-submission validation: eligibility, coding logic, modifier use, payer-specific rules | Scrubbing rule-engine configuration, custom edit creation, payer-rule library maintenance |
| 4. Claim Submission | Clean claim submitted to payer directly or through a clearinghouse (Change Healthcare, Availity) | Clearinghouse integration, acknowledgement handling (997/999), claim status tracking (276/277) |
| 5. Adjudication | Payer reviews coverage, medical necessity, and coding; approves, partially pays, or denies | Denial analytics, prior-auth integration, payer response handling and routing |
| 6. Payment Posting (ERA) | 835 Electronic Remittance Advice received; payment matched to the original claim | ERA auto-posting, payment variance analysis, secondary claim generation |
| 7. Denial Management | Denied claims worked: reviewed for appeal, corrected, and resubmitted within payer timelines | Denial workflow automation, appeal letter generation, denial-trend root-cause analytics |
| 8. Patient Billing | Patient-responsibility amount billed after insurance payment; collections for unpaid balances | Patient payment portal, financial assistance screening, propensity-to-pay analytics |
Standardised Medical Coding
Healthcare billing relies on universal alphanumeric codes to classify procedures and diagnoses, ensuring accurate reimbursement and data tracking across every payer and provider. These codes are not optional: every claim requires them, and errors directly cause denials.
ICD-10-CM Codes
International Classification of Diseases, 10th Revision, Clinical Modification. Used globally to document and classify diagnoses, symptoms, and conditions. Every claim must include at least one ICD-10 diagnosis code justifying the medical necessity of the service. The US moved from ICD-9 to ICD-10 in October 2015. ICD-11 adoption is in early planning stages.
CPT Codes (Current Procedural Terminology)
Used to report medical, surgical, and diagnostic procedures and services performed by providers. Maintained by the AMA. CPT codes are the primary driver of professional claim reimbursement. Every outpatient service, office visit, surgery, and diagnostic test has a specific CPT code.
HCPCS (Healthcare Common Procedure Coding System)
Level II codes for supplies, equipment, and services not covered by CPT, including durable medical equipment (DME), ambulance services, and drugs. Used primarily for Medicare and Medicaid billing. Level I of HCPCS is actually CPT codes; the terms are sometimes used interchangeably for Level I.
DRGs and Inpatient Payment
Diagnosis-Related Groups (DRGs) are the payment groupings used for hospital inpatient claims. Rather than paying per service, Medicare and many commercial payers pay a fixed amount per DRG for inpatient stays, covering the full hospitalisation. The DRG is assigned based on the primary diagnosis, procedures performed, complications, and comorbidities. DRG assignment accuracy directly affects hospital revenue, making DRG coding accuracy an important revenue cycle IT project area.
Regulatory Compliance in US Healthcare
Due to the sensitive nature of medical data and the significant financial stakes, healthcare is one of the most heavily regulated sectors in the US. Every IT system touching patient data or claims processing operates under a layered compliance framework.
| Regulation | What It Is | IT Project Requirements It Generates |
|---|---|---|
| HIPAA (1996) | Health Insurance Portability and Accountability Act. A US federal law that sets the standard for protecting sensitive patient health information (PHI) from disclosure without consent. The Privacy Rule and Security Rule are the two most IT-relevant components. | PHI encryption (at rest and in transit), access controls and audit logs, Business Associate Agreements (BAAs) for vendors, PHI de-identification for analytics, breach notification procedures |
| HITECH Act (2009) | Strengthened HIPAA enforcement; introduced financial incentives (Meaningful Use) for EHR adoption; toughened breach notification requirements. | Meaningful Use / Promoting Interoperability EHR certification, enhanced audit logging, breach notification workflows |
| ACA (2010) | Affordable Care Act. Expanded coverage via Marketplace exchanges and Medicaid; introduced value-based care models; prohibited pre-existing condition exclusions. | Marketplace IT systems, Medicaid eligibility expansion, ACO and MSSP value-based care reporting, quality measure dashboards |
| 21st Century Cures Act (2016/2021) | Mandates healthcare interoperability, prohibits information blocking, and requires FHIR R4 API implementations for payers and EHR vendors. | Patient Access API (FHIR R4), Provider Directory API, Prior Authorisation API, information-blocking documentation, patient data portability portal |
| EMTALA (1986) | Emergency Medical Treatment and Labor Act. Requires hospitals with emergency departments to provide care regardless of insurance status or ability to pay. | ED registration for uninsured, charity-care eligibility screening, financial assistance workflows |
| GDPR (EU) in context | General Data Protection Regulation: EU law governing personal data privacy, including health records. Does not apply directly in the US, but matters for US healthcare IT teams working with international patients, or for multinational health systems with European operations. | Cross-border data handling policies, consent management for EU patients, data processing agreements alongside BAAs when international data is involved |
Healthcare IT and Interoperability
Modern healthcare operations rely heavily on digital systems to manage patient information, clinical workflows, and financial processes. Understanding the difference between systems, and how they connect, is essential for IT and BA professionals in this sector.
EHR vs EMR: What Is the Difference?
An EMR (Electronic Medical Record) is a digital version of a patient’s chart within a single practice or facility. An EHR (Electronic Health Record) is designed to move with the patient across different care settings and organisations, supporting data sharing between providers. In practice, EHR is the preferred and more commonly used term, as modern systems are designed for interoperability rather than siloed use. The major EHR platforms in the US are Epic, Oracle Health (Cerner), Meditech, athenahealth, and Allscripts/Veradigm.
Healthcare Interoperability Standards
| Standard | What It Is | IT / BA Relevance |
|---|---|---|
| HL7 FHIR | Fast Healthcare Interoperability Resources: the current standard for healthcare data exchange using RESTful APIs and structured FHIR Resources (Patient, Encounter, Claim, etc.) | Required for all CMS-mandated API projects: Patient Access, Prior Authorisation, Provider Directory. The dominant integration standard for new healthcare IT projects. |
| HL7 v2 | Legacy messaging standard still dominant for real-time clinical messaging within and between facilities | EHR-to-ancillary interfaces: lab results (ORU), orders (ORM), admissions (ADT), scheduling (SIU). Still widely used despite FHIR adoption. |
| EDI X12 (837 / 835 / 270 / 271) | Electronic Data Interchange for healthcare financial transactions. Mandated by HIPAA for covered entities. | Claims (837P/837I), remittance advice (835 ERA), eligibility verification (270/271), claim status (276/277). Every RCM project involves EDI. |
| ICD-10 / CPT / HCPCS | Medical coding standards for diagnoses and procedures used in every claim | Revenue cycle projects require understanding of coding logic, charge capture, and scrubbing rules based on these codes. |
| DICOM | Digital Imaging and Communications in Medicine: standard for medical imaging data | PACS implementation, radiology workflow projects, imaging exchange between facilities. |
What IT Professionals and Business Analysts Need to Know
US healthcare is one of the most demanding sectors for IT and BA work: every system touches regulated data, every business rule has a financial or patient-safety implication, and the multi-payer model means no two projects are identical.
| Activity | Without Domain Knowledge | With Domain Knowledge |
|---|---|---|
| Requirements elicitation | Misses prior-auth requirements, HIPAA obligations, EDI transaction specs, and payer-specific rules | Asks precise questions about claim type, payer rules, coding requirements, and HIPAA scope |
| User story writing | Happy-path only; misses denial scenarios, partial payment, prior-auth failure, ERA mismatch | Covers the full revenue cycle including exception paths, payer-specific edge cases, and regulatory constraints |
| Test case design | Generic test cases miss claim edit rules, HIPAA PHI handling, and coding validation | Covers 837/835 validation, eligibility scenarios, PHI de-identification in test data, coding logic |
| Stakeholder communication | Needs prior auth, EOB, CPT, DRG, ERA, HEDIS explained in every meeting | Communicates as a peer with billing teams, compliance officers, clinical informatics, and payer integration teams |
Common IT Projects in US Healthcare
- EHR Implementation or Migration: Epic, Oracle Health, or Meditech go-live; the most complex and highest-value healthcare IT projects.
- Revenue Cycle Transformation: Replacing or upgrading billing, claims, or RCM platform. Consistently the highest-volume category of healthcare IT work.
- FHIR API Implementation: Patient Access, Provider Directory, and Prior Authorisation APIs mandated by CMS under the Cures Act.
- Prior Authorisation Automation: Reducing the administrative burden of manual prior-auth with FHIR-based electronic workflows.
- Denial Management Analytics: Root-cause analysis of claim denials, automated appeal workflows, payer rule library management.
- Patient Portal and Engagement: Patient-facing digital tools for appointment scheduling, test results, bill payment, and care messaging.
- HIPAA Compliance Programme: Access control review, audit logging, PHI de-identification, breach response planning.
- Health Information Exchange (HIE): Connecting providers across organisations for care coordination and transitions of care.
Ready to work on US healthcare IT projects?
Explore Techcanvass’s training and domain guides for IT professionals and Business Analysts entering or growing in the US healthcare sector.
Frequently Asked Questions
What is the US healthcare domain?
What are the main payer types in the US healthcare system?
What is the claim lifecycle in US healthcare?
What is the difference between Medicare and Medicaid?
What is HIPAA and what does it mean for an IT project?
What is HL7 FHIR and why does it matter?
What is an EOB in healthcare?
Explore Related IT Domain Guides
US healthcare is one of the most project-rich IT verticals globally. These guides connect it to the broader landscape of domains IT professionals and Business Analysts work in.
Healthcare Business Analyst: Skills, Role and Deliverables
What the BA role looks like within US healthcare, the key deliverables, and how to position yourself for healthcare BA opportunities.
Read guide InsuranceInsurance Domain Fundamentals: How the Industry Works
Core principles, product categories, the claims lifecycle, IT systems, and global regulations for insurance projects worldwide.
Read guide BFSI OverviewWhat Is the BFSI Domain? Full Form, Meaning and Complete Guide
Banking, financial services, and insurance as a combined sector: what IT professionals need to know about each pillar.
Read guide BankingBanking Domain Fundamentals: How the Industry Works
CBS, the lending lifecycle, payment rails, and regulatory frameworks for banking IT projects globally.
Read guide Career GuidanceWhich BA Domain Should You Choose?
Healthcare vs banking vs payments vs telecom: a structured comparison to help IT professionals decide where to build expertise.
Read guide TrainingUS Healthcare Domain Training for IT and BA Professionals
Payers, providers, claims lifecycle, RCM, HIPAA, FHIR, and EHR platforms with a healthcare project capstone.
View training
