Reference 0008

Temporal Insurance Model

A quick reference for deciding whether an insurance fact should be effective-dated, observed, snapshotted, or corrected.

Use this when fixing bugs where old claims changed after registration edits, eligibility overpromised payment, or support cannot reconstruct what happened.

Three Clocks

Clock	Question	Example
Service date	What coverage should this encounter use?	January visit uses January coverage, even if edited in March.
Observed at	What did an external party say, and when?	271 eligibility response received before claim creation.
Submitted at	What did we send externally?	837P claim payload submitted to a clearinghouse.

Write Pattern Chooser

Situation	Pattern	Do This
Payer, member ID, plan, relationship, or priority changes by date.	EFFECTIVE	Add a date-bounded coverage version.
Payer, clearinghouse, or MAC sends a response.	OBSERVED	Store raw response, parsed fields, source, and observed timestamp.
A claim version leaves your product.	SNAPSHOT	Freeze submitted insurance facts and outbound payload identifiers.
A submitted claim must be fixed.	CORRECT	Create an explicit corrected version linked to the original.

Red Flags

Current-Only Joins

Claim screens that always join to current coverage will rewrite historical claims in the UI.

Date Confusion

Using today's date for old encounters produces false inactive or false active coverage decisions.

Parsed-Only Responses

Parsed fields without raw response make clearinghouse and payer disputes hard to audit.

Source Anchors

CMS Electronic Health Care Claims describes front-end edits, implementation-guide edits, coverage/payment edits, rejection, correction, denial, and acknowledgment workflows.
CMS Eligibility Inquiry frames 270/271 as eligibility data for claim preparation, beneficiary liability, and service eligibility checks.
CMS MLN Insurance and Authorization anchors insurance card, insured ID, and prior authorization facts.