# Mission: Insurance Claims and Clearinghouses in EMR / Healthcare SaaS

## Why
The user wants to build practical product judgment for healthcare SaaS revenue-cycle workflows: how EMR data becomes insurance claims, how clearinghouses fit between providers and payers, and how the claim lifecycle maps to real product states.

## Success looks like
- Map common EMR and billing events to the right HIPAA transactions, including eligibility, claims, claim status, and remittance.
- Design a claim workflow that separates draft, validation, submission, acceptance, adjudication, denial, payment, and posting states.
- Explain what a clearinghouse does, what it does not do, and where payer-specific rules still matter.
- Identify the minimum data domains a claim workflow needs: patient, subscriber, payer, provider, diagnosis, procedure, service line, place of service, charges, and remittance adjustments.
- Troubleshoot workflow issues by distinguishing claim rejections, claim denials, payment adjustments, and posting exceptions.

## Constraints
- Lessons should be short, practical, and tied to product design or implementation decisions.
- Use authoritative sources first: CMS, NUCC, CAQH CORE, X12, and reputable revenue-cycle communities.
- Start with U.S. HIPAA administrative transactions and professional claims, then expand to institutional claims, payer companion guides, and clearinghouse APIs.

## Out of scope
- Becoming a certified medical coder.
- Pharmacy-specific NCPDP claim workflows unless they become relevant later.
- Deep X12 segment syntax before the user has the claim lifecycle mental model.
- Payer contract negotiation and reimbursement strategy beyond what is needed to understand claim outcomes.