An MIB code hit on a life-insurance application is a binary triage problem with a long tail of structured follow-up. The Medical Information Bureau (MIB Group, Inc.) maintains a consortium-shared database of coded impairment information submitted by member life carriers; codes are returned on new applications when MIB's identity-match algorithm matches the proposed insured to a prior submission. When MIB returns code 670 (cardiovascular impairment, severity unspecified), the underwriter's job is to triage the hit against the application's disclosure, the Milliman IntelliScript Rx history, the ExamOne ScriptCheck output, and the LexisNexis MedAdvisor pharmacy-claims feed; decide whether the hit is dispositive (decline or knockout to traditional UW), informational (continue with documented adjustment), or requires APS/paramedical follow-up; and produce the requirement order to the field force, the APS request to the treating physician, and the proposed-insured letter. The 2026 carrier discipline is to document every decision in the chain - what hit came in, what data feeds corroborated or contradicted it, what the underwriter decided, why - for the L&H file note, the Colorado Reg 10-1-1 algorithm-inventory entry on the L&H model, and the eventual contestable-period defense file if the policy claims out in the first 24 months. This lesson walks the MIB 670 hit handling end-to-end with structured prompts, decision logic, and worked-example outputs for the field-force requirement order, the APS request to the cardiologist, and the proposed-insured letter.

MIB Code 670 and the Anatomy of an MIB Hit

The MIB code system organizes impairment information into roughly 300 codes spanning cardiovascular, oncology, neurological, endocrine, psychiatric, respiratory, hepatic, renal, hematologic, and behavioral categories. Code 670 is in the cardiovascular cluster; codes in the 600-690 range cover hypertension, coronary artery disease, arrhythmias, heart failure, valvular disease, and post-cardiac-procedure status. Code 670 specifically indicates "cardiovascular impairment, severity unspecified" - the reporting carrier identified a cardiovascular condition but did not specify whether the impairment was mild (controlled hypertension), moderate (post-MI five-year stable), or severe (active heart failure, low ejection fraction). The unspecified-severity coding means the current carrier must develop the medical evidence to resolve severity from APS, paramedical exam, or the applicant's own disclosure.

MIB's identity-match algorithm uses name, date of birth, sex, and other identifying attributes to match the current submission against prior submissions; matches are probabilistic and the carrier must verify the match is the same individual. The MIB report returns codes plus a reporter-carrier identifier (the prior carrier that reported the code) and an approximate report date. The current carrier may contact the reporter carrier under MIB's rules for limited additional information but cannot disclose MIB content to the applicant beyond what the applicant already knows. The applicant's MIB authorization (signed at application) permits the inquiry; the MIB consent letter included with the application explains the consumer's rights including the right to file disclosure from MIB directly.

Rx History Feeds: IntelliScript, ScriptCheck, MedAdvisor

The carrier triangulates the MIB hit against Rx history pulls from one or more of three primary feeds. Milliman IntelliScript aggregates pharmacy benefit manager (PBM) data across the major U.S. PBMs and returns a chronological prescription history with NDC codes, dispense dates, prescriber NPI, and supply days. ExamOne ScriptCheck offers a similar feed with somewhat different PBM coverage and a different aggregation methodology. LexisNexis MedAdvisor (the LexisNexis pharmacy-claims service) provides a third aggregation perspective with overlap to IntelliScript and ScriptCheck but distinct coverage gaps. Most large carriers run one as primary and a second as backup for cases where the primary returns thin or inconsistent data.

On the worked MIB 670 hit, IntelliScript returns: lisinopril 10mg dispensed monthly for 36 months (consistent with hypertension management); atorvastatin 20mg dispensed monthly for 28 months (consistent with lipid management); metoprolol succinate 50mg dispensed monthly for 24 months (consistent with rate-control therapy - could indicate hypertension, arrhythmia, or post-MI management); aspirin 81mg dispensed quarterly (consistent with cardioprotection or post-procedure prophylaxis). The Rx pattern corroborates that the MIB 670 hit reflects a real cardiovascular impairment - three cardiovascular drugs over multi-year periods is not consistent with no cardiovascular condition. The pattern does not resolve severity: lisinopril + atorvastatin + metoprolol could be controlled hypertension with lipid management, or could be post-MI management with secondary prevention, or could be heart-failure management. APS becomes the resolving data source.

The Triage Decision Tree

The carrier's structured triage on MIB hits operates on a three-state decision: (1) Dispositive hit - the hit, corroborating data, and application disclosure together establish a decline or non-negotiable knockout regardless of further evidence (e.g., MIB code for active metastatic cancer corroborated by oncology Rx with no remission); (2) Informational hit - the hit, corroborating data, and application disclosure together establish a class adjustment that can be made without further APS/paramedical (e.g., MIB code for well-controlled hypertension corroborated by single-drug monotherapy and applicant disclosure); (3) Requires-follow-up hit - the hit and corroborating data are insufficient to make a final class decision and APS, paramedical, or both are required. The MIB 670 hit on the worked case is in the third state - the Rx pattern corroborates the impairment but does not resolve severity; APS-cardiology is the resolving evidence.

The triage memo documents the decision state and the supporting reasoning. Sample memo structure: "MIB code 670 (cardiovascular impairment, severity unspecified) returned on inquiry [date], reporter carrier [redacted], approximate report date [year]. IntelliScript Rx pull [date] returns lisinopril 10mg × 36mo, atorvastatin 20mg × 28mo, metoprolol succinate 50mg × 24mo, aspirin 81mg × multi-year. Application disclosure section 7B discloses 'high blood pressure, controlled with medication' but does not disclose metoprolol use, prior cardiac procedure, or lipid management beyond a yes-no checkbox. Triage decision: requires-follow-up. APS-cardiology ordered from prescribing physician of record (Dr. [name], [practice], NPI [number] per Rx feed) targeting echocardiogram, lipid panel, stress test results, any prior cardiac procedure documentation, and current treating physician's assessment of cardiovascular status. Paramedical examination ordered targeting current blood pressure, resting EKG, lipid panel, HbA1c, urine specimen. Underwriter signature [name, date]."

The Field Force Requirement Order

The field force - the carrier's network of agents, brokers, and case-management coordinators - receives a structured requirement order that lists what the case needs to progress. AI drafts the requirement order against the carrier's filed template; the underwriter reviews and releases. The order's structure: (1) Case identification - application number, applicant name (without specific medical disclosures beyond what the applicant knows), product, face amount. (2) Requirements - paramedical examination (specify provider - typically ExamOne with the carrier's paramed code), APS request (specify physician name, practice, NPI, and the targeted records - last 24-36 months of cardiology records, specific test results requested). (3) Timing expectations - paramed scheduled within 7 business days; APS request typical turnaround 14-21 days; carrier's case-management SLA for follow-up at days 14 and 21. (4) Applicant communication script - what the producer should say to the applicant about the requirements without disclosing MIB content (e.g., "Your application requires additional medical information to complete underwriting; the carrier is requesting a paramedical exam and your physician's records").

The producer-side disclosure discipline matters under MIB's rules and the carrier's market-conduct profile. The producer cannot disclose the specific MIB code or the specific Rx findings to the applicant; the producer communicates the requirements and the timing without revealing the triggering reasons. The applicant has full HIPAA-authorized access to their own medical records and Rx history through their providers and pharmacy; the applicant can disclose any medical history to the carrier directly. The producer's role is administrative - scheduling, follow-up, document collection - not medical disclosure.

The APS Request to the Treating Physician

The Attending Physician Statement request goes to the physician of record identified through the Rx prescriber NPI plus the applicant's disclosed providers. For the MIB 670 case, the cardiologist or internist prescribing the cardiovascular medication is the primary target. The APS request is HIPAA-compliant communication signed under the applicant's HIPAA authorization (separate from the FCRA authorization). The request specifies: (1) Records covered - typically last 24-36 months of cardiology and primary care records; specific test results (echocardiogram, stress test, lipid panel, EKG); any prior cardiac procedure documentation (cath, stent, bypass, ablation, ICD, valve repair). (2) Format - narrative summary from the treating physician preferred over raw records when available; raw records acceptable with physician's cover letter. (3) Timing - typical 14-21 days; expedited options at additional cost. (4) Carrier contact - case management coordinator name and direct number for physician's office questions.

The APS comes back as a multi-page document with the physician's narrative, test results, and supporting documentation. AI assists the underwriter with chronological summarization, identification of ICD-10 codes (I10 for essential hypertension, I25.10 for atherosclerotic heart disease without angina pectoris, I50.9 for unspecified heart failure, etc.), CPT codes for procedures (33533-33548 for CABG range, 92928-92929 for percutaneous coronary intervention), and flagging of the test results that drive the mortality-rating decision (left ventricular ejection fraction, lipid values, stress-test results, ambulatory blood pressure averages). The underwriter applies professional judgment plus the carrier's mortality table - typically supported by reinsurer mortality libraries from Swiss Re, RGA, SCOR, or Munich Re - to assign the eventual class.

The Proposed-Insured Letter

The proposed-insured letter - distinct from the FCRA §615 adverse-action notice - is the carrier's direct communication to the applicant about case status. Many carriers send a proposed-insured letter at the requirement-order stage to manage expectations and reduce churn. The letter's content: (1) Acknowledgment that the application is in active underwriting; (2) Brief statement that additional information is needed (without specifying MIB content); (3) Identification of the requirements (paramed scheduled, APS requested); (4) Expected timeline; (5) Applicant's options if the timeline is problematic; (6) Carrier contact for questions. The letter is not legally required at this stage and does not trigger any specific compliance obligations beyond the carrier's filed policy on applicant communications.

The letter's compliance discipline: no medical-information disclosure (consistent with HIPAA limits and MIB rules); no implication of decline or adverse decision (the case is in active underwriting); no producer-specific commitments (the carrier underwrites, not the producer); language consistent with the carrier's filed applicant-communication standards. AI drafts against the template; the underwriter or case manager reviews and releases. The letter combined with the producer's communication produces a coherent applicant experience that reduces complaint volume at this critical stage.

The File Note and Reg 10-1-1 Inventory Entry

The L&H file note records the MIB hit handling chain: MIB inquiry date and code; Rx feed pulls and findings; triage decision with reasoning; requirement orders issued (paramed, APS); applicant-communication issued (proposed-insured letter, producer-facing script); APS receipt date; paramed receipt date; eventual underwriting decision with class and reasoning; FCRA §615 notice issued (if adverse). Each entry references the specific data sources, prompt versions if AI-assisted, and the underwriter or case manager responsible. The file note is the durable record that supports contestable-period defense (the first 24 months when claims face full underwriting scrutiny), market-conduct examinations, and any consumer-complaint or litigation review.

The Colorado Reg 10-1-1 algorithm-inventory entry on the L&H model captures the MIB-hit handling at the case level: rules invoked by the accelerated-UW platform if applicable (Magnum / AURA NEXT / Velogica), the MIB code returned, the Rx-pattern category, the triage decision state, the eventual decision. Aggregated across cases, the inventory supports the quarterly Colorado DOI submission demonstrating the carrier's L&H underwriting model operates with documented governance. The per-case discipline supports the aggregate accuracy; sloppy per-case entries produce aggregate inventory defects that examiners surface.

Key Takeaways

• MIB code 670 (cardiovascular impairment, severity unspecified) is one of approximately 300 MIB codes spanning cardiovascular, oncology, neurological, endocrine, psychiatric, respiratory, hepatic, renal, hematologic, and behavioral categories. Severity-unspecified codes require the current carrier to develop medical evidence (APS, paramed) to resolve.
• Three Rx feeds - Milliman IntelliScript, ExamOne ScriptCheck, LexisNexis MedAdvisor - triangulate the MIB hit by returning chronological prescriptions with NDC codes, dispense dates, prescriber NPI, and supply days. Most large carriers run one primary and a second backup; the Rx pattern corroborates or contradicts the MIB hit.
• The triage decision tree has three states: dispositive (decline or non-negotiable knockout), informational (class adjustment without further follow-up), or requires-follow-up (APS, paramed, or both). The worked MIB 670 case with multi-drug cardiovascular Rx pattern is requires-follow-up because severity is not resolved from feeds alone.
• The field force requirement order specifies paramed (typically ExamOne) and APS with target records - last 24-36 months of cardiology, specific test results, prior cardiac procedure documentation. Producer-side applicant communication addresses requirements and timing without disclosing MIB or Rx content.
• The APS request to the treating physician goes under the applicant's HIPAA authorization with specific record targets, narrative-summary preference, 14-21 day turnaround, and a case-management contact. AI assists with chronological summarization, ICD-10 / CPT identification, and flagging of mortality-rating drivers.
• The proposed-insured letter manages expectations during the APS/paramed cycle without disclosing medical content or implying decline. Combined with producer communication, it reduces applicant churn and complaint volume at the most critical wait period.
• The L&H file note records the entire chain - MIB inquiry, Rx pulls, triage decision, requirement orders, applicant communication, APS receipt, paramed receipt, eventual class decision, FCRA §615 notice if adverse. The file is the durable record for contestable-period defense and market-conduct examination.
• The Colorado Reg 10-1-1 algorithm-inventory entry on the L&H model captures MIB-hit handling at the case level; per-case discipline supports aggregate inventory accuracy that examiners review on quarterly submissions. Sloppy per-case entries produce aggregate defects.